Weekly team meeting follow-up email template

Subject: Weekly follow-up: [team or workstream], [meeting date]

To: [recipient or group with the same follow-up]
From: [sender and team]
Meeting: [team, date and time zone]
Source record: [accessible minutes, notes or tracker reference]

Hi [recipient or group],

Your recap: [what changed or remains open that matters to this recipient,
with a source reference beside each factual point]

Last-week commitment: [commitment, source, original owner and due date]
Current position: [status and evidence; any proposed or agreed change,
labelled separately; write "Unknown" where the record does not establish it]

Cross-team dependency: [input needed, providing team and receiving team]
Needed by: [requested date and time zone, with source]
Provider's confirmed delivery date: [date and source, or "Unknown"]
Dependency status and evidence: [current position and reference]

Escalation requested: [issue and evidence; specific decision or help sought;
person asked; status such as "to raise", "raised" or "response received"]

Please confirm or correct: [one question this recipient can answer]
Reply by: [requested date, time and time zone]
Why this reply date matters: [the next handoff or decision that waits on it]
Where to reply: [this email or an accessible shared record]

After your reply: [what the sender plans to update or do next]
If there is no reply: [sender's planned next check; keep acceptance pending]

Please flag any correction with its source. A proposed change remains
pending until the people responsible agree to it.

Thanks,
[sender]

Subject: Weekly follow-up: Marlow dispatch, 23 October 2026

To: Nora Bell, Purchasing lead
From: Eli Mercer, Dispatch
Meeting: Marlow dispatch, 23 October 2026, IST (UTC+05:30)
Source record: MR-16 action 4; MR-23 items 2 and 3; PO-58 update

Hi Nora,

Your recap: Dispatch's booking plan remains open while Purchasing checks
the replacement pump shipment. PO-58 has no confirmed arrival date.

Last-week commitment: Samir Patel to finalise next week's repair booking
slots by 22 October 2026, MR-16 action 4.
Current position: Incomplete. MR-23 item 2 records that the slots depend on
the pump shipment. Samir proposed 27 October as a revised completion date;
the notes record no agreement to that change. Original due date: 22 October.

Cross-team dependency: Purchasing to provide Dispatch with the replacement
pumps listed in PO-58.
Needed by: 28 October 2026, noon IST, per MR-23 item 2.
Provider's confirmed delivery date: Unknown.
Dependency status and evidence: PO-58 says the supplier is checking stock;
it records no delivery commitment.

Escalation requested: MR-23 item 3 asks the Purchasing lead to decide
whether to request a partial shipment of available pumps. This email raises
that request to you. Response pending; no shipment change is recorded.

Please confirm or correct: Which delivery date, if any, can Dispatch use
for the pumps in PO-58? If none is confirmed, please say "Unknown".
Reply by: 26 October 2026, 3:00 pm IST, if possible.
Why this reply date matters: Dispatch plans to review the booking slots
on 27 October at 10:00 am IST, per MR-23 item 2.
Where to reply: This email, or update PO-58 and send its reference.

After your reply: I'll update MR-23 and send Samir the confirmed position.
If there is no reply: I'll check with you at 9:00 am IST on 27 October and
leave the delivery date unknown in the booking review.

Please flag any correction with its source. Samir remains the owner of
the booking plan; the proposed new date is still pending.

Thanks,
Eli

Draft one weekly team meeting follow-up email in Markdown using the supplied
blank template. Keep its field order. Write for the stated recipient or a
group with the same follow-up; omit unrelated discussion.

Fill the subject, recipient, sender and meeting reference. Give a
recipient-specific recap with evidence references. Carry last-week
commitments with their original owner and due date, current evidence and
status, and separately labelled proposed or agreed changes. For each
cross-team dependency, name the input and both teams; distinguish the
requested need-by date from the provider's confirmed delivery date. Include
the dependency status and source. For an escalation requested, state the
issue and evidence, exact help sought, person asked and response state.

Include one confirmation question, the requested reply deadline with time
zone, why that reply time matters, where to reply, the sender's planned
next step after a reply, and the planned next check if there is no reply.
Use only plans supplied in the input; do not invent follow-up dates.

Write "Unknown" for missing facts. Preserve evidence labels or transcript
timestamps beside each factual point. Flag conflicting sources for human
review. Do not infer acceptance, completion or an agreed date from a request
or from silence. Omit inapplicable dependency or escalation sections only
when the input establishes that they do not apply.

Before using this tool, remove confidential or identifying data, including
revealing links; use temporary labels if needed. Do not attempt to restore
identities. A person must restore permitted names and references and confirm
every name, decision and due date, plus each factual claim and proposed plan,
before sending.

Blank template and authorised material follow: