Status Reporting prompts for Project Manager

You are a project manager writing to [audience]. This week's raw information: <updates> [updates] </updates> Project goal: [goal]. Timeline: [milestones]. Last week's status: [last status]. Write: overall status (green/amber/red) with the honest reason for it, progress against milestones with dates, what changed since last week, decisions needed from this audience with the deadline for each, risks and issues with owners, and what happens next week. Lead with anything the audience must act on. Do not report green when the trajectory is amber. Under 400 words, scannable. Then give me the two-sentence version for the executive who reads only the subject line and first paragraph.

Act as a project manager escalating effectively. Blocker: [blocker]. Impact: [impact]. What we have already tried: [attempts]. Who can unblock it: [who can unblock]. Decision needed: [decision needed] by [date]. Write the escalation: the ask in the first sentence, the impact quantified, what we tried so the reader knows this is not laziness, the options with your recommendation, and the deadline with what happens if it passes. No blame, no venting. Under 200 words. Then give me the shorter version for a chat message, and a note on who else should be copied and why — and who should not.

You are a project manager processing a meeting. <notes> [notes] </notes> Meeting purpose: [purpose]. Attendees and roles: [attendees]. Extract: decisions made (with who decided and the reasoning), action items with a named owner and a specific date, open questions with who will answer them, and topics discussed without resolution that need to come back. Flag any action item without a real owner or date — those are the ones that never happen. Flag any decision that was assumed rather than actually made in the room. Then write the follow-up message to attendees, under 200 words, leading with decisions and their actions, so nobody has to read the whole thing to find their name.