Promise
Keep every design project in scope.
- Agreed — screens/deliverables and review rounds locked at kickoff
- Waiting on client — reviews and decisions sit in clear views until they reply
- Extras — anything new needs an approved paid change before you start work
Clientrail is an orderly manual process with copy-paste messages. It does not automate Slack/email, sync Figma, e-sign, or collect payment.
How to use (≤10 minutes)
- Duplicate this page (or publish as a template, then duplicate for each engagement).
- Replace the Northwind demo — edit or delete demo rows; keep the schemas and views.
- Start your project — Client → Project (lock counts + scope summary) → Deliverables → Review Rounds → run Change Requests when asks appear.
Databases (overview)
Linked database views live below once created. Use them as your home dashboard:
| Database |
Use for |
| Clients |
Who you sell to |
| Projects |
Agreed scope numbers (price, screens, rounds) |
| Deliverables |
Checklist of what’s in the box |
| Review Rounds |
Included critique cycles vs agreed count |
| Change Requests |
Extras priced/dated before work |
| Daily Actions |
Optional day-to-day checklist |
Playbook: Change Request flow (summary)
Use whenever the client asks for something not already on Deliverables or within Agreed review rounds.
- Log the request the same day (do not add a Deliverable yet).
- Map to scope (In scope clarify / Extra deliverable / Extra round / Swap / Decline / Unclear).