Project status updates
Fewer 'how's it going?' calls. Customers and the owner hear where each project stands every week, and nobody writes it from scratch.
Hours back
3
hours a week back, typically
How it runs
What we build, step by step.
This is the usual shape. Yours gets built around how your team actually does the job.
- 01
The week's progress collected
Tasks completed, hours on site, photos taken and any delays or changes logged against each live project.
- 02
Blockers and decisions pulled out
Anything waiting on the customer (a colour choice, a payment, access) is listed separately so it's clear who needs to act.
- 03
A short update drafted per project
What got done, what's next and anything the customer needs to decide, with two or three photos. Where the record and the messages disagree, the update shows it instead of smoothing it over.
- 04
Checked by the project lead
The lead reads the draft, fixes anything and sends it. Most take a couple of minutes.
- 05
An owner's roll-up
One page covering every live project: on track, at risk or late, with the reason for each.
Shown with software we see a lot. If your team uses something else, we build it into that instead.
Built for your business
Same job, different business. We build yours.
Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.
Your steps
Built around the order your team already works in, odd exceptions included.
Your software
Runs inside the tools you already pay for, set up the way you use them.
Your rules
Your wording, your limits, your sign-offs. Nothing generic goes out in your name.
You sign off
Your team keeps the final say.
Every customer update is read and sent by the project lead. The system never commits to a new date, price or change in scope.
What it's worth
What those hours add up to.
3 hours a week, over 46 working weeks, is 138 hours a year. At $50 an hour, that’s
$6,900
back in the business, every year.
Typical, not promised.
Before and after
The job, before and after.
How it runs today
On a longer job, customers ring to ask how it's going, and the office has to ring the site lead to find out. Weekly updates get written for the big jobs when someone remembers, and not at all for the rest.
What we build
- The week's progress collected
- Blockers and decisions pulled out
- A short update drafted per project
- Checked by the project lead
- An owner's roll-up
A month in
Every live customer gets an update every week, not just the big jobs. The phone rings less, decisions the customer owes you are in writing, and the owner sees every project on one page.
The update does more work than it looks
Most complaints on longer jobs aren't about the work. They're about not knowing what's happening. A short, regular update with a couple of photos heads off most of those calls. It also puts the decisions a customer owes you in writing, which helps a lot when a job runs late because a choice was made late.
FAQ
Do we need project software for weekly status updates?
No. Jobber and a group chat are enough. The weekly project update can be drafted from the job notes, photos and the messages your team already sends, and the proposal sets out exactly what's read.
Can the customer reply to the update?
Yes. Customer replies to a project update go to the project lead with the project's details alongside, so nothing gets lost in a general inbox.
More for operations
See them all →Next step
Bring this one to a free live build.
Thirty minutes on project status updates. We build its elf with you, live, and you keep it.