Recurring meetings are the load-bearing walls of a team’s week — and they’re usually assembled ad hoc, once, by whoever created the series, and never redesigned. Six months later the same people meet for the same hour to discuss a purpose nobody has reread since the kickoff.
A meeting workflow treats the recurring meeting as a small product: it has a template, owners, a record, and a review cycle. None of it is complicated. The value comes from the fact that it happens every time, automatically, without depending on one organized person.
What a meeting workflow actually is
Strip away the calendar and every recurring meeting consists of five moments: before (what participants do to prepare), open (how the first three minutes run), middle (the agenda and facilitation pattern), close (how decisions and actions are captured), and after (where the record lands). A workflow just makes each moment explicit and repeatable.
The single-meeting version of this is covered in Preparing for More Productive Online Meetings. This guide is about what changes when the meeting repeats: the preparation compounds, the record accumulates, and the format itself becomes something you can audit.
Build a meeting template
For each recurring meeting, create two artifacts once and reuse them forever:
- An agenda template — the standing structure with pre-filled sections. A weekly team sync might have: metrics (5 min), blockers (10), decisions needed (15), wins (5), wrap (5). The agenda lives in a linked document, and each week gets a new dated section rather than a new file.
- A notes document per series — one running document per meeting series, newest entries at top, with a fixed structure: date, attendees, decisions, action items. One document per series beats one per session: it’s searchable in one place, and the URL never changes, so it can live in the channel topic.
Rotate and share the roles
Standing meetings calcify when the same person always facilitates and the same person always takes notes. Rotation fixes two problems at once: the meeting stops depending on one person’s presence, and everyone who runs it once understands what a well-run version feels like.
- Facilitator — rotates monthly, not weekly. People need a few sessions to get comfortable.
- Note-taker — rotates weekly. It’s a 20-minute responsibility that teaches the discipline of capturing decisions as they happen.
- Owner — does not rotate. Someone must hold the responsibility for the meeting’s purpose and its format. If nobody owns it, the meeting is an orphan and should be cancelled or adopted.
Keep a decision log
The highest-value artifact of a recurring meeting is its decision log: a reverse-chronological list of every decision with its date, the decision, the owner, and one line of reasoning. It lives at the top of the notes document, where people will actually see it.
The log earns its keep months later, when someone asks why the team does something. “We decided in March, because the vendor couldn’t guarantee the API,” is a two-second answer instead of a 40-message scrollback dig. Decisions fade; the log doesn’t.
Review the cadence
Every recurring meeting deserves a scheduled interrogation. Add a final agenda item to the last session of each quarter: is this meeting still worth its cost? Multiply attendees by duration — a weekly hour with eight people is a workday every week — and compare that against what the meeting produced this quarter.
Legitimate answers include: keep as is, shorten it, halve the frequency, reduce the invite list, replace it with a written update, or end it. Ending a meeting is not failure; it’s maintenance. Fold this review into the broader practice described in Reviewing and Improving Digital Collaboration Practices.
Signs a recurring meeting needs to change
- The first ten minutes are recaps of things everyone already knows — a symptom that the meeting is a status report in disguise. Write it instead.
- Regular attendees are optional in practice — people decline without consequences or join late routinely. The meeting is broader than its real audience.
- Agenda items are always “carry over from last time.” The meeting is slower than the work. Reduce the frequency or fix the blockers upstream.
- Nobody can state the purpose without checking the invite. That’s a formatting error with a deadline attached.
- Decisions happen in the hallway afterward. The meeting is the wrong shape for the conversation it needs to host — split it, or make it smaller.
Getting the team on board
Introduce workflows one meeting series at a time, starting with whichever one hurts most. The sequence that works:
- Draft the template and notes doc with the current facilitator — not for them.
- Run two weeks with the template, then ask the group one question: “What should the standing agenda actually be?”
- Adjust, then freeze the format for a quarter before touching it again.
Meetings resist redesign fatigue just like people do. One deliberate change per quarter is enough to keep a series healthy — and dramatically less than the default, which is zero changes forever.
For what happens between the meetings, return to Practical Ways to Improve Workplace Communication, or browse the full guides library.