Jobs
Add progress notes to the job record during delivery
A running record of communications that protects you in disputes and keeps you organised across multiple jobs.
Review recordBlueprint journey
Lesson 19 / 36
0 completed
Next best lesson: Start Here: How to use Blueprint week by week
Guided operating lesson
Win and retain clients through communication habits that signal professionalism, even when the job gets difficult.
Who this is for
Tradespeople who do good technical work but lose clients over communication issues — delays, silence, or inconsistent updates.
Why it matters
Most client complaints about contractors are communication problems, not quality problems. A contractor who communicates consistently is perceived as more professional than one who delivers better work in silence.
Lesson outcome
A communication rhythm you apply to every job that keeps clients informed, calm, and confident in your professionalism.
Real-world problem
A builder is running a kitchen renovation. Materials are delayed by two days. He knows. The client does not. On day 2 of silence the client calls, frustrated. On day 3 she calls her husband, who calls the builder's competitor to get a quote "just in case." On day 4 the builder shows up without warning and the client feels like the job is out of control. None of this was about the quality of the work — all of it was about the absence of communication.
Why this happens
When you are on site, silence feels normal. To the client waiting at home, silence feels like uncertainty or avoidance. The gap in perspective causes most communication complaints.
When something goes wrong — a delay, a cost change, an unexpected complication — many contractors say nothing and hope it resolves. This always makes things worse.
Professional standard
A professional contractor contacts the client before the client contacts them. Updates about delays, schedule changes, or progress should come from you, not in response to a chase.
If something has gone wrong or is likely to, tell the client immediately with a solution in hand if possible. Clients can handle problems. They cannot handle surprises.
Step-by-step operating system
Before work begins, tell the client what to expect: expected timeline, your working hours, how and when you will communicate, and what decisions they may need to make during the job.
BuilderBuddi: Record the agreed scope and timeline in the job notes in BuilderBuddi.
For jobs longer than 2–3 days, send a brief update every 2 days. "Day 3 — framing is done, plumbing starts tomorrow, on track for Friday." This takes 60 seconds and eliminates most follow-up calls.
Any change to cost, scope, or timeline — communicate it the same day it becomes known. Include what changed, why, and what the plan is.
When the job is done, send a message confirming completion, noting any items for the client's attention, and stating the invoice is on its way.
BuilderBuddi: Mark the job complete in BuilderBuddi and send the invoice from the job record.
BuilderBuddi workflow cards
Use job notes and status fields in BuilderBuddi to keep your communication log and ensure nothing falls through the cracks.
Jobs
A running record of communications that protects you in disputes and keeps you organised across multiple jobs.
Review recordJobs
Job status reflects reality, not memory — useful when managing more than two or three jobs simultaneously.
Open in BuilderBuddiContext: A tiler's tile order was delayed by 3 days. He did not tell the client until the scheduled start day.
Challenge: The client had arranged access and taken time off work. She was angry — not about the delay itself but about the late notice. She did not refer the tiler to her sister as planned.
Recommended response: Communicate delays the moment you know about them, not when they land on the client. A proactive message turns an inconvenience into evidence of professionalism.
Field notes
Key takeaways
Common mistakes
Consequence: The client interprets silence as a lack of control. They begin to distrust the project even if the work is fine.
Prevention: Build update messages into your job routine. Every 2 days for jobs over 3 days. Same day for any change.
Consequence: A 2-day delay that is communicated immediately is manageable. The same delay revealed at the last minute is a crisis.
Prevention: Adopt the rule: communicate changes the same day you know about them, not when they cannot be avoided.
Consequence: Contractors often assume clients understand trade timelines, material lead times, or scope constraints. They almost never do.
Prevention: Over-explain once rather than under-explain and face a complaint. The client's frame of reference is not yours.
Complete this in BuilderBuddi
Tick these only when the real business output exists. This keeps Blueprint tied to work done, not pages viewed.
Practical action
On your next job, send a start-of-job message before work begins outlining the timeline and how you will communicate. Then send one update mid-job. Note the client reaction.
Worksheet prompt
Think about the last client complaint or difficult conversation you had. How much of it was a communication issue rather than a quality issue? What would you do differently now?
Worksheets and templates
Start-of-job, mid-job, and completion message templates for consistent client communication.
Ready for immediate use
Next step