Play Select Center · Editorial
People behind Play Select Center
Our games guide is maintained by a small editorial team with distinct responsibilities. We explain what we can observe, make comparisons easier to follow, and keep a route open for readers to flag details that deserve another look.
Editorial responsibilities
These role descriptions explain how the work is divided. They describe editorial functions rather than personal credentials or employment histories.
Games editor
The games editor maintains category explanations and feature comparisons. This role keeps terminology consistent across the guide, checks that a comparison describes the same kinds of features on each side, and revisits category language when the available information changes. The editor aims to make distinctions useful to readers without presenting a preference as a universal result.
When a listing changes, the games editor considers whether the change affects a category description or a comparison. Small wording revisions can matter: a label should communicate what it covers, while leaving room for differences among individual games and services.
Research editor
The research editor gathers provider information and checks the details that can be observed in the material available for review. This includes recording what a provider says, comparing it with the visible listing, and noting where a statement cannot be independently confirmed from the reviewed information.
The research editor keeps source claims separate from editorial observations. That distinction helps a reader understand whether a point comes from provider wording, a visible feature, or the team's interpretation. When evidence is incomplete, the description stays within its limits rather than filling gaps with assumptions.
Reader correspondence editor
The reader correspondence editor triages corrections, questions, and update requests. Messages are assessed for the page or comparison they concern, and relevant details can be passed to the editors responsible for that material. A reader's note is a prompt to review, not automatic confirmation that a listing is wrong.
This role also helps keep follow-up focused. Clear references to a page, label, or provider detail make it easier to locate the point in question. The team may revise copy when a review supports a change; not every suggestion necessarily alters the guide.
Research and review
Our workflow begins with the question a page is meant to answer. Editors collect provider information relevant to that subject, then compare observable details across the material being considered. A comparison is useful only when its terms are clear and the same kind of detail is being discussed consistently.
During review, wording is checked against the information gathered. Provider statements remain attributed as claims; visible features are described as observations; and evaluative language is kept recognizably editorial. This separation avoids implying that a provider's description has been independently verified when the review only records what was presented.
Editors also look for limits in the available material. A feature may be described differently across pages, a detail may be absent, or a listing may change after it was reviewed. In those cases, the guide should not overstate certainty. The team can narrow a comparison, clarify its wording, or revisit the relevant page as appropriate.
Maintenance is ongoing rather than a promise that every detail is current at every moment. Readers can point us to a possible correction, and editors can recheck the affected information. A material change may lead to revised descriptions or comparisons. The goal is a careful, readable guide that distinguishes what has been observed from what has been supplied and what is an editorial assessment.