Four roles belong in a working meeting: the person who decides, the people who have to agree, the people who hold information the decision needs, and the person keeping the record. Everyone else is there to be informed, and being informed is not a reason to spend an hour.
The advice you will find elsewhere is that attending non-mandatory meetings is important — that optional invites are where visibility happens, where you hear the thing nobody wrote down, where being in the room compounds. That is not wrong. It is just incomplete in a specific and expensive way: it is true of some optional invites and false of most, and nobody tells you how to sort them. Here is the sort.
What “optional” means on an invite
Almost nothing, and that is the problem.
The optional field in a calendar invite is a technical distinction that most organisers use as a politeness marker. It rarely means “we have decided you are not needed”. It usually means one of three things, and they demand completely different responses:
- Genuinely optional. The organiser thought you might want to know and has no expectation either way. Declining costs nothing and is invisible.
- Optional as courtesy. You are needed but the organiser did not want to presume. Declining is noticed.
- Optional as insurance. The organiser is covering themselves against “why wasn’t I asked”. Declining is fine; not being invited would have been the actual offence.
You cannot tell these apart from the invite. You can tell them apart from one question, which is the whole trick and it takes ten seconds.
The four roles, and the test for each
Work out which of these you are for a specific meeting. If you are none of them, you are an audience.
| Role | You are this if | Can it be async? |
|---|---|---|
| Decider | The decision is yours to make or to veto | No |
| Consenter | The decision needs your agreement to proceed | Sometimes — in writing, beforehand |
| Input | You hold information or judgement the room lacks | Usually — write it down |
| Recorder | You are producing the record others rely on | No, but it can rotate |
| Audience | You are there to be kept informed | Always |
The two that surprise people are Consenter and Input.
Consenter feels like it requires presence and often does not. If your agreement is conditional on things you already know, you can give it in advance with the condition stated — “yes to the migration date provided support are staffed for the weekend” — and the room proceeds without you. You only need to be there when your agreement genuinely depends on hearing the discussion.
Input is the role that puts most people in most rooms, and it is the most convertible of the four. If you are there because you know how the billing system behaves under load, the room does not need you, it needs that fact. Write the fact down and send it the day before. You will be quoted accurately, which is more than can be said for the version where you say it out loud at minute forty.
Being the audience is not shameful and it is not always wrong — see the end of this post. It is just not a reason that survives being stated.
The ten-second test for an optional invite
One question, asked of yourself, not the organiser:
“If I don’t go, what specifically goes wrong?”
Answer it with a named consequence or accept that there isn’t one.
- “A decision gets made about my team’s scope without me” — go.
- “Someone will assign work to me that I can’t push back on” — go, or send your position in writing beforehand and ask to be consulted before anything lands on you.
- “I won’t know about it until the notes” — do not go. That is what notes are.
- “It’ll look bad” — this is a real answer, and it is the one everything below is about.
If the answer is the fourth one, you have a visibility problem rather than an information problem, and sitting silently in a meeting is one of the least efficient solutions to it available. the real cost of declining covers the visibility question directly; the short form is that being visible in the record beats being present and quiet, and the record is cheaper.
The message that gets you off the list
Three versions by situation. All three do the same two things: they remove you from the room without removing you from the topic, and they offer something in exchange for the hour.
When you are Input and can be async:
“I don’t think I need to be on the Thursday review — most of what I bring is the load numbers, and those are better written down than said out loud. I’ll put them in the doc every Wednesday. Grab me if something comes up that needs an actual conversation.”
When you are Audience and want to stay informed:
“Taking myself off the product sync — not because it isn’t useful, I just can’t hold the slot. I’ll read the notes. If anything touches onboarding, ping me directly rather than assuming I caught it.”
That second clause matters more than the first. The risk of leaving a meeting is not missing information, it is people assuming you have information you do not have. Naming the thing you want to be told about converts a passive exit into a specific arrangement, and it gives the organiser a reason to say yes.
When you genuinely do not know which role you are:
“Before I decline the Tuesday call — am I on it for a reason? Happy to be there if you need a view from support, but if it’s just to keep me in the loop I’d rather read the notes and give you the hour back.”
Asking is not weak. It is the only version that gets you a real answer, and the answer is frequently “honestly, I’m not sure why you’re on it”, which resolves the whole thing in one message.
The ladder of partial exits — attending for one item, delegating, sending input beforehand — is laid out properly in the alternatives to declining. Use it when the answer to the role question is “sort of”.
Trimming someone else’s invite list
If the meeting is yours, you have a harder job, because removing people from a recurring invite is read as a status signal whatever you intend.
Do it as a question, never as an action. The wording in the redesign guide covers the general case; the specific thing to avoid is a bulk edit with no message, which is how a routine tidy-up becomes three people quietly wondering what they did.
Two rules that make it survivable:
Ask everyone, not just the people you want to cut. A message to the whole list — “I’m tidying this invite; tell me if you’d rather be on notes than in the room” — costs nobody anything. A message to three specific people is a performance review.
Never cut someone junior without a conversation. For someone early in a role, the optional meeting may be where they learn what the decision-making actually sounds like. That is a real benefit and it does not show up in any attendance metric. If you are removing them, say why and say what replaces it.
When being in the room is the right call
The honest cases, because the sorting above is not a licence to decline everything optional.
A new role, a new team, or a new manager. For your first few weeks anywhere, the audience seat is doing real work — you are learning who defers to whom, which is not written down anywhere and cannot be. Sit in more than you need to, deliberately, and stop when you have it.
Anything that decides your own scope. If the room might redistribute work, budget or headcount that touches you, you are a Consenter whether the invite says so or not. Written input is not enough here, because the discussion moves and your written position gets read against a question that has changed.
When the organiser is senior and asked you personally. The invite is not the request; the message attached to it is. A personal ask from someone senior is a Courtesy-optional invite, and declining it is a decline — a real one, with the usual costs. the manager case is the version of that conversation worth having.
When you are the only one who will say the thing. Sometimes you are in the room as the person who asks the question everyone else has decided not to ask. That is not a role on any attendance chart and it is occasionally the most valuable hour in your week. You know when this is you.
The rest of the time: four roles, one question, one message. Most optional invites do not survive it, and that is the correct outcome rather than a failure of collegiality.