Your Steam demo just cleared build review. The checklist in Steamworks went green. It is tempting to treat that as "good enough for Press Preview."
It is not. Valve's own Next Fest docs say build review only validates that the game has the features you promised and that it runs. It is not a full QA process. It will not catch, or even look for, most bugs. The pass is a store gate. Your players still get the first crash, softlock, or broken claim.
What build review is actually for
Treat the published Steamworks process as process, not a certification promise.
Build review is there so Steam can confirm the build you submitted roughly matches the features and store presentation you claimed, and that the title starts. That protects the store from empty shells and obvious mismatch. It is not a substitute for a cold-install pass on the same depot players will download.
Steam also tells you to submit demo assets and build at least 3-5 business days ahead of your relevant deadline, with buffer if the first review fails. That clock is about getting through Valve's queue. It is not buffer for fixing severity-1 bugs you only discover after Press Preview opens.
For studios already registered for Steam Next Fest: October 2026, Valve's calendar listed 14 September for submitting the demo build and store page for Press Preview readiness, and 28 September for remaining required review items. Registration closed on 31 August. Press Preview begins on 8 October at 10am PDT, and the festival runs from 19 October at 10am PDT to 26 October at 10am PDT. The September dates have passed. The remaining QA work should focus on the build players will receive, selected fixes and any later demo updates.
Distinct from our recent notes
We already covered what to QA before you submit a Next Fest demo, how closed testing tracks are not a QA pass, when to start external QA before a dated store window, and hiring versus partnering for external game QA.
This note sits after the Steam green check. The object under test is the build that already cleared review, and every depot you push after that, because Steamworks is explicit: you may update the demo after build review, but Valve will not review that update. Shipping a game-breaking change is on you.
What to prove on the reviewed build
Scope the pass to what a stranger does in the first session after they hit Play on the public demo.
- Cold install from the exact reviewed depot. Not a developer package with leftover saves, console cheats, or a private branch that never reaches the store.
- Boot, first-loop blockers, and softlocks. Tutorial gates, broken new-game flows, and crashes that end the session before the hook lands.
- Feature and store parity. Capsules, screenshots, short description, controller or Deck claims, multiplayer promises. Anything public must match the build Steam already accepted. Completeness and claim mismatch are how later reviews and player refunds start.
- Input and hardware paths you advertise. Keyboard/mouse, common controllers, Steam Deck verification path if you claim Deck support. Name PC, iOS, Android, TV, Web, XR and other emerging platforms only for SKUs in this drop.
- Save / cloud / progress hygiene on the demo slice. A demo that wipes progress every relaunch trains wishlisters to leave.
- Severity triage before volume. One reproducible blocker with logs beats fifty "feels off" notes you cannot ship a fix for before Press Preview.
Say what is out. Crowdsourced Discord opinions are not a severity list. Inventing lab counts or tester-pool numbers in the brief does not make the depot safer.
Re-test after every post-review depot
This is where most Next Fest demos break.
Steamworks allows demo updates after you pass build review. It also warns that those updates are not re-reviewed. So the green check on last Tuesday's build does not cover Thursday's content drop, the localization pack, or the "quick" multiplayer patch.
Before you set a post-review depot live:
- Diff the change list against the must-pass list above. Anything that touches boot, save, input, networking, or store-claimed features is in scope again.
- Re-run cold install on a clean machine or clean Steam library folder. Side-by-side with the old depot is not enough if players only ever get the new one.
- Smoke the wishlister and Press Preview path: store page, demo button, first launch, first 15 minutes. Broken invite UX looks identical to a dead game.
- Freeze marketing claims until the new depot survives that smoke. Do not advertise a feature you just destabilised.
If Press Preview or fest open is inside your fix window, shrink scope. Prioritise blockers that end the session. Park balance notes and deep content polish for a later depot, or leave the older green build live.
Book the pass against Press Preview, not the fantasy launch
Work backwards from the day strangers can play.
- Freeze the depot label you will show Press Preview (or fest open) before the QA pass starts. If new content lands during the pass, the earlier results no longer describe the demo you will show.
- Leave one programmer fix cycle after the first useful blockers and before you flip the demo public.
- Keep a rollback depot ready. If the post-review update fails smoke, revert rather than "hope overnight."
- If your studio is already registered for the October edition, plan QA around the next public demo build and any updates before Press Preview or festival opening. Confirm the current depot, leave time for selected fixes and keep a rollback build available.
If the public date is already inside that window, shrink the pass. Cold install, first-session blockers, and claim parity first.
Brief the partner in one page
You do not need a novel. You need rails that match the depot.
- Exact AppID / demo AppID / depot and the branch players will download.
- Platforms in this drop only. Name PC, iOS, Android, TV, Web, XR and other emerging platforms only if this build ships there. Cross out later SKUs.
- Must-pass list: cold install, first-loop blockers, login/save, claimed features, input paths you advertise, crash severity.
- Out of scope: full campaign beyond the demo slice, certification paperwork, marketing copy rewrites, live-ops tooling you will not ship in this depot.
- Fix owner and turnaround before Press Preview, fest open, or the next public depot flip.
GameCloud is a 16-year-old company that runs external game QA for studios and publishers who need a dated, store-shaped pass on PC, iOS, Android, TV, Web, XR and other emerging platforms. Tell us the build window and platforms. We will return a one-page project total. For a Steam demo after build review, or any other dated window, write Sales@GameCloud-Ltd.com.
Steam build review is a store gate. It is not a project-specific QA pass, and a QA pass does not create late registration, festival inclusion, or store approval. For a defined scope on the demo or release candidate, see Demo and Release Readiness Sprint.