Skip to content
anavem.com

AI Productivity & Meetings

Run a Decision-Focused Recurring Meeting

Build a recurring meeting around explicit decisions, realistic time boxes, prepared inputs and a controlled carry-over list.

Editorially validatedReviewed Last verified

What you will have at the end

A reusable agenda and decision log that reserve meeting time for choices, preparation and unresolved work instead of status narration.

Difficulty
Beginner
Time
25–40 minutes for the first setup, then 10–15 minutes per recurrence.

Testing scope

What was actually exercised, and what still requires verification in your own environment.

The dry run used a synthetic 30-minute weekly product meeting with six candidate topics, three required decisions and two absent decision-makers. The agenda-design and overload-repair prompts were run in Codex, then checked against the available minutes. Fellow and Fathom were not connected to a live calendar or meeting; documented capabilities only were used to define where an agenda and transcript could live.

Tools referenced

Profiles and official implementation options used by this workflow; see the testing scope for which integrations were exercised.

Steps

  1. Step 1: Define the decisions before adding topics

    Write the outcome of the meeting as decisions that must exist by the end: approve, choose, reject, assign or escalate. Convert vague topics such as “roadmap” into answerable questions such as “Which two roadmap items enter the next sprint?” Name the decision owner and required participants for each question. If the decision-maker cannot attend, move the item or redefine the meeting as preparation only. Verification is simple: every agenda item must end in a decision, a named deliverable or an explicit reason it belongs as information.

  2. Step 2: Collect pre-reading and unresolved carry-over

    Attach the minimum evidence participants need before the meeting: options, constraints, prior decision, owner and requested preparation. Pull forward only unresolved actions or questions that still affect the new decisions. Do not copy the entire previous agenda. Give pre-reading a deadline and state what participants should do with it. The step passes when someone opening the agenda can prepare without searching another channel and can see why each carry-over item remains open.

    Tool: Fellow

  3. Step 3: Build and time-box the agenda

    Use the outcome-led agenda prompt with the meeting duration, participants and decision questions. Allocate time for presenting evidence, discussing trade-offs and recording the decision. Reserve a closing block for actions and unresolved questions. Keep status updates asynchronous unless discussion is required. Sum every block, including transitions; if the total exceeds the meeting length, the agenda is not viable. Verification requires a complete time total and a clear facilitator or decision owner for each block.

  4. Step 4: Pressure-test scope and attendance

    Run the pressure-test prompt and challenge the draft manually. Look for decisions without the right authority, dependencies hidden in pre-reading, more topics than the time allows and agenda items that could be a written update. Use the repair prompt when the schedule is overloaded; defer lower-value items instead of shortening every discussion to an unrealistic duration. Record what was removed and why. A good agenda makes exclusions visible rather than pretending all work fits.

  5. Step 5: Capture decisions and prepare the next recurrence

    During or after the meeting, record the final decision, its owner, effective date, supporting rationale and any dissent or condition. Link each action to the decision that created it. At closing, identify unresolved questions and decide whether they need asynchronous work or a future meeting. Build the next agenda from the decision log and unresolved list, not from memory. Verify the record with the decision owner before distributing it, particularly when transcript wording could make a tentative statement look final.

    Tool: Fathom

Official sites for implementation. Their presence here does not mean a live account or integration was tested.

Prompts used

Copy them from the linked pages.

Editorial validation record

Illustrative scenario reviewed on Oct 3, 2026. This is not proof that the named third-party integrations were run.

  • OutputIllustrative scenario: overloaded agenda repaired

    Synthetic fixture: six topics requested for 30 minutes. The first draft required 52 minutes. After checking authority and purpose, two status updates moved asynchronous and one decision moved because its owner was absent. The final agenda totalled 30 minutes with three decision blocks and a five-minute close.

  • DatasetTesting limitation

    The meeting, agenda and participants were synthetic. The process was executed in Codex on 2026-10-03; no Fellow workspace, Fathom meeting or real calendar event was used.

Last verified

Quick answers

How long does it take?
25–40 minutes for the first setup, then 10–15 minutes per recurrence.

Sources

More AI Productivity & Meetings workflows

See the category →

Prompt packs behind this workflow

New workflows by email

New editorial workflows and changes to the tools they reference. Sponsored items are labelled.