Designers · problem and fix
Scope creep on design projects on Mac: how to cap unlimited revisions in 2026
Scope creep on design projects happens when a client keeps asking for work that was never in the agreed price. It starts with one small favor and ends with rounds nobody quoted. You can stop most of it with a written scope, a change process, and a saved record of what was approved.
The short answer
- Scope creep is work that grows past the agreed deliverables without a new price.
- Unlimited revisions drive most of it, because nobody has set the end of feedback.
- Write the scope, state the revision rule, and quote every change as a change order.
- Keep approved versions in Figma's version history, and check your history limit.
- Lazur helps with menus, drafts and dictation. It does not run the project or send changes for you.
What unlimited revisions and scope creep costs you
Unpaid hours you never bill
The most direct cost is time you never invoice. A revision round that takes an afternoon feels small on its own. Repeat it again and again, and the project grows a second job nobody priced. Track hours per round, even if you do not bill them, so the cost shows up in your own numbers.
Late money and cash flow
Scope creep and late pay often travel together. The Freelancers Union 2022 survey found 91% of respondents had late or overdue wages at least once. That survey measured late pay, not revisions. Still, a project that keeps growing has more to argue about when the invoice arrives.
A lower real hourly rate
A fixed fee looks safe until the rounds stack up. Divide the fee by the real hours, including every revision, and compare the result with the BLS median of $30.27 per hour. That median is an employee figure, so use it as a rough check, not a freelance benchmark.
Delayed starts on the next job
Every extra round pushes your calendar. The next client waits, and your buffer for real emergencies shrinks. A late start can cost more than the revision itself, because it affects projects you have not taken yet. That cost is hard to measure, but it is real.
Tired work and weaker ideas
Long tails of feedback wear down the work itself. Tired designers make more mistakes and take fewer creative risks. This one is hard to measure, so treat it as a practical risk, not a measured rate. Notice it in your own energy at the end of a project.
Why it happens
A vague brief at kickoff
Most scope creep starts with a brief that describes goals but not deliverables. Words like clean, modern or a few options leave room for interpretation. Each interpretation can become a round, and each round can become a new request.
The planning fallacy in your quote
People underestimate how long tasks take and what can go wrong, even when past projects say otherwise. Kahneman and Tversky first identified the pattern. Your quote may assume one smooth round, and the real project will not follow that script.
Feedback with no owner or deadline
When three stakeholders send notes by chat, email and voice memo, nobody owns the final list. Changes pile up, and some contradict each other. Name one person who consolidates notes, and set one date for the last round.
No change control
Without a written change process, every request feels like a favor. Clients cannot see the cost of what they ask, so they ask again. A change order makes the cost visible at the moment of the request, which is the moment it matters.
Saying yes to keep the relationship warm
Designers want clients to like them, so they absorb small asks. That is a kind instinct. It also teaches the client that the price includes unlimited help. The next request then arrives with the same expectation.
Unclear revision rules in the contract
If the contract has no limit on rounds, a client may read silence as permission. A line on included rounds, response time and what counts as a new deliverable closes that gap. Without it, every disagreement starts from zero.
How to fix it
These work with or without any app.
Write a scope statement with an out-of-scope list
List the deliverables, formats, sizes and screens. Then list what is out, such as print files, animation or an extra brand guide. Keep it to one page. Send it with the quote, and ask the client to reply yes in writing.
Set a revision rule and a response window
Name the rounds that are included and the time the client has to respond. State that late feedback can move the delivery date. Use the same sentence in every proposal, so the rule feels normal, not personal.
Use the outside view before you quote
Look at your last few projects and note the hours per round, not the hours you guessed. This is reference class forecasting. The Decision Lab recommends using data from similar past projects, and it notes that awareness of the bias alone is not enough.
Split the project into signed milestones
Break the work into stages, such as discovery, concepts, final design and handoff. Get approval at each stage. Each approval closes the last round and shows exactly where new work starts.
Decide your reply ahead of time
Write an if-then rule: if a request is new work, then I send the change order the same day. A 2024 meta-analysis by Sheeran, Listrom and Gollwitzer covered 642 tests and found small to moderate effects of this kind of planning. Treat it as a nudge, not a cure.
Freeze approved versions in Figma
Open the menu next to the file name and choose Show Version History. Note the version and date you sent for sign-off. If the client wants a change to an approved screen, the history gives you a dated record to compare against.
Keep feedback in one thread per round
Use one comment thread for each round, in the tool the client already uses. If you try Frame.io, its free plan lets clients review through share links with no sign-up. Internal-only comments start at the Team plan at $25/month, so you do not need them to begin.
Review each project in a short debrief
Ask three questions: which changes were priced, which were absorbed, and which should have had a boundary. Write one rule from each answer into your template. Over time, the template does more of the arguing for you.
Scope creep is the slow growth of work beyond what you agreed to deliver. On a design project it looks like small favors. The client wants one more logo variant, a new hero banner, or a fresh color test. Each request looks harmless. Together they can add days of work without anyone signing a new price. Unlimited revisions make this easy, because the contract often says nothing about when feedback stops.
What scope creep costs you in real money
Most designers feel the cost first as time. The bill comes later, if it comes at all. The Freelancers Union ran a 2022 survey of freelancers in New York, with the Authors Guild, the Graphic Artist Guild and others. Of those respondents, 91% had late or overdue wages at least once. That survey measured late pay, not revisions. It also did not state its sample size, so read it as a warning sign, not a precise rate.
91%
of New York freelancers in a 2022 survey had late or overdue wages at least once
Over 60% of NY freelancers report not being paid for work performed$30.27
BLS median hourly pay for graphic designers, May 2025, an employee figure
Graphic Designers: Occupational Outlook Handbook30%
of psychology students finished their theses by the date they predicted, in Buehler et al. (1994)
Planning fallacy30 days
of version history for users on Drafts or the Starter plan in Figma
View a file's version historyHourly math makes the cost concrete. The BLS median pay for graphic designers was $30.27 per hour in May 2025. That is an employee figure, not a freelance rate. Still, every unpaid hour is time you could have billed or rested. Count the hours in your last few revision rounds before you decide the cost is small.
Why unlimited revisions drive scope creep
A revision limit is a boundary you can point to. Without one, every round looks like part of the deal. Clients rarely think they are asking for extra work. They think they are asking for a better result, and they may be right. The problem starts when nobody has said what counts as a revision and what counts as new work.
Signs your project has scope creep
- The brief changed, but the price and the deadline did not.
- A client asks for a new screen and calls it a small tweak.
- Feedback arrives in chat, email and voice notes, with no owner.
- You reopen work the client already approved.
- Your week is full of changes nobody priced.
A worked example: the logo round that never ended
A small studio agrees to design a logo, one color version and a one-page brand sheet. The quote covers the agreed concepts. In the second week, the client wants a new mark because the first one feels too corporate. You make it, as a favor. Then the client asks for a dark version, a set of social images and a mockup for a trade show. Nobody writes down what changed. By the end, the work is far larger than the quote, and the invoice still shows the original total.
The fix is not to be stricter in the moment. The fix is to make the boundary visible before the first round starts. Write what is in. Write what is out. Name who can ask for changes. A boundary on paper is easier to point to when a favor turns into a habit.
Why estimates break before the first revision
The planning fallacy explains a lot of this. People tend to underestimate how long a task will take, what it will cost and what can go wrong. They do it even when past projects tell them otherwise. Kahneman and Tversky first identified the pattern.
In a 1994 study, Buehler, Griffin and Ross asked psychology students to predict when they would finish senior theses. Only 30% finished by the date they predicted. Design quotes often leave out feedback rounds entirely. That gap is the same kind of error, and it hides in the first estimate.
Large projects show the same optimism at a bigger scale. The Decision Lab cites the Sydney Opera House, projected at $7 million and finished at $102 million, about a decade later than planned. You will not build an opera house. But a quote that assumes one clean round and a yes on the first try has the same blind spot.
Set the scope before the first sketch
Start with a short scope statement in the proposal. Use plain words. Say what you will deliver, in which formats, and on which screens or pages. Then write the out-of-scope list. Most scope fights happen over things nobody wrote down, not over things that were written.
Put the revision rule in the same place. State how many rounds of feedback are included, how long the client has to respond, and what happens after the last round. A round should be one consolidated set of notes, not a stream of messages. Keep that sentence in your contract template, and use it every time.
| Change type | Usually in scope? | What to do |
|---|---|---|
| Fixing your own error | Yes | Fix it, do not charge, and say so in writing |
| Feedback on a concept already in scope | Yes, within the agreed rounds | Log it and count it as a round |
| New deliverable, such as a trade show mockup | No | Send a change order with a price and a date |
| Changes to files after sign-off | No | Quote the work, then wait for approval before you start |
| Brand change from a new stakeholder | Depends on the contract | Pause and confirm the scope before you continue |
Handle change requests without a fight
When a request comes in, reply within one working day. Keep the tone calm. Acknowledge the idea, then name the price and the new date. A short reply works well: this is new work, here is the quote, and I can start once you approve it.
Use a written change order. Describe the change, the extra time, the price and the new deadline. Ask for a yes in writing before you start. An email reply counts as a record. A signed proposal is stronger. If you need terms with legal weight, check with a lawyer who handles contracts where you live.
Your own files can show what was approved. In Figma, open the menu next to the file name and choose Show Version History. The history appears in the right sidebar. When you send work for sign-off, note the date and the version you sent, so you can compare later.
To go back, open the version's menu and choose Restore This Version. Then click Edit current version to exit. Figma adds two autosave checkpoints, so restoring does not erase the current work. It does not bring back deleted comments, so keep a copy of feedback in your own notes.
The history limit matters. Figma's help center says users on Drafts or the Starter plan can access only 30 days of version history. If a project runs longer, export sign-off PDFs or key frames, and keep them in the project folder. Do not rely on the history alone.
Review tools that cut back and forth
Feedback gets messy when it lives in too many places. One review thread per round helps. Frame.io's free plan lists up to 2 members and 2GB, and clients can review through share links with no sign-up or login. Internal-only comments, which keep team talk away from the client, start at the Team plan at $25/month. You do not need them to begin.
Figma's pricing page says viewers are unlimited on paid plans. People can view, comment, inspect or export without taking a full editing seat. That helps when a client wants to look but not edit. Check the pricing page before you promise a client a specific plan, because plan terms change.
Mistakes that make scope creep worse
- Saying yes in the moment to keep the peace.
- Doing the extra work first and asking about price later.
- Trusting a verbal brief with no written change record.
- Treating every comment as a round, or every silence as approval.
- Letting one stakeholder add changes that the others never saw.
- Forgetting that your own mistakes are not billable.
Some changes deserve a yes. If the client is right about a fact, such as a wrong address or a typo in their own copy, fix it quickly. If the change fixes your error, the cost is yours. Keep those cases separate in your notes, so you do not argue the same point twice.
A new idea that replaces an approved direction is new work, even if it looks small. Ask the client to confirm the trade-off in writing. A short email is enough. The point is to make the choice visible, not to win an argument.
Where Lazur helps, and where it does not
Lazur is a voice assistant for the Mac. Hold Option and Command to ask about anything on your screen. Lazur answers out loud and points at menus. Hold fn to dictate text at your cursor in any app. Lazur does not click buttons, edit your Figma file or send your change order. You still do the design work and the sending.
Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models. Client files can still hold private details, so check your client agreement and your employer's rules before you show Lazur anything sensitive.
A routine that keeps scope in check
Run a short review after every project. Look at which requests came after sign-off, where the time went and which changes you priced. Write one line on the scope that failed, then add it to your template. The template gets better with each project, so the next argument is shorter.
- Which requests came after sign-off?
- Which rounds took longer than the quote allowed?
- Which changes did you price, and which did you absorb?
- What one sentence would have stopped the first favor?
What to do after the next client call
Write the change request before the call ends. Use the sentence from your template. If the client asks for something new, say you will confirm the price by email. Then send it that day. Waiting turns a friendly ask into a habit, and habits are hard to reverse.
Faster with Lazur
Where Lazur helps with unlimited revisions and scope creep
Hold ⌥ ⌘ and say what you want. Lazur sees your Figma window. Lazur draws a circle and a label around the button or menu you need.
- 1
Hold ⌥⌘ and talk
- 2
Lazur draws a circle and a label around the button or menu you need.
- 3
You stay in Figma. Nothing to copy into a chat window.
More things to say in Figma
- “Hold Option and Command, then ask where the version history menu is.”
- “Ask Lazur to walk you through restoring an older Figma version.”
- “Ask Lazur to draft a change order for a new mockup.”
- “Hold fn and dictate your reply to a change request.”
- “Ask Lazur to check a review tool's pricing page for plan limits.”
- “Remind me to send the change order by end of day.”
Free for 3 days, then $18/month. Download for Mac
You say“Hold Option and Command, then ask where Show Version History is.”
Lazur · points at itLazur draws a circle and a label around the menu, and you click it yourself.
What designers say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Hold Option and Command, then ask where the version history menu is.”
Lazur draws a circle and a label around the menu on your screen, and you click it yourself.
Points at it
“Ask Lazur to walk you through restoring an older Figma version.”
Lazur guides you one click at a time and waits for each click before it moves on.
Walks you through it
“Ask Lazur to draft a change order for a new mockup.”
Lazur drafts the text. You check the price and dates, then send it yourself.
Drafts it
“Hold fn and dictate your reply to a change request.”
Clean, formatted text appears at your cursor in any app.
Types what you say
“Ask Lazur to check a review tool's pricing page for plan limits.”
Research runs in Lazur's own Chrome tabs and comes back with a summary and a report.
Researches in the background
“Remind me to send the change order by end of day.”
Lazur adds the reminder to Apple Reminders, so the follow-up does not get lost.
Handles the small stuff
A plan you can start this week
- Day 1
Pull your last projects
Open your invoices and calendar for the last few projects. Note the hours per round, not the hours you guessed. Write the totals in one sheet. These numbers become your outside view for the next quote.
- Day 2
Write the scope statement
Draft one page with included deliverables, formats and screens. Add an out-of-scope list with examples from past projects. Use plain words, and avoid vague phrases like a few options or clean look.
- Day 3
Draft the revision rule
Write the rule for included rounds and the client's response window. Draft a change order template with fields for the change, the price and the new date. Ask Lazur to draft the wording, then edit it in your own voice.
- Day 4
Set sign-off points in Figma
Pick the milestones where you will ask for approval. Before each one, open the menu next to the file name and choose Show Version History. Note the version and the date in your project notes.
- Day 5
Practice the reply
Write your standard reply for new work. Hold fn to dictate it at the cursor in Mail or Slack. Save it as a snippet if you use it often, so it is ready next time a request arrives.
- Every Friday
Review and adjust
List the changes you received that week and how you handled each one. Note any that slipped past the boundary. Add one clear line to your template for each slip, so the same gap does not return.
Questions people ask
Is scope creep always the client's fault?
No. Vague briefs, unclear contracts and quotes that skip feedback rounds make it likely. Clients ask for more because nothing showed them where the line was. Fix the process first, then talk to the client.
How many revisions should I include?
There is no standard number, so do not copy one from a forum. Use your last few projects. Count the hours per round, then decide what you can include at your price. Put the number in writing.
Can I charge for every revision?
You can if your agreement says so and the client agrees before the work starts. Use a change order for each request. For terms with legal weight, check with a lawyer who handles contracts where you live.
Does Figma version history prove what a client approved?
It gives you a dated record of earlier versions, and you can restore one. It does not bring back deleted comments. Users on Drafts or the Starter plan can access only 30 days of history, so export sign-off PDFs too.
Can Lazur write my change order?
Lazur can draft the wording, and you read it, edit it and send it yourself. It does not send emails or edit your Figma file. Check the price and dates before anything leaves your desk.
Does Lazur see my client files?
Lazur looks at the screen only while you hold the shortcut. The screenshot goes to AI providers to answer and is not stored. Client confidentiality rules still apply, so check them first, and follow your employer's rules.
Is there a free way to share reviews with clients?
Frame.io's free plan lists up to 2 members and 2GB. Clients can review through share links with no sign-up. Plan details change, so check the current limits on Frame.io's pricing page.
Do I need a special Mac version of Figma for version history?
The Figma desktop app for Mac needs macOS 12 or later, and it has the same features as the browser version. Version history steps are the same in both. Check your version under Apple menu > About This Mac.
Sources
- Over 60% of NY freelancers report not being paid for work performed · Freelancers Union · checked 2026-11-07
- Planning fallacy · The Decision Lab · checked 2026-11-07
- Graphic Designers: Occupational Outlook Handbook · U.S. Bureau of Labor Statistics · checked 2026-11-07
- View a file's version history · Figma Help Center · checked 2026-11-07
- Guide to the Figma desktop app · Figma Help Center · checked 2026-11-07
- Figma Pricing · Figma · checked 2026-11-07
- Frame.io Pricing · Frame.io (Adobe) · checked 2026-11-07
Fix unlimited revisions and scope creep with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.