Keep the work.
Check the proof.

# Acceptance brief

Fill this in before work begins. Share it with the builder and reviewer. You do not need Ranex.

## The task

Change: [one concrete change]
Who needs it: [person or role]
Problem it solves: [what they cannot do today]
Out of scope: [what this task does not include]

## What a person should be able to do

Starting point: [page, command or current state]
Action: [what the person does]
Expected result: [what they can observe]

Example: From an empty contact form, submit without an email address. Show an email error, keep the message text and do not send the form.

## Acceptance cases

| Case | Starting state and action | Expected result | Evidence needed |
| --- | --- | --- | --- |
| Normal use | [input and action] | [observable result] | [test output or recording] |
| Invalid or missing input | [input and action] | [clear failure behavior] | [test output or recording] |
| Permission boundary, if applicable | [role and action] | [allowed or denied result] | [test output] |
| Existing behavior | [nearby workflow] | [what must still work] | [regression check] |

## Review agreement

Acceptance criteria agreed by: [name]
Saved before work begins at: [commit or dated document]
Evidence must identify: [the exact commit or build under review]
Reviewer: [person responsible for acceptance]
If a check cannot run: [record it as unverified and assign a next step]
If the criteria change: [record why and obtain review before treating the new criteria as accepted]

## Handoff

Version delivered: [commit or build]
Evidence: [links]
Known gaps: [list]
Review decision: [ready / changes needed / unverified]

---
From Ranex: https://ranex.dev/resources
Free to use, edit and share, including in commercial projects. No attribution required.

# Bug report

Title: [action + unexpected result]
Example: Submitting an invalid email clears the message field.

## Where it happens

App or repository: [name]
Version: [commit, build or release]
Page or command: [URL or command]
Environment: [browser / OS / runtime and version]
Account role, if relevant: [role, not credentials]

## Steps to reproduce

Starting state: [what must be true before step 1]
1. [first action and sample input]
2. [next action]
3. [action that exposes the failure]

Use made-up sample data. Remove passwords, tokens and personal information from attachments.

## Expected result

[What should have happened? Link to the acceptance brief if there is one.]

## Actual result

[What happened instead? Include the exact error text where useful.]

## Evidence

Screenshot or recording: [link]
Relevant output: [small excerpt or attachment]
Does it happen every time? [always / sometimes / once; number of attempts]
Last known working version: [version or unknown]

## Impact

Who is affected: [users or workflow]
What is blocked: [consequence]
Workaround: [steps or none known]

## How to check the fix

Repeat the steps above on: [fixed version]
Expected observation: [result]
Nearby behavior to recheck: [workflow]
Checked by: [name and date]

---
From Ranex: https://ranex.dev/resources
Free to use, edit and share, including in commercial projects. No attribution required.