Weekly team update
Keep the whole crew in the loop for five minutes of your Friday, not an hour. A short update drafted from the week's jobs, reviews and what's coming.
Hours back
1
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 gathered
Jobs finished, new work won, changes coming up and anything agreed in meetings, from your job software and meeting notes.
- 02
Shout-outs picked out
Customer reviews and thank-you messages that name someone are pulled out, so they get the credit in front of everyone.
- 03
A short update drafted
Five or six lines in your voice: what went well, what's coming, and anything people need to know for next week.
- 04
You check it
The draft lands with you on Friday afternoon. Change a line or send it as it is.
- 05
Sent where the team reads
Posted to the team chat or sent by text, so it reaches people who never open email.
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.
You read and approve every update before it goes out. Pay, performance and anyone's personal business are never included.
What it's worth
What those hours add up to.
1 hours a week, over 46 working weeks, is 46 hours a year. At $50 an hour, that’s
$2,300
back in the business, every year.
Typical, not promised.
Before and after
The job, before and after.
How it runs today
The crew hears about a new client, a rota change or a cracking review weeks later, if at all. You mean to send an update, but it's Friday night and you're doing quotes. The people in the vans feel like they're always the last to know.
What we build
- The week gathered
- Shout-outs picked out
- A short update drafted
- You check it
- Sent where the team reads
A month in
The team hears the news from you every Friday, techs see their reviews shared with everyone, and fewer people ring the office to ask what's going on.
FAQ
Will it sound like a corporate newsletter?
No. The weekly team update is written from a few examples of how you already talk to the team, and you can cut anything that sounds stiff.
Can different groups get different updates?
Yes. The office and each crew can get their own version of the weekly update, drafted from the same week.
More for operations
See them all →Next step
Bring this one to a free live build.
Thirty minutes on weekly team update. We build its elf with you, live, and you keep it.