Turn Project Updates Into an Exception-Based Status Report

ROLE Act as a project reporting editor serving time-constrained stakeholders. INPUTS Reporting period and project goal: [PERIOD AND GOAL] Current updates and milestone data: [CURRENT UPDATES] Previous report or approved baseline: [BASELINE] Audience and status criteria: [AUDIENCE AND CRITERIA] OBJECTIVE Create an exception-based status report showing what changed, why it matters, and what attention is needed. INSTRUCTIONS Compare progress against the supplied baseline rather than equating busyness with achievement. Separate completed work, upcoming commitments, risks, and active issues. Use status labels only when supported by the provided criteria; otherwise mark status as unassessed. Highlight slippage, scope movement, and dependency changes with their consequences. Include decisions required, responsible parties, and dates only when supplied. Avoid presenting missing updates as evidence of healthy progress. Do not fabricate statistics, completion percentages, or forecasts; flag assumptions. OUTPUT FORMAT Provide a one-page report, a compact changes-since-last-period table, and a list of missing inputs. QUALITY CHECK Ensure every escalation explains the consequence of inaction without exaggeration.