Raci for meetings cut attendance by 40 stop reopening decisions

Most meetings are too big because nobody defined who actually needs to be there. Four people do the real work while ten others sit silent. The Accountable person makes a call, then finds out two days later that someone Consulted had a blocking concern nobody surfaced. Informed roles show up out of habit because nobody told them they could skip. RACI fixes this. It assigns four roles to every meeting — Responsible, Accountable, Consulted, Informed — and gives each role explicit rules for attendance, prep, and opt-out. Teams using RACI cut average meeting size by 40% and reduce reopened decisions by 60%.

The RACI matrix template

Copy this into every recurring meeting invite. Assign one row per stakeholder before sending.

Real filled example: executive quarterly planning

Before RACI: 12 people attended. Meeting ran 2 hours. Same questions asked 3 times. Decisions reopened via email the next day.

After RACI: 5 core people. 45 minutes. Memo sent to Informed roles by 3pm. No re-discussion.

Why meeting attendance bloats

The problem is structural. Nobody in the invite explicitly says "you don't need to be here." So people accept to stay informed, to protect their interests, or because opting out feels risky.

The three clearest symptoms: the core decision team is 4 people but 12–15 accept the invite. The meeting is scheduled for 60 minutes and runs 2 hours because seven people each have "one thing." The Accountable person decides, then the next day a Consulted role escalates a blocking concern via email — reopening the decision entirely.

RACI ends all three by making every role's obligation explicit before the meeting starts.

How each role works

Responsible

Does the work. Presents the proposal, responds to questions, iterates based on feedback. One person per meeting. Must attend.

Accountable

The decision-maker. Exactly one — never shared. Listens to R and C, then makes the call. Owns the outcome if it goes wrong. Documents the decision within 30 minutes of the meeting ending. Must attend.

Consulted

Two to four people with critical domain knowledge. Must read the pre-read (2 pages max) before the meeting. Flags risks and asks clarifying questions. Can opt out if they submit written feedback before the meeting starts. Cap at 4 — beyond that, run an async pre-read review instead.

Informed

Receives the decision memo after the meeting. Never attends live. Reacts in team chat if needed. The opt-out rule is automatic — no need to ask.

Who should attend: by meeting type

The meeting invite template

Copy into your calendar invite

Subject: [Meeting Name] | Decision: @[Accountable] | Required: @[Responsible], @[Consulted] | Recap only: @[Informed]

