Client revision bucket sheet

Output when you are done: scope/bug/taste sorting

Buckets before panic.

When to use this

Workflow: QA / review loops
Operators who already produce this artifact by hand
You will use the same structure more than once.

Skip if: People who have not decided what good looks like

Properties

| Field | Value | |-------|-------| | Workflow | QA / review loops | | Finished artifact | scope/bug/taste sorting | | Reuse | Same headings every cycle; swap facts only |

Body (copy and fill)

# Client revision bucket sheet

Purpose: scope/bug/taste sorting

## Context
- Audience:
- Time window:
- Source of truth:

## What happened - - 

## What matters (judgment) - ## Next steps (owner · date)
- [ ] 
- [ ] 

## Open questions
-

Prompt to fill it faster

Fill this template for my QA / review loops update.
Finished artifact should be: scope/bug/taste sorting
Use only the notes I paste. Mark unknowns with [CHECK].
Keep plain English. No fake metrics. No fluff.

Done looks like

The artifact is ready to send or save: scope/bug/taste sorting
Owners and dates are filled or marked [CHECK]
You are not rewriting the structure next time

If you’re stuck

Start free assessment (AI Readiness) at https://faisalrizvi.com/ , See where we’re wasting hours. 3 minutes. Score + prioritized roadmap. No login.

Book a free 30-min call only if you want help after the roadmap.