Skip to content

Lesson 5 of 6

Write the Weekly Status Update: Status First, Needs Named

Write a one-screen update that states the status and its reason in the first line, lists what was done, names what is needed from whom and by when, and is drafted from the action log and finished by a person.

6 minForward Deployed Engineering

After this lesson you will be able to write a weekly status update that a busy sponsor can act on in one minute, and that tells the truth when the truth is uncomfortable.

It is Friday 12 June. You promised Larchmont's operations director a written update every Friday by 15:00. Yesterday's demo went well, and the pilot is in some danger. The update has to say both.

What a status update is for

A status update is not a diary of your week. It answers three questions for the sponsor: will this arrive when I expect it, is there anything I must do, and is there anything I should worry about?

The operations director runs nine practices and will give your message about a minute. Anything they must do has to be visible within that minute.

The shape

Use the same shape every week. A reader who knows where to look reads faster and misses less.

  • The status and its reason, in the first line.
  • What was done this week, as outcomes.
  • What you need from the customer: who, what, and by when.
  • What you will do next week.
  • When they will next hear from you.

Keep it to one screen. If it needs scrolling, the detail belongs in an attachment.

Three words with fixed meanings

Say at the start what your status words mean, and never bend them.

  • On track: the agreed date will be met, and nothing you know of threatens it.
  • At risk: the date can still be met, but only if a named thing happens by a named day.
  • Off track: the date will not be met. A new date, or a decision, is needed.

The hard one is "at risk". It is tempting to stay on "on track" while a problem might still solve itself. Do not. "At risk" in good time lets the sponsor help. The same news a week later, after seven days of "on track", arrives as proof that your updates cannot be relied on.

Draft it from the log

The facts in an update are already in the action log: what was finished, what is open, what is late and what it blocks. Collecting them by hand each week is slow, and it invites you to leave out the awkward ones. Let a script collect them. Save this as status.py, next to actions.py.

"""Draft the weekly status update from the action log. A person finishes it.

Usage: python status.py YYYY-MM-DD     the last day of the week being reported
"""

import sys
from datetime import date, timedelta

from actions import as_of, days_late, load


def describe(row, day):
    text = f"- {row['owner']}: {row['action']}. Due {row['due']:%a %d %b}"
    late = days_late(row, day)
    if late:
        text += f", {late} day{'s' if late != 1 else ''} late"
    if row["blocks"]:
        text += f". Blocks: {row['blocks']}"
    return text + "."


def main(day):
    done, still_open = as_of(load(), day)
    week_start = day - timedelta(days=6)
    late = [row for row in still_open if days_late(row, day)]
    blocked = sorted({row["blocks"] for row in late if row["blocks"]})
    if blocked:
        hint = "at risk, because a late action blocks " + " and ".join(blocked)
    elif late:
        hint = "on track, with late actions to chase"
    else:
        hint = "on track"
    print(f"DRAFT status update, week ending {day:%a %d %b %Y}")
    print("Lines that start with >> are yours to write.")
    print()
    print(f">> Status: (the log suggests: {hint})")
    print()
    print("Done this week")
    for row in sorted(done, key=lambda row: row["done"]):
        if row["done"] >= week_start:
            late_by = days_late(row, day)
            note = f", {late_by} day{'s' if late_by != 1 else ''} late" if late_by else ""
            print(f"- {row['owner']}: {row['action']} ({row['done']:%a %d %b}{note}).")
    for side, title in (("customer", "Needed from Larchmont"), ("us", "Our open actions")):
        print()
        print(title)
        for row in still_open:
            if row["side"] == side:
                print(describe(row, day))
    print()
    print("Next week")
    print(">>")


if __name__ == "__main__":
    if len(sys.argv) != 2:
        sys.exit(__doc__)
    main(date.fromisoformat(sys.argv[1]))
python status.py 2026-06-12
DRAFT status update, week ending Fri 12 Jun 2026
Lines that start with >> are yours to write.

>> Status: (the log suggests: at risk, because a late action blocks Pilot start)

Done this week
- Operations director: Confirm the start date with both practice managers (Mon 08 Jun).
- Head nurse: List the items that must never be suggested for reorder (Tue 09 Jun, 1 day late).
- FDE: Demo reorder suggestions on May's order history (Thu 11 Jun).

Needed from Larchmont
- IT manager: Get a read-only key for the practice system from its supplier. Due Wed 10 Jun, 2 days late. Blocks: Pilot start.
- Head of clinical services: Decide who approves each order during the pilot. Due Mon 15 Jun. Blocks: Pilot start.
- Practice manager: Book 30 minutes of training at each pilot practice. Due Wed 17 Jun.

