The instinct, when you decide you want daily updates, is to design a format. What you did, hours spent, percentage complete, blockers, next steps. Perhaps a template so everybody answers consistently.
Every field you add reduces the number of people who send anything at all, and the fields you added are rarely the ones you end up reading.
Ask for three lines
This is the whole specification:
- What got finished
- What is stuck, and on what
- Anything carrying over to tomorrow
In their own words, no format. A real one looks like this:
“Rotors came in and the Civic’s done. Transit’s still stuck waiting on the turbo. Need to ring Mrs Ali tomorrow.”
Nine seconds, typed one-handed walking to the van, and it contains almost everything you needed: one job closed, one blocked with the reason, one carried over. Compare that to the form version, which takes five minutes, gets filled in with invented percentages, and stops arriving by Thursday.
What to leave out, and why
Hours and time spent. That is a different conversation – a legitimate one, but mixing it into a daily update makes the whole thing feel like surveillance, and people respond to surveillance with the minimum that passes.
Percentages complete. Nobody knows. Everybody rounds to a number that keeps you off their back. You have gained a figure that looks like data and is not.
Anything you will not read. If you are not going to read it, asking for it costs you credibility every single evening.
The real reason it stops in week two
Here is the pattern almost every owner has lived through. Everybody sends an update for three days. By day nine two people have stopped. By day fourteen it is three, and within a month the only person still sending one is the person who was already organised.
It is tempting to read that as an attitude problem. It is more often a design problem, and the design is yours. An update is a small unpaid piece of admin at the end of a tiring day, and people keep doing small unpaid things only when they can see that they mattered.
So the question is not how to make people comply. It is: what happened to the first updates they sent?
- Nobody replied, so it looked like it went nowhere.
- Nothing changed as a result, so it looked like it changed nothing.
- It took too long, because you asked for structure instead of sentences.
- Somebody’s honest update was used against them, and everybody heard about it.
The five things that make it stick
The effort belongs at the start, not spread thinly over months. Do these for three weeks and the habit survives.
- Reply to the first ten. A sentence is enough. “Good – I’ll chase the turbo.” Silence is what kills it.
- Fix one blocker fast. Somebody reports being stuck; you unstick it within a day and say so. Now reporting problems visibly works, which is the single most persuasive thing that can happen in week one.
- Ask at the same time every day. Predictability turns a request into a routine.
- Send your own. Visibly. It stops the whole thing looking like something done to them.
- Do not punish honesty. The first person who admits something slipped sets the tone for everybody, and your reaction is the entire message.
The warning sign to watch for
A team that only reports good news is more dangerous than a team that reports nothing, because it looks like everything is fine right up until it is not. If the updates have gone uniformly positive, somebody was punished for honesty and everybody adjusted.
The fix is to ask about blockers rather than output. “What are you stuck on?” is help. “What did you do today?” is inspection. The information you get back is almost identical, and the response rate is not.
There is a longer treatment of all of this, including what to do when updates stop entirely, in getting staff to report.