What to know
Confirm the app name, subtitle, description, keywords, category, support URL, privacy policy URL, screenshots, and every required locale. Review the version number, copyright, release setting, age rating, content rights, and App Review contact information.
If the app needs a login, provide a working demo account and clear review notes. Test the exact build you submit. Remove claims that suggest features, awards, rankings, or results you cannot support.
Run the preflight in four passes. First, test the release build on a clean device. Second, compare the submitted metadata and screenshots with the current product. Third, open every support, privacy, and contact link without an account. Fourth, read the reviewer notes as if you had never seen the app before.
Use a read-only readiness report when you can. Then have a person approve the final changes and record the submission time.
Give the final check an owner and a clear cutoff. Compare the submitted build with the screenshots, preview, login path, privacy answers, and support links. A checklist is strongest when it points to evidence, not just a tick box.
Keep the approved snapshot with the version number and locale list. If review asks a question, the team can explain what was submitted and which product behavior supports the claim.
Do not treat a checklist as a promise of approval. Apple’s requirements and review guidance can change, and a complete form cannot fix a broken flow or unsupported claim. Reopen the relevant Apple documentation whenever the app adds login, payments, user content, health features, or a new distribution region.
Turn the preflight into an evidence matrix with one row for each field or asset: current value, source or build proof, locale, owner, test result, and approval state. A row marked “not applicable” should include a reason. This makes missing work visible without pretending that every release has the same risk.
Run the final pass from the reviewer’s starting point. Use the submitted build, the exact login or demo instructions, a clean device, and public links outside a saved session. Record where the reviewer can find each promised feature, what happens when a service is unavailable, and which support route answers questions.
Freeze the approved snapshot only after the last build and metadata comparison. If a late screenshot, privacy answer, or release-note edit changes the story, reopen the affected rows and repeat the relevant test. A checklist is useful when it describes the version actually submitted, not the version the team intended to submit.
Mark each evidence row by risk: reviewer-blocking, user-facing, legal or privacy-sensitive, operational, or informational. This helps the owner sequence work without treating a missing demo account, a stale caption, and a cosmetic note as equal release risks.
Use a late-change rule after the cutoff. Any change to the build, login path, metadata claim, screenshot, preview, privacy answer, support route, or reviewer instruction reopens its related rows and records a new approval. Do not quietly patch the submitted packet after the final comparison.
Run one final clean-start rehearsal with the exact submitted identifiers and links. Save the result, unresolved questions, and stop decision. If the rehearsal cannot be completed, pause submission or document the narrow condition a reviewer needs to reproduce.
Record the final submit-or-pause decision beside the evidence index. List the remaining exceptions, their risk, owner, next action, and reason the team is submitting or waiting. A completed checklist is not permission to ignore a reviewer-blocking or product-truth gap.
Require a named person to approve the decision after reading the exceptions, not only the green rows. Keep the approval date, build, locale scope, source dates, and any conditions that would invalidate the decision so a late change has a clear point of return.
ASOgenic can turn this preflight into a reviewable draft with field limits, source notes, and an owner for each check. The team still keeps the final publish decision and should verify the build and Apple guidance before submission.