About This Page

Covers the certification process for PlayStation (TRC), Xbox (TCR), and Nintendo (LOT checks). Main page: Console Development. See also: Console Development - PlayStation, Console Development - Xbox, Console Development - Nintendo Switch.

Why Certification Matters

Every game, patch, and DLC must pass certification before it can appear on a console store. A failed cert submission means weeks of delay + re-submission fees. Knowing the rules before shipping saves enormous time and money.

What is Console Certification?

Overview

Certification = Technical Review Compliance

Each platform holder maintains a list of mandatory technical requirements:
  PlayStation: TRC (Technical Requirements Checklist)
  Xbox:        TCR (Technical Certification Requirements)
  Nintendo:    LOT Checks (Lot Check — named after submission batches)

Purpose:
  Ensure games don't crash consoles or brick hardware
  Guarantee consistent user experience on the platform
  Verify platform features are implemented correctly
  Prevent piracy / unauthorized network access
  Protect consumer data and privacy

What gets certified:
  Initial game release
  Every title update / patch
  Every DLC release
  Game mode changes (going from single-player to online-required)

Certification Submission Process

flowchart TD
    Dev[Development Complete] --> IQA[Internal QA Testing]
    IQA --> TCR[Run Platform TCR/TRC/LOT Checklist]
    TCR --> Fix{Issues Found?}
    Fix -->|Yes| FixBugs[Fix All Issues]
    FixBugs --> TCR
    Fix -->|No| Build[Create Submission Build]
    Build --> Upload[Upload to Partner Portal]
    Upload --> PlatformQA[Platform Holder QA Testing]
    PlatformQA --> Result{Pass?}
    Result -->|Pass| Approved[Game Approved!]
    Result -->|Fail| Report[Failure Report Issued]
    Report --> FixBugs2[Fix Listed Issues]
    FixBugs2 --> Resubmit[Re-submit]
    Resubmit --> PlatformQA
    Approved --> Release[Game Goes Live on Store]

Certification Timeline

PlayStation TRC

TRC Overview

TRC = Technical Requirements Checklist

PlayStation TRCs are divided into categories:
  Required (MUST pass — automatic fail if violated)
  Recommended (SHOULD implement — not a fail, but noted)

TRC documents are provided via the PlayStation Partners portal.
Updated periodically — always use the current version!

Major TRC categories:
  Application Lifecycle  — start, suspend, resume, shutdown
  User Management        — multiple users on one console
  Save Data              — save system behavior
  Trophy System          — trophy implementation
  Online Features        — PSN integration requirements
  Network Access         — internet usage policies
  UI & UX                — button mapping, icons, accessibility
  Content Rating         — PEGI/ESRB rating display
  Localization           — language support requirements
  Audio                  — DualSense audio routing
  Performance            — no indefinite hangs

Critical TRC Requirements

Application Lifecycle TRC (highest failure rate):

TRC-R4001 — Game must start within 15 seconds of launch icon press
  Fix: Minimize startup work, show loading screen immediately

TRC-R4002 — Game must respond to suspend event within 5 seconds
  Fix: Flush IO, pause audio, disconnect network in suspend handler
  Never block suspend handler — platform will force-kill game

TRC-R4003 — Game must handle unexpected shutdown gracefully
  Fix: Auto-save every 15 minutes minimum, never corrupt save on crash

TRC-R4004 — Game must handle profile switch (user switch mid-game)
                Fix: Save current user progress, prompt to save before switch

Save Data TRC:

TRC-S1001 — Never write to save during scene loads (IO bottleneck)
TRC-S1002 — Must warn player before a non-reversible action (delete save)
TRC-S1003 — Save data must survive console shutdown mid-write
  Fix: Write to temp file, verify, then rename (atomic write pattern)

Trophy TRC:

TRC-T1001 — Every PS4/PS5 game MUST have at least one trophy set
TRC-T1002 — Trophies must not be unlockable by in-game purchase
TRC-T1003 — Trophy artwork must meet resolution requirements (256×256)
TRC-T1004 — Trophy descriptions must be accurate (no "TBD" in submission)

Common TRC Failures

Atomic Save Pattern (Prevents TRC-S1003)

// Atomic save — never corrupt save data on crash/power loss
 
