Junior Communications: writing reminders, invitations and follow-ups from templates

As a junior coordinator you're not paid to change the company brand's tone of voice: you're paid to produce invitations, reminders and follow-ups starting from predefined templates and to measure send-out (number sent, bounce rate) without yet pretending to analyze engagement. This guide teaches you to calibrate the cadence of pre-event communications, to handle the audience's inbound feedback, and to recognize which communications require the senior's approval before sending. Three case studies (GitLab async handbook, Stripe Sessions promo cadence, Bending Spoons all-hands).

TL;DR

The event's internal communications are the most seemingly simple skill at the L1 level and the one where the traps are the most subtle: the company template modified without sign-off, the reminder cadence that's too aggressive (spam) or too bland (people forget), the send-out metric mistaken for engagement, the missing senior approval when the communication touches a sensitive topic. The good news for the junior is that at the L1 level the decision-making perimeter is very limited: you apply standard templates, you respect pre-defined cadences, you measure technical metrics (delivered, bounce, open rate if available) without interpreting them. The three things that separate an L1 junior who grows from one who burns out are: the discipline to NOT personalize the template without sign-off (even if 'my copy would be better'), the standard 4-touchpoint cadence (save-the-date, formal invitation, T-7 reminder, T-1 reminder), and the sensitivity to recognize when an inbound message from the audience (e.g. a request to change the time, a flagged calendar conflict) requires escalation to the senior. You'll also find three case studies (GitLab Handbook async + writing culture, Stripe Sessions promo, Bending Spoons all-hands), three anti-patterns (unauthorized template-rewriting, misaligned cadence, send-out mistaken for engagement) and an Event Brief 1-pager template where the audience section is the basis of communications distribution.

When you need it / Prerequisites

