Trade jobs run into delays. Weather turns. Parts do not arrive. Previous work is worse than expected. Another trade is late. A tenant misses access. None of that automatically means someone has broken a promise. The trouble starts when a delay is handled like a shrug.
A fair delay has a reason, a record and a new plan. A broken promise usually has silence, shifting stories or dates that keep moving without anything written down.
A delay should have a reason
The reason does not need to be dramatic. Rain stopped exterior work. A part is backordered. Hidden damage needs extra repair. The customer changed the scope. The supplier sent the wrong item. A reason gives the other side something to understand and check. "We are delayed" is not enough for long. If the reason affects cost or timing, it should be written down.
Silence changes how the delay feels
Most customers can handle a delay better than silence. A tradie who says early that the job has slipped keeps more trust than one who disappears until the customer chases. The same goes the other way. A customer who cannot provide access or approval should say so early. Silence makes the other side fill the gap with suspicion. A two-line update can prevent days of frustration.
A new plan matters more than an apology
An apology is useful, but it does not move the job forward. A delay update should include what happens next: new date, new time window, expected part arrival, inspection plan, revised sequence or decision needed from the customer. Without a new plan, the apology becomes noise. The person waiting needs to know whether the job is still active and what the next practical step is.
Some delays are caused by the site
Site conditions can fairly change a timeline. Hidden rot, damp framing, unsafe access, old wiring, blocked drains, asbestos suspicion, termite damage and non-compliant previous work can all slow a job. The tradie should explain what was found and what needs to happen. The customer should not assume every site surprise is an excuse. But the tradie still needs to document it, preferably with photos.
Some delays are caused by the customer
Customers can cause delays too. Late approvals, changed selections, missed payments, locked gates, unavailable tenants, wrong supplied items and unclear decisions all push a job around. If that happens, own it. Tradies should keep the record calm and specific. The goal is not blame. It is to stop the customer-caused delay being confused with poor trade performance later.
Repeated date changes need a harder conversation
One changed date can be normal. Several changed dates with weak explanation is a pattern. Ask for the current status, the reason for each delay, the new expected date and what must happen before work continues. Put it in writing. Tradies should do the same when a customer keeps moving access or approvals. A pattern needs a written reset, not another casual promise.
Do not turn a delay into a review fight too early
A delay may become part of a fair review later, but using reviews as a threat while the job is still recoverable usually makes things worse. First, get the facts and the new plan. If the behaviour stays poor, the review can say that clearly. The strongest review will be the one with dates, messages and outcomes, not the one written during the first annoyed phone call.
Record dates without making it hostile
Keep a simple timeline: quote accepted, deposit paid, start date, missed dates, delay reasons, new dates and completion. This does not need to be a legal file. It is just memory written down. A calm record helps both sides separate fair delay from broken promise. If the job finishes well, nobody needs it. If it does not, the timeline becomes very useful.
Put the agreement in one place
For the difference between a delay and a broken promise, the useful record is usually short: what was agreed, who agreed it, when it was agreed, and what it does to price or timing. Keep that in one message, quote, invoice note or job file entry. Scattered details across calls and texts are where honest people start remembering different things. One written record gives both sides a calmer place to return to if the job later gets tense.
Keep the proof with the job
Save the quote, photos, messages, payment record, invoice and any approval tied to the issue. The proof does not need to be dramatic. It just needs to be findable. A customer can use it to explain a concern clearly. A tradie can use it to show what was done and why. The person with the clean record usually has the easier conversation when something is questioned later.
Make the later review factual
If the experience later becomes a review, write about behaviour and records, not just mood. Say whether the quote was clear, access was handled, messages were answered, changes were written down, payment terms were plain, and problems were fixed. That helps the next person reading the review. It also gives the business useful feedback instead of a public argument with no detail behind it.
A delay is not automatically a failure. It becomes a problem when nobody explains it, records it or resets the plan. Name the reason, write the new date, keep the timeline and watch the pattern. That is how both sides tell the difference between a job that slipped and a promise that stopped meaning anything.