Patch day QA checklist for Steam updates
34 checks for Early Access patches, content updates and post-launch fixes on Steam: regression, saves, changed areas, performance and the first 48 hours. 34 checks, free, ticks saved in your browser.
For PC studios shipping updates on Steam. Tick items here (they stay saved in this browser), print the list, and run it on the exact build you are about to set live.
A launch gets weeks of testing. A patch often gets an afternoon, and it goes to players who already know the game well. They notice when something that worked yesterday is broken today, and they say so in reviews. On Blood West, a patch broke enemy AI on release day; tracing the cause to corrupted navigation data let the team ship a focused fix instead of rolling the update back.
How often does patch day come early? In September 2026, 22.1% of new Steam games with at least 10 early reviews announced a patch within 24 hours of release, and 73.3% within 7 days (Steam Launch Bug Index, October 2026 edition, n=592). The details are in Day-one patch: what the data says.
Ticks are saved in this browser only (localStorage), nothing is sent anywhere.
1. Before you build: know what changed
Why it matters: Most patch bugs come from changes nobody thought were risky.
2. Build and branch
Why it matters: Testing a build that is not the one going live tells you very little.
3. Regression: what already worked still works
Why it matters: Players notice what broke more than what is new.
4. Saves and continuity
Why it matters: A lost save after an update turns a fan into a negative review.
5. Changed areas
Why it matters: Moved geometry and tweaked values are where AI, collision and triggers break.
6. Performance and hardware
Why it matters: A patch that runs worse than the last build gets called out fast.
7. New text and localization
Why it matters: Missing translations make an update look unfinished.
8. Multiplayer, if you have it
Why it matters: Version mismatches and server order can break sessions for everyone.
9. Release and the first 48 hours
Why it matters: The first two days decide whether a problem stays small.
Want a second pair of eyes before the next update?
A patch is where an outside tester helps most: fresh eyes on the areas you changed, and a regression list someone actually works through. A Smoke Test (€290, one tester, 8 hours, report in 2 business days) fits a hotfix or a small content patch. For bigger updates the Launch Health Check (€590) brings two testers and a Team Lead for around 30 hours.
See the Smoke Test, €290 Book a 30-min call
Also free: the Next Fest demo QA checklist.
Last updated 2026-10-27 · Written by JJ, founder of Jumbo Jelly.