An invitation is the one thing the other person looks at ten minutes before the meeting. It’s on their phone, three weeks after they agreed to come. Whatever they need at that moment has to sit inside the event itself. The thread it was agreed on is somewhere else entirely.
- The email and the event travel together as two different objects. Only one of them lands on somebody else’s calendar, and most of what people write ends up in the other half.
- The empty field that costs the most is wherever the joining instruction should have gone.
- A sentence saying what the meeting is for beats a list of topics. The evidence on that is more lopsided than the usual advice suggests.
- Nearly everything the invitation needs has already been said in the thread. The job is choosing which parts, and giving each one a field.
What the other person is holding at 9:50
An invitation gets read at three moments. Whoever writes it is usually picturing the first one.
It’s read when it arrives, for about four seconds, while somebody decides whether to accept. It’s read again at the reminder, on a lock screen. About six words and a time are all that show up there. And it’s read at the moment it has to be used, when the person needs the room number or the link in the next ninety seconds.
Most invitations are written to be accepted. Write yours to be used.
Here’s why the event carries all of that weight rather than the correspondence around it, and this one fact explains most of the mistakes. An invitation arrives as an email, but it isn’t one. It’s a structured object with named fields, specified in RFC 5545, the Internet Calendaring and Scheduling Core Object Specification, published in September 2009 and still the format calendars exchange events in. An event carries a SUMMARY, a DTSTART and DTEND, a LOCATION, a DESCRIPTION, an ORGANIZER and a list of ATTENDEEs. Those fields are what get copied into the other person’s calendar.
The covering note you typed in the mail window stops in their inbox, where it gets archived by Thursday. Anything you wrote there, and anything the thread agreed, lasts for the recipient only as long as they’re willing to go searching for it. At 09:58 they’re out of time.
So the working rule is a plain one. If a piece of information matters at the meeting, it goes in a field. If it only matters now, the message is fine.
What each empty field costs
Each empty field below produces something specific and predictable. Usually a message you then have to answer. Occasionally a person in the wrong place. They’re listed roughly in order of what they cost.
Where, and how to get in. This is the expensive one, and it goes missing for the most ordinary reason there is: you already know the answer. RFC 5545 defines LOCATION as the “intended venue for the activity defined by a calendar component”. For a video call the venue is a URL. In October 2016 RFC 7986 added a property for exactly that. CONFERENCE “specifies information for accessing a conferencing system”, and it holds a dial-in number with access codes as readily as a video room. Joining detail has had a home of its own in the standard for a decade. Leave it in the covering email and you get a message at 09:59 asking for the link, which you answer at 10:02 from inside the empty call. For a physical address, the field wants the part the map leaves out: the door, the floor, the buzzer, and where a car can go.
The end time. An event carries an end, or a duration, and under-booking is the common error. An hour of conversation put into a thirty minute box is a decision you’ve made about somebody else’s afternoon. They arranged their day around your number. At twenty-eight minutes you either cut the useful part short or run into whatever they booked next. Book the length you think it’ll actually take, including the five minutes at the start that go on hellos.
The time zone. You notice this one only when it’s wrong, and then you really notice it. It has its own piece: scheduling across time zones.
The title. RFC 5545 asks SUMMARY for “a short, one-line summary or headline for the calendar component”, and headline is the right word for it. Your title gets read in a list of eleven other things, out of context, weeks later, on a screen that shows about half of what you type. “Call” fails there. “Catch up” fails there. Something closer to “Year end handover: Merrow and Finch” survives, because it says who and what in the space available. A vague title costs you a second time when you look up at the wrong hour. A very specific one costs you a second time too, because the words are the most widely visible part of your calendar, readable by anyone you’ve given detail-level access to. A client’s name in an event title is a decision worth making deliberately, for the same reasons set out in using an AI inbox without breaking confidentiality.
Who else is on it. Two gaps live here. The first is the person who should have been on the list, and the meeting itself is usually where that surfaces. The second is quieter. A colleague reads the invitation and wonders whether they’re there to present, to contribute or to listen, so they prepare the wrong thing or arrive empty-handed. A line naming what each person is there for costs you eight words.
One fact about the guest list catches people out. Google’s own help page on sharing events says of the “See guest list” permission that “this is the default setting”. It adds that “Even when the ‘Guests can invite others’ permission is off, people can still add themselves and others as guests through the shared link” (checked August 19, 2026). So everyone on an invitation can ordinarily see everyone else’s address, and the list stays open. Put two clients who are strangers to each other on the same event and you’ve introduced them.
You, and how to reach you in the next four minutes. Somebody lost, late or in the wrong building is usually looking at the invitation and little else, and a cell number sitting in it turns a lost half hour into a two minute call. There’s a second reason it matters. RFC 5546, the iCalendar Transport-Independent Interoperability Protocol of December 2009, is blunt about who owns the event: “Attendees do not make direct changes to the master iCalendar object. They can, however, use the COUNTER method to suggest changes to the Organizer. In any case, the Organizer has complete control over the master iCalendar object.” Every correction routes back through you by design. Being reachable is part of the job you took on when you sent it.
The reply. The same protocol gives an attendee four answers: ACCEPTED, DECLINED, TENTATIVE or DELEGATED. It gives one more move, COUNTER, described there as “Counter a REQUEST with an alternative proposal. Sent by an Attendee to the Organizer.” An acceptance is the cheapest confirmation you’ll ever be given, and most people skim straight past it. Silence is the early warning you get, and it reaches you days ahead rather than at the hour. Read it as a reason to check rather than as proof of who’s coming. What to do about a thread that’s gone quiet belongs to unanswered emails, and the threads that come back.
The reminder. Whatever alert the event carries is a default rather than a decision you made. Your client agreed to this six weeks ago. A nudge the day before is worth considerably more to them than one fifteen minutes before, because the day before is when the preparation can still happen.
What they need to have read. If the meeting only works when somebody has looked at a document, the invitation is the last reliable place to put it. An attachment on the event travels with the event. A file linked in message four of a thread stays in message four.
That’s the logistics, and it’s most of what an invitation is for. One field decides whether the other person arrives prepared rather than merely present. That’s the description, and it’s the one worth spending a minute on.
The one sentence that does more than an agenda
The standard advice is to attach an agenda. The evidence for it is thinner than you’d expect, and what the evidence does support is more useful to know.
The Chartered Institute of Personnel and Development and the Center for Evidence-Based Management published Productive meetings: an evidence review in May 2023, written by Eric Barends and Denise Rousseau. It screened 618 studies and reduced them to 30. Then it tabulated the effect sizes for everything anybody has measured against perceived meeting effectiveness.
Two rows of that table sit a long way apart. A formal agenda correlates at r = .14 to .18. Goal clarity correlates at r = .51 to .54. The reviewers put it plainly: “although the popular literature emphasizes the importance of meeting rules/procedures and the advance distribution of a formal agenda, only small correlations between these and perceived meeting effectiveness were found”.
Their definition of the thing that does work is the sentence to carry away. Goal clarity is “the degree to which attendees understand why the topics on the agenda are important, and what the meeting leader wants to achieve by discussing them”. So: why the topics matter, and what you’re trying to get out of them.
Two honest caveats, because the review supplies them itself. Of its 30 studies, 25 were graded level D, which the reviewers gloss as “a low level of trustworthiness”, and most were cross-sectional surveys. So this is correlation among self-reports, and the shape is worth more than the decimal. The second caveat rescues the agenda. Cohen and colleagues, in one of the studies reviewed, did find a formal agenda correlating with meeting quality, “but only when the agenda was accessible prior to the meeting”. That’s the entire argument for putting it in the invitation rather than handing it out at the table, since the event is the one document guaranteed to be in front of everybody beforehand.
So the description field wants three things, in about four sentences.
What will be decided or produced. The outcome, rather than the subject. “By the end we agree the scope and the fee” gives the reader a different instruction than “Discuss scope and fees”. One of them brings somebody who arrives with an opinion. The other brings somebody who had every reason to keep an open mind.
What they need to bring or have looked at, named exactly. “The signed engagement letter” rather than “the paperwork”.
What to do if it stops working. One line inviting them to say so is worth having. It gives the person who quietly can’t make it an easy way to tell you, instead of an awkward one. How that conversation goes when it comes is when they ask to move.
Written out, that’s short enough to read on a phone:
“Half an hour on the year end. By the end we want a decision on whether to file the extension, so I will bring the draft accounts (attached) and it would help if you have glanced at the two flagged entries. My cell is in the invitation if anything changes.”
Four sentences. A description that runs to a full screen gets skimmed away, and everything below it gets scrolled past, including the joining link.
Writing it from the thread instead of retyping it
By the time you send an invitation, one of you has already written down every fact in it. The work is selection, and it takes about ninety seconds while the reply is still open on the screen.
Four things are in the thread, and each has a field waiting for it.
The time you both agreed goes in the start and end fields, and there alone. Restating it as a sentence in the description feels helpful and is a trap. Move the meeting and the fields follow, while the sentence stays where it was, and the sentence is the one a hurried reader believes. That failure has its own repair in moving a meeting, and leaving it unplanted is much easier.
What they asked for, usually in their own words in the first or second message, goes in the opening line of the description, tightened. Their phrasing is the cheapest proof available that the meeting is about the thing they wanted rather than the thing you heard.
The document or the figure somebody mentioned gets attached or named. It came up once, in passing, and by Thursday you’ll both be hunting for the message it was in.
The constraint that arrived in a subordinate clause. “I have a hard stop at eleven” sets your end time. “Sarah should probably be on this” sets your guest list. Constraints usually arrive tucked inside another sentence, which is exactly why they’re the most commonly dropped thing between a thread and an event.
Three things stay in the thread.
The quoted chain. Pasting the correspondence into the description is the most common shortcut and the worst one. That field travels with the event into every attendee’s calendar, onto their phone, and into whatever else they’ve connected to it. A remark about a third party, a discussion of price, a client’s home address: all of it ends up in copies you no longer control. It moves information around rather than saving you typing.
The negotiation. Thursday can simply be Thursday. That it was the third option offered stays between the two of you.
The warmth. Put it in the covering message, which is where it gets read anyway. At 09:55 somebody is hunting for a link, and a pleasant sentence about their vacation belongs where they’ll enjoy it.
Two smaller habits save more time than they look like they should. Write the invitation in the same sitting as the reply that agreed the time, because the constraint you can still remember is the one that makes it into the fields. And give the event its own title. Threads are named for a request, so they read “Re: quick question about the year end”, while events are named for what they are. Copying the one into the other is the single commonest way a careful invitation ends up with an unusable name.
The covering message has one job left. Say the invitation is attached, and say what to do if the time stops working. If you’re still making the offer rather than confirming it, that’s a different message doing a different job, and it’s the one that decides how long the whole thing takes: scheduling without the email chain.
When an invitation is the wrong object
An event on somebody else’s calendar is a claim on their time. A few things that feel like meetings belong somewhere else.
A dated commitment that is nobody’s hour. “Accounts to be filed by the 14th” is a real obligation and a bad event. It blocks time that could stay free, it teaches everyone to skip past your invitations, and it’s out of sight at the moment the work would actually be done. That belongs with the rest of the dated work, in email task management, without writing it down.
A block on your own time. Perfectly sensible, and it stays on your own calendar. What matters about it is whether it’s marked in a way that keeps your availability from being sold out from under you, which is dealt with in booking links that show real availability.
A question shorter than the invitation. If the whole exchange fits in four sentences, send the four sentences.
A meeting somebody else’s office is arranging. When a client’s assistant runs the calendar, your invitation becomes a second copy of an event they’re about to create properly. Two invitations for one meeting is worse than none. The accepts split across both, and neither one tells the truth. Send them the details in a form they can lift, and let the invitation come from where the calendar lives.
Sending it from the thread it was agreed on
Point is a full email client sitting on top of the Gmail or Microsoft 365 mailbox you already have. The correspondence and the calendar sit in one surface, so you stop copying between two windows. That matters here for a narrow, practical reason. The constraint sitting in paragraph three of somebody’s reply is in front of Point as well as you.
Ask for a meeting in plain words on the thread. Point runs the back and forth from there, checks your reconciled calendars, and puts real times in front of the other person. Once a time is agreed you approve it. The invitation goes out with everyone on it, and it’s written into your real calendar as a proper event rather than a note about one. This works across time zones. A request to move something gets picked up even when it’s buried in a reply about something else.
Scheduling has its own autonomy setting, separate from the rest of what Point does. Out of the box it sits on review. The times proposed and the invitation written both come past you first, and you raise the setting once you’ve watched a few go out. At the top of the dial Point runs the correspondence without asking. Everything Point did is recorded in order, and undo works back through that record. The plain limit is that an invitation already sitting in a client’s calendar is withdrawn rather than erased. The benefits page covers what changes in the rest of a mailbox.
Common questions
What should a calendar invitation include?
The joining detail first, because that gap is the one that costs a message at 09:59. Then a realistic end time. Then a title that identifies the meeting when it’s read cold on a lock screen. Then the guest list, with a word on what each person is there for. Then a way to reach you in the next four minutes, and a short description saying what will be decided and what to bring. Everything on that list is a field on the event, which is the test: information that matters at the meeting goes in a field, information that only matters now can go in the covering email.
Where should the meeting link go?
In the event’s own fields, rather than the message around it. The standard has had a dedicated property for this since October 2016, when RFC 7986 added CONFERENCE for “information for accessing a conferencing system”, and the location field held it before that. Be strict about it, because the covering email gets archived while the event stays on the calendar. An hour before the call, the link is either in the thing they’re looking at or it’s nowhere.
Should I put an agenda in the invitation?
Put the purpose in, and the agenda too if there genuinely is one. The 2023 CIPD and CEBMa evidence review found a formal agenda correlating with perceived meeting effectiveness at r = .14 to .18. Goal clarity correlated at r = .51 to .54, meaning attendees understanding why the topics matter and what you want to achieve. One sentence naming the decision does more than a list of headings. Where the agenda earned its keep in that literature was when it reached people beforehand, and the invitation is the one place guaranteed to.
Can the people I invite see each other’s email addresses?
Ordinarily yes. Google’s help page on sharing events says the “See guest list” permission is on by default, and that people can still add themselves and others through a shared link even when guests are not permitted to invite others (checked August 19, 2026). So an invitation with two unrelated clients on it introduces them to each other. When you’d rather keep them apart, the answer is two invitations rather than one carefully worded description.
Do I need to send an invitation if we already agreed the time by email?
Yes, and the agreement is exactly why. The thread records a decision in a place you’ll both scroll past. The event puts it on both calendars, holds the time against everything else that gets arranged this week, and carries the joining detail to the moment it’s needed. The acceptance you get back is also the cheapest confirmation available that the other person actually wrote it down.
Is it rude to send someone an invitation they did not ask for?
It depends entirely on whether the time was agreed. An invitation is a record of a decision, so sending one after a yes is bookkeeping and reads as organized. Sending one instead of asking makes the decision on somebody else’s behalf, and it leaves them declining a thing that’s already on their calendar. While the time is still open, the message that settles it fastest is a short offer of real slots.
The short version
An invitation and the email carrying it are two different objects, and one of them arrives on the other person’s calendar. Everything that matters at 9:50 belongs in the event’s own fields. The correspondence around it will have been archived days earlier, and a person who’s already late is looking at their calendar.
Fill the fields in the order of what an empty one costs. Joining detail first. Then an end time long enough to be true. Then a title that identifies the meeting when it appears cold on a lock screen. Then a guest list with a word about why each person is on it, and a number that reaches you in the next four minutes. Then use the description for the thing the research is unusually clear about: what will be decided and what to bring, in about four sentences rather than a list of topics.
One of you has already written nearly all of that in the thread. The job is lifting it rather than composing it, with the quoted chain left firmly where it is. A coaching practice running the same session every two weeks can write one good invitation and reuse it forever, so the effort belongs in the reminder and the preparation line. A consultancy meeting four people at a client’s office for the first time has a different bottleneck entirely: the address, the floor and who is expected to speak. The rest of the trades this is built for sit somewhere between the two.