Why your status update gets skimmed and a decision gets read

Watch the short version (0:49)

Most weekly updates report activity and get skimmed. Put the decision your manager needs in the first line. Three updates rewritten, with the AI prompt.

On this page

More responsibility every year, same title. Part of the reason is one line long.

Two updates land in the same inbox on a Friday afternoon.

The first one starts: "Worked on the vendor review this week."

The second one starts: "We need to choose a vendor by Friday. I recommend B."

Same week. Same work. The same person could have written both.

Which one gets a reply?

A status update is a receipt

Most weekly updates are receipts. An itemised list of where the week went: what was finished, who was met, what was started.

A receipt is accurate. It is also something nobody acts on. You glance at the total and put it away.

Your manager reads your update the way you read a receipt. They are looking for one thing: is there anything here I have to do? If the answer isn't in the first line, they assume it is no, and they move on to the message where the answer is yes.

That isn't laziness. It is the job. A manager's week is a queue of things waiting for a decision. An update that asks for nothing goes to the back of the queue, however good the work behind it was.

So the work gets done and the person who did it stays invisible. Not because the work was small. Because the update filed it under "nothing needed".

For the step-by-step version with the prompt, see How to Write a Weekly Status Update Your Manager Acts On.

The decision line

The fix is one line long. I call it the decision line: the first sentence of your update is the decision your manager needs to make.

Not a summary. Not the headline of your week. The thing you need from them, with your recommendation attached.

Everything else stays. It just moves down.

You don't have to rewrite it yourself. Before you send the update, paste it into AI with one instruction:

TEXT
Rewrite this so the first line is the decision my manager needs to make.

Three updates, rewritten

When you need a decision

Before: "Kept working through the request backlog. The contractor who helps with it finishes at the end of the month, and the backlog won't be cleared by then."

After: "I need your decision this week: extend the contractor by a month, or accept that the backlog won't be cleared when they leave. I recommend extending."

The facts were already in the update. They were sitting in the second sentence, phrased as weather.

When there is no decision

Before: "Continued the migration. Testing is ongoing and we are still on plan for the end of the month. No blockers."

After: "No decision needed this week. The migration is on plan for the end of the month."

"No decision needed" is still a decision line. It tells them they can stop reading, and that you know the difference.

When the news is bad

Before: "Made progress on the report. The regional data arrived late, so we may slip by about a week unless we leave that part out."

After: "The report will be a week late unless we drop the regional breakdown. I recommend dropping it. I need your call by Wednesday."

Bad news in the first line feels risky. It is the opposite. Bad news with a recommendation reads as someone managing the problem. Bad news in the third paragraph reads as someone hoping it won't be noticed.

Two things to check before you send

  1. AI will sometimes add what your update didn't say: a deadline, a number, a reason. Read the new first line against your original. If the date you need an answer by is missing, put it in yourself. Don't let the tool guess it.
  2. Keep your recommendation. If AI softens "I recommend B" into "we could consider B", change it back. The recommendation is the part that shows judgment.

Why this is about more than email

The people who decide who gets the bigger role mostly don't watch you work. They read what you send.

If everything you send is a receipt, the picture they hold of you is someone who is busy. If what you send is a decision with a recommendation, the picture is someone who already thinks one level up.

You are probably doing the bigger job already. The first line is where it starts to show.

Try it on this week's update, before you hit send.

Share

Frequently asked questions

(3)

Why does nobody reply to my status updates?

Because most updates list what was done and ask for nothing. A reader skimming for "is there anything here I have to do?" finds no answer in the first line and moves on. Put the decision you need at the top and the update gets read as a request.

What is a decision line?

One opening sentence that names the decision the reader has to make, by when, and what you recommend. Everything else in the update becomes the evidence for that line.

Should every update start with a decision?

No. If nothing needs deciding, say so in the first line and keep the rest short. The point is that the reader knows in one sentence whether they have to act.

The daily step goes out on LinkedIn and X.