Journal

How to Tell a Client a Project Is Going Over Budget

12 October 2026 4 min read

Tell the client as soon as you reach 75 percent of the estimated hours, before the original budget is actually exhausted. Waiting until the limit is exceeded turns a manageable scope discussion into a dispute over an unexpected bill. Early notification gives the client control over whether to increase the budget, cut remaining features, or pause the work.

Spotting the overrun before the budget runs out

Tracking billable hours in real time allows you to compare actual elapsed time against remaining deliverables continuously. An overrun rarely happens without warning; it builds up when individual tasks take 20 or 30 percent longer than planned, or when minor client requests accumulate across multiple working sessions. If you have allocated 40 hours to a project, you should review your burn rate at the 25 to 30 hour mark. If only half the deliverables are completed at that stage, an overrun is guaranteed unless scope or pace changes immediately.

Raising the issue when a quarter of the budget remains gives the client sufficient time to review internal priorities, consult internal stakeholders, or approve additional expenditure without halting project momentum. Waiting until hour 39 creates panic and forces an emergency decision. If you use Punch O'Clock, you can export a CSV of your recorded time to examine the precise breakdown of how hours were distributed across earlier sessions before drafting your communication.

Categorising why the hours are increasing

Before contacting the client, determine the precise cause of the variance. Hour overruns generally stem from two distinct sources: scope expansion or structural complexity. Scope expansion includes direct client requests for additional features, extra rounds of revisions beyond the original agreement, or changes to previously signed-off designs. Structural complexity occurs when the underlying technical environment requires more labor than anticipated due to undocumented legacy code, faulty third-party tools, or unexpected integration hurdles.

Distinguishing between these two causes determines how you structure your explanation. If the overrun stems from client-requested additions, point directly to those specific change requests and show how they consumed hours outside the initial baseline. If the overrun comes from an underestimation on your part, acknowledge the underestimation plainly. Clients respect honest accounting, but they expect you to propose a reasonable compromise if the variance was driven by an internal estimation error rather than new requirements.

Giving the client clear choices

Never send a message that simply states you are running out of hours and asks the client what they want to do. You must present defined, structured options so the client can evaluate trade-offs and make an informed decision quickly. Presenting concrete choices shifts the conversation from a friction-filled complaint about unexpected costs into a collaborative project planning exercise.

Provide three distinct options whenever an overrun occurs:

Authorise additional hours at the agreed rate to complete the full original scope alongside any new additions.
Maintain the original hour limit by removing or deprioritising non-essential deliverables from the remaining phase.
Pause the remaining work immediately at the current hour threshold while delivering all completed assets and documentation.

Writing a direct and neutral notification

The tone of your update should be objective, professional, and free of defensive language or unnecessary apologies. Avoid phrases that convey panic, and do not blame the client's team for asking questions during development. State the current numerical status, explain the variance concisely, outline the choices, and state clearly what happens next if no choice is selected before the remaining hours expire.

Structure your notification email into four distinct parts. Begin with a clear summary of hours consumed versus total estimated hours to establish the current facts. Follow with a short explanation of what caused the variance, linking hours spent to specific tasks or requests. Present your proposed options with precise hour estimates for any additional work, and conclude with a firm deadline for a response. State explicitly that work on remaining tasks will pause once the existing cap is reached until a choice is confirmed, ensuring unapproved billable time does not accumulate.

Securing written approval and updating the project baseline

Once the client selects a path, confirm the decision in writing before resuming or extending work. If the client chooses to expand the budget, issue an updated agreement or formal change order specifying the exact number of extra hours approved and the new overall cap. If the client chooses to trim the scope, list the specific features, revisions, or tasks that have been removed or deferred to a future milestone.

Update your internal tracking records to reflect the new agreed budget limit immediately. Proceeding with tasks without explicit written sign-off creates ambiguity that often leads to uncollectible invoices when the final bill is submitted. Maintaining a clear, documented record of every scope modification ensures both parties remain aligned on expectations, timelines, and final billing outcomes.