Write a progress report for [PROJECT OR WORKSTREAM] covering [REPORTING PERIOD] for [AUDIENCE]. Use only the information supplied below; do not turn plans into completed work. Objectives, scope, and success measures: [OBJECTIVES AND SCOPE] Completed work and evidence: [COMPLETED WORK] In-progress work, owners, and target dates: [CURRENT WORK] Risks, blockers, dependencies, and decisions needed: [RISKS AND DECISIONS] Prior report commitments and report format: [PRIOR COMMITMENTS AND FORMAT] Begin with an overall status of Green, Yellow, or Red and give a one-sentence rationale based on scope, schedule, resources, or quality. If the inputs do not justify a status, state that explicitly rather than guessing. Separate facts from forecasts. Use exact dates where supplied; label estimates as estimates and identify their owner or dependency.
Produce this report structure: 1. Executive summary: 3 to 5 bullets, including status and the material change since the last report. 2. Progress against each objective: completed work, evidence or outcome, and remaining work. 3. Milestone table with milestone, status, owner, original date if supplied, current forecast, and next step. 4. Risks and blockers ranked by impact, each with owner, mitigation, and decision or help required. 5. Next-period plan with owner and date for every action. 6. Decisions requested, written so an executive can approve, decline, or redirect them. Keep the tone factual and concise. Do not conceal misses behind activity, assign an owner who was not provided, claim a dependency is resolved without evidence, or imply approval. Before answering, reconcile prior commitments with current status and flag any date, owner, scope, or dependency conflict. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROJECT OR WORKSTREAM] | Enter the project name or workstream being reported. | Customer onboarding redesign |
| [REPORTING PERIOD] | Enter the dates covered by this update. | September 1–14 |
| [AUDIENCE] | Enter the stakeholders receiving the report and their decision-making role. | VP Product, Head of Customer Success, and engineering leads |
| [OBJECTIVES AND SCOPE] | Enter agreed objectives, deliverables, scope boundaries, and success measures. | Reduce time to first successful import; redesign onboarding checklist and import guidance; success measure is a 15% improvement in completion rate after launch |
| [COMPLETED WORK] | Enter completed items with evidence, outcomes, or links where relevant. | Reviewed 18 support tickets; approved new checklist copy; usability-tested prototype with five existing customers; four completed the import flow without facilitator help |
| [CURRENT WORK] | Enter active work items, responsible owners, and target dates. | Nina: build checklist by Sept 25; Omar: instrument completion funnel by Sept 23; Priya: legal review of data-import language by Sept 20 |
| [RISKS AND DECISIONS] | Enter known risks, blockers, dependencies, mitigations, and requested decisions. | Legal review could delay launch; engineering has not estimated analytics work; decision needed by Sept 18 on whether to include CSV mapping in version one |
| [PRIOR COMMITMENTS AND FORMAT] | Enter last report’s commitments and any required reporting template or length. | Prior update promised prototype test and engineering estimate; one-page weekly executive update |
How to use
- Paste a reporting period with source facts, not a collection of chat excerpts or unverified verbal updates.
- Include the previous commitments so the report can show what moved, slipped, or changed in scope.
- Confirm the owner and forecast date for every next action before sending the report.
- Follow up with: “Create a 90-second verbal update that leads with the decision requested and does not add new facts.”
Variations
Executive update
Use this for leaders who need decisions and exceptions, not task detail.
Write a one-page executive project update for [PROJECT] for [PERIOD] using [STATUS FACTS], [MATERIAL CHANGES], [RISKS], and [DECISIONS NEEDED]. Start with Green, Yellow, or Red and its evidence-based rationale. Include only milestones that affect business outcome, date, budget, scope, or customer impact. Give each requested decision an owner, deadline, and consequence of delay. Do not report activity as progress or invent forecast dates. Flag unsupported status claims. Ask up to 3 questions only if a required input is missing.
Client report
Use this for a customer-facing update where commitments must be explicit.
Create a client-facing progress report for [ENGAGEMENT] covering [PERIOD] from [COMPLETED DELIVERABLES], [OPEN ITEMS], [CLIENT DEPENDENCIES], and [NEXT STEPS]. Use a professional, plain tone. Clearly distinguish work delivered, work awaiting client input, and work planned next. Include owners and dates only where supplied. State change requests, assumptions, and risks without assigning blame. Do not promise outcomes, approvals, or delivery dates that are not confirmed. Check that all commitments match the source notes. Ask up to 3 questions only if needed.
Team standup
Use this for a short internal operating update.
Turn these updates into an asynchronous team standup for [DATE]: [TEAM UPDATES], [BLOCKERS], and [TODAY’S PRIORITIES]. Produce sections for done since last update, doing next, blocked, and decisions needed. Every doing or blocked item must have one supplied owner and a concrete next step. Preserve uncertainty and use exact dates only when provided. Do not synthesize hidden work or assign responsibility. Flag duplicate ownership or unresolved dependencies. Ask up to 3 questions only if required information is missing.
Tips
- Report outcomes and evidence alongside activity; “prototype tested with five customers” is more useful than “research completed.”
- Make forecast dates distinguishable from committed dates, especially when a dependency is outside the team’s control.
- List decision requests separately so leaders can act without reading the full milestone detail.
- Carry forward prior commitments until they are completed, formally changed, or explicitly cancelled; otherwise slippage disappears from the narrative.
FAQ
Should a progress report use Green, Yellow, or Red status?
Use it only when your team has shared criteria. Pair the label with the specific schedule, scope, resource, or quality evidence behind it.
How should I report a missed date?
State the original date, current forecast if known, cause, impact, owner, and recovery action. Avoid vague wording such as “moving forward.”
Can AI estimate the new timeline?
It can help organize assumptions, but the accountable owner should provide the forecast. Do not present a model-generated estimate as a commitment.