Joining Instructions Template: Details and Reminders With AI

Training joining instructions should give the venue and how to reach it, start and finish times, what to bring, any pre-work, access and dietary arrangements, a named contact and a day-of phone number. AI can produce first drafts of the template and the reminder emails in an hour; your booking sheet supplies the real names, dates and room details.

Keep the two jobs apart. The AI writes wording once, with placeholders; your sheet fills them per delegate. If you let the AI invent a car park name or a start time to make a draft look finished, you will send it, and a delegate will turn up at the wrong place. These are instructions for people attending a course, not onboarding paperwork for new employees.

Follow me on Instagram@sagnikteaches

Every field a delegate needs, and the question it prevents

Most joining instructions grow by accident: one email from a past course, patched after each complaint. A better method is to start from the questions delegates actually ring about and make sure each has an answer on the page. The table below is the working list I would give a small training company, with the call each section removes.

Connect on LinkedInSagnik Bhattacharya

Notice that the last column is the real specification. When a delegate rings, log the reason in a spare column of the booking sheet for the next three courses. After a month you have a ranked list of what your instructions failed to say, which beats any generic template.

Subscribe on YouTube@sagnikteaches

A booking sheet that can feed the emails

Everything personal lives in the sheet, everything that is the same for the whole group lives in a second tab, and the AI only ever sees the placeholders. Here is a layout that works in Excel or Google Sheets.

Take a small training company running a two-day "First-Time Manager" course for 12 delegates at a hired meeting room. The delegates tab holds one row per person: booking reference, first name, surname, email, company, dietary note, access-needs flag (yes, no, replied), pre-work status and a column for each reminder sent. The course tab holds one row: course title, dates, room name, address, parking details, joining time, finish time, tutor name, day-of mobile, pre-work link and pre-work deadline. A venue change then means editing one cell, not rewriting twelve emails.

Every mail-merge tool does the same job, dropping a column value wherever a placeholder sits, but each writes its placeholders differently. Word's mail merge calls them merge fields, takes an Excel sheet or Outlook contacts as its source, and sends the emails directly from Word. Gmail has its own mail merge on eligible Google Workspace plans (Business Standard and Business Plus among them): you type @ to insert tags such as @firstname, and when you link a Google Sheet, its column headers become the tags. Mailchimp wraps tags in asterisks and pipes, so first name is *|FNAME|*. Ask the AI for plain square-bracket placeholders such as [first name], then convert them to your tool's format with one find-and-replace.

One catch with the two-tab layout: Gmail's merge reads recipient data only from the first tab of the linked sheet, so put the delegates tab first and copy the course facts (room, parking, joining time) into extra columns on it just before each send; a fill-down from the course tab takes seconds, so the course tab stays the one place you edit. Plan the same way for any tool that reads a single list. If you are still deciding which data may reach an AI tool at all, the tutorial on classifying business data before using AI tools gives a simple red, amber and green sort.

Drafting the master template with a prompt

Give the AI the structure, the tone and the fields, and ask it to leave placeholders alone. Below is a prompt I would use for the example course. It contains no delegate data, only course facts you are happy for any tool to see.

You are drafting joining instructions for a classroom training course.
Write in plain British English, friendly and brisk, no jargon.
Course: First-Time Manager, two days, 9:30 to 16:30 each day.
Use these placeholders exactly as written, in square brackets, and never replace them with real values:
[first name], [course title], [dates], [venue name], [address], [room], [parking details], [joining time], [finish time], [tutor name], [day-of mobile], [pre-work link], [pre-work deadline].
Sections, in this order: where and when; getting there; parking; what to bring; pre-work (about 90 minutes); food and drink; access needs (ask one open, neutral question and give a reply-by date of 7 days before the course); if something goes wrong.
Do not invent any venue facts, prices, distances or travel times. Where a fact is missing, write [CHECK: what is needed].
Keep it under 400 words and use short paragraphs and a few bullets.

The line about [CHECK: ...] markers matters. Models fill gaps confidently. With the instruction, gaps show up as visible flags you can search for before sending; without it they show up as plausible falsehoods. A typical illustrative result looks like this:

