Definition of Done for Creative Milestones: A Freelancer Checklist
How to write Definition-of-Done items per milestone so client approval is clear, disputes drop, and Payment Release Gate opens on facts: not arguments.
- milestone approval
- deliverable approval
- client approval workflow
- freelance contract approval
- creative project workflow
Definition of Done (DoD) answers one question before anyone says "approved": What must be true for this milestone to be complete? Without DoD, approval is subjective, the client expected animation; you delivered static frames; both feel cheated.
This guide shows how to write DoD for creative milestones, how it connects to Approval Lock™, and why it reduces payment disputes.
Why DoD matters for milestone approval
Approval without DoD:
- Client withholds payment for "missing" items never listed
- Creative considers work done when client wanted more polish
- Revision rounds blur into new scope
DoD makes completion checklistable, both sides see the same finish line.
DoD lives in the locked agreement
Best practice: define DoD per milestone when you Agreement Lock™, not invented ad hoc at invoice time.
Example milestone: Homepage UI design (desktop)
| DoD item | Done when |
|---|---|
| All listed screens designed per wireframe | Figma file linked; screens named |
| Design system tokens applied | Colors, type, spacing documented |
| Responsive notes for dev handoff | Breakpoint behavior described |
| Client consolidated feedback through round 2 | Revision Boundary tracked |
Each item should be observable, not "client is happy."
DoD vs acceptance criteria vs deliverables list
- Deliverables list, what artifacts exist (e.g. "10 social templates")
- DoD, conditions those artifacts must meet to call the milestone complete
- Acceptance, approver locks approval after DoD is satisfied
Deliverables without DoD invite "I thought it included copywriting."
Who marks DoD complete?
Usually the creative marks items complete when objectively true; the client approver verifies and locks approval. If an item needs client input ("provide brand photography"), split it:
- Client obligation, blocks creative completion until delivered
- Creative obligation, blocks approval until finished
Surface blockers in Accountability Chat instead of silent stalls.
DoD and revision rounds
DoD does not replace Revision Boundary™. Typical flow:
- Submit milestone v1
- Client feedback → revision round 1
- Resubmit → round 2 if needed
- Creative marks DoD items complete
- Approver reviews against DoD → Approval Lock
If feedback demands work outside DoD scope, that is scope drift → change order.
Sample DoD snippets by discipline
Brand identity milestone
- Logo files in agreed formats (SVG, PNG, PDF)
- Color and typography specs documented
- Basic usage guide (minimum 2 pages)
Video edit milestone
- Final cut at agreed duration ± agreed tolerance
- Color and audio levels broadcast-safe per spec
- Project file archived; exports delivered via agreed channel
Development milestone
- Features in SOW pass agreed test checklist
- No P0/P1 bugs open per defined severity table
- Deployed to staging URL; README updated
Adjust to your contract, specificity beats generic "work complete."
DoD unlocks Payment Release Gate
Zlaip enforces ordering: Approval Lock may only be created after every DoD item for that milestone is complete. That invariant protects clients from premature sign-off and creatives from "we never said it was done" payment blocks.
Payment follows approval, DoD is why approval means something.
Bottom line
Definition of Done turns fuzzy creative milestones into auditable completion. Write DoD when you lock the contract, track it through review, then approve and invoice on the checklist, not on vibes.
Related: What is Approval Lock? · Developer milestone approval