Weekly project status report
An 8-slide weekly status deck made from a written report for an invented customer portal migration. GenPPT made all 8 slides. The prompt is on this page.
Why this deck works
- The first slide gives the project, the week, and the overall status.
- Each status is a colour and a word. A reader who cannot tell red from green can read the word.
- Each risk has an effect, an owner, and an action.
- The last slide lists two decisions. Each decision has a person and a date.
The prompt that made it
GenPPT prompt
Turn this weekly status report into an 8-slide project status deck for the sponsor. Slide order: 1 title with the reporting period and the overall status, 2 executive summary, 3 RAG dashboard, 4 progress since the last report, 5 plan for next week, 6 risks and blockers, 7 key dates, 8 decisions needed. Rules: write each slide title as a full sentence that states the conclusion. Show each status as a colour and a word. One idea per slide. Style: plain and businesslike, white background, dark grey text, and red, amber, and green only for status. No logos. Customer portal migration weekly status: AMBER, week ending Oct 2 Overall status: AMBER Summary: Data migration finished two days early. The payment vendor's sandbox API is two weeks late, but go-live on Nov 16 holds if it arrives by Oct 12. We need two decisions from you by Oct 9. Status by area Schedule: AMBER - integration test may start 1 week late Scope: AMBER - CR-14 (single sign-on) waits for approval Budget: GREEN - $184,000 spent of $200,000 planned to date Risk: AMBER - one vendor dependency on the critical path Done this week - Migrated all customer records with 0 failed validations - Finished the account settings pages (design and build) - Signed off the cutover runbook with IT operations Planned next week - Start the billing page build - Luis - Oct 5 - Security review of the login flow - Priya - Oct 8 - Vendor API delivery checkpoint - Dana - Oct 9 Blockers and risks - Vendor sandbox API is late. Impact: integration test start slips from Oct 19 to Oct 26. Owner: Dana. Mitigation: build against a mock API from Oct 5. - CR-14 is not approved. Impact: 6 days of work with no slot in the plan. Owner: sponsor. Decisions needed - Approve or reject CR-14 (single sign-on) - sponsor - by Oct 9 - Approve one contractor for 3 weeks of test automation - steering committee - by Oct 9 Key dates - Integration test start: Oct 19 (at risk) - User acceptance testing: Nov 2 (on track) - Go-live: Nov 16 (on track)
The report in this prompt is from the project status report template.
1 message after the prompt
- Slides 2, 3, 5, and 7 use the deck title as the headline. Give each slide a full-sentence headline and keep the design. Slide 2: "Go-live holds for Nov 16 if the vendor API arrives by Oct 12." Slide 3: "Budget is green. Schedule, scope, and risk are amber." Slide 5: "Billing pages and the security review start next week." Slide 7: "Go-live on Nov 16 is on track, and the integration test start is at risk."
All 8 slides
1. Title and overall status 
2. Executive summary 
3. RAG dashboard 
4. Progress this week 
5. Plan for next week 
6. Risks and blockers 
7. Key dates 
8. Decisions needed