bool SaveGameSafe(const SaveData& data, const char* savePath) {
    // 1. Write to temporary file
    std::string tempPath = std::string(savePath) + ".tmp";
    
    FILE* tempFile = fopen(tempPath.c_str(), "wb");
    if (!tempFile) return false;
    
    // 2. Write data + checksum
    uint32_t checksum = CalculateCRC32(&data, sizeof(data));
    fwrite(&data, sizeof(data), 1, tempFile);
    fwrite(&checksum, sizeof(checksum), 1, tempFile);
    
    // 3. Flush to ensure OS writes to disk
    fflush(tempFile);
    fclose(tempFile);
    
    // 4. Atomic rename — if power lost here, old save intact
    //    If power lost before here, temp file is corrupted (not real save)
    rename(tempPath.c_str(), savePath);
    
    return true;
}
 
bool LoadGameSafe(SaveData& data, const char* savePath) {
    FILE* file = fopen(savePath, "rb");
    if (!file) return false;
    
    SaveData loadedData;
    uint32_t storedChecksum, calcChecksum;
    
    fread(&loadedData, sizeof(loadedData), 1, file);
    fread(&storedChecksum, sizeof(storedChecksum), 1, file);
    fclose(file);
    
    // Verify integrity
    calcChecksum = CalculateCRC32(&loadedData, sizeof(loadedData));
    if (calcChecksum != storedChecksum) {
        // Corrupted — try backup save
        return LoadBackupSave(data);
    }
    
    data = loadedData;
    return true;
}

Xbox TCR

TCR Overview

TCR = Technical Certification Requirements

Xbox TCR documents are provided via Partner Center.
ID@Xbox members get full TCR documentation.

TCR categories:
  Fundamentals    — startup, crash recovery, input
  Xbox Live       — achievements, presence, cloud saves
  Game Hub        — store listing, screenshots, trailers
  Accessibility   — required accessibility features
  Multiplayer     — online session requirements
  Content         — age ratings, content policies
  Performance     — hang detection, memory
  Packaging       — binary format requirements
  Update          — title update requirements
  Quick Resume    — suspend/resume behavior

Critical TCR Requirements

Fundamentals:

TCR-F001 — Game must start in under 2 minutes from logo to gameplay
  Fix: Optimize startup loading, add progress indicator

TCR-F002 — Game must never hang (infinite loop with no output)
  Fix: Watchdog timer — force-restart if no progress in 60 seconds

TCR-F003 — Game must handle all 4 users on one console
  Fix: Test every feature with 4 different user accounts

Xbox Live (if using Xbox Live features):

TCR-XBL001 — Achievements must unlock during normal gameplay only
  Fix: No dev-console commands to force-unlock achievements

TCR-XBL002 — Cloud saves must sync before save access
  Fix: Wait for XGameSave sync before reading/writing saves

TCR-XBL003 — Presence string must reflect current activity
  Fix: Update presence string on game state change

Quick Resume:

TCR-QR001 — Game must resume from Quick Resume in under 15 seconds
TCR-QR002 — After Quick Resume, all gameplay must function correctly
  Fix: Reconnect audio, network, validate game state on resume

Accessibility:

TCR-ACC001 — Game must support button remapping (or use system remapping)
TCR-ACC002 — Game must support Narrator (screen reader) in menus
  Fix: Add proper UI focus management and accessible labels

Common TCR Failures

Nintendo LOT Checks

LOT Check Overview

LOT Check = Nintendo's certification process
Named "LOT" from Japanese manufacturing term (lot = batch)

Nintendo is the strictest of the three platforms.
LOT checks are extremely thorough — expect 50–150+ test cases.

LOT check categories:
  Basic Operation    — start, stop, error handling
  Sleep Mode         — lid closed, wake behavior
  Joy-Con handling   — attach/detach during play
  Network            — online features, offline fallback
  Save Data          — corruption resistance
  Controller types   — all supported controllers
  Handheld/Docked    — mode switching
  amiibo             — if supported
  Local Wireless     — if supported
  Nintendo Switch Online — if using NSO multiplayer
  Content Policies   — age ratings, violent content rules
  Language support   — required languages per region

Critical LOT Requirements

Sleep Mode (highest failure rate):

LOT-001 — Game must handle sleep (lid closed) within 2 seconds
  Fix: Pause game, stop audio, suspend network on sleep signal

