A meeting confirmation email should tell everyone what the group has agreed, who needs to attend, and what happens next. For a small team working with external stakeholders, that means more than announcing a time: you also need to distinguish agreement from a missing reply.
Use the examples below to confirm a settled plan, request one outstanding answer, or explain why a meeting remains tentative. All names, dates, locations, and meeting details in the examples are fictional; adapt them to your actual arrangement before sending.
Meeting confirmation email: a copyable starting template
Start with the decision, then give recipients the practical details. Here is the first of four templates, written for an internal team whose required attendees have already agreed.
Template 1: Confirm an internal team meeting
Subject: Confirmed: launch review, 12 November, 14:00 UTC
Hi team,
Thanks for confirming your availability. Our launch review will take place on 12 November, from 14:00 to 14:30 UTC, in the Cedar meeting room at our main office.
Required: Priya, Marcus, and Elena, who will make the launch decision. Optional: Noah, who can contribute support feedback in advance or join the discussion.
We will review the remaining blockers, agree on the launch decision, and assign owners to any follow-up actions. Please read the launch checklist attached to this email beforehand.
Please respond to the calendar invitation by 10 November at 16:00 UTC. If your availability has changed, reply directly to me. Noah, we will proceed if you cannot attend.
Thanks, Alex
This version separates two tasks: agreeing to the meeting time and responding to the calendar invitation. An attendee may have completed the first task in an email or conversation while still needing to complete the second.
Keep that distinction explicit. If someone has never agreed to the time, do not use this wording to imply that they have.
Check that the group has agreed before you confirm
Before writing, identify the people whose attendance the meeting actually requires. Ask whose absence would prevent the group from reaching its intended outcome. Treat everyone else as optional only after checking their role with the meeting owner.
Then choose the message that matches the evidence you have.
| Situation | Status to communicate | Appropriate next step |
|---|---|---|
| Every required attendee explicitly agreed to the chosen time | Confirmed meeting | Send the details and ask for calendar responses if necessary. |
| A required attendee has not answered the scheduling request | Tentative hold | Ask that person to confirm availability by a specific deadline. |
| A required attendee agreed by email but has not answered the calendar invitation | Agreed time, outstanding calendar reply | Request the calendar response without reopening the time. |
| Only an optional attendee has not replied | Confirmed for required attendees | Follow up individually if their answer affects preparation. |
| A required attendee reports a conflict | Unresolved scheduling decision | Discuss another time or an explicitly agreed substitute. |
A deadline tells people when you need an answer. It does not turn silence into acceptance. Decide what you will do if the deadline passes: contact the person directly, keep the hold tentative, or return to scheduling.
If the group still needs to compare options, use the process in how to schedule a meeting with multiple people before drafting a confirmation.
Worked example: turn poll responses into a confirmation
Imagine Alex needs Priya, Marcus, and Elena for a launch decision. Noah can provide optional support feedback. Alex proposes three meeting times and collects responses.
Priya and Marcus can attend the second option. Noah cannot. Elena has not replied. Alex has a promising option, but no evidence that every required attendee can attend.
Alex sends Elena a direct message: “Can you attend the launch review on 12 November, 14:00–14:30 UTC? We need your launch decision. Please reply by 10 November at 12:00 UTC; I will keep the time tentative until you answer.”
Once Elena agrees, Alex sends Template 1. Noah’s absence does not block the meeting because Alex has already established his optional role. If Elena declines, Alex returns to the options instead of announcing a confirmed meeting.
When you need to establish that shared opening, create a group scheduling poll with WhenNOT. Participants mark when they are NOT available, and the poll surfaces dates that work for everyone. Check who has answered before turning the result into a commitment; a missing response does not establish availability.
Include the date, time zone, duration and joining details
Give recipients enough information to act without searching through the earlier thread. Include these details in both the confirmation and the calendar invitation:
- Purpose: Name the decision or work the meeting will cover.
- Date: Spell out the month to avoid ambiguity.
- Time and time zone: State the start and end time, plus a clear zone.
- Duration: Make the expected commitment easy to scan.
- Joining details: Include the actual meeting link or a complete physical location.
- Attendance: Identify required and optional participants when that distinction matters.
- Preparation: Name the document to read or the information to bring.
- Response: State who needs to reply, how, and by when.
For an external guest, an internal room name alone does not provide useful directions. Add the street address, floor, reception instructions, and a contact person. For an online meeting, include the usable link rather than assuming everyone can find an earlier message.
Keep the agenda proportional to the meeting. A short decision meeting might need only three items: review the issue, choose an approach, and assign the next action. Avoid attaching a long project history when a brief summary will do.
If you still need to ask recipients for possible times, use these how to share your availability email templates. That request comes before confirmation.
Four templates for internal teams, clients, hybrid groups and attendee replies
Template 1 covers the internal team. These three additional versions handle an external client, a hybrid meeting awaiting agreement, and an attendee confirming their own attendance.
Each example uses a specific arrangement rather than empty fields. Replace the example details, attach any documents you mention, and verify the joining instructions before sending.
Template 2: Confirm a client meeting
Subject: Confirmed: project scope review, 18 November, 10:00 UTC
Hi Jordan,
Thanks for agreeing to meet on 18 November, from 10:00 to 10:45 UTC.
We will meet at your office: 24 Example Street, second-floor reception. I will ask for you when I arrive.
You and I will agree on the project scope. Casey will join as the technical lead; Morgan can attend optionally for background.
Our agenda covers the deliverables, approval responsibilities, and the first milestone. I have attached the scope summary for review.
Please respond to the calendar invitation by 16 November at 15:00 UTC. If any detail differs from your understanding, reply here and I will resolve it with you.
Best, Sam
Use this after the client agrees to the time. If you only offered the slot, change the status to proposed and ask for agreement first.
Template 3: Keep a hybrid meeting tentative
Subject: Tentative: supplier review, 20 November, 15:00 UTC
Hi everyone,
Please hold 20 November, 15:00–15:45 UTC, for our supplier review. The meeting remains tentative while we await Rowan’s availability.
Required: Rowan, Mei, and Jules. Optional: Taylor, for purchasing background.
Mei and Jules plan to meet in Cedar at the main office. Rowan and Taylor can join remotely; I will include the joining link in the final confirmation once we agree on the time.
We will compare the two proposals and agree on the next negotiation steps. Please review the comparison sheet attached here.
Rowan, please confirm whether this time works by 18 November at 12:00 UTC. Everyone else has already answered and does not need to reply again.
I will confirm the meeting or send the next scheduling step after Rowan responds. If I do not hear back, I will contact Rowan directly and keep the hold tentative.
Thanks, Alex
This message names the unresolved dependency and the next action. Before sending the final confirmation, replace the promise of a joining link with the actual link.
Template 4: Reply as an attendee
Subject: Re: Confirmed: project scope review, 18 November, 10:00 UTC
Hi Sam,
I confirm that I will attend on 18 November, from 10:00 to 10:45 UTC, at our second-floor office on 24 Example Street.
I have accepted the calendar invitation and will review the scope summary beforehand. I will bring our proposed approval responsibilities for discussion.
I can confirm only my own attendance; Casey will reply separately.
Thanks, Jordan
An attendee should confirm their own commitment unless someone has explicitly authorized them to answer for others. Avoid “We will be there” when you only know your own availability.
Handle outstanding replies without reopening every decision
Follow up with the person whose answer you need. Explain whether you need agreement to the time or simply a response to the invitation.
For an agreed time, a direct sentence works: “You confirmed 12 November at 14:00 UTC by email; please also respond to the calendar invitation by 10 November at 16:00 UTC so I can check attendance in one place.”
For an optional attendee, explain the consequence: “We will proceed at the agreed time. Please let me know whether you will join so I can include your update in the agenda.”
If a required attendee now cannot attend, address the actual conflict. Use a reschedule meeting email when the group needs a new arrangement. Do not quietly change the time and assume the earlier agreement still applies.
Check your confirmation against the calendar invitation
Read the email beside the invitation before sending. Match the date, start and end time, time zone, attendance expectations, location, and agenda. Check that the subject says either confirmed or tentative consistently.
Open the joining link, check access to preparation materials, and remove stale details from copied messages. Make sure an external attendee can understand the instructions without access to your internal chat.
Send the confirmation once the required attendees agree. If you still need that agreement, start with the scheduling step.
Ready to schedule your next group event without the headache? Find the perfect dates in minutes with WhenNOT.