Unpaid work rarely appears all at once. It accumulates through small boundary gaps that were never written down.
Mistake 1: starting without a brief
A verbal brief feels faster until the first review. Write the outcome and constraints before the first billable block.
Mistake 2: not naming the reviewer
A project with several reviewers can produce contradictory feedback. Ask for one owner and a consolidated response.
Mistake 3: leaving revisions undefined
Say how many review rounds are included and what counts as a new request. The revision log makes the boundary visible.
Mistake 4: a handoff with no checklist
Missing files and permissions create unpaid cleanup. Use a short handoff list every time.
Mistake 5: no closeout
Archive the final files and decisions. A clean closeout reduces future support and makes the next project easier.
A quick repair
| Item | Example |
|---|---|
| Symptom | Repair |
| Feedback conflicts | Name one reviewer |
| Scope grows | Use a revision log |
| Handoff repeats | Use a delivery checklist |
What to watch for
- Relying on memory for scope.
- Letting the loudest reviewer set the direction.
- Treating closeout as optional.
A useful next step
Choose one repair for the next project. A boundary that is written down is easier to keep than one that depends on being assertive in the moment. If a request is outside the brief, write it in the log as new work before doing it. The short pause creates a choice; doing it silently creates an unpaid precedent. If the same client repeatedly adds requests, show the revision log at the next review and agree on a separate scope. Record the new scope before the first hour of work, not after delivery. Send the scope note before the next call, not after the work is done.