Decide what a new-version rating reset would actually erase

Describe the exact effect before discussing benefits

Apple’s current help calls this an overview-rating reset. It occurs with a new version release, cannot restore the previous rating afterward, affects all countries or regions simultaneously and leaves written reviews visible. For universal apps, its scope is the selected platform version. These facts were checked on 7 November 2026.

Put those consequences at the top of the decision packet, before any conversion hypothesis. Distinguish the aggregate score from written customer accounts and from the product issues that generated them. A reset does not settle a complaint, remove a recurring defect or make a previous statement untrue. If the proposal depends on customers no longer seeing criticism, the rationale is unsound and should be rejected.

Ask whether the product change explains the decision

Have the product owner describe the material change and identify which older experiences no longer describe the released app. Use documented behavior rather than a general claim that the redesign is much better. Separate resolved problems from problems still open. A change in colors or a new advertising campaign is not evidence that the service experience has fundamentally changed.

Consider the information value of the existing rating history, including favorable experience that would also be lost from the aggregate. Different storefronts may have different histories even though the reset acts across countries. Ask whether the team is comfortable making the same irreversible choice for all affected regions, not only the market used in the presentation. Do not promise that a new aggregate will be higher or return quickly.

Compare alternatives that preserve the record

Options include retaining the aggregate while publishing accurate release notes, responding appropriately to reviews, addressing unresolved defects and collecting genuine feedback through permitted, neutral processes. These alternatives can explain improvement without erasing the aggregate context. They should not become selective requests for praise or pressure on customers to revise criticism.

Write the costs and uncertainties of both choices. Keeping the rating may leave older experience prominent; resetting removes the prior aggregate and creates a period in which the new rating is not yet established. Apple says a reset notice appears and a new aggregate appears after enough new ratings. Do not invent a numerical threshold or predict when that will happen. The decision should be viable even if the first new feedback remains critical.

Record the decision before the release action

State the chosen platform version, intended release, affected scope, reasons and alternatives considered. Keep actual execution with the authorized release owner. A planning worksheet is not permission to select the reset control, and a general launch approval should not silently include an irreversible rating change. Require an explicit decision about this consequence within the organization’s normal approval process.

If the choice is to retain the rating, document that decision so a later operator does not treat the unchanged setting as an omission. If a reset is separately authorized and performed, preserve the reset date in internal reporting and keep before/after rating series clearly labeled. Do not present the new series as continuous improvement over the old one without explaining the reset. Continue reading and responding to legitimate criticism because the product responsibility survives either choice.

Make the reasoning concrete.

A fictional transit app fixes a substantial offline-map defect before a new release. Marketing proposes a reset because the old aggregate is weak, but the team has not considered strong ratings in other storefronts or the continued visibility of written reviews.

The team postpones any action until the product and regional consequences are reviewed. It keeps written criticism in view and does not assume that a reset will improve customer sentiment.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Effect

   What aggregate changes, what survives and what cannot be restored?

2. Scope

   Which platform version and all-region consequences apply?

3. Rationale

   Which documented product change makes older ratings less representative?

4. Alternative

   How could improvement be explained while retaining the aggregate?

5. Record

   How will any separately authorized reset be labeled in later reporting?

Watch for the wrong conclusion.

• Treating reset as deletion of written reviews.
• Considering only the weakest storefront.
• Presenting post-reset ratings as an uninterrupted performance trend.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis, not supplier implementation instructions or measured business results. Sources support only the specifically attributed platform facts. Supplier controls, contracts and local requirements can change; verify the actual placement and current provider guidance before implementation.

• Apple: Reset an app overview rating →Primary platform documentation · Supports: Supports release timing, irreversibility, all-region and platform-version scope, surviving written reviews and reset notice; ethical decision framework and alternatives are editorial.