You will be able to name the four things a status update must answer for a manager.
It's Friday afternoon at an insurer's back office in Tampines, and you're moving the team's customer records to a new system. Your manager messages: "How's the migration going?" You write back a long paragraph. You had three calls with the vendor, cleaned up the customer file, fixed a bug in the import script, sat in on the IT meeting and started on the testing plan. You hit send feeling you've shown how hard you worked.
Your manager reads it and still doesn't know the one thing they asked. Is the migration going to be ready on the 30th or not?
A manager reading a status update is trying to answer four questions, whether or not they say so.
What is done? This means work that is finished and can be counted on, which is a shorter list than everything you touched.
What is next? The next step or milestone, with a date.
What is at risk? Anything that could make you late, push you over budget or change the outcome, while there's still time to do something about it.
What do they need to decide? Any choice that's theirs to make, and by when.
Those four questions cover almost everything a manager needs from you about a piece of work. A good update answers all four, even if the answer to one is "nothing". "No risks this week" and "no decisions needed" are useful lines, because they tell your manager they can stop worrying about that part.
Here is the Friday reply rewritten.
Migration: on track for 30 June. Done: customer file cleaned and loaded into the test system. Next: user testing with the finance team, 18 to 20 June. Risk: the vendor hasn't confirmed the go-live support date. I'm chasing them on Monday. Decision needed: none this week.
Five lines, and your manager can stop reading after the first if all they wanted was the headline.
Your manager is usually not the last reader. They're often reporting upward, to their own manager, a steering committee, a client or a weekly management meeting, and they have to summarise the work of several people at once.
So write lines they can lift and forward without editing. That means each line stands on its own, names the project, and avoids shorthand only your team understands. "Fixed the thing with the batch" is fine in a team chat. "Fixed the error that stopped the overnight file from loading" can go straight into a report for someone two levels up.
A good test: if your manager pasted your update into an email to their director, would it make sense without your manager adding a word? If it would, you have saved them ten minutes and made them look prepared, and managers remember who does that.
Start every update with a single word or short phrase that says where the work stands: on track, at risk, or late. Some teams use green, amber and red. Others use their own terms. Whatever you use, it goes first, before any explanation.
The one-word status does two jobs. It gives the reader the answer to the question they most care about in under a second. And it forces you to make a call. Writing "at risk" is uncomfortable, which is exactly why it's useful, because it brings the problem to the surface while there's still time to act. Lesson 3.2, Raise bad news early and bring options, goes into how to handle that moment.
Be honest with the status. An update that says "on track" every week until the week it says "late" damages trust more than an "at risk" three weeks earlier would have.
The Friday paragraph at the start of this lesson was a list of activity: calls, meetings, fixes, plans. Activity tells your manager you were busy. It doesn't tell them whether the work is closer to done.
Progress is described in outcomes and dates. Compare these lines.
Activity: "Had three calls with the vendor about the support arrangements."
Progress: "Vendor support agreed for go-live week, 30 June to 4 July."
Activity: "Worked on the testing plan."
Progress: "Testing plan drafted, needs your review by Wednesday."
It's natural to want your manager to see the effort, especially early in your career or when the work has been hard. The effort shows up anyway, in the outcomes. A manager who sees a steady line of finished items and well-flagged risks doesn't need a list of meetings to know you're working.
A civil servant updating a director on a policy review, a junior accountant updating an audit senior, and a nurse educator updating the ward manager on a training rollout all face the same test. Whatever the field, the update should answer the four questions with outcomes and dates.
Think about the piece of work your manager asks about most often. You probably already know the answer to each of the four questions, and the one-word status is probably clear in your head too. Getting them onto five lines is the activity below.
Write a five-line update on your main piece of work using done, next, risks and decisions needed, with a one-word status on top.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).