Weekly Roll-Up Checklist for Team Leads: What to Include Before Friday

If your team leads send weekly updates and you still can't tell where the week actually went, the problem is usually the roll-up itself — not the people writing it.

Definition: weekly roll-up

A weekly roll-up is a short, structured summary a team lead sends at the end of the week. It covers what was planned, what actually happened, what is blocked, and what is coming next.

Definition: plan vs fact vs gap

Plan vs fact vs gap is a three-line comparison: what the team said they would do, what they actually did, and the difference between the two. It turns vague updates into visible operational signals.

What a Weekly Roll-Up Should Actually Contain

Team leads often treat the weekly roll-up as a status meeting in text form. It should not be. The goal is to give the owner or COO enough signal to decide whether to intervene, wait, or reassign — without scheduling a call.

Every weekly roll-up needs four blocks:

1. Plan vs fact. Three to five priorities from last week, marked done, in progress, or moved. If a priority moved, say why — one sentence, no drama.
2. Blockers and risks. Anything that stopped progress or could stop it next week. Include who is waiting and what decision is needed.
3. Decisions needed from above. Explicit asks: budget, headcount, vendor approval, priority change. Do not bury them in paragraph three.
4. Next week's top three. Not a wish list. Three outcomes the team commits to, with owner names.

That is it. If the roll-up runs longer than one screen, it is becoming a status meeting.

How to Write It in Under 10 Minutes

Most team leads overthink the weekly roll-up because they try to narrate the whole week. Do not narrate. Summarize.

1. Open last week's roll-up. Copy the "next week" block into this week's "plan" block.
2. Mark each item: shipped, moved, or blocked.
3. Add new blockers and decisions needed.
4. Write next week's top three.
5. Send it at the same time every Friday.

Consistency matters more than polish. An owner who receives the same shape of update every week stops reading for entertainment and starts reading for exceptions.

Tool tip (AiAdvisoryBoard.me): A weekly roll-up is where the Plan → Fact → Gap logic becomes visible to the owner. If you want that surface automatically across the company — every day, not just Friday — see how the 7-day diagnostic works.

Good vs Bad: Weekly Roll-Up Examples

Bad: "This week was busy. We worked on the client migration, fixed some bugs, and talked to the design team. The API is mostly done. Next week we hope to finish testing."

Good:

• Plan vs fact: Client migration — done (3 of 3 environments). Bug fixes — moved 2 to next week (waiting on QA access). API — done.
• Blockers: QA access for staging environment. Waiting on IT approval since Tuesday.
• Decisions needed: Approve QA sandbox budget ($200/mo) by Monday.
• Next week: Complete regression testing (owner: lead engineer), schedule client walkthrough (owner: PM).

Manager Scan: What the Owner Should See in 60 Seconds

When the weekly roll-up lands in the owner's inbox, they should not have to hunt for signal. Here is what a 2-minute digest looks like:

• Team lead name and function.
• Plan vs fact: 3 priorities, status emoji or word (done / moved / blocked).
• One blocker line: what is stuck and who can unblock it.
• One decision line: what the owner needs to say yes or no to.
• Next week's top three outcomes.

If the team lead cannot fill this in five minutes, the team's priorities are probably not clear enough yet.

Micro-Case: What Changes After Two Weeks

A services company with about 60 people started requiring team leads to send a weekly roll-up using the four-block format. Before that, the founder learned about delays during Monday meetings, when it was already too late to adjust. After two weeks of roll-ups, the founder spotted a recurring QA bottleneck on Wednesday instead of Friday. The team lead had written it in the blockers block, and the founder approved a contractor the same day. The client deadline moved from next week to the week after — without a fire drill.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

FAQ

Who should write the weekly roll-up — the team lead or the manager? The team lead writes it. The manager reads it and decides whether to escalate, unblock, or leave it alone. If the manager writes it, the team lead stops owning the signal.

What if nothing shipped this week? Say so explicitly. "No shipping this week" is valid information if it is paired with why and what is unblocking next week. Silence is worse than a slow week.

Can we use AI to summarize the roll-ups? AI can help draft or summarize, but the team lead must own the plan vs fact judgment. An AI summary without human context tends to hide the gap.

How is this different from a daily report? Daily reports track today's work. Weekly roll-ups track whether the week's priorities actually happened. They answer different questions.

Should the whole company see these? Usually no. Weekly roll-ups go from team leads to the owner or COO. If you want cross-team visibility, aggregate them into a leadership digest — do not make every team read every other team's roll-up.

Internal Links

Pair the weekly roll-up with a Friday shutdown ritual so the team lead starts the next week with clear priorities: Friday Shutdown Ritual That Sets Up Next Week's Plan. For frontline staff who never sit at a desk, use a written check-in format that feeds into the team lead's roll-up: Written Check-In for Frontline Shift Staff Who Never Sit at a Desk. If roll-ups reveal recurring AI-project failures, diagnose the pattern: Signs of a corporate AI program that actually leaves results in your company.

A weekly roll-up is not bureaucracy. It is the cheapest way for an owner to see plan vs fact across the company without adding another meeting. Pick one team lead, run the four-block format for two weeks, and decide whether to scale it.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works: https://aiadvisoryboard.me/?lang=en