When to warn a client that a project is running over budget

Most clients can accept that a project costs more than planned. Few accept hearing it for the first time at the final invoice. This post gives you a simple warning routine: checkpoints on the budget, a forecast you can calculate in a minute, and wording for the conversation when the forecast says the project will run over.

Why early warnings matter

A budget overrun is easier to handle when you spot it while there is still time to choose. Early on, the client can reduce scope, move a date or approve more budget. Near the end, the only choices left are to absorb the cost or argue about it.

An early warning also protects trust. Clients tend to forgive a cost that was flagged early and explained. They rarely forgive a surprise.

Set budget checkpoints

Agree on a few checkpoints before the project starts. Three are enough: 50%, 75% and 90% of the hours budget.

Say a project has a budget of 120 hours, which is 120 x 100 = $12,000 at $100 an hour. The checkpoints fall at:

• 50%. 120 x 0.50 = 60 hours.
• 75%. 120 x 0.75 = 90 hours.
• 90%. 120 x 0.90 = 108 hours.

At each checkpoint, stop and compare the hours used with the share of the work that is finished. Use your own budget and your own rate. The figures here are an example.

Compare hours used with work done

Hours used alone do not tell you much. A project that has used 55% of its budget is fine if 55% of the work is done, and in trouble if only 40% is done.

For each project, track two numbers every week:

• Share of budget used. Hours so far divided by total budgeted hours.
• Share of work complete. Your honest judgment, ideally tied to finished tasks or milestones.

If the second number lags well behind the first, the project is drifting.

Forecast the final hours

You can turn those two numbers into a quick forecast. Divide the hours used by the share of work complete.

Say you are in week five. You have logged 66 hours, which is 66 / 120 = 55% of the budget. You believe 40% of the work is complete. The forecast is 66 / 0.40 = 165 hours.

That is 165 - 120 = 45 hours over budget. At $100 an hour, the overrun is 45 x 100 = $4,500, which is 45 / 120 = 37.5% above the plan.

Now compare a healthier case. With the same 66 hours and 55% of the work complete, the forecast is 66 / 0.55 = 120 hours, exactly on budget. The same hours-used figure can mean two very different projects, which is why the forecast matters.

This method assumes the work continues at the same pace, and your estimate of progress is a judgment. Treat the result as a warning signal, not a prediction.

Choose a tolerance

Decide in advance how much of a forecast overrun you will absorb quietly and how much you will raise with the client.

For example, set a tolerance of 10%, which on a 120-hour budget is 12 hours. If the forecast is within it, keep an eye on the project. If the forecast goes beyond it, tell the client.

In the example above, the forecast of 165 hours is 45 hours over, far beyond a 12-hour tolerance. That is a conversation to have this week.

Find the cause before you call

An overrun has different causes, and the cause changes what you ask for.

• The client changed or added work. That belongs in a change order. See how to prevent scope creep with clear change orders for how to handle it.
• Dependencies were late. Waiting for content or approvals often costs time. It may justify an adjusted schedule or a fee.
• Your estimate was too low. This one is yours to handle. You may absorb some or all of it, and you should learn from it.

Be honest with yourself about which one it is. Clients can tell when an explanation does not match the facts.

What to say to the client

Keep the message short and give the facts first. A good structure has four parts:

1. The numbers. "We have used 66 of 120 hours, and we estimate 40% of the work is complete."
2. The forecast. "At this pace, we expect to need about 165 hours."
3. The cause. One plain sentence, such as "The extra rounds of feedback on the design added time."
4. The options. "We can reduce the scope, extend the budget by 45 hours, or adjust the timeline. Which would you prefer?"

Ask for a decision by a specific date. Then record the answer in writing, so it is clear what was agreed.

Make the numbers trustworthy

A forecast is only as good as the hours behind it. If time is logged late or missed, the hours used are too low and the warning arrives too late. Where billable hours go missing covers common gaps. What is a billable hour? is a good reference if your team is unclear on what to log.

Review the figures weekly. A five-minute check on every active project is enough to catch most problems.

Match the routine to how you price

If you sell a fixed price, an overrun comes out of your margin unless the cause is a change from the client. With hourly billing, the client pays for the hours but may still need to know the budget is moving. Hourly, fixed fee or retainer: how to choose a pricing model explains how each model shares the risk.

Use your tools

HireOrSell offers budget tracking and progress monitoring on projects, and can record time against projects and milestones on its paid plans. Check the pricing page for current plan details. A simple spreadsheet with hours used, share complete and the forecast also works.

Next step

Pick one active project. Write its hours budget, hours used and your honest estimate of the share complete. Divide hours used by the share complete to get the forecast. If it goes beyond your tolerance, contact the client this week, using the four-part message above.