A follow-up email after a meeting is the record everyone will actually read: what was decided, what is still open, who owns each action, and when the next check-in happens. Six worked examples below cover client checkpoints, kickoffs, internal weeklies, workshops and the meeting where nobody wrote anything down — plus a builder that exports the same record as Word or PDF.
Build a follow-up email and action record from the same fields. The structured draft keeps what was decided separate from what remains open and makes every action owner and due date visible.
Guided draft builder
* marks fields required for final exports. Blank fields remain visible as placeholders in draft preview.
Same values in every output
Draft — review required
Subject: Follow-up — [Meeting title]
Hello everyone,
[Meeting summary]
[Next check-in]
[Correction or reply route]
Thanks, [Sender name]
Copy is an honest paste workflow. Downloads are real files built after server-side validation.
Before final export
Editorial examples
Six meeting shapes with invented names and dates. Confirm decisions, owners and dates with attendees before treating any recap as an agreed record.
Use when: A regular progress meeting where decisions affect scope, dates or cost.
Subject: Website launch checkpoint — 5 August: decisions and actions
Hello all,
Summary: we reviewed launch readiness and agreed the remaining approval sequence. Launch stays on 12 August.
Decisions
• Launch date remains 12 August.
• The client team owns final copy approval; we will not change copy after 8 August.
• The blog migration moves to phase two and is out of scope for launch.
Actions
• Riley — share final image assets — 7 August
• Jordan — approve launch copy — 8 August
• Morgan — confirm DNS cutover window with hosting — 8 August
Open questions
• Who owns the first-week performance report?
Blockers
• Analytics access is still pending with the client IT owner. Jordan is chasing it.
Next check-in: Friday 9 August, 10:00–10:30.
Please reply by Thursday if any decision, owner or date above is wrong; otherwise I will treat this as the agreed record.
Morgan Ellis
What to change: Keep the out-of-scope decision in writing. That single line prevents the phase-two work reappearing as a launch expectation.
Use when: The first working meeting, where the decision process itself is what you are agreeing.
Subject: Harbor & Co kickoff — agreed process, owners and first dates
Hello all,
Summary: kickoff for the Harbor & Co website launch. We agreed how decisions get made, who signs off, and the first three milestones.
Decisions
• Riley is the single point of contact on our side; Jordan on the client side.
• Two consolidated review rounds are included. Additional rounds are change requests.
• Sign-off is by written confirmation from Jordan, not verbal agreement in a call.
• Weekly status is sent Tuesday; urgent blockers go to the project channel same day.
Actions
• Jordan — confirm access owners for hosting, DNS and CMS — 7 August
• Riley — circulate the milestone plan with dates — 8 August
• Morgan — set up the shared project channel and invite both teams — 6 August
Open questions
• Is there a brand guideline document we have not seen?
Next check-in: Tuesday 12 August, 09:30–10:00.
Reply by Friday if anything here is not what you understood; I will treat it as agreed after that.
Riley Nkemelu
What to change: The sign-off decision is the most valuable line in a kickoff recap. Write it explicitly, including what does not count as sign-off.
Use when: A short recurring meeting where only changes since last week need recording.
Subject: Ops weekly — 5 August: 3 decisions, 4 actions
Team,
Summary: cleared last week’s two blockers and re-prioritised the reporting work.
Decisions
• The monthly report ships from the new pipeline in September, not August.
• We stop the manual reconciliation once the September report is verified.
• Support cover on 18–22 August is Priya.
Actions
• Sam — verify pipeline output against August manual figures — 12 August
• Priya — confirm support cover with the support lead — 7 August
• Devon — retire the old reconciliation sheet after verification — 15 August
• Morgan — update the ops calendar with the September cutover — 8 August
Blockers
• None outstanding from last week.
Next check-in: Tuesday 12 August, 09:00.
Corrections by end of Wednesday, please.
Morgan
What to change: For a recurring meeting, record only what changed. A weekly recap that repeats standing information stops being read by week three.
Use when: The session generated options rather than conclusions, and you need to record that honestly.
Hello all,
Summary: we worked through three options for the reporting rebuild. No option was selected today — the choice needs cost figures we do not yet have.
Decisions
• We will choose between options B and C only; option A is ruled out because it needs a second data source we do not own.
• The decision will be made by Priya as sponsor, at the 19 August session, with costs available beforehand.
Open questions
• Implementation cost for option B, including the vendor licence.
• Whether option C can meet the September reporting deadline.
• Who maintains the pipeline after handover.
Actions
• Sam — get written cost estimates for B and C — 14 August
• Devon — confirm whether option C can meet the September deadline — 14 August
• Morgan — circulate both estimates 48 hours before the session — 17 August
Next check-in: Tuesday 19 August, 14:00–15:30 — decision session.
Reply by Friday if you believe a decision was reached that I have listed as open.
Morgan Ellis
What to change: Record “no decision” as the outcome, with who decides and when. A recap that implies a conclusion nobody reached is worse than no recap.
Use when: The discussion was useful but nobody committed to anything specific, and you are writing the follow-up to force clarity.
Hello all,
Summary: we discussed the support backlog and agreed it needs to come down before the September release. We did not agree how, so I have written what I think we landed on and what still needs an owner.
Decisions
• The backlog target is under 40 open tickets by 1 September.
• Nothing new is added to the release scope until the target is met.
Needs an owner and a date — please claim or correct these by Thursday
• Triaging the 120 tickets older than 30 days.
• Deciding which ticket categories can be closed with a template reply.
• Reporting weekly progress against the 40-ticket target.
Open questions
• Do we need temporary support cover to hit 1 September?
Next check-in: Thursday 7 August, 16:00 — 20 minutes, owners confirmed.
If I have misrepresented the discussion, correct it in a reply rather than in the meeting; that way the record is fixed in writing.
Morgan Ellis
What to change: Publishing an unowned list with a claim-by date is the most effective use of a follow-up email. It converts a vague meeting into three named actions without another meeting.
Use when: Attendees are senior, absent stakeholders will read it, and the record may be referenced later.
Subject: Reporting programme steering — 5 August: status, decisions, escalations
Hello all,
Summary: programme status is amber. Delivery is on plan; the September deadline depends on one unresolved dependency.
Decisions
• Programme continues to plan with the current scope.
• The vendor licence decision is escalated to the finance committee on 12 August.
• Contingency: if the licence is not approved by 19 August, the September deadline moves to October and the sponsor communicates that.
Actions
• Priya — present the licence case to the finance committee — 12 August
• Sam — provide the cost breakdown for the licence case — 8 August
• Morgan — circulate the revised plan if contingency is triggered — 20 August
Escalations for this group
• Vendor licence approval is the single dependency for the September deadline.
Absent but affected: Rae Whitcombe (finance) — this record has been sent to her directly.
Next check-in: Tuesday 19 August, 11:00–12:00.
Corrections to me by Thursday 7 August, after which this stands as the programme record.
Morgan Ellis — Programme office
What to change: Name the contingency and its trigger date. A steering record without one leaves the group believing a date is safe when it is conditional.
These examples are written illustrations, not records of real customers, invoices or clients. To produce a version with your own verified details — and a real Word or PDF file rather than a copied block of text — use the builder above.
Field coverage
The builder above requires the items marked with an asterisk before it will produce a final file. This list is the reasoning behind that field model.
Method
Same day is better. Memory of who agreed to what degrades fast, and a late recap invites relitigation instead of confirmation.
“We agreed launch stays on 12 August and the client team owns final copy approval” is a useful first line. “Thanks everyone for your time” is not.
When they share a list, open questions get remembered as decisions. Two headings prevent an argument three weeks later.
Use “Riley — share final assets — 7 August”. A shared action with no date is the row that is still open at the next meeting.
A blocker recorded without somebody resolving it is just a complaint. If nobody owns it, that is itself the decision to record.
A dated correction window turns the email into an agreed record. Without it, the record is only ever “what Morgan wrote”.
Questions
Answers from the same editorial review that owns the builder. Where a question touches legal, tax or regulatory ground, the answer says so rather than guessing.
Report a correctionWithin one working day, and same-day where any action falls due before that. Recollection of who committed to what fades quickly, and a recap that arrives after the first action was due gets read as an accusation rather than a record.
A one-line purpose and outcome, decisions listed as decisions, actions with one owner and one date each, open questions kept separate, blockers with a named resolver, the next check-in with a date and time, and a correction deadline.
A recap is a short operational record of decisions, actions and open items, written to be read by everyone. Minutes are a fuller account of the discussion, sometimes required by a governing body or a constitution. If minutes are required, the recap is what you send to get the work moving while the minutes are approved.
Reply to the same thread with the correction stated plainly, and keep both the original and the correction. Silently editing a shared document destroys the value of having a record. This is why the builder includes a correction route with a deadline as a required field.
Attach them only if somebody will use them. The decisions and actions belong in the body of the email, readable without opening anything — recipients on phones and stakeholders skimming later will not open an attachment to find out what they owe you.
Record that as the outcome, then name who will decide and when. “No decision was reached; Priya decides at the 19 August session with costs available beforehand” is a genuinely useful recap. Implying a conclusion nobody reached is the failure mode to avoid.
Editorial and review record
Added six reviewed follow-up examples (client checkpoint, kickoff, internal weekly, open-decision workshop, unowned actions, steering update), decision/action separation guidance, and six reviewed answers. Field model and export behaviour are unchanged.
Confirm decisions, owners, dates, and any confidential content with attendees before treating the follow-up as an agreed record.
Sources inform field coverage and conservative boundaries. They do not certify the generated document or endorse TemplateNook.
Attendees, agenda, summaries, decisions, action owners, and deadlines.
Blockers, delivery dates, status updates, and next check-in.
Adjacent jobs
Customer recovery
Reviewedv1.1.0 · reviewed 2026-07-25
Draft a specific, accountable apology with the impact, action taken, next step, and escalation route kept visible.
Controlled operations
Reviewedv1.1.0 · reviewed 2026-07-25
Create an organization-scoped SOP covering revisions, ownership, approval, controlled copies, review, archive, and exceptions.