How do I show my manager what my team actually delivered this week?
Send the week's deliveries as a record list: each delivered job with its handover link, its acceptance state, and its one-line outcome, plus the exceptions (held, unresolved, slipped) in their own short section. Assembled from the records in minutes, it shows what was delivered in a form your manager can open and check.
Weekly summaries fail upward in a specific way: they are written by the person whose work they describe, in the week the work happened, from memory and optimism. Managers learn to discount them, teams learn to inflate them, and the meeting becomes theatre. The record list breaks the cycle by changing the artefact: not your account of the week, but the week's jobs, each one openable.
Assembly is a filter, not a writing task. The week's completed jobs, with links; the decisions clients recorded on them; the in-progress jobs whose state matters; and the exceptions, written plainly because the records make plainness safe: a held handover names its item, an unresolved source names itself. A manager reading this list manages from the work, asking about two exceptions instead of re-litigating ten summaries.
The habit also protects the team. Delivered work that exists as records cannot be forgotten in a review cycle or reattributed in a reorganisation; the weekly list, filed, becomes the team's own archive of what it actually did, which is a sentence most teams cannot say about last quarter.
Template: the weekly delivery list
Header: team, week, preparer. Section 1, delivered: job, client, outcome in one line, handover link, acceptance state. Section 2, decisions recorded: acceptances and holds with dates. Section 3, in progress: job, current step, expected delivery. Section 4, exceptions: held items, unresolved sources, slipped dates, each in one line with the next action. Rule: every claim in Sections 1 and 2 carries its link; Section 4 is never omitted, only ever empty.
Worked example
One row of Section 1 opens like the public record at https://zambo.dev/handover/508a46e2-8d6e-4099-bd12-7ae461c72c55 : a four-step job, readable in minutes by a manager who was nowhere near the work. A week of such rows is a report that needs no adjectives.
Frequently asked questions
My manager wants a narrative, not links. What do I send?
Both, in that order of construction: write the three-line narrative last, from the list, and attach the list beneath it. Managers who can check the narrative against the records stop asking for longer narratives.
What about work that is not client deliverables?
Internal jobs are recorded the same way and listed in their own section. The format's value is uniform: if it mattered this week, it has a record; if it has no record, its claim on the week is a sentence, labelled as such.
Does the list expose the team to micromanagement?
It exposes the work, which is what healthy management reads. In practice the list reduces check-ins, because the manager's questions get answered by the records before the meeting, and the meeting shrinks to the exceptions.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai