# App feedback and retest log

App/build under review: [exact build]
Round owner: [team role]
Decision date: [date]
Primary journey: [user goal]

Copy the finding block below for each issue. Use report IDs rather than personal names. Preserve the observed behavior even when you decide to defer it.

## Finding [ID]

Source report IDs: [IDs]
Task and starting state: [task, account and permission state]
Affected build/device/OS: [known scope; state what has not been checked]
Observation: [what the tester actually encountered]
Expected behavior: [what the task or product promised]
Frequency: [attempts and observations, or unknown]
Impact: [blocked task / lost work / confusion / cosmetic]
Confidence: [reproduced / evidence only / needs clarification]
Related findings: [IDs, or none]

Owner interpretation: [keep separate from the observation]
Priority and reason: [impact, recurrence and scope]
Decision: [fix / investigate / follow up / defer]
Decision explanation: [specific reasoning]
Assigned role: [team role]
Change reference: [ticket or revision]

Retest build: [exact build]
Retest starting state: [fresh/returning, permissions, network]
Retest task: [same journey, plus regression concern]
Observed retest result: [specific evidence]
Status: [resolved / remains / changed / not retested]
Remaining uncertainty: [untested scope]

## Round release decision

- [ ] Blocking findings have a recorded decision and owner.
- [ ] Relevant fixes were retested on the named build.
- [ ] Known limitations are stated accurately to users.
- [ ] Purchase tests used provider-supported test workflows.
- [ ] Access and support links were checked from the intended starting state.
- [ ] Reports and attachments contain no credentials or sensitive production data.

Release decision: [release / continue testing / limited rollout]
Evidence supporting the decision: [references]
Known remaining limitations: [specific items]
Follow-up task and owner: [next investigation]

This log organizes your evidence. A checked box, submitted report or completed build does not prove store approval or that every production path works.

Template by RateMyApp: https://ratemyapp.io/resources/app-testing-templates/
Free to copy and adapt for your team's private testing. No attribution required.