Reusable template · Updated October 2, 2026
A website feedback template that makes the next action clear.
Separate what you observed from what you want changed. A marked screenshot shows where; a written request explains what to do.
Copy this for each change
Change title: Page address: Device / viewport: Screenshot / marked area: What I observed: What I want changed: How we will review the result: Status: Open / Resolved / Dismissed
You can paste the observation, requested change and review condition together into the editor’s change text. The beta does not have a separate acceptance-condition field.
Example: mobile contact form
| Field | Example |
|---|---|
| Change title | Expand the contact fields on mobile |
| Page and viewport | Contact page · 390 px wide |
| Observation | The inputs appear much narrower than their surrounding form container. |
| Requested change | Make inputs use the available form width, retaining the container padding. |
| Review condition | Open the page at 390 px, compare the field width with the container and check for horizontal scrolling. |
| Status | Open until a person has checked the updated page. |
Three checks before sending
- Can the recipient find the page? Include its address and device context.
- Is there one action per note? Split independent changes so each can be discussed separately.
- Is the expected result observable? Replace “make it better” with a concrete layout or text change.
Keep evidence and opinions separate
“The button overlaps the heading in this screenshot” is an observation. “This is costing us customers” needs separate evidence. If you are suggesting a design preference, label it as a preference rather than a defect.
When this template is not enough
Login problems, failed payments and intermittent behaviour need reproduction steps and actual testing. This template is for visual feedback and agreed changes; it does not replace functional QA or a shared issue tracker.