River
Y CombinatorBacked by Y Combinator

For consultants reporting to a client every week

Project Status Report Generator for Clients

Paste the week's notes and emails, or drop your tracker. Get a one-page client update with honest red, amber or green, and the decisions you need.

Free to start. No card needed.

Example
Status report · Week ending 5 June
WorkstreamStatusWhy
OverallAmberGo-live on 30 June holds only if test data arrives by 12 June
Finance processesGreenProcess maps signed off by the client on 2 June
Data migrationAmberTest data a week late; the 19 June rehearsal is at risk
TrainingRedSessions on 16 June will be missed: no trainer booked

Decision needed from the client: approve the smaller pilot scope by Thursday 11 June.

What you'll get

A one-page client update with RAG status, risks and decisions needed

  • Red, amber or green overall and per workstream, each with its reason
  • Done, next, and top risks with an owner and a next step
  • Decisions needed from the client by a date, plus an email version

Before and after

Your week in. A status report you can send.

What you paste (example)

A week on a finance systems project: Tuesday's call notes, six client emails, the tracker exported from Excel, and a message saying the test data will be late again.

What you get (example)

Overall: Amber. Go-live on 30 June holds only if test data arrives by 12 June (email from Sam, 3 June). Done this week: finance process maps signed off by the client (call notes, 2 June). Top risk: test data late from client IT. Owner: Sam (client). Next step: agree a delivery date at Thursday's call. Decisions needed from the client 1. Approve the smaller pilot scope by 11 June, so training can be rebooked. Email version Subject: Week ending 5 June: Amber, one decision needed by 11 June…

Every color comes with its reason and its source, so green always means green.

Why it works

What goes in a project status report?

A project status report tells the client, on one page, whether the project is on track, what moved this week, what could go wrong and what you need from them. River builds it from the notes, emails and tracker you already keep. You get an overall red, amber or green with a one-line reason, and a status for each workstream. Below that come done and next, top risks with owners, the decisions the client needs to make by a date, and an email version.

The color has to mean something. River marks a workstream green only when your material shows progress, such as a milestone met or a task signed off. Amber means a date or the scope is at risk, and red means a milestone will be missed unless someone acts. The UK government's Infrastructure and Projects Authority ratings draw a similar line between green, where delivery "appears highly likely", and amber, where "significant issues already exist". River never invents progress or dates.

Use it at the end of each week, or on the morning the update is due. Paste your notes and the client's emails, or drop the tracker as Excel or CSV along with any meeting notes. If you'd rather fill in a fixed layout yourself, start from the weekly status report template. Client calls during the week turn into minutes with the meeting minutes generator, and the risks this report raises belong in your RAID log, where each one keeps its owner.

What lands in your doc

What's in your status report

  • An overall red, amber or green with a one-line reason that points to the evidence
  • A status for each workstream, never green without proof in your notes, emails or tracker
  • Done this week and planned next week, each line tied to the note or email behind it
  • Top risks and issues in a table, each with an owner and a clear next step
  • Decisions needed from the client, each with a by-when date and what slips if it's late
  • A short email version for your client sponsor, with the status and decisions at the top

How it works

From your week to a client update

  1. Paste the week

    Paste your notes and emails, or drop the tracker, minutes and last report, up to ten files.

  2. River checks the evidence

    It reads everything first, matching each milestone and date to where it appears before choosing a color.

  3. Get your report

    A one-page status report lands in your doc, with color reasons, risks, decisions and an email.

  4. Review and send

    Fill any placeholders, check each color against your own judgment, then send the email to your client.

How to write a weekly status report by hand

Start from evidence, not memory. Pull the week's tracker, your meeting notes and the client's emails, and list what actually finished, what slipped and what's blocked. Then set each workstream's color against rules you agreed with the client at kickoff, not against how the week felt. Complex IT projects "fail one day at a time, and generally only after numerous warning signs," note researchers writing in MIT Sloan Management Review. A weekly report is where those signs should first show.

Next, write the section your client has to act on: the decisions you need from them. Name each decision, the options if there are any, the date you need it by, and what slips if it comes late. A risk without an owner and a next step is only a worry, so give every risk both. Keep the list to the top five and move the rest to your full risk log, so the report still fits on one page.

Last, write the email. Put the overall status and the decisions needed at the top, with their dates, then two or three lines on progress, and attach the full report. Send it on the same day each week, so the client knows when to expect it and notices when it's late. Anything that needs a decision above the project team goes to the steering committee, so list it under the decisions you need, with the date you need it by.

Questions consultants ask

Common questions

What is a project status report, and what should it include?

A project status report is a one-page update that tells the client whether the project is on track and what you need from them. It gives the overall status with a reason, a status per workstream, done and next, the top risks with owners, and the decisions needed with dates. Put the status and decisions at the top, because those are what the client acts on.

How does River decide red, amber or green?

From the evidence in what you paste or drop. Green needs proof, such as a milestone met or a deliverable signed off. Amber means a date or the scope is at risk. Red means a milestone will be missed unless someone acts. Each color comes with a one-line reason that names its source, and you can change any color before you send.

What if my notes don't cover a workstream?

Then the report says "No update this week" for that workstream and leaves its status for you to confirm, rather than calling it green. Missing owners, dates and by-when dates get a bracketed placeholder and go on a short list to check before sending. River never fills a gap with progress it can't see in your material.

Can it write the weekly status update email too?

Yes. Every report ends with a short email for your client sponsor: a subject line, the status and its reason, the decisions needed with dates, and a few lines of progress. It's signed with a placeholder for your name, so you can paste it into your email, read it once more and send it.

What files can I drop in?

Up to ten files at a time: Word, PDF, text, CSV, Excel or PowerPoint. That covers most trackers, last week's report, meeting minutes and saved emails, and you can paste email threads straight into the box. Next week, add the new files to the same project space, and River can use this week's report as the starting point.

Is my client's project information private?

Your notes, emails and trackers stay in your own River space unless you share them. Under River's privacy policy, nothing uploaded is used to train AI models, and River's AI providers are bound by their agreements with River not to train on it. If your client contract limits where project information can go, check it before you upload.

Where do the full risk list and escalations go?

The status report shows only the top risks and the decisions due soon. Keep the full list of risks, assumptions, issues and dependencies in a RAID log, with an owner for each. Decisions that need a sponsor's authority belong on the steering committee agenda, and River can turn this report into a short pre-read for that meeting.

Report the week as it really went

Paste your notes or drop the tracker. Every color comes with its reason and source, so you can stand behind it on the call.