This guide is applicable from the moment you have the validated brief (with a defined target audience) and you need to start communicating with participants for the invitation and the pre-event reminders. The typical case is a single-BU event of 50-150 participants where you are the junior responsible for the operational communications, the senior provides coverage only on messages that touch sensitive topics (e.g. the BU sponsor's send-out, cross-functional communications to adjacent teams), and you have to manage 3-5 touchpoints via email/Slack/Teams in the month before the event, collect inbound feedback, and do the post-event follow-up.

There are four prerequisites. First: the event brief is validated and includes the audience section with concrete numbers (e.g. 80 participants, engineering team of the Product BU, mid-senior levels). Without a defined audience, the communications start out too generic. Second: you have the actual distribution list - an Excel sheet or an export from your intranet with name, email, role, team. For a single-BU event the list is provided by the HR lead or the BU sponsor. Third: you have access to a company email-sending tool (Mailchimp, ActiveCampaign, or Outlook with an internal mailing list) or to an internal newsletter platform. For small events (under 30 participants) Outlook with BCC may be enough; above 30 you need a tool with tracking. Fourth: you have the team's standard communications templates or the brand guidelines.

What is not a prerequisite at the L1 level is the ability to write original content in the brand's tone of voice. That ability is built up over 12-18 months of exposure to the brand through reading, feedback from the marketing/comms team, and iterative writing with review. At the L1 level the company templates EXIST TO BE USED: your job is to apply them, not to rewrite them. The difference between a good junior and a junior who burns out on this point is stark: the good one accepts the discipline of the template, the second one personalizes it thinking he's improving it and ends up producing off-brand communications that the senior has to correct after the fact.

If one of the prerequisites is missing, stop. Without standard templates you'll write communications the senior will have to rewrite; without a defined audience you send everyone the same thing; without a tool with tracking you don't know how many emails actually arrived. The cost of fixing this now is a few hours; the cost of proceeding without is weeks of re-work.

Conceptual framework: send-out as an L1 metric, engagement as an L2 metric

The framework that guides the event's communications distinguishes two levels of measurement. Send-out (L1 level, junior) is the technical measure of distribution: how many emails sent, how many delivered, how many bounced, how many opened if the tool tells us (open rate). Engagement (L2-L3 level, mid-senior) is the behavioral measure: how many click-throughs to links, how many RSVPs, how many registrants actually attend, how much the audience's sentiment shifts after the communications.

The junior measures send-out because it's technically verifiable and requires no interpretation: the email went out or it didn't, it arrived or it bounced. Engagement already requires interpretation (what does it mean that the open rate is 35% - good, normal, poor?) and that interpretation is the responsibility of the mid or senior. The junior who pretends to interpret engagement as a beginner risks producing false-positive reports (e.g. high open rate, great engagement when in reality a high open rate only means the subject line was good).

The operational framework is anchored to the writing culture codified by GitLab Handbook - Communication: every important communication is written, every email has a clear subject line (imperative verb or specific number), every message has an explicit requested action. For the junior this means: no event email goes out with a vague subject like Event update; the correct subject is RSVP by Friday 24/05 - Engineering BU event on 06/06. Specific number + verb + deadline + event name. Four elements, in four key words. Everything else lives in the body.

The operational principle that guides the cadence of reminders is the 4-touchpoint rule: for a single-BU event of 50-150 participants with 3-4 weeks of preparation, the optimal sequence is (1) save-the-date 3-4 weeks before, (2) formal invitation 2 weeks before with an RSVP deadline, (3) T-7 reminder for those who confirmed + final RSVP call, (4) T-1 reminder with practical instructions (time, location, parking, dress code, any technical requirements for a hybrid event). This cadence is consistently cited by Cvent Blog, PCMA Convene and MPI as a baseline for medium corporate events.

Under 30 participants the cadence compresses to 3-touchpoint (save-the-date + invitation + T-1 reminder); above 200 participants it extends to 5-6-touchpoint with dripping of special content (e.g. meet the speaker, agenda preview, 48-hour countdown). For the junior just starting out, the 4-touchpoint rule is the safe baseline - any other variation should be agreed with the senior.

The final principle is minimum segmentation: at the L1 level you don't do strategic audience segmentation (that's an L2-L3 marketing task). You only do minimum operational segmentation when it makes sense: confirmed vs unconfirmed (at the T-7 reminder you send two different emails), speakers vs participants (speakers receive additional info on presentation preparation), internal vs external (external guests receive practical info on how to reach the venue, internal ones don't). Everything else is strategic segmentation and should be agreed with the senior.

Operational steps: five steps to manage the event's communications

The five steps cover from the first save-the-date to the post-event follow-up. Timings indicated for an event of 50-150 participants with 3-4 weeks of preparation.

Step 1 - Save-the-date (T-21 to T-28 days)

The save-the-date is the first communication of the cycle. Purpose: block the date in the target audience's calendars before they fill them with other commitments. Minimum format: 4-6 lines with date, time, location (even generic if not confirmed), event title, target audience, link to add to calendar. No detailed agenda (there isn't one yet), no RSVP request (you'll ask for it with the formal invitation two weeks later), no commercial call-to-action.

The company template for the save-the-date typically already exists. If it doesn't, ask the senior or the marketing/comms team. The operational rule: apply the template, replace only the variables (date, location, title), don't touch the base copy. Subject line: Save the date | [Event name] | [Date]. Four elements separated by pipes, all in plain sight for whoever scans the inbox in 2 seconds.

On the save-the-date distribution list: at the L1 level you send to the complete target audience, without segmentation. For a single-BU event of 80 people, you send to all 80 even if you know that 5-10 won't be able to attend due to planned holidays or other commitments. The rule: better a clean over-send than cherry-picking. The save-the-date is also an act of political transparency - telling everyone the event exists avoids exclusions being interpreted as slights.

Three practical rules of the save-the-date. First: always send from the official company channel (Mailchimp, ActiveCampaign or Outlook with an institutional signature), never from your personal email account. Second: the save-the-date always includes an add to calendar link that generates an .ics file - modern email tools support it natively. Third: set a monitored reply-to - if someone replies to the save-the-date (typically sorry, I'm on holiday that week, can I attend remotely?) someone has to read and reply within 24 hours. The junior does the triage and escalates to the senior only requests above their own autonomy.

Step 2 - Formal invitation + RSVP (T-14 to T-12 days)

The formal invitation is the second communication of the cycle, and the most important one because it contains the detailed agenda, the confirmed speakers, the precise location, the practical instructions. Typical format: 8-12 lines + agenda as a bullet list + RSVP link with an explicit deadline. Total length: 1 mobile screen (under 200 words) - above 250 words readership drops drastically.

The company template for the formal invitation typically exists and has 5-7 placeholders to fill (date, time, location, agenda, speakers, RSVP link, contact reference). The operational rule for the junior: fill all the placeholders with concrete information; if a placeholder is still TBD (e.g. the keynote speaker hasn't confirmed yet), do NOT send the official invitation - send a second update save-the-date with the warning final agenda coming soon, and send the real formal invitation only when you have all the pieces.

On the RSVP, two practical rules. First: an explicit deadline, typically 5-7 days before the event. Example: for an event on 06/06, RSVP deadline 30/05 at 17:00. Second: an RSVP link that opens a simple form (max 3 fields: name, yes/no confirmation, any special requests such as intolerances or accessibility). Long forms (10+ fields) have drastically lower completion rates - a figure from Mailchimp benchmarks shows that every additional field reduces the completion rate by 6-8%.

The subject line of the formal invitation is critical. A pattern that works: RSVP by [date] | [Event name] | [Event date]. Real examples: RSVP by 30/05 | Engineering All-Hands BU Product | 06/06. The imperative verb (RSVP) activates the reader's mental action; the deadline in the subject suppresses the I'll do it later; the event name allows quick triage in the inbox.

Another operational rule: the formal invitation is the communication that the senior signs. Literally: the email goes out with the senior's signature (e.g. Maria Rossi, Senior Event Coordinator) and the junior in copy for the replies. This setup has two effects: it gives political authority to the communication (invitations signed by the senior have a measurably higher RSVP rate), and it protects the junior from slippery political decisions. If someone replies to the invitation with a complicated question (e.g. why isn't team X invited?), the junior forwards it to the senior without having to answer it themselves.

Step 3 - T-7 reminder + final RSVP call (T-7 days)

At 7 days before the event the first reminder goes out. The format differs depending on the recipient. For those who have already confirmed their RSVP: a reminder with practical details (time, location, parking, dress code), a link to add to the calendar if they hadn't done so, a contact reference for last-minute questions. For those who haven't replied yet: a final RSVP call with an explicit deadline (e.g. RSVP by Friday 30/05 at 17:00, after which we won't be able to include you). For those who declined: no communication (don't bother people who already said no).

This is the first minimum segmentation of the cycle: three groups (confirmed, non-responders, decliners) that receive three different communications (or none). For an event of 80 participants you typically have, at T-7, 50-60 confirmed, 15-25 non-responders, 5-10 decliners. The percentages are in line with the Cvent Blog benchmarks on corporate RSVP rates (60-75% at T-7 for internal BU events).

On the reminder's copy, a rule that works is the single requested action principle: the reminder has ONE main call-to-action, not four. If the recipient is confirmed, the action is add to your calendar if you haven't. If they're a non-responder, the action is confirm or decline by Friday. If they declined, no action, no email. Mixing actions (e.g. confirm + add to calendar + read the agenda preview) dilutes attention and lowers the completion rate.

The same cadence/segmentation mechanism also applies to the company's internal Slack/Teams channel. If the event has a dedicated channel (#event-bu-engineering-2026-06), the junior posts the three respective messages in the channel on the same day as the email reminder. Cross-channel coordination: same copy, same day, two channels. The audience receives the message in the channel it uses most without the junior having to guess it. Bending Spoons uses a similar pattern for its own company all-hands - see the case study below.

Step 4 - T-1 reminder with practical instructions (T-1 day)

The T-1 reminder is by far the most useful for reducing the last-minute no-show rate. Format: 6-8 lines with extremely specific practical instructions - room opening time, exact address, how to get there by car/transportation, where to park, dress code, any guest wifi connection, Zoom/Teams link for remote participation if it's a hybrid event. Subject line: Tomorrow | [Event name] | [Time] | [Location]. No wasted words.

The T-1 reminder is typically sent at 16:00-17:00 the day before - the audience finishes the workday, reads the inbox, prepares for the following day. Sending it on the morning of T-1 is less effective because the audience is busy with other things and the message gets lost in the day's inbox.

On the operational content of the T-1 reminder, a practice that works is the participant checklist: 3-4 items the participant must check before the event. Examples: (1) Have you added the event to your calendar? (2) Do you know where to park? (3) Do you have the technical requirements if you're attending remotely? (4) Do you have any specific dietary requests?. This list turns the reminder from a passive message into a participant self-checking tool.

A non-aggressiveness rule: don't send a T-0 reminder (the morning of the event itself). It's perceived as harassment. If you need a T-0 touch-point, use the internal coordinator team's Slack/Teams channel or a push notification from the event app if you have one. The T-0 email DOES NOT WORK.

Step 4b - Managing the audience's inbound feedback (throughout the cycle)

In parallel with the outbound touchpoints, the junior manages the inbound flow: replies to emails, messages in the dedicated Slack/Teams channel, requests via the RSVP form. The typical volume for a BU event of 80 people is 15-25 inbound messages in the 21 days before the event. The junior does the triage and replies directly to operational requests within 24 hours (e.g. can I park in the courtyard?, does the agenda include lunch?, is it possible to attend remotely?); they escalate to the senior the requests that exceed their autonomy (e.g. can I bring a colleague from another team?, is it possible to move the event by an hour?).

The operational rule for triage is the impact-decision matrix: two binary dimensions (low/high impact, operational/political decision). Requests with low impact + operational decision (something that concerns only that person, a decision the junior can make without precedent) are resolved directly. Requests with high impact + political decision (something that could set a precedent for other people, a decision that impacts the brief) are escalated to the senior. Examples of an operational decision: changing the time for a single participant (operational, low impact). Examples of a political decision: admitting a participant external to the target BU (political, high impact because it sets a precedent).

A useful practice is the inbound feedback log: an Excel sheet shared with the senior with 5 columns (date, sender, request, decision, follow-up). Every inbound feedback ends up in the log within 24 hours. The setup produces three benefits: (1) an audit trail in case someone claims that I wrote to you and you didn't reply, (2) a database for the post-mortem (the most frequent requests indicate what the brief hadn't clarified well enough), (3) political protection for the junior - if a decision is documented in the log, it's verifiable and defensible.

On inbound channels, the rule is channel convergence: even if people write via email, Slack DM, Teams chat, phone, all the feedback ends up in the single log. The junior's temptation is to manage each channel separately, but this produces inconsistency (different decisions for similar requests arriving from different channels) and information silos. Channel convergence means consistent decisions and complete visibility, and it protects you from the pattern where you answer the same question differently to two different people because you don't remember what you told the first one. The setup applied disciplinedly for three consecutive events becomes automatic; for the first two it instead requires voluntary discipline.

A useful sub-practice for the junior just starting out is the FAQ library: after the first event you accumulate a dataset of 15-25 inbound requests; by the fourth-fifth edition the cumulative dataset is 60-100 requests with standardized answers. That library becomes an internal team asset, and for the next junior who manages similar events the learning curve compresses drastically. Building the FAQ library takes 15 minutes after each event; using the FAQ library saves 3-5 hours of work for every future event. It's an investment with an immediate ROI.

Step 5 - Post-event follow-up + survey link (T+1 to T+5 days)

The post-event follow-up is the closure of the communications cycle. Format: 5-7 lines with (a) a thank-you, (b) three event highlights (3 lines maximum), (c) a link to the post-event survey (see L1-C5 for the survey detail), (d) a link to any shared materials (keynote slides, event photos, recordings if there are any), (e) a preview of the next similar event if one is already planned.

On timing: 24-48 hours after the event is the optimal moment. While it's fresh (within 24 hours) the audience has a vivid memory and completes the survey with higher probability; within 48 hours the memory is still vivid. Beyond 5 days, survey completion rates collapse drastically. Cvent Blog cites a figure: survey completion drops from the average 28% at 24 hours to 9% at 7 days.

On the follow-up's subject line, a pattern that works: Thanks + share + survey | [Event name]. Examples: Thanks, here are the materials and the survey | Engineering All-Hands 06/06. The presence of thanks in the subject has a measurable effect on the open rate: people open to read the recognition, even if quickly.

A useful sub-element is the contextual materials collection: most speakers and sponsors send the slides or post-event materials to the junior coordinator within 48-72 hours of the event. The junior collects them in a shared folder (SharePoint, Google Drive, Dropbox) and the link to that folder goes into the follow-up. This setup makes the organization seem much more professional than it actually is (the audience receives the materials within 48 hours, perceives high care) and is relatively low-effort for the junior (an hour of collection and organization work).

Real case: GitLab Handbook Communication, Stripe Sessions, Bending Spoons

Three case studies covering three complementary dimensions of internal communications: GitLab's asynchronous writing culture, the promotional cadence of Stripe Sessions, Bending Spoons' adaptation to the Italian scale-up context.

GitLab covers the structural dimension (template + writing culture). Stripe Sessions covers the dimension of promotional cadence for large events.

For the Italian scale-up context the reference is Bending Spoons, which has publicized specific practices.

Three additional sources: Mailchimp Resources has email marketing benchmarks by industry; HubSpot Marketing Statistics has data on email engagement and best practices; Harvard Business Review - Communication has research on internal organizational communication.

Anti-patterns: three first-year communications mistakes

Templates, checklists and next steps

The most useful template for the junior comms is the 1-pager brief, because the audience section of the brief is the basis of the communications distribution list.

The personal growth path along the Communications axis (C4) moves from applying-the-company-template at the L1 level to adapting-the-template-to-the-segmented-audience at the L2 level. The critical transition is the moment you start to measure engagement (not just send-out) and to calibrate the message for different segments (e.g. early-career junior vs senior management at the same event). See the next L2-C4 step. On the other L1 skills, communications ties to: L1-C1 single-BU ownership, L1-C2 direct-team stakeholders, L1-C3 operational checklists, L1-C5 post-event survey. The cornerstone contains the extended framework applied to all levels.

Three readings for the junior communications skill. On Writing Well by William Zinsser (Harper Perennial, 30th anniversary edition 2006) is the definitive book on clear writing, as applicable to company emails as to longform journalism. Made to Stick by Chip and Dan Heath (Random House 2007) explains what makes a message memorable in business contexts - fundamental for the junior who wants to write reminders the audience actually remembers. The GitLab Handbook - Communication is free online and contains real case studies of internal company communications. For the Italian context, the people operations blogs of Bending Spoons, Scalapay and Musixmatch often publish behind-the-scenes looks at their own internal communications.

What I learned writing this