Your team, thoughtfully built.

How to Write a Project Status Update With AI

By Staffmor Staff

Practical guides from the team building Staffmor.

To write a project status update with AI, give it the task list and the check results, and ask for three sections: done, blocked and next, with an owner and a decision on every blocker. A status update exists so its reader can decide what to do. It should report what the evidence shows, including when that is less than anyone hoped.

The example is a made-up workshop launch, reported on a Friday.

Collect the evidence first

The page copy is approved.
The booking email failed its check: it shows the wrong arrival time.
The venue address is waiting on confirmation.

Give each item a source: the approved copy, the check report, the task. A cheerful message in chat is context. A failed check that came after it is the status.

The request

The request: "Write a Friday status update from the task list and check reports below. Separate done, blocked and next. Give every blocker one owner and the decision needed. Do not call the launch ready while the booking email check is failing. Keep it short. This is an internal update, not a customer announcement."

What comes back

Page copy is approved. The booking email still shows the wrong arrival time, so the launch is on hold. Priya owns the fix and the re-check. The owner needs to confirm the venue address. Next: check the corrected email against the approved offer and review the address, then decide whether to publish.

Under it, three lines of evidence: approved copy version 3, failed email check, venue task. Those three lines are what make "on hold" useful. Without them it is a mood.

The mistakes to watch for

"90% done." Ninety percent of what? Unless the project has a defined count of things, the number tells the reader nothing and sounds like progress. Say what is done and what isn't.

Averaging a disagreement. If one report says the email is fine and a later check says it failed, the status is "failed, as of the later check." It is not "mostly working."

Approved is not published. Approved copy is a file. A published page is a URL that loads. Report whichever one is true.

Make the next one easy to trust

When the email passes, add the new check and keep the failed one as history. A status record that never shows a failure reads as one that isn't looking. If the page goes live, put the address and the date in the update.

Run it in your Staffmor office

Open the office on the computer running it with its Start Staffmor launcher. If you already have a paired web office, open it here. Paste this request and the source material into the conversation. Use your approved Codex connection, or ask your open Claude Code session to "Check Staffmor for work." A saved request is not a completed result. Review the answer or file when it comes back and reply with corrections. Ask for the evidence to be reconciled first and the prose second.

This request summarizes the checks you supply. It does not prove that a missing check passed or that your project tool was updated. New to Staffmor? Set up your office with Codex or Claude Code and an empty folder. Use your own supported AI account and approve the download, office activation and local folder/network access during setup. Claude Code pickup is manual; keep that local session open.