Genre Focus: Progress Reports


Video | Introduction | At a Glance | Project Summary | Overall Status | Deliverable Status | Issues & Risks | Sample Report | Conclusion | Sources

In this video, project management consultant Adriana Girdler walks through the four sections of a project status report, using an example from a real project.


Introduction

A progress report tells the people connected to a project how it’s going compared to the plan.

Once a proposal is approved, the work begins, and the people who approved it want to know how it’s going. A progress report answers that question at regular points along the way. Suzan Last’s Technical Writing Essentials describes it as an update to a supervisor, colleague, or client on work completed over a set period, and explains why it matters: “Whoever is paying for this project wants to know whether tasks are being completed on schedule and on budget.”

A progress report is a communication tool, but it’s also persuasive. “The main function of a progress report is persuasive,” Suzan Last writes. It reassures readers that the project is moving forward, or explains clearly why it isn’t and what you’re doing about it. Chapter 15 of Open Technical Communication adds that progress reports let you share early findings, invite feedback, and raise concerns before they turn into bigger problems.

  • Progress report or status report? The terms are often used interchangeably. When people do distinguish them, a status report is a snapshot of the project’s health right now (is it on track or at risk?), while a progress report tracks the work completed against the plan (how far along is it?). A good report answers both questions, so these notes treat them as one genre.
  • Audience: Everyone with a stake in the project, from team members who know every detail to executives and clients who see it only from a distance. Open Technical Communication advises, “Assume there will be nonspecialists reading your progress report.”
  • Format: A memo or email for readers inside an organization, a letter for readers outside it, a formal report for large projects, or a page on a shared project site. Suzan Last puts a typical memo progress report at one to four pages.
  • Frequency: Often monthly on long projects, which gives enough time for real progress between reports. A year-long project might get a report every three months.

In practice: A progress report is how a project stays visible after the excitement of approval wears off. Stakeholders who hear nothing for weeks start to assume the worst. A short, honest report keeps their trust, even when the news isn’t all good.


At a Glance

A typical progress report has four sections. Each one is explained below.

  1. Project Summary: A quick reminder of what the project is: its scope, priorities, and major milestones.
  2. Overall Status: A one-glance answer to “How’s it going?”
  3. Deliverable Status: The detail: where each deliverable stands.
  4. Issues & Risks: Problems and risks that could affect the project, and what you’re doing about them.

1. Project Summary

The project summary reminds every reader what the project is, so the rest of the report makes sense.

It always comes first. Some readers follow the project closely, but others haven’t thought about it since they approved it, and some are brand new. The summary gets everyone on the same page in a few lines. It has three parts.

▸ Scope Statement

The scope statement restates what the project is responsible for delivering.

Keep it to a sentence or two, and draw it from your proposal. If the scope has changed since the proposal, say so here.

▸ Priority Matrix

The priority matrix shows which part of the project is fixed and which parts can bend.

Every project balances three things, often called the triple constraint: scope (what the project will deliver), time (how long it will take), and cost (the budget). Adam Farag’s Essentials of Project Management explains that a change to one affects the others: adding to the scope usually costs more time or money. A priority matrix labels each one:

  • Constrain: Fixed. It can’t change.
  • Enhance: Worth improving if possible.
  • Accept: Allowed to flex if needed.

The matrix is especially useful when someone asks to “just add” one more thing. If time is your fixed constraint, it shows that new work has to come out of scope or budget somewhere else.

▸ High-Level Milestones

The milestones show what the project is delivering and when, at a glance.

List only the major ones, such as “research complete” or “draft ready for testing,” with their target dates. The detail comes later in the report.


2. Overall Status

The overall status gives a one-glance answer to “How’s the project going?”

Many organizations use a stoplight system, sometimes called RAG (red, amber, green). Amber and yellow mean the same thing. The color should match what’s really happening, so it helps to have clear definitions. North Carolina Central University’s Project Management Office ties each color to scope, schedule, and resources, and the University of Cambridge defines each color by who needs to act:

Status What it means (NCCU) Who needs to act (Cambridge)
Green “On track with no significant issues; schedule, scope, and resources are stable.” No one. “On track, no intervention required.”
Yellow “Issues exist that may affect schedule, scope, or resources; mitigation plans are in place.” You. It’s “within control of [the] Delivery Team to resolve.”
Red “Major issues threatening delivery; requires Steering Committee attention and escalation.” Someone above you. It “requires Oversight Group intervention to resolve.”

The Cambridge version gives you a simple test: if you can fix the problem yourself, it’s yellow. If you need help from the people reading the report, it’s red.

