No game reaches a console storefront without passing the platform holder's review. That process is invisible to players and shapes both release schedules and parts of every game's interface.
Certification checks compliance, not quality
The review does not judge whether a game is good. It verifies that the software behaves correctly as a citizen of the platform under a long list of defined conditions.
Testers confirm that the game handles suspension, controller disconnection, account switching, storage removal and network loss without corrupting data or hanging.
They also check terminology, iconography and messaging, which is why every game on a given console uses the same words for the same system concepts.
The requirements produce visible conventions
Rules about saving explain why games display a warning symbol while writing and why removing storage mid-save is handled gracefully rather than catastrophically.
Requirements for offline behaviour explain why a game with online features still has to do something reasonable when the connection disappears rather than freezing.
Accessibility, age rating display and legal notices are all specified centrally, which is why those screens look almost identical across unrelated titles.
Failure costs a full cycle
A submission that fails is returned with the issues listed, and the corrected build must be resubmitted and reviewed again from the beginning.
Each cycle takes a defined period, so a late failure can consume the remaining schedule entirely and force a delay that has nothing to do with the game's readiness.
Studios therefore submit early, run internal compliance testing against the platform's published rules, and treat certification as a milestone rather than a formality.
Patches go through it too
Updates are also reviewed, which is why a fix known on launch day can take days to reach players even when the code was written immediately.
Platforms provide expedited routes for severe problems, but those are limited and cannot be used routinely, so ordinary patches follow the ordinary schedule.
Studios batch fixes for this reason, which is why console patch notes tend to be longer and less frequent than their PC equivalents.
Day one updates are a consequence of the timeline
The build that goes to manufacturing must be finalised weeks before release, and development continues throughout that period.
Everything completed after the deadline arrives as an update on launch day, which explains why a disc so often installs a large patch before it can be played properly.
The alternative would be shipping the older build and holding the improvements, which serves nobody, so the practice has become standard across the industry.