If you don't track revisions, you can't enforce revision limits. And if you can't enforce revision limits, you can't prevent scope creep.
Why manual tracking fails
Email threads aren't a tracking system. When a client sends feedback in three separate emails, is that one revision or three? When you make a change and the client says "almost — just tweak this one thing," does that count? Without a clear system, these ambiguities compound into hours of free work.
What revision tracking looks like
A good revision tracking system associates each round of revisions with a specific deliverable, increments a counter each time a revision is submitted, shows both you and the client the current count vs. the limit, and triggers a change order process when the limit is reached.
The tooling
Spreadsheets work but require discipline. Project management tools like Asana or Notion can be configured for this but don't have built-in revision counting. ScopePilot is purpose-built for this: every deliverable has a revision limit, every round is tracked, and the system automatically flags when limits are hit and facilitates the change order.
The mindset shift
Tracking revisions isn't about being rigid — it's about being transparent. When both you and the client can see the revision count, there are no surprises. The conversation shifts from "I feel like I've done a lot of revisions" to "we've used 2 of 3 included rounds — here's what happens next."