Create a productivity report from the information below. This is an operational document, not a list of activity. Show what moved forward, what did not, who owns the next move, and when it is due. REPORT PERIOD: [REPORT PERIOD] AUDIENCE AND PURPOSE: [AUDIENCE AND PURPOSE] GOALS OR COMMITMENTS: [GOALS OR COMMITMENTS] WORK UPDATES AND EVIDENCE: [WORK UPDATES AND EVIDENCE] TEAM, OWNERS, AND CAPACITY CONSTRAINTS: [TEAM, OWNERS, AND CAPACITY CONSTRAINTS] First, ask up to 3 clarifying questions only if a required input is missing. Do not invent completion, dates, effort, savings, performance gains, or ownership.
Produce a report in this format: 1. Executive summary: 3-5 bullets covering material progress, missed or at-risk commitments, and the most important decision or dependency. 2. Goal scorecard: a table with each goal, target or definition of done, current status (on track, at risk, blocked, or complete), evidence, and variance from plan. 3. Completed work: group outcomes by goal. State the delivered result and its practical effect; exclude routine activity with no stated outcome. 4. Work in progress: for each item, list current stage, next concrete step, named owner, deadline, and dependency. 5. Blockers and decisions needed: distinguish a blocker from a risk. For each blocker, name the person or group that can remove it and the decision or input required. 6. Next-period plan: no more than 7 prioritized actions, sequenced where dependencies require it. Use direct language and preserve uncertainty. Before answering, check that every listed owner and deadline came from my input or is explicitly marked proposed, and flag any goal whose status lacks supporting evidence.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [REPORT PERIOD] | Enter the dates or week the report covers. | September 15-19, 2026 |
| [AUDIENCE AND PURPOSE] | Enter who will read the report and what decision or action it should support. | Operations director; decide which launch tasks need escalation before Monday. |
| [GOALS OR COMMITMENTS] | Enter the goals, deliverables, targets, or promises for this period. | Publish onboarding flow v2; reduce first-response backlog below 40 tickets; finalize vendor migration plan. |
| [WORK UPDATES AND EVIDENCE] | Paste status notes, metrics, meeting notes, completed work, and known issues. | Onboarding copy approved and QA passed on desktop; mobile QA found two payment-form errors. Backlog fell from 76 to 44 tickets. Vendor sent revised export spec Thursday; data mapping is 60% complete. |
| [TEAM, OWNERS, AND CAPACITY CONSTRAINTS] | List responsible people, available capacity, planned absences, and relevant limits. | Maya owns onboarding, Colin owns support operations, Priya owns migration. Engineering release window is Wednesday; Priya is out Friday. |
How to use
- Paste the period, commitments, raw updates, and names rather than writing a polished narrative first.
- Check every “complete” status against the evidence column; change unsupported claims to “in progress” or “unverified.”
- Confirm that each next action has one accountable owner and a date, especially where several teams are involved.
- Then send: “Turn the next-period plan into a Monday-to-Friday work plan with a daily checkpoint and a clear escalation trigger.”
Variations
Executive update
Use this for a short leadership readout.
Write a one-page executive productivity update for [AUDIENCE] covering [REPORT PERIOD]. Use these goals and updates: [GOALS AND UPDATES]. Include: three outcome-focused highlights, a compact scorecard of goal/status/evidence, the two largest risks, and the decisions needed from leadership. Exclude routine activity and do not claim impact without evidence. Ask up to 3 questions only if required information is absent. Before answering, flag any status that cannot be supported by the notes.
Individual review
Use this for a manager and employee check-in.
Create an individual productivity review for [PERSON] for [REPORT PERIOD] from [WORK NOTES] against [ROLE PRIORITIES]. Produce sections for delivered outcomes, work still open, priorities for the next period, support needed from the manager, and development observations grounded only in the notes. Separate facts from proposed goals. Ask up to 3 clarifying questions only if a required input is missing. Check that no performance judgment is presented as fact without an example.
Project recovery
Use this when a project is behind plan.
Prepare a project recovery report for [PROJECT] using [BASELINE PLAN], [CURRENT STATUS], and [CONSTRAINTS]. Show the missed milestone, root causes stated in the evidence, critical-path tasks, decisions required, and a revised plan with owner, due date, dependency, and recovery assumption for each action. Do not assign blame or invent causes. Ask up to 3 clarifying questions only if needed. Check that the revised dates are labeled proposed unless supplied by me.
Tips
- Report outcomes separately from effort: “migration mapping is 60% complete” is useful; “worked on migration” is not.
- Use “blocked” only when progress cannot continue without a specific external decision, access, or input; use “at risk” for work that can still proceed.
- For shared work, name one accountable owner for the next step even when several contributors are involved.
- Keep the next-period plan short enough that it reflects actual capacity, not every unfinished task.
FAQ
Should a productivity report include every task completed?
No. Include work that changed delivery, risk, cost, quality, customer experience, or a stated goal. Keep routine activity only when it explains a material constraint.
How do I report a missed deadline without making the report defensive?
State the original commitment, current state, evidence, cause if documented, and the decision or action needed next. Avoid guessing at causes or assigning blame.
Can AI assign owners and due dates?
It can propose them, but the report should label proposals clearly. Confirm accountability and dates with the people doing the work.