In this guide
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.
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.
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.
Separate rating trends from your written-review sample
A report of all ratings and a set of written reviews answer different questions. Keep their denominators separate. Record the listing, reporting dates and scope before comparing periods; do not describe a small selected sample as the sentiment of every customer.
| Example field | Illustrative value | Interpretation |
|---|---|---|
| Written reviews examined | 20 new reviews in the chosen scope | A sample of written feedback, not all app ratings. |
| Sign-in mentions | 6 of the 20 reviews, classified manually | 30% of this sample; not 30% of users. |
| Rating metrics | Copy from the same source and scope each period | Do not substitute the sample average for the displayed store rating. |
| Owner and next step | Support: connect reports to the sign-in issue | A decision made by the team. |
| Outcome next week | Check the released fix and subsequent feedback | An observed change does not by itself prove causation. |