Our open actions
- FDE: Round every suggestion up to whole boxes. Due Tue 16 Jun.
- FDE: Write the one-page guide for the pilot practices. Due Thu 18 Jun.

Next week
>>

The script has done the collecting. Everything finished in the last seven days is listed, with a note where it was late. Everything open is listed under the side that owns it, the customer's first, with the days late and whatever it blocks.

Two lines begin with >>. Those are left for you. The script offers a suggestion for the status, from a simple rule: if a late action blocks something, the suggestion is "at risk". It cannot know whether that is right. It does not know that the demo went well, that the supplier has been silent, or what the operations director could do about it. Judgement of that kind is yours.

Finish it by hand

Here is the update that was sent.

Subject: Stock pilot: status, week ending Fri 12 June

Status: AT RISK. The read-only key for the practice system has
not arrived. Without it the pilot cannot start on Mon 22 June.

Done this week
- Demo held on Thu 11 June on Ashby Road's orders for May. The
  head nurse will use the suggestions once they are in whole
  boxes.
- The never-suggest list is in place. No controlled drugs appear.
- Start date confirmed with both practice managers.

Needed from Larchmont
- IT manager: the read-only key. Due Wed 10 June, now 2 days
  late. It is the one item that can move the start date.
  Request: could you ask the supplier's account manager for a
  delivery date, by Wed 17 June?
- Head of clinical services: who approves each order during the
  pilot, by Mon 15 June.
- Practice manager: training booked at both practices,
  by Wed 17 June.

From us next week
- Suggestions rounded up to whole boxes, by Tue 16 June.
- One-page guide for the pilot practices, by Thu 18 June.

Next update: Fri 19 June, or the same day if the key date changes.

Compare it with the draft. The facts are the same. What you added is this.

  • A status with a reason. The first two sentences say what is wrong and what it threatens. A reader who stops there knows the most important thing.
  • Outcomes. The draft said the demo was done. The update says what the demo showed.
  • A request. The draft said the key was late. The update asks the operations director to do one particular thing by one particular day. The sponsor knows the supplier's account manager and you do not. A late item with no request attached is a complaint. With a request it becomes something the sponsor can act on.
  • Your own actions, with dates. You are asking others to keep dates, so you show yours.

Notice also what it leaves out. It does not say whose fault the late key is. The IT manager asked the supplier on time, and the supplier has not replied. Naming a person as the cause, in a message copied to their director, makes an enemy of someone you will need next week. State the fact, the effect and the request.

Mistakes that cost trust

Four habits make status updates worthless, and each is common.

  • Reporting activity. "Continued work on integration" tells the sponsor nothing. Say what is now true that was not true last week.
  • Burying the problem. If the one thing that matters is in the fourth paragraph, it will not be read.
  • Staying green. A project reported as on track for five weeks and then as two weeks late was not on track for five weeks.
  • Skipping a week. The week you have nothing good to say is the week the sponsor most needs to hear from you. Send it anyway, and on time.

The operations director replied within the hour and agreed to call the supplier's account manager on Monday. The next lesson begins with the answer.

Key takeaways

  • Put the status and its reason in the first line. Many readers stop there.
  • Use three words with fixed meanings: on track, at risk and off track.
  • Name each thing you need, the person you need it from and the date.
  • Report outcomes, not activity. "Demo held, head nurse will use it" tells the sponsor more than "worked on the demo".
  • Let a script draft the facts from the log, and write the judgement yourself.
  • Say "at risk" as soon as it is true. A project that is green until the day it is red loses the sponsor's trust.

Try it

Suppose the key had arrived on Thursday 11 June. Put 2026-06-11 in the done column of row A04 in actions.csv, between the due date and Pilot start, and run python status.py 2026-06-12 again. A good result changes the suggested status to on track, and moves the key into "Done this week" marked as 1 day late. Then write the first line of the update for that week. A good first line says the pilot is on track for Monday 22 June and names the one thing still needed before then, which is the decision on who approves each order.

Official documentation

Ready to use this in a job?

Rolebound applies to matching roles for you.

Start now

Written with AI and checked automatically. Nobody has run these steps by hand, and tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.

    Cookies on Rolebound

    We use necessary cookies to sign you in and keep the site working — those cannot be turned off. We would also like to set analytics and advertising cookies so we can see which pages help people get interviews and which adverts brought them here. Nothing optional is set unless you say yes, and you can change your mind at any time from “Cookie settings” in the footer. Read our Privacy Policy.

    Write the Weekly Status Update: Status First, Needs Named | Work with the Customer: Discovery Calls, Demos and Status Updates | Rolebound