{{project}} / current product/version [ ] / change owner {{business}} / review {{deadline}}

Purpose: establish what deserves a change and what remains a report or hypothesis.
Evidence record: issue/source ID | date/version | intended task | exact symptom | expected and observed result | environment | recurrence window | independent reproduction | consequence | private-data handling | current disposition. Preserve source wording and distinguish observed behavior, self-report, opinion, and a new feature request.
Use harmless fixtures to reproduce technical problems. Verify product identity and source version; keep the buyer’s only backup untouched. De-identify pattern records and retain private originals only where authorized and necessary. A support queue without a buyer/usage denominator cannot establish incidence or general satisfaction.
Group related reports by mechanism, not merely wording. Separate a download that cannot be located, unsaved work that was never exported, invalid-file rejection, and a valid-backup reader defect. Each needs its own expected behavior and acceptance case.
Decision: correct defect / clarify instructions / investigate / defer request / outside supported scope. Reason and owner [ ]. Prioritize task impact, likelihood supported by evidence, data consequences, and the cost/dependencies of a safe correction. Do not inflate sparse feedback into guaranteed sales or a promise of universal compatibility.
Acceptance hypothesis: when [specific condition], [candidate] should produce [observable result] without changing [protected existing behavior]. Failure must be distinguishable from a success message alone.
Ready when the issue can be checked against the current artifact, the impact is explicit, and a real change can be described without inventing evidence.

Your decision
What user evidence supports this change?
My answer: [ ]
Source and date: [ ]
Still to check: [ ]
Next action, owner, and due date: [ ]

Before you start
- Buyer feedback: [Source or notes]
- Current version: [Source or notes]
- Regression cases: [Source or notes]

What you will make
A defined update with release notes and checks for existing behavior.