Weekly Operating Review Agenda and Pre-Read Template

Problem context

• Teams arrive at the meeting with different update formats and no common narrative structure.
• Leaders cannot quickly distinguish between informational updates and issues needing immediate decisions.
• Follow-through quality drops when action items are not embedded in the review artifact itself.

Template setup steps

1. Create the pre-read header: Document review date, business stream, source cutoff, and primary decisions required from leadership.
2. Insert the exception table: Capture KPI drift, blocked work, severity, owner, and recommended next action in one section.
3. Add the agenda block: Sequence discussion time by business impact so the meeting starts with the highest-risk issues.
4. Attach the action log: Reserve one section for approved actions, deadlines, owners, and next-cycle check points.

Who this is for

Useful for operators standardizing review prep across business units or functional teams.

• Managers preparing recurring weekly operating packets.
• Program leads introducing one common meeting format across teams.
• Leaders who need clear ownership for every decision and blocker.

FAQ