Scope creep rarely shows up as a formal change request. It shows up as a Slack ping at 4:47pm: "Quick one — can we also add X? Shouldn't take long."
You know you should pause. You also know saying yes keeps the relationship warm. So you say yes. Later there's no paper trail, and invoicing it feels awkward.
Contracts help. Revision limits help. What still fails is the moment between the ask and the work.
The 60-second pause
Before you start anything new mid-project:
- Restate the original scope in one line
- Classify the ask: in scope / out of scope / unclear
- Give two paths: quote it, or defer to a later phase
- Don't start until they confirm in writing (even a "yes" reply)
Tiny freebies are fine — if you choose them. Log them as $0 so they don't become invisible hours.
What I put in a change log
- Date + who asked
- What they asked (paste the message)
- In / out / unclear
- Est. hours and price (including intentional $0)
- Approved? How?
- Started only after yes
After a couple projects you see leakage in dollars instead of vibes.
A line that doesn't sour the client
"Happy to add that — it's outside what we scoped, so I'll send a quick estimate (hours + timeline) and start once you confirm."
You're not saying no. You're replacing memory with a record.
Free template
I packaged those columns into a free spreadsheet (Excel / Google Sheets) if you want a starting point instead of building it from scratch: https://fluidoxygen.gumroad.com/l/vogjtv
Use it, fork it, ignore it — the habit matters more than the file.
Curious how others handle the 4:47pm "quick ask." Do you log it, absorb it, or quote every time?