Decision: [One sentence — what we're deciding]

Pre-read: [Link] — 2 pages, due [time]

Roles: R = [Name], A = [Name], C = [Names], I = [Names]

Opt-out rule: C can skip if feedback submitted before the meeting. I gets the recap — no attendance needed.

Blocker? Post in #blockers and tag @[Accountable]. Response within 4 hours.

3 real examples

Executive quarterly planning

Before: 12 attendees, 2-hour meeting, same questions asked 3 times, decisions reopened via email the next day.

RACI: R = Finance Manager. A = VP Operations. C = VP Product, VP Engineering, CFO. I = all dept heads, CEO, HR.

After: 5 core people. Thursday 2pm, 45 minutes. Pre-read: 2-page Finance doc, due Wednesday noon. C submit feedback by Thursday 10am or trust the memo. Result: no re-discussion. Memo to all I roles by 3pm.

Product sprint planning

Before: 8 attendees, unclear if 60 engineering points were feasible, scope expanded during the meeting, ownership unclear.

RACI: R = Product Manager. A = Director of Product. C = Engineering Lead, Design Lead, QA. I = Support, Data.

After: 5 core people. Tuesday 10am, 90 minutes. Pre-read: 2-page spec due Monday 5pm. C flag concerns by 9am Tuesday or attend live. Support and Data get async recap. Result: scope locked in 90 minutes, no post-meeting renegotiation.

Sales pipeline review

Before: 8 reps plus VP Sales plus Finance, 90 minutes. Same deals debated twice. No written decision meant reps heard different things.

RACI: R = Sales Ops. A = VP Sales. C = Sales Manager, Finance. I = Marketing, Customer Success.

After: 4 core people. Tuesday 9am, 60 minutes. Pre-read: 1-page pipeline due Monday 5pm. All reps not on leadership get the recap and individual coaching. Result: three at-risk deals resolved in the meeting, one-paragraph memo in team chat by Wednesday.

Common mistakes and how to fix them

No single Accountable person

Everyone votes, nobody decides. The same decision surfaces again three days later. Fix: every meeting needs exactly one A. If you can't name them before sending the invite, postpone the meeting.

Too many Consulted roles

Eight people, three speak, meeting runs two hours, no decision lands. Fix: cap C at 4. If more input is genuinely needed, run an async pre-read review — post a 2-page doc, collect written feedback by a deadline, A reviews before the meeting.

C and I don't know they can opt out

They assume attendance is required. They show up regardless of workload. Fix: state it explicitly in the invite — "C can skip if workload is high. C must read the pre-read and submit feedback. I gets the recap — no attendance needed."

Pre-read is missing or too long

Consulted roles see the proposal for the first time in the meeting. Or it's 15 pages and 40% actually read it. Fix: pre-reads are always 2 pages max, bullet points. Share 24–48 hours before. If C opts out, they still read and submit written feedback.

Accountable delegates or won't decide

A says "whatever you all think." Consensus never lands. Fix: A listens, then calls it. They can ask for input, but they own the final decision. Document any dissent in the memo.

No blocker escalation path

Consulted spots a risk but waits for the live meeting to raise it. They attend out of obligation even when they could have resolved it earlier. Fix: add this line to every invite — "Blocker? Post in #blockers and tag @[Accountable]. Response within 4 hours. No need to attend if the concern is captured."

Metrics to track

7-day rollout plan

Day 1: List all recurring meetings. Categorize each as decision, alignment, or status. Pick the top 5 that have the most attendees or most frequently get reopened.

Day 2: Map RACI for the 3 most important meetings. Assign R, A, C, and I for each. One Accountable per meeting — no exceptions.

Day 3: Walk through the RACI assignments with each Accountable. Get their buy-in. Adjust if a role doesn't make sense.

Day 4: Send updated invites to the full roster. Make the opt-out rule explicit: "C can skip if workload is high, but must submit feedback. I gets the recap and never attends."

Day 5: Run the first RACI-structured meeting. Track: how many opted out? Did everyone read the pre-read? Was a clear decision reached?

Day 6: Debrief. Check meeting size, opt-out rate, and decision clarity. Adjust the RACI assignments if anything felt off.

Day 7: Roll RACI out to all recurring meetings. Publish assignments in a shared folder. Schedule a 5-minute check-in the following week to catch any friction.

How Spry surfaces attendance bloat

RACI works best when you know which meetings are already oversized before you start redesigning them. Guessing wastes time — you want to go straight to the meetings with the biggest gap between attendees and actual contributors.

Spry's calendar analytics show average meeting size per team and per meeting type across your whole calendar. You can see at a glance which recurring meetings are running with 12+ attendees, which have no agenda, and which are eating the most combined employee time per week. That's the data you need to prioritize your RACI rollout — start with the meetings that cost the most, not just the ones that feel the most painful.

FAQs

Can someone be both Accountable and Responsible?

No. Responsible is hands-on — they present and iterate. Accountable decides. Separating the roles keeps the decision-maker from defending their own work instead of evaluating it objectively.

What if Consulted strongly disagrees with the Accountable's decision?

They make their case before the decision is made. Once A decides, C supports it publicly — even if they disagreed. Document the dissent in the memo so the reasoning is on record.

Can Informed people attend if they want to?

Yes, but with no obligation. They'll get the memo and can ask follow-up questions in team chat. Make it clear they're not expected and won't miss anything by skipping.

What if there's no single Accountable person?

Fix it before the first meeting. Either one person is A, or two share the role with an explicit tiebreaker rule. A meeting without a named Accountable will produce a decision nobody owns.

What if Responsible wants 6 Consulted roles?

Push back. More C means longer meetings and less airtime per person. If 5 or more are genuinely needed, split the decision into smaller parts or run an async pre-read review instead of expanding the live meeting.

How do you handle Consulted roles who don't read the pre-read?

They skim during the first 10 minutes, or they opt out and submit written feedback within 2 hours of the meeting ending. The rule is that a Consulted role cannot slow the meeting down because they skipped the pre-read.

Can RACI assignments change mid-quarter?

Yes, if the purpose of the meeting shifts. Update the assignments and notify the team. RACI is a living document, not a fixed structure.

How do you prevent RACI from becoming bureaucratic?

Use it for your top 10–15 recurring meetings, not every meeting. Review quarterly. If filling in the matrix is taking longer than the meeting saves, simplify or stop. The goal is fewer people in better meetings — not perfect documentation.