The Scenario
A weekly status report is the deliverable a junior coordinator produces most often. Hiring managers want to see whether your reports actually communicate progress and risk, or whether they read like padding. The same project at different phases needs different emphasis.
The Brief
Pick a fictional 6-month project. Produce three weekly status reports: one in early planning (week 3), one in mid-execution (week 14), and one in pre-closure (week 24). Each report should reflect what genuinely matters at that phase.
Deliverables
- Three status reports, each one page, with consistent sections: RAG status (overall, scope, schedule, cost, quality, risk), highlights since last week, planned for next week, decisions needed, top risks, and key issues
- A short paragraph before the reports explaining what shifts in emphasis as the project moves through its lifecycle
- For at least one of the reports, explicitly model an "amber" or "red" status with a clear explanation of why and what is being done about it
- A reflection paragraph: which report was the hardest to write, and why
Submission Guidance
A status report is not a meeting agenda or a list of activities. It is an executive answer to "are we on track, and if not, what are you doing about it?" If a stakeholder cannot answer that after reading 30 seconds of your report, the report has failed.
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.