Arrive Ready: The Meeting Invite That Saves Everyone Twenty Minutes
Most meeting invites arrive like a takeaway menu: a date, a time, and a short list of topics with no clue what you are meant to do with them. You turn up, someone shares a screen, and the first ten minutes disappear into a verbal version of a document nobody sent. The agenda said 'budget'. It did not say whether you were there to approve it, challenge it, or simply hear about it.
That is not an agenda problem. It is a writing problem. And it is fixable in the invite.
The invite is part of the meeting, not admin
We tend to treat the calendar invite as logistics: room, link, time. But the invite is the first thing people read about the meeting, and often the only thing they read before it. If it only lists topics, everyone arrives cold and the meeting becomes a live unboxing of information that should have been sent in advance.
A meeting invite that does half the work answers four questions before anyone joins: Why are we meeting? What are we deciding? Who owns each item? What should I read first? That is not bureaucracy. It is courtesy with a deadline attached.
Four ingredients of an invite that earns its place
Context, in one sentence. Not a paragraph of history. Just enough so people know why this conversation is happening now. 'Following the client's feedback on the pilot' is context. 'Project update' is not.
The decision, named plainly. If the meeting is for information only, say so. If a decision is needed, write it as a question: 'Do we extend the pilot by six weeks or stop at the end of March?' People can prepare a view on a question. They cannot prepare a view on a noun.
An owner for every item. Not just a presenter — someone responsible for bringing the pre-read, starting the item, and landing the decision. In a hybrid meeting, ownership is the difference between a tidy twenty-five minutes and a tour of everyone's open tabs.
One thing to read, watch, or check beforehand. This is the bit most invites skip. Do not attach a 40-page deck and call it preparation. Point to the single page, chart, or paragraph that will let someone contribute. If there is genuinely nothing to read, say 'No pre-read — come ready to discuss options A and B.' That is still information.
Before and after: a weekly team meeting
Here is a typical invite for a UK hybrid team in 2026. It is not bad. It is just not doing any work.
Subject: Weekly Ops Meeting — Thursday 10am Hi all, Agenda:
- Project update
- Budget
- Warehouse move
- AOB Thanks, Priya
Now the same meeting, rewritten. Same length, roughly. Very different arrival.
Subject: Decision needed Thursday: print supplier for Q1 Hi team, We need to choose between PrintCo and Northway for the Q1 print run. The decision is on Thursday's 30-minute call, so please come with a view.
1. Print supplier — decision (10 mins). Owner: Priya. Pre-read: one-page comparison attached. Decision: which supplier, and whether to accept the three-week lead time. 2. Warehouse move — update (5 mins). Owner: Tom. No pre-read. Tom will share the new date and one risk. 3. Team offsite — decision (10 mins). Owner: Sam. Pre-read: two venue options below. Decision: which venue, by end of meeting. 4. AOB (5 mins). No pre-read. Bring one thing only.
If you cannot make it, reply with your supplier vote and any offsite preference before Thursday 9am. Notes will be in the channel by Friday.
The second invite is not longer in a way that annoys people. It is longer in the way that saves them a meeting. It tells a hybrid team what to do with their eyes before the call, and what to do with their voice during it.
The one-thing pre-read rule
A pre-read should be small enough to read on a phone while waiting for a train. If it cannot be, it is not a pre-read; it is homework. The rule is simple: one link, one page, one question. If people need more, put the extra material in an appendix and tell them it is optional.
For hybrid teams, this matters more than it did when everyone shared a corridor. In an office, you could catch someone at the kettle and explain the budget gap. On a video call, the quiet person who did not read anything is just a black square with a mute button. The invite has to replace the corridor.
Hybrid details that belong in the invite
Say whether the meeting is in a room, on a call, or both. If it is both, say who is hosting the room and who is hosting the call. Name the channel for notes. Add a line for anyone joining remotely: 'We will use the room camera; please put questions in chat.' These are small things, but they stop the first five minutes becoming a tech rehearsal.
Also, give people a way to contribute without speaking. 'Add comments to the one-pager before Wednesday 5pm' is an instruction. 'Come ready to discuss' is a hope. In a hybrid team, the written channel is not a backup. It is part of the meeting.
A quick checklist before you hit send
- Does the subject line name the decision or the purpose, not just the meeting?
- Does every item have an owner and a type — decision, update, or discussion?
- Is there exactly one pre-read, and is it clearly labelled?
- Have you said what happens if someone cannot attend?
- Would a new starter understand why this meeting exists?
If the answer to those is yes, you have written an invite that does half the work. The other half is turning up and letting the meeting be shorter.
The meeting starts before the meeting
The best compliment an invite can get is not 'thanks for organising'. It is 'I read the one-pager, here's my view'. That is what happens when the agenda stops being a list and starts being a set of instructions for thinking. Send that, and the first ten minutes of your next meeting can be spent on the decision rather than on catching everyone up.