Subject: Your joining instructions for [course title], [dates]

Hi [first name],

We're looking forward to seeing you on [dates]. Please arrive between [joining time] and 9:30 so we can start on time; we finish at [finish time].

Where: [venue name], [address], [room]. [CHECK: which entrance and whether reception holds delegate names]

Parking: [parking details]. [CHECK: payment method and cost for a full day]

Bring: a notebook, a pen and your pre-work notes. [CHECK: is a laptop needed on day two?]

Before the day: about 90 minutes of pre-work at [pre-work link], please finished by [pre-work deadline].

Access: if there is anything that would help you take part fully, such as seating, breaks, materials in another format or a hearing loop, reply to this email by [date] and we'll sort it with the venue.

If something goes wrong on the day, ring [tutor name] on [day-of mobile].

That draft is good, and it exposes exactly what you must go and find out: the entrance, the parking cost and whether laptops are needed. Fix those in the template, not in each email.

Writing the access-needs line so people answer it

This is the paragraph most templates get wrong. "Please state any disabilities" feels like a form from a government office and gets blank replies. A neutral invitation works better: it says what you can adjust, names a deadline, and says who reads the answer. Ask the AI for three versions in different tones and then choose with a person who has attended your courses.

Three rules hold whichever you pick. First, give a reply-by date at least a week out, because a hearing loop or a ground-floor room is not always possible at short notice. Second, say where the answer goes: a named person, not a shared inbox the whole company reads. Third, never put the reply, the delegate's name and the condition into a consumer AI tool. If you want help turning one reply into a briefing note for the tutor, strip it to the adjustment needed ("seat near the door, breaks every 45 minutes") before pasting.

Dietary information follows the same rule in a lighter form. Put it in the sheet, let the venue have the list, and let the AI help only with the wording of the question ("Tell us about any allergies or dietary needs so we can pass them to the caterer").

The reminder timeline, with the job of each message

One email is rarely enough, and five is too many. For a two-day course, the sends below do the work. Each has one purpose and a subject line that says what it is.

If delegates are sent a mobile text on the evening before, check that you collected a number and consent to use it for this purpose. Many bookings capture only an email.

Prompting for the whole reminder sequence at once

Once the master template is settled, ask the AI for the later messages in the same voice, so the tone does not change between day one and day three. Paste the approved master and the timeline and say what each message is for.

Here is our approved joining-instructions email. Write three follow-ups in the same voice using the same placeholders:
1. 14 days before: nudge for pre-work and ask anyone who has not told us about access needs to reply. Maximum 80 words.
2. 3 days before: practical refresh with time, place, parking and the day-of number. Maximum 100 words.
3. Evening before: a text under 160 characters.
Never add facts that are not in the approved email. Flag any [CHECK] needed.

Illustrative result for the second message:

Subject: [course title] on [dates]: your practical details

Hi [first name], a quick refresh before we start. Arrive from [joining time] at [venue name], [room]. Parking is [parking details]. We finish at [finish time]. If anything changes on the day, ring [tutor name] on [day-of mobile]. See you there.

It is short enough to read on a phone, which is the point. Fix in the editing pass: anything beginning "Just a quick reminder" can go, and the subject should carry the date so it survives a crowded inbox.

Merging from the sheet without leaking a list

The practical routine is dull and reliable. Export or link the delegates tab, map each placeholder to its column, send one test to yourself and one to a colleague, and read both on a phone. Look for three failure shapes: an empty field that leaves "Hi ," at the top, a date column that has switched from 04/11 to 11/04 in the merge, and a field that pulled in the wrong row because the sheet was sorted after you mapped it.

Before the real send, create a dummy delegate row with your own email and an unusual name, so you can see exactly what a delegate sees. If you send through a scheduling feature, remember a late booking made after the batch runs will miss the 14-day nudge; add a rule that anyone booked inside 14 days gets the master and the practical refresh together. For the pattern of triggering messages on a timer, scheduled reminders with ChatGPT covers what scheduling can and cannot do.

Adapting the template to three course types

One template rarely fits every course. Here is how the same skeleton bends.

Open course at a hired venue

