When a Project Goes Over Budget: FAQ for Freelancers

Budget overruns happen to most freelancers at some point. The question is what you do once you notice, and how you set things up so you notice earlier next time.

At what point should you tell the client?

As soon as you hit 80% of your quoted hours with significant work still remaining. Waiting until you are already over budget puts you in a weaker position. Flagging it at 80% gives both sides room to make a decision, whether that is adjusting scope, adding a change order, or agreeing on a cap.

What does a change order conversation actually look like?

Something direct: you have logged 16 of your estimated 20 hours, and there are still three deliverables outstanding. You can either reduce the remaining scope or add a $400 CAD change order to cover the additional time. Giving the client a clear choice is less awkward than either absorbing the loss silently or sending a surprise invoice.

How do you prevent this on the next project?

Build a monitoring checkpoint into your project workflow from the start. After completing 50% of estimated hours, review what is actually done versus what remains. That midpoint check is where most overruns become visible before they become a problem.

Should the original quote be revised upward next time?

Usually yes, but only after you understand why you went over. Revision rounds and unclear briefs are different problems than underestimating task complexity. Fixing the quote without fixing the process just delays the same issue.