LOT-002 — Game must resume from sleep correctly
  Fix: Resume audio, refresh network connections, sync time

LOT-003 — Save data must not corrupt on sleep during save
  Fix: Never save during sleep transition (atomic writes)

Joy-Con Handling:

LOT-010 — Joy-Con detach during gameplay must not crash
  Fix: Handle NpadId disconnect event gracefully, pause or show prompt

LOT-011 — All gameplay must be playable with one Joy-Con (horizontal)
  Fix: In single Joy-Con mode, remap to SL/SR/stick only
  (OR explicitly declare game requires dual Joy-Con)

LOT-012 — Pro Controller must work if game supports it
  Fix: Test all controller types — NpadStyleSet must be correct

Performance:

LOT-020 — Handheld mode must maintain minimum 30 FPS
  Fix: Dynamic resolution, reduce quality in handheld
  Fail: If game dips to <20 FPS regularly in handheld

LOT-021 — Docked mode must not exceed thermal limits
  Fix: Nintendo monitors GPU temperature — don't run at 100% GPU 100% of time

LOT-022 — Battery drain must not exceed specified rate
  Fix: Monitor GPU/CPU utilization — use Nintendo's power profiler

Sleep Mode Implementation

// Nintendo Switch sleep mode handling (conceptual)
 
// Register for system event callbacks
AppletHookCookie hookCookie;
appletHook(&hookCookie, AppletHookCallback, nullptr);
 
void AppletHookCallback(AppletHookType type, void* param) {
    switch (type) {
    case AppletHookType_OnExitRequest:
        // Player pressed home button — exit cleanly
        g_gameRunning = false;
        SaveGameState();        // save progress
        AudioEngine::Shutdown();
        NetworkManager::Disconnect();
        break;
        
    case AppletHookType_OnFocusState:
        // Focus changed (sleep, overlay, etc.)
        AppletFocusState focusState = appletGetFocusState();
        
        if (focusState == AppletFocusState_InFocus) {
            // Resumed — restore everything
            AudioEngine::Resume();
            NetworkManager::ReconnectAsync();
            SyncGameTime();
        } else {
            // Lost focus — pause game
            AudioEngine::Suspend();
            g_gamePaused = true;
        }
        break;
        
    case AppletHookType_OnOperationMode:
        // Docked/handheld mode changed
        AppletOperationMode mode = appletGetOperationMode();
        bool isDocked = (mode == AppletOperationMode_Console);
        RenderSettings::AdjustForMode(isDocked);
        break;
    }
}

Common LOT Failures

Pre-Certification Checklist

Universal Requirements (All Platforms)

☐ Game launches successfully from cold start
☐ Game launches successfully from sleep/suspend resume
☐ Game handles unexpected shutdown without save corruption
☐ Save data writes are atomic (temp file + rename)
☐ Backup save exists and loads on primary corruption
☐ All supported controller types tested
☐ Correct platform button icons shown (not generic / wrong platform)
☐ Age rating displayed at startup (ESRB/PEGI/CERO)
☐ Game handles multiple user accounts
☐ Online features degrade gracefully when offline
☐ No debug/dev-only code paths in submission build
☐ All required languages shipped (check per-region requirements)
☐ All placeholder text removed ("TODO", "TBD", "PLACEHOLDER")
☐ Game does not access filesystem paths it doesn't own
☐ No infinite loops / hangs tested (10 hour soak test)
☐ Memory usage within approved budget
☐ Frame rate meets minimum target (30 FPS minimum, sustained)

PlayStation-Specific Checklist

☐ Trophy set implemented correctly (at least 1 set, Platinum if 2+ Gold)
☐ Trophy artwork at correct resolution (256×256 PNG)
☐ DualSense haptics implemented (required for PS5 certification)
☐ Adaptive triggers implemented or explicitly disabled
☐ Activity Cards configured (PS5 recommended)
☐ Game Help hints configured (PS5 recommended)
☐ Suspend event handled within 5 seconds
☐ PSN presence string updated correctly
☐ Save data uses PSN save APIs (not raw filesystem)
☐ Cross-save implemented if supporting PS4 → PS5 upgrade
☐ PS4 → PS5 upgrade path tested (if supporting both)

Xbox-Specific Checklist

