Purchase Request — full story
Click each step to see what gets recorded. Six months later, you can reconstruct the entire history.
Problem: Excel forms
Initial workflow
Client sign-off
Add manager approval
Manager step added
Need finance step too
Finance approval added
All stakeholders OK
Shipped to production
Add attachment upload
Attachment UI
Ready to build
Patch release
Step 1 — Create the feature
Create Purchase Request under your project. Problem statement: "Users currently submit Excel forms with no audit trail."
Problem: Users currently submit Excel forms…
Step 2 — Prototype v1
Generate a clickable prototype (v0, Figma, etc.). Record as Prototype v1 — Initial workflow. Nothing gets overwritten later.
Step 3 — v1 Approved
Client reviews and approves. Record: Approved by Operations Manager, with optional meeting notes.
ApprovedStep 4 — Change Request #12
Client says: "Can we also add manager approval?" Log it as a Change Request — don't just build it silently.
Step 5 — Prototype v2
Update the prototype with the manager step. Create v2 — v1 stays in history forever.
Step 6 — v2 Rejected
Finance says: "We need to approve purchases over $5,000 too." Record rejection with remarks — full approval trail.
RejectedRemarks: "Need finance approval step"
Step 7 — Prototype v3
Add finance approval to the prototype. Create v3 with summary: "Added manager + finance approval"
Step 8 — v3 Approved
All stakeholders sign off. Feature status → Approved. Now build exactly v3.
Step 9 — Released in v1.0
Deploy to production. Record Deployment v1.0 linking Purchase Request → Prototype v3.
Step 10 — Change Request #18
Post-release feedback: "Can we attach quotations?" New CR — scope is visible, not hidden.
Step 11 — Prototype v4
Prototype the attachment upload UI. v4 created. Client can see exactly what they'll get before you build.
Step 12 — v4 Approved
Sign-off on attachment feature. Build and ship.
Step 13 — Released in v1.1
Deployment v1.1 records Purchase Request → Prototype v4. Complete audit trail.