App Review Notes template for App Store Connect

Write notes that help a reviewer use this build

Review Notes should explain how to reach the parts of your app that need context. Use the labels and screens in the submitted build, state relevant prerequisites, and describe what the reviewer should see. Keep marketing copy in the store listing.

Separate general access instructions from a response to a previous rejection. Both may be needed, but a long discussion of a guideline does not replace an executable path through the app.

Copy and adapt this template

APP AND BUILD
App: [APP NAME]
Version / build: [VERSION] / [BUILD]

REVIEWER ACCESS
Sign-in required: [YES / NO]
Demo account: [Provided in App Review Information, if needed]
Prerequisites: [Required setup, region or hardware; otherwise none]

CORE FEATURE WALKTHROUGH
1. Launch the app and [starting action].
2. Open [screen] and choose [control].
3. Confirm [visible expected result].

PAID FEATURES, IF APPLICABLE
Navigation: [Exact route to purchase screen]
Products: [Relevant product identifiers and access rules]
Restore path: [Exact route, when applicable]

CHANGES FOR THIS SUBMISSION
[Verified changes, linked to the previous review question if relevant]

SUPPORTING MATERIAL
[Attachment name and the behavior it demonstrates]

KNOWN REQUIREMENTS
[Explain any relevant external dependency or limitation]

Remove sections that do not apply. Do not describe an untested behavior as a passing result, or invent a demo account that is not usable.

Give exact navigation and access conditions

“The feature is in settings” leaves too much to discover. A better note gives a path such as Home → Settings → Account → Delete account, then explains the confirmation step and expected result. That example is a format, not a claim about your app or a universal required screen layout.

For a feature that requires special hardware, a region, a subscription, uploaded content or a prepared account, describe those conditions explicitly. Check your backend availability and that the supplied review access works before submission.

Make supporting screenshots and recordings identifiable

Label every attachment and connect it to a particular step. Capture the actual submitted build. When a screenshot only shows a button, do not treat it as evidence that the operation behind the button succeeds.

A short recording can clarify a path, while logs can help explain a failure. Remove private customer information, credentials and unrelated data before preparing demonstration material.

Check the notes immediately before submitting

Read the walkthrough from a fresh installation or the intended starting state. Confirm the version and build, account access, product setup and attached files. Update the notes whenever the navigation changes.

Consult Apple’s App Review guidance for Apple’s submission preparation guidance and Apple’s current App Review Guidelines for the applicable rules. The template is an independent writing aid and does not guarantee review acceptance.