How do I recap a verbal work agreement in writing?
Quick answer
Send a brief email soon after the conversation. State the agreed outcome, each person’s responsibilities, deadlines or check-in dates, and any open questions. Use neutral wording, distinguish confirmed decisions from your understanding, and invite corrections. Don’t treat silence as agreement. If an unresolved decision affects what happens next, ask for a direct answer before proceeding with that part of the work.
The question, the details, the next step.
What should I include in a recap after a verbal agreement at work? We talked through a change to a project, but I want a written record without making it sound like I distrust anyone.
Treat the email as a shared memory aid, not a record of blame. Include four things: the outcome you understood, who is doing each part, when it is due or reviewed, and what remains undecided. Keep it short enough that the other person can quickly confirm or correct it.
A useful opening is: “Thanks for talking this through today. I’m writing down my understanding so we can work from the same plan.” That explains the purpose without suggesting the other person needs to defend themselves. If the agreement affects other colleagues, name their responsibilities only if those were actually discussed.
How do I make sure I don’t accidentally turn an assumption into an agreement? For example, we discussed moving a draft review, but I’m not certain whether the final delivery date changed too.
Separate what was clearly agreed from what you still need to confirm. Don’t write “We agreed the delivery date is Friday” unless that was explicit. Instead, record the review change and ask about delivery:
“Confirmed: I’ll send the draft for review on Tuesday instead of Monday. I understood that the final delivery date remains Friday, but we didn’t confirm that during our conversation. Could you let me know whether Friday still works?”
If you are unsure whether even the review date was settled, label it as your understanding: “My understanding is that I’ll send the draft Tuesday; please correct me if I’ve got that wrong.” This makes uncertainty visible rather than burying it in confident wording.
Can you show me a complete example with owners, timing, and an open question? Assume this is a routine project discussion, not a formal contract.
Here is a copyable example using placeholders. Replace them with what was actually discussed; don’t leave a responsibility or deadline in the message merely because it sounds plausible.
Subject: Recap: [project or task] plan
Hi [name],
Thanks for discussing [task] today. I’m writing down my understanding so we can work from the same plan:
- Outcome: We’ll use [agreed approach] for [part of the work].
- Responsibilities: I’ll [your task]. You’ll [other person’s task], as discussed.
- Timing: I’ll send [item] by [date or time]. We’ll review [milestone] on [date], if that timing is confirmed.
- Open question: We haven’t settled [specific point]. Could you confirm [the decision needed]?
Please correct anything I’ve missed or misunderstood. I’ll proceed with the confirmed items and wait for your answer before acting on [item that depends on the open question].
Thanks, [your name]
Keep “if that timing is confirmed” only if the date is genuinely tentative. If it was clearly agreed, state it plainly. Make your request specific to the unresolved item rather than asking for blanket approval.
What if they don’t reply, or they correct one detail? I don’t want to imply silence means they agreed.
Don’t describe silence as agreement. If a detail needs a decision before work can continue, follow up with a short, focused question and say what you’ll do meanwhile only if that interim plan is appropriate and understood. For example: “I’m checking whether Friday is still the delivery date. Please let me know by [date] so I can plan the next step.”
If they correct the recap, acknowledge the correction and send back the revised point, especially if it changes an owner, deadline, or outcome. You can write: “Thanks for clarifying. I’ve updated my notes: [corrected detail]. The remaining open item is [question].” Keep the original message and the correction together in the project thread so the record is easy to follow.
A practical checklist
Send the recap while the conversation is still easy to remember.
State the outcome in plain language and distinguish confirmed points from your understanding.
Name each owner and task only as actually discussed.
Record agreed deadlines, review dates, or milestones; label tentative timing clearly.
List unresolved questions separately and ask for the specific confirmation needed.
Invite corrections neutrally, then update the thread if an important detail changes.
A few more useful answers
Should I ask the other person to confirm every line?
Usually, ask them to correct anything missing or misunderstood, and request a direct answer to unresolved decisions. For a simple recap, a blanket approval request can create unnecessary friction.
What if the verbal discussion was too vague to recap confidently?
Write down the points you do understand and identify the uncertain ones as questions. Ask for a short follow-up conversation if the missing detail affects who does the work, what outcome is expected, or when it is due.
Should I copy other colleagues on the recap?
Include people who need the information to carry out or coordinate the agreed work. Avoid adding recipients just to apply pressure; if unsure, ask the participants who should be kept informed.