How to request an expedited App Store review

Test the circumstance before drafting the request

Apple gives two concrete examples: fixing a critical bug in the app, or releasing alongside an event the developer is directly associated with. Those examples share urgency, external impact, and evidence. They are different from preferring a faster launch.

• Critical bug: the currently available app seriously harms core use, safety, access, or essential data, and the submitted version contains the fix.
• Associated event: the event has an immovable date and the app or organization has a direct, explainable role in it.
• Weak basis: a self-selected marketing date, impatience with a normal queue, or a promise made without review buffer.

Assemble the evidence packet first

1. Record the app name, Apple ID, platform, version, build, and current submission status.
2. For a bug, write minimal reproduction steps against the live version and state the affected user population.
3. Name the submitted fix and how a reviewer can verify it without exposing private user data.
4. For an event, provide its public name, exact date and timezone, and the app's direct association.
5. Confirm the build, metadata, demo access, and backends are already review-ready before asking Apple to prioritize them.

Critical-bug request template

Keep severity concrete. ‘Users cannot access purchased content after sign-in’ is investigable; ‘important improvements’ is not. Make sure the reproduction path works before sending it.

We are requesting expedited review for [app/version/build] to fix a critical issue in the current App Store version.

User impact: [specific impact and affected users].
Reproduction on live version: 1) [step] 2) [step] 3) [observed failure].
Submitted fix: [what changed].
Reviewer verification: [steps and expected result].
Current submission status: [status] since [UTC timestamp].

Event-related request template

Apple recommends planning and scheduling event releases in App Store Connect. Explain why the remaining review timing now threatens a directly associated event rather than relying on urgency language alone.

We are requesting expedited review for [app/version/build] in connection with [event].

Event date/time: [date, time, timezone].
Our direct association: [organizer, official partner, participant, or required app function].
Why timing is immovable: [external fact].
App role during the event: [specific functionality].
Reviewer path: [credentials and numbered steps are in App Review Information].

After submitting, preserve the exact case you described

Do not replace the build, break the demo account, or alter the test path without a material reason. Monitor the submission and respond quickly if Apple requests more information. An expedite request asks for prioritization, not approval; the app still must meet the guidelines.

If the request is not granted, continue through the normal process and update users or event stakeholders with a range you can support. Repeated requests without new evidence dilute the case rather than strengthening it.