What to know
Apple requires an age rating for App Store apps. The rating helps people understand the content and supports parental controls. It is based on answers about the app’s content, controls, and capabilities.
Make a short inventory before opening the questionnaire. Check user-generated content, messaging, advertising, health or wellness topics, mature themes, chance-based activities, and other features that may affect the answers. Use the current build, not a planned feature list.
Review the whole user journey, including onboarding, search, chat, social features, notifications, ads, purchases, and content loaded from a server. Record the screen or product rule that supports each answer. If a feature changes by account, location, or age, record that condition instead of choosing the least restrictive answer.
Save the evidence behind the answers and review them when the app changes. An inaccurate answer can make the store page misleading. Pair this check with the App Store release checklist and privacy label guide.
Treat the rating as a product and content check, not a marketing lever. A lower rating is not a reason to omit a real feature, and a higher rating is not a substitute for moderation or safety controls. Update the answers when you add user-generated content, social features, or a new content source.
Create a questionnaire evidence sheet with the question, selected answer, supporting screen or rule, build number, locale, and reviewer. Include server-controlled content and account-specific behavior, not only the default path. If a feature is unavailable in a country or age group, record that condition instead of assuming the public listing tells the whole story.
Use change triggers to reopen the rating review. Examples include adding chat, comments, user uploads, ads, location-based content, health claims, gambling-like mechanics, or a new content provider. A small product change can change the answer even when the screenshots and description look the same.
Compare the final rating with the store copy and access path. The age rating should not hide a real feature, and the product page should not imply content that the questionnaire does not describe. Ask a person who did not build the feature to read the evidence before submission.
For each answer, capture the observed behavior rather than a conclusion alone. Note where the content appears, whether it is user-created or server-supplied, who can access it, and which control or moderation rule applies. This makes a later review possible when the person who completed the questionnaire is unavailable.
Run the evidence sheet against both the default path and the highest-risk path. Test a new account, an account with access to social or user-generated features, and any location or age condition that changes content. If the server can change what users see without a new binary, include that behavior in the review.
When content is server-controlled, record the default and highest-risk content paths, account and region conditions, moderation controls, and how the reviewer reaches them. A binary can stay unchanged while the answer changes because the server content or rules changed.
Use a signoff row for each answer: question, selected response, evidence screen or rule, build and locale, data owner, and reviewer. Mark unknowns explicitly and stop submission until a responsible person resolves them.
Reopen the questionnaire when a provider, content source, moderation rule, chat or upload feature, region, or age gate changes. Keep the old and new evidence sheets so the change is explainable during the next review.
Treat the rating as a release dependency. Assign an owner, build number, locale, and review date, then reopen the sheet when the feature list, content provider, moderation rules, or store copy changes. Keep the current Apple definitions beside the record because category wording can change.
For example, if a community app hides comments until a user joins a group, review both the new-user path and the group-member path. The questionnaire evidence should explain the access condition and moderation controls, not only record what appears on the first screen.
ASOgenic can keep the rating questionnaire beside the build evidence and flag when a release brief changes a feature that may affect the answers. Your team still reviews the current Apple definitions and submits the final responses.