Write a recurring project status update
Keeps the same shape every time so readers can spot change, leading with what moved since the last update.
| Category | Office work › Reports |
|---|---|
| Tags | ReformattingReviewingOffice worker |
Write a project status update. Structure: 1. Changed since last update — the only section a regular reader reads closely. Lead with it. 2. Against plan — a table: milestone / planned date / current forecast / delta in days. 3. Blocked, with who can unblock it. 4. Unchanged — one collapsed line, not a list. 5. Next period. Rules: - Compare against the previous update I gave you. *If an item has said "on track" for three or more periods with no detail, flag it* — that phrasing usually means unmeasured. - Deltas in days, not adjectives. "Two weeks late" not "slightly behind". - If the current state does not tell you something the plan expects, write "not reported" rather than assuming it is fine.
After pasting, fill in the fields at the bottom (Plan · Current state · Previous update)
What this prompt does
Status reports only work when the format is stable enough to read differentially. This leads with what changed since last time, collapses unchanged items, and counts how many periods an item has sat at "on track".
More in this category
| AI Productivity Artifact Generator | |
| AI Workflow Automation Specialist | |
| Comprehensive Image Analysis Report | |
| Corporate Intel Report | |
| Developer Daily Report Generator |