☐ Achievements implemented (1,000 Gamerscore base)
☐ Achievement artwork at correct resolution (1920×1080 min)
☐ Cloud saves implemented via Xbox Game Save API
☐ Quick Resume implemented (game resumes cleanly from suspended state)
☐ Presence string updates with game state
☐ Smart Delivery configured if shipping Xbox One + Series versions
☐ Button remapping supported (or system remapping enabled)
☐ Narrator/accessibility mode tested in all menus
☐ 4-user local testing (all features work with 4 different accounts)
☐ PLM events handled (suspend, resume, constrained)
☐ Network timeout tested (graceful offline handling)
☐ MicrosoftGame.config correct (TitleId, StoreId, version)

Nintendo Switch-Specific Checklist

☐ Sleep mode tested (lid close + wake-up)
☐ Joy-Con detach tested mid-gameplay (no crash)
☐ All controller types tested: dual Joy-Con, single Joy-Con, Pro Controller
☐ Handheld mode performance: sustained 30 FPS
☐ Docked mode resolution: 1080p output
☐ Mode switch (dock/undock) tested during gameplay
☐ HD Rumble implemented (required for Joy-Con games)
☐ Home button press handled (game pauses gracefully)
☐ Offline mode tested (all features without internet)
☐ Japanese fonts included if shipping in Japan
☐ Battery drain within Nintendo guidelines (6 hour minimum target)
☐ Thermal stress test (1 hour continuous play, check for throttling)
☐ microSD card tested (slower load times — no hang)
☐ System applets tested: camera, news, shop overlays don't crash game

Submission Best Practices

Build Hardening for Cert

Before submitting — harden your build:

1. Remove all dev shortcuts:
   No "press F1 to unlock all levels"
   No invincibility debug modes
   No achievement force-unlock commands
   No "skip to level" console commands

2. Remove all placeholder content:
   No "TODO" strings in any text
   No missing translation strings (should fallback to English, not crash)
   No broken asset references (missing textures show as error in cert)

3. Run the build in certification mode:
   PlayStation: use devkit in "Testkit" mode (simulates retail behavior)
   Xbox: enable "Retail Sandbox" mode
   Switch: use EDEV in production mode

4. Run soak tests:
   Leave game running for 8–12 hours straight (memory leak detection)
   Leave game in menu overnight (no freeze/crash)
   Rapid controller connect/disconnect for 30 minutes

5. Check all edge cases:
   Full storage (no space for save) — show error, don't crash
   No internet — all online features disabled gracefully
   Network disconnect mid-session — reconnect or show message

Submission Checklist Final

Final submission checklist:

Build:
☐ Build compiled in Release/Final mode (not Debug)
☐ Correct version number in manifest
☐ Platform SDK version matches required minimum

Store Listing:
☐ Game title correct
☐ Description accurate and in all required languages
☐ Screenshots meet resolution requirements
☐ Trailer uploaded (if required)
☐ Age rating certificate uploaded (ESRB/PEGI/CERO submission done)
☐ Content descriptor flags set correctly (violence, language, etc.)
☐ Price and release date set

Technical:
☐ All platform TRC/TCR/LOT items verified
☐ Soak test passed (8+ hours)
☐ Crash-free on all target hardware
☐ Performance targets met on all hardware

Submit:
☐ Upload to partner portal
☐ Fill out submission questionnaire
☐ Specify submission type (initial / patch / DLC)
☐ Note any waiver requests (if any requirements inapplicable)
☐ Confirm contact info for cert team questions

Patch Certification

Title Updates

Every patch requires certification — same process as initial submission.

Patch certification is typically faster:
  Platform has your game in their system already
  Only changed features need full testing (regression testing)
  Emergency patches (game-breaking bugs) can request expedited review

Patch strategies:
  Plan patch submissions 3–4 weeks before desired live date
  Batch small fixes — don't submit weekly (each submission takes time)
  Test patches on the same hardware as original cert

Day-one patch:
  Very common — final cert changes fixed post-submission
  Submit day-one patch immediately after initial cert passes
  Platform approves simultaneously when possible

Hotfix (emergency):
  Contact partner manager — explain severity (crash/data loss)
  Platform holders have expedited process for game-breaking issues
  Submit fix ASAP — document the bug and fix clearly