Raising a Problem Before It Is a Dispute
Nearly every dispute was a problem somebody noticed weeks earlier and did not mention. The timing is the whole technique.
Overruns, scope drift, blocked work and uncertainty about quality all arrive gradually. Raised early they are adjustments; raised late they are disputes.
The issue in “Raising a Problem Before It Is a Dispute” becomes easier to manage when the record and its limits are explicit. A team reviewing Monitask guide to managers and team leaders for boss vs leader should choose only the necessary evidence, explain how it will be used and keep a human correction path open.
The four to raise early
The estimate is going to be exceeded.
For an independent reference relevant to “Raising a Problem Before It Is a Dispute”, consult the Acas workplace guidance; compare its principles with the proposed contract, collection, access model and real review process.
The scope has grown beyond what was agreed.
Something is blocked and the client can unblock it.
Or you are uncertain whether what you are producing is what they wanted.
Each is cheap at week two and expensive at week eight.
The overrun warning
At roughly three quarters of the estimate: "we are at this point, I expect the total to be around that. Here are the options."
Options matter: reduce scope, accept the overrun, stop here.
A client given a choice responds differently from one given a bill, and this single message prevents most billing disputes.
Scope drift
Small additions accumulate until the project is a different project.
"That is outside what we agreed — I can do it, and it adds roughly this much" said each time, lightly.
Not as a refusal; as bookkeeping.
The alternative is absorbing it until the margin is gone and then resenting it, which helps nobody.
Blocked work
Flag it the day it happens, name what you need and from whom, and say what you will do meanwhile.
A blocker nobody mentioned becomes "why is this late" three weeks later.
Uncertainty about fit
"Before I go further, can I show you where this is heading?"
Fifteen minutes that prevents a fortnight of work in the wrong direction.
Contractors avoid this because it feels like admitting uncertainty; clients value it enormously, which is one of the more reliable asymmetries in this work.
How to raise things
In writing, briefly, with a proposal rather than only a problem.
Not apologetic, which invites doubt about competence.
Not accusatory where the client caused it, which invites defensiveness.
Factual and forward-looking: here is where we are, here is what I suggest.
For the client
Respond to these promptly, because the contractor is losing time while waiting.
And treat an early warning as good practice rather than as a problem, because the alternative is finding out late.
A client who reacts badly to an early warning will not get another.
Why this replaces monitoring
Nearly everything a client fears — hours wasted, work in the wrong direction, a project drifting — is prevented by this rather than detected by frames.
And it costs five minutes rather than an engagement's worth of overhead.
What to check
Has anything on your current engagement been quietly absorbed?
Is the estimate on track, and does the client know?
Is anything blocked that you have not flagged?
And when you last raised something early, how was it received?