Don’t be afraid of yellow and red. A project that’s always green raises doubts, because real projects run into problems. A report that shows them, along with a plan, tells readers you understand what’s happening.

In practice: An honest yellow today is much easier to explain than a surprise red next month. Readers forgive problems. They don’t forgive learning about them too late.


3. Deliverable Status

The deliverable status section reports where each deliverable stands, and it’s the heart of the report.

Use the same deliverables and milestones from your proposal, so progress is measured against what was promised. Suzan Last gives the same advice. Briefly define each deliverable so readers don’t bring their own assumptions about what it includes.

For each deliverable, give a stoplight status and a short comment. A helpful way to write the comment comes from both Suzan Last and Open Technical Communication: say what’s completed, what’s in progress, and what’s remaining. Both textbooks also note that you can organize a report by time period or by topic, but organizing by deliverable keeps it tied to your plan.

Individual deliverables can be yellow or red while the overall project is still green. For example, a project might mark one deliverable red because qualified hires are hard to find, yet stay green overall because there’s a plan in place to address it.


4. Issues & Risks

This section covers problems and risks that could affect the project’s scope, time, or budget.

An issue is a problem that’s already happening. A risk is something that might happen. Use this section for anything that doesn’t fit neatly under a single deliverable. For each one, explain:

  • What it is and why it’s happening
  • How you’ll address it
  • What it could change, such as extra time needed or a smaller scope
  • What you need from the reader, if anything

That last point matters. NCCU’s status report template includes a section for decisions or escalations needed, which tells readers exactly how they can help. Suzan Last adds that if work is behind schedule or over budget, the report should say why and state how much more time or money is needed.

Stay factual. Suppose the timeline is at risk because team members keep getting pulled onto another project. A good report explains why it’s happening without blaming anyone, then describes the plan to fix it. Raising risks early also creates a paper trail showing that you told everyone in time.


Sample Report

Here is what a short progress report might look like for Theo’s final project.

Theo is building a new-player training guide for his campus D&D club. His report follows the four sections above.

MEMORANDUM

DATE: November 23, 2026
TO: Course Instructor
FROM: Theo
SUBJECT: Progress Report: New Player Training Guide

This report covers my progress on the New Player Training Guide since my proposal was approved. Overall status: Green. The project is on track for the Finals week due date. One deliverable is red and needs a decision from you, described under Issues and Risks.

Project Summary

Scope. A four-page Google Sites training guide for new club members: Before Your First Game, Your First Combat, Building a Character, and a 20-term glossary. Since my proposal, I moved combat to page two, because my interviews showed it is where new players struggle most. Game master duties, advanced rules, and the campaign storyline are not included.

Priorities. Time is constrained (the guide is due Finals week). Cost is constrained (free tools only). Scope is accepted: the glossary or one video can be trimmed if needed.

Milestones. Research complete (Week 13, done); full draft (Week 14); reader testing (Week 15); final guide (Finals week).

Deliverable Status

Deliverable Status Comment
Before Your First Game page Green Completed: drafted, including the dice table.
Your First Combat page and flowchart Yellow In progress: page drafted. A test reader got lost in the flowchart, so I am redrawing it with fewer branches. On track to finish by Wednesday.
Building a Character page and annotated sheet Green In progress: text half drafted. Remaining: annotate the character sheet screenshot.
Glossary Green Remaining: narrowed to the 20 terms new players ask about most. Scheduled for next week.
Two how-to videos Red In progress: the character video is recorded. The combat video has unusable audio. Decision needed (see below).

Issues and Risks

Issue: Combat video audio. The game table is too noisy to record over. I will try once more with a phone microphone during a quieter session this week. If that fails, I propose replacing the video with a step-by-step series of annotated screenshots, which still meets the five-visual requirement. Decision needed: Is this substitution acceptable?

Risk: Fewer testers over the holiday. The club does not meet during Thanksgiving week, so in-person testing may slip. To stay on schedule, I will run one online test session with two new members.

Notice that Theo’s overall status is green even though one deliverable is red. He has a plan for the problem, and he’s asked his reader for the one decision he can’t make alone.


Conclusion

A progress report keeps a project visible, honest, and on track.

It reminds readers what the project is, tells them at a glance how it’s going, shows where each deliverable stands, and flags problems while there’s still time to solve them. Suzan Last suggests closing with an overall assessment, the expected completion date, and anything that needs the reader’s help. The best progress reports don’t hide the yellows and reds. They show that the writer is paying attention, has a plan, and is keeping everyone informed.


Sources & Further Reading