Delegates arrive as strangers from different companies. Add a line on the dress code and a note that lunch is shared, and make the parking and door instructions the most prominent parts. Late booking is common, so build the "booked inside 14 days" rule above.

In-house course at a client site

The delegates' manager is often the person who booked, and you rarely have each delegate's email. Send the joining instructions to the booker with a one-page forwardable version, and include security details the client's reception needs: whether names must be pre-registered, ID at the desk, where to leave bags. The venue section becomes a short note on who is meeting the tutor.

For that in-house course, the practical refresh might read as follows, sent to the booker to forward. It is illustrative, and the details would come from the course tab.

Subject: Thursday's team-leader course: what reception needs

Hi [first name], to help Thursday run smoothly: the tutor arrives at 8:45 and will need the training room and a screen. Delegates should have photo ID for the front desk, and names are pre-registered, so please send us the final list by Tuesday. Lunch is provided; tell us about dietary needs by the same day. The tutor's mobile on the day is [day-of mobile].

Compare that with the open-course version: the in-house one cares about the booker's actions, the open one about each delegate's journey. Same skeleton, different fields switched on.

Online instructor-led course

Drop parking and replace it with a technical checklist: browser or app, a headset, a quiet room, the test-call date, camera on or off, and what to do if the link fails. Include a phone number that is staffed in the first fifteen minutes. A short "test your link" email a week out finds most problems while there is time to fix them. Time zones deserve their own sentence: write the start time with the zone abbreviation and one converted example, never just "9:30".

Replies that say "I can't make it"

Cancellations and swaps arrive by reply, so decide the rules once and write them into the template: how late a substitute can be named, whether a fee applies inside a set number of days, and whether the delegate can move to another date. If those rules are not written down yet, drafting a training course cancellation policy with AI is the place to settle them first. An AI can then turn your policy into three short reply templates (swap accepted, transfer offered, fee applies), each with a placeholder for the date. Have a person approve every fee reply before it goes, because a wrongly applied charge costs more goodwill than the admin saves. Log each outcome in the sheet so the 3-day refresh goes to the right people.

An illustrative swap reply, drafted from a policy that allows a named substitute up to two working days before the course:

Hi [first name], thanks for letting us know. You're welcome to send a colleague in your place: just reply with their name and email by [substitute deadline] and we'll send them these joining instructions and the pre-work link. If nobody can go, we can move your place to [next course date] instead.

What to fix before it becomes a template: a first AI version of this reply might add "at no extra cost", which would be true for swaps but not for date transfers inside the fee window. Any sentence about money must match the policy word for word, so keep fee wording out of the AI's hands and paste it in from the policy.

Mistakes that look small and cost a morning

Here is a realistic one, told as an illustration. A company reused last quarter's template for a new venue, changed the address and forgot the parking paragraph. Six delegates parked in a customers-only car park and one car was clamped. The AI had nothing to do with it, but it would have caught it if asked to "list every statement in this email that depends on the venue" and compare against a venue fact sheet. Build that into your routine: run the finished email through a check prompt.

Read this email. List every statement that depends on the venue, the date or the room, one per line, so I can verify each against our venue sheet. Do not correct anything.

A second mistake is the invented detail. Ask for "directions from the station" and some models will produce confident ones. Never let an AI write travel directions; paste the venue's own text and ask it only to tidy the language. A third is pre-work that nobody can find: a link to a shared drive that needs a login delegates do not have. Open every link in a private browser window before the send.

A fourth is the over-long email. If the master runs past about 400 words, delegates skim and miss the one fact that matters. Move reference material (a venue plan, a full agenda) to an attachment or a page, and keep the email to what someone needs on the morning.

Admin minutes for twelve delegates, before and after

Illustrative sums for the example course, so you can test the idea against your own diary. Writing and merging twelve individual confirmations by hand might take three minutes each, 36 minutes in all, plus 20 minutes answering the same three questions by phone and email. Run six such courses a quarter and that is roughly five and a half hours of admin, most of it repeated typing.

