Treat a catalogue as a dated reference set
A public game-room catalogue helps a buyer understand how an operator describes its offer. It does not tell you which items belong in your venue order. Start by saving the page URL, the date you read it and the exact wording attached to each room or offering. Then keep that reference record separate from the purchase scope that your team and supplier will confirm.
The distinction matters when a page combines a room count with time-sensitive labels. The current PlayKinetix page presents a nine-game-room headline and identifies CUBE SPIN and OCTO STRIKE as new in October. Those statements are useful observations about the page; they are not proof of a particular opening-day package, installation count or supplier relationship.
Separate rooms, events, games and modes
Before you count anything, define the unit in the catalogue. A game room may be a physical space, while a game or mode may describe content available inside that space. An event room may support a different use altogether. Put each reference in its own category instead of turning every name into another equipment line.
Recre8play's current homepage is a useful example of why this classification is necessary: it labels eleven game rooms plus one immersive event room, while also using a twelve-room description. That public wording does not establish twelve identical game stations. It shows why the worksheet should preserve both the category and the wording that the buyer is trying to interpret.
Keep future and conflicting availability unresolved
Availability is not a procurement status. Copy the source's label into the reference column, add the observed date and flag any future wording or disagreement. Do not convert a future entry into an opening-day commitment, and do not resolve a date conflict by choosing the interpretation that makes the purchase list look complete.
The PlayKinetix page labels NEON GRID as new from December 2026. A buyer reading the page on a different date could reasonably see a different status later, so the reconciliation sheet must preserve when the wording was observed. The next column should ask the supplier or project owner to confirm whether the item is part of the proposed opening scope, rather than silently treating the public label as a delivery promise.
Build the catalogue-to-scope reconciliation sheet
Use one row per public reference and keep the source record intact. Add the category, availability wording, proposed buyer line, inclusion status and unresolved question. If the buyer cannot match a listing to a model or project requirement, write no correspondence established instead of forcing a match. This is the step that turns a browsing exercise into a controlled procurement conversation.
Include a separate field for operating context. Recre8play's FAQ recommends two to six players as a group and says larger groups are separated into different groups. That is group guidance from an operator's FAQ, not a room count, legal occupancy approval or a specification for the equipment you are considering. Keep those kinds of facts in their own columns so the purchase sheet does not quietly become a capacity claim.
Match each reference to a written buyer line
Once the reference table is complete, create a second, clearly labelled proposed purchase section. For every proposed line, record whether it is included, optional, excluded or unconfirmed. Add the selected model, version and delivery mode only when the project documents support them. A public listing can inspire a requirement, but it cannot fill in an absent supplier mapping or contract decision.
Use the existing CYDON comparison method as a guardrail: equipment, content, software, installation and service are separate scope layers. The purpose here is narrower and different. The reconciliation sheet first explains where a proposed line came from, then the project proposal confirms what CYDON or another supplier is actually being asked to deliver.
Close every included line with acceptance evidence
An inclusion status is not complete until the buyer knows how it will be checked. Add the demonstration, document or site confirmation needed for each included line. If the line depends on a particular version, room arrangement, network condition or operator action, write that dependency beside the acceptance evidence rather than hiding it in a general note.
The CYDON installation checklist and platform page keep installation access, room responsibilities, software scope and project-specific acceptance visible. Apply the same discipline to the catalogue worksheet. It should end with a short list of unresolved owners and tests, not with an invented availability date, price, capacity or outcome.
Our planning perspective
Our proposed decision unit is a traceable catalogue reference, not a room name copied into a wish list. Record what the public page says, when it was observed, which category it belongs to and whether the buyer has a corresponding written line item. Keep future or unmatched offerings unresolved until the supplier confirms the model, version, delivery scope and opening-day test. This method connects market-facing language to procurement without treating a directory as proof of inventory, capacity, price or a CYDON commitment. It also gives the operating team a short list of questions to resolve before a catalogue-inspired concept becomes an order.
Buyer decision checklist
- Capture the source URL, observed date and exact public name before making a proposed purchase line.
- Classify each reference as a game room, event room, game, mode or unresolved label.
- Preserve the page's availability wording and mark future, conflicting or time-sensitive statements.
- Map each reference to a separate buyer line item, or explicitly record that no correspondence is established.
- Mark inclusion as included, optional, excluded or unconfirmed and do not fill gaps with assumptions.
- Attach the selected model, version and opening-day acceptance evidence only after written project confirmation.
Sources and scope
Source material supports the stated facts, not a guarantee of capacity, revenue, safety certification or project outcomes. Final equipment and software scope require a project review.