Weekly App Review Report Template for Product Teams

In this guide

1. Copy the template
2. Worked example: a small written-review sample
3. What ReviewBot fills and what you add
4. Make comparisons fair
5. Give the report a next action

Copy the template

Fill one report per store listing before combining results. Keep the data source and scope visible so a change in collection does not look like a product improvement.

Weekly report template

WEEKLY APP REVIEW REPORT
Period / timezone: [start – end / timezone]
Owner: [name]   Next review: [date]
App / store / public listing: [one listing and URL]
Data source: [written-review data / complete ratings / other]
Countries or languages covered: [scope]
Data refreshed: [time]   Missing or delayed data: [details]

RATING SUMMARY (use the source report)
Total ratings in period: [count]   Previous comparable period: [count]
Average score: [score]   Previous: [score]
5★ [count] | 4★ [count] | 3★ [count] | 2★ [count] | 1★ [count]
Comparison uses the same source, scope and period length: [yes / explain]

REVIEW TEXT SAMPLE (manual)
Reviews read: [count]   Sampling method: [all / recent / low-star / other]
Theme: [description]   Examples: [links]   Mentions in sample: [count]
Do not label sampled mentions as a percentage of all users or ratings.

DECISION AND FOLLOW-UP (manual)
Main finding: [one sentence with evidence]
Action: [specific task]   Owner: [name]   Due: [date]
Issue / support link: [URL]   Status: [open / investigating / resolved]
Next check: [what evidence would confirm improvement]

Download plain text

Worked example: a small written-review sample

Illustrative example only: a team reads 20 written reviews for one Android listing during a seven-day period. Five mention sign-in difficulty, so the report records five mentions among 20 reviews read. It does not claim that 25% of customers cannot sign in, or that the sample represents all star-only ratings.

Finding: five sampled reviews describe sign-in failures after an update; links attached.
Action: support owner Alex links the reports to a sign-in investigation, due Friday.
Next check: compare a new review sample after a verified fix using the same sampling method.
Leave rating totals and average score blank until copied from a source report; do not manufacture them from the example.

What ReviewBot fills and what you add

A ReviewBot status report supplies total ratings, average score, star distribution and period changes for its source. Google Play coverage depends on the selected data mode and freshness. Themes, representative links, owners and actions in this template are your manual interpretation.

Set up a rating report

Make comparisons fair

Use equal-length periods and the same app, country/language scope and data source. A written-review average is not interchangeable with the store’s overall rating. Note missing data and releases separately; a change after a release is a signal to investigate, not proof the release caused it.

Give the report a next action

End with one owner and one checkable action. A report with no decision can be archived; an unresolved issue should have a follow-up date and a link to the investigation. Weekly delivery is useful when someone can act weekly; otherwise use monthly reporting.