With a checked template and a merge, the first build takes a week of odd hours (the five-day routine at the end), but each course afterwards takes about 15 minutes: update the course tab, send a test, press send, and scan the call log. The five and a half hours become about ninety minutes a quarter. The bigger gain is the one you cannot time: fewer people arriving flustered at ten past nine.

Checking that the instructions worked

Three numbers tell you whether the instructions are doing their job, all of which you can track in the sheet. The first is the late-arrival count per course: if two or more people in twelve arrive after the joining time, the timings or the directions are unclear. The second is the number of "where do I go" calls in the first hour. The third is the pre-work completion rate before day one. If fewer than about two-thirds complete it, the deadline or the link is the problem, not the delegates.

Sit down after each of the next three courses with the call log and edit the master template once. That is the whole maintenance cost. Reuse the same method for post-course emails; the tutorial on quizzes that show what stuck turns pre-work into evidence of learning, and reducing no-shows with AI reminders goes deeper on timing for any booking business.

If you would rather map the booking-to-course-day steps with someone, that is what my AI implementation consultation covers: finding the admin job worth automating first, and handing over a version your team can run.

A routine for the week you build it

1. Day one: list the questions delegates ring about; add a column for them to the sheet.
2. Day two: write down the fixed venue facts and verify each against the venue's own pages or a phone call.
3. Day three: build the course tab, run the master prompt, resolve every [CHECK] marker by hand.
4. Day four: draft the follow-ups, then set up the merge with a dummy delegate.
5. Day five: test on two colleagues' phones, open every link privately, and schedule the first sends.

That is a week of part-time work for a template you will reuse for years, and it replaces the per-course scramble with one cell to update.

Questions trainers ask about joining instructions

How far ahead should joining instructions go out?

Send them as soon as the booking is confirmed if the course is more than three weeks away, with a short refresh about seven days before. For a course booked inside a week, send them the same day. The point is to leave time for pre-work and for people to raise access needs.

Should I put delegate names into ChatGPT to personalise the emails?

No. Ask the AI for a template with merge fields such as [first name], then let your mail merge insert real names from the booking sheet. The AI never needs to see the list, and you avoid putting personal data into a tool you have not approved for it.

Can AI check my joining instructions for gaps?

Yes, and it is a good use. Paste the finished text with all names removed and ask it to list anything a first-time delegate would still need to ask, such as door codes, lunch arrangements or what to do if a train is late. Treat its list as prompts, not as facts.

What is the difference between joining instructions and a confirmation?

A confirmation says the place is booked and what was paid. Joining instructions say how to turn up ready: where, when, what to bring, what to do beforehand and who to call. Many companies combine them for short courses, but they do different jobs.

Do online courses need joining instructions too?

Yes. Swap the venue and parking sections for the joining link, a tested-device checklist, camera and microphone expectations and a fallback phone number. Online no-shows are often people who could not find the link, so the instructions matter as much as for a classroom.

Further reads

• How to Automate Pre-Arrival and Post-Stay Emails With AI — The same before-and-after email pattern, set up for guests.
• How to Build a Staff Training Matrix With AI — Track who has done which course across the whole team.
• How Photographers Can Handle Client Emails With AI — A client email routine you can borrow for course admin.
• AI for a Music School: Lesson Notes and Parent Emails Worked Through — Another education business turning one record into many emails.
• How to Train Employees on AI in a Clinic: Four Short Sessions — How to run short training sessions once the admin is sorted.
• Can AI Answer Student Questions for Your Online Course? — Handling the questions that still arrive after good instructions.
• Can AI Summarise Training Feedback Forms for a Client Report? — Score ratings in a spreadsheet, theme the comments with AI, and produce a one-page client summary that protects delegates' anonymity.
• Training Proposal: Scope, Price and Outcomes Written With AI — How a training company turns discovery notes into a client proposal with AI: scope, an options table, outcomes, terms and a figure check.
• AI for Corporate Training Companies: Proposals to Certificates — Proposals, joining instructions, feedback summaries, certificates, reminders and invoices: what AI drafts for a training company and what trainers keep.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Microsoft Support guide to Word mail merge, Gmail Help article on mail merge for Google Workspace, Mailchimp merge tags cheat sheet (all checked 4 November 2026).