BlogTemplates
Project status meeting follow-up email template
A project status meeting follow-up email turns milestone changes, dependency updates and an open decision into a short message for the person who needs to respond. Use it when the update has one clear recipient and one answer to request. Keep the agreed date beside the current forecast, and give the reply deadline a date and time zone.
Short answer
- Send one recipient the part of the status update that affects their work or decision.
- Keep the agreed milestone date beside the forecast and explain the variance's calendar basis.
- Ask for one clear confirmation or decision, with a named reply deadline.
- Leave unknown status and unconfirmed decisions open; point to the source that would settle them.
What should a project status follow-up email include?
- For
- A project lead who needs one person to confirm a change or decision
- What it does
- Turns status notes into a recipient-specific recap with milestone changes, a decision request and a reply date.
- Works in
- Plain Markdown; paste into any notes or docs app
Use the Copy button on the blank email, or select it and copy. For Google Docs, open a blank document and paste; Google documents copying and pasting between files [1]. For plain text, paste without formatting and keep the labels on separate lines.
Template
Subject: [Project] status: [decision or confirmation requested] by [date and time zone]
To: [recipient name or role]
Cc: [optional; include only people who need the update]
Hi [recipient name],
Here is the project status update relevant to your work or decision.
Project and reporting period: ____________________
Meeting date: ____________________
Source note or project record: ____________________
Your recap
- What changed since the agreed plan: ____________________
- Milestone: [name / reference] | agreed date: __________ | current forecast: __________
- Variance: __________ [calendar days / working days; name the calendar if working days]
- Evidence or source reference for the change: ____________________
- Dependency: [needed input / reference] | status and evidence: ____________________
- Provider or owner and next check: ____________________
- Effect on the project if the dependency is late: ____________________
Decision or confirmation requested
- Question for you: ____________________
- Decision owner or person confirming: ____________________
- Options or facts that need confirmation: ____________________
- Recommendation, if one was stated: ____________________
- Current state: [open / confirmed / no decision recorded]
- Source reference and confirmation date, if confirmed: ____________________
Please reply by [date, time and time zone] with [the exact answer or confirmation needed].
Reason for this reply deadline: ____________________
Next step after your reply: ____________________
Next check date and owner, if agreed: ____________________
Related plan, issue or record: ____________________
Thanks,
[sender name or role]
The block is the reusable email. A recipient-specific recap means you trim the meeting record to what that person can confirm or act on; it does not mean changing the underlying project status for each reader.
Filled example
This is an original fictional example. Names, dates, records and project details below are invented. It is written to one decision owner; no real meeting or email is being reported.
Subject: Harbour billing migration: decision on partial test start by 26 October, 15:00 IST
To: Isha Menon, operations director and decision owner
Cc: Kabir Rao, project notes owner
Hi Isha,
Here is the status point that needs your decision from the 23 October review.
Project and reporting period: Harbour billing migration, 12–23 October 2026
Meeting date: 23 October 2026
Source note or project record: BILL-184 review note, 23 October; FIN-72 update
Your recap
- The reconciled test-data milestone was agreed for 22 October. Its current forecast is 28 October if a corrected finance export arrives by 26 October: a six-calendar-day variance.
- Evidence: the 22 October export checklist lists two missing tax-code fields. The cause is not confirmed.
- Dependency: corrected finance export / FIN-72. Finance has not confirmed a delivery date.
- Leena Das is checking with finance; next check is due 26 October. If the export arrives later, the two tax cases remain blocked and the forecast needs review.
Decision or confirmation requested
- Question for you: should the team start test cases that do not use the two missing tax fields, or hold the full run?
- Decision owner: Isha Menon.
- The two tax cases need the corrected export. Omar recommends starting unaffected cases while those two stay blocked.
- Current state: open; no decision was recorded in the review note.
- Source reference: BILL-184 review note, 23 October. No confirmation date yet.
Please reply by 26 October 2026, 15:00 IST with “start unaffected cases,” “hold the full run,” or another decision.
Reason for this reply deadline: Omar's proposed split-run plan is due for review that afternoon.
Next step after your reply: Omar updates the test plan; Kabir records the decision and checks the milestone forecast.
Next check: 26 October 2026, Leena to confirm the export date.
Related record: BILL-184.
Thanks,
Kabir
The forecast stays conditional, and the decision stays open until Isha replies. If the source note does not support a status sentence, leave it out or mark it unknown.
When to use this
Use this after a project status meeting when one person needs to confirm a changed forecast, report a dependency, or make a decision. It is useful when sending the full notes would bury a small request in the rest of the discussion. Keep a shared record in your project files; the broader minutes template hub is the related guide.
The layout is optional. Set the reply deadline to the time the work actually needs an answer, and say why; this template creates no response duty. Follow your team's own process for the official project record, approvals and sharing. Use a project plan or issue tracker for the full delivery schedule, not a chain of email replies.
What to customise
Use your project's terms for “milestone,” “dependency” and status. Choose calendar or working days and name the project calendar before using a working-day variance. Remove Cc, recommendations or sections that do not apply. Keep the recipient and confirmation fields when the email asks for a decision; without them, the message can look like a general update when it needs an answer. Add a source link or record ID, not a copied thread, when the reference is enough to find the evidence.
Field-by-field guidance
| Field | What to enter | Where to get it | Common mistake |
|---|---|---|---|
| Recipient and subject | Person or role who needs to act; project and exact reply request | Project roles and the decision or dependency | Sending one vague subject to people with different asks |
| Project and reporting period | Project name, meeting date and period covered | Meeting record or project update | Mixing an old update into the current period |
| Milestone and variance | Reference, agreed date, forecast and calendar basis | Baseline plan plus dated status evidence | Replacing the agreed date with the forecast |
| Dependency status | Needed input, evidence, provider or owner, next check and late effect | Dependency owner or source record | Calling something “blocked” without saying what is missing or who will check |
| Decision or confirmation | Exact question, decision owner, options, any recommendation, current state and source | Meeting record and person responsible for the decision | Writing the preferred option as if it were already agreed |
| Reply deadline | Full date, time zone, requested response and reason for timing | The next work step and the people who depend on it | Using “ASAP” or implying silence means yes |
| Next step and reference | What happens after a reply, agreed owner/date and related record | Confirmed commitments and project files | Assigning an unaccepted owner or deadline |
Keep observations separate from interpretations. “Two fields are missing from the export checklist” is an observed status; “the provider caused the delay” is a claim about cause and needs evidence. An email can ask a person to confirm the cause, but it should not quietly upgrade a guess into a fact.
Voice and AI workflow
After the meeting, dictate a short recap or map an authorised transcript to the fields above. Keep a source note ID or transcript timestamp beside each extracted claim. A transcript can show what someone said; it may not show whether a proposal was accepted. Leave unknowns open, then have a person confirm names, decisions, dates and the recipient's requested reply before sending. Do not paste confidential or identifying records into an AI service; remove those details first. See working from a transcript and recording meetings for the related workflows.
Copy this prompt with the blank template and non-confidential notes:
Write a draft project status meeting follow-up email using the supplied template.
Output type: follow-up email. Preserve these fields: recipient-specific recap;
milestone name/reference, agreed date, current forecast, variance and calendar
basis; evidence/source reference; dependency and its status, owner, next check
and effect if late; decision or confirmation requested; decision owner; options;
recommendation if stated; current state; source and confirmation date; reply
deadline with time zone and reason; next step; next check owner/date; related
record.
Use only the supplied notes. Keep unknowns unknown. Do not infer that a decision,
owner, due date or dependency date was confirmed. Keep a forecast beside the
agreed date, a recommendation separate from a recorded decision, and source
references beside the claims they support. If sources conflict, state the conflict
and ask for confirmation. Do not treat silence as agreement. Do not invent a
recipient's answer or send the email.
Remove confidential or identifying information before using this prompt. A person
must confirm every name, decision, status and due date before sending.
Questions
How can I follow up on an in-person work meeting when my notes make little sense afterwards?
Send one short email to the person who needs to act, and build it only from what your source note supports. If the note does not support a status sentence, leave it out or mark it unknown, and point to the record that would settle it.
If my boss asks about a project I'm pretty sure won't meet its deadline, what should I tell them?
Give the agreed date and the current forecast side by side. State the variance in calendar or working days, name the evidence for the change, and say what happens to the project if the dependency is late.
Does silence mean approval?
No. This template keeps a decision open until the decision owner replies, and it warns against implying that silence confirms anything. Ask for one clear answer by a named date, time and time zone, and record the confirmation date once the answer arrives.
What this page can't tell you
This email cannot verify the project record, decide who has authority, or make a reply deadline binding. Those answers come from your project process and the people involved.
About this page
Candor is being built as personal voice intelligence for everyone. You can join the Candor waitlist at candor.inc. Candor's own documentation is at candor.inc/docs.
Last checked: 4 November 2026. Report an error to support@candor.inc.
Sources
- Copy and paste text and images, Google Docs Editors Help — https://support.google.com/docs/answer/161768?hl=en — checked 2026-11-04