Mastermind Group Agenda Template: A Complete 90-Minute Plan

A mastermind group agenda template should show who gets time, how a member’s question will be explored and what the group records afterward. This original ninety-minute plan serves six members and a facilitator, with two volunteer cases. It includes prompts, a preparation brief and a complete fictional meeting with later follow-through.

Coachful is our #1 recommendation for organizing the roster, session, preparation resources and chosen actions around this format. Keep private preparation and agreed shared takeaways distinct. A well-organized workspace supports the process; the value of the discussion still depends on relevant questions, careful facilitation and members’ own decisions.

Define what this meeting offers

A mastermind here means a facilitated peer discussion of members’ real working questions. It is different from a training class in which the host must deliver a fixed curriculum, or a consultancy engagement that promises a prescribed answer. Explain when members will ask questions, share experience or offer ideas, and when the presenter can decline them.

Describe the actual airtime. Six members with two cases per meeting can each receive one case over three meetings if everyone wants a turn and those meetings happen. That is an opportunity, not a requirement to disclose a problem. A member who passes still participates in the agreed ordinary meeting.

The facilitator manages the process, including time and participation. A presenter remains responsible for their business decisions. Clarify any change into coaching or professional advice rather than quietly adopting an expert role. The International Association of Facilitators’ Statement of Values and Code of Ethics, adopted in June 2004, discusses autonomy, appropriate methods, conflicts and this distinction between process and content.

Agree boundaries before admitting sensitive material. Members can promise to respect confidentiality, but a host cannot guarantee what every participant will later remember or repeat. Use only information appropriate for this audience and retain the relevant professional routes for legal, financial, clinical or employment matters.

A complete ninety-minute mastermind agenda

The five segments total 15 + 30 + 30 + 10 + 5 = 90 minutes. The facilitator is additional to the six members and uses the orientation and practical close; they do not take an extra two-minute member update. The structure contains no scheduled break. Discuss that openly and adapt the duration or content if members need one.

For example, retaining a five-minute break within ninety minutes requires removing five minutes elsewhere by agreement. Do not advertise two full thirty-minute cases and silently shorten the second. A larger roster also needs a new time budget, not faster speech or the assumption that nobody will want to contribute.

Prepare the people, case brief and access

Send the purpose, times, participation options, case process and information boundaries beforehand. Invite volunteers with a clear reply date. Publish the rotation and a fallback if a presenter withdraws: another willing prepared member, a shorter general process discussion or a revised meeting. Passing should not trigger an improvised demand for a personal confession.

Ask how members can participate comfortably. Offer a readable text agenda and prompts rather than relying only on a decorative image. Someone may prefer to read a question, type it or ask the facilitator to read an approved version. Verify the actual route with that person, and allow time for using it.

A short original brief can contain these six fields:

• Question: What do I want to decide or understand?
• Context: What does this audience need to know, and what am I omitting?
• Constraints: What time, authority, obligations or practical resources matter?
• Attempts: What have I already tried, with what result?
• Contribution: Would clarification, experience, options or another form of help be useful?
• Record: What may be retained or shared after the discussion?

Read the submissions before the call. Ask for missing context or remove unnecessary identifying detail with the presenter. A private submission is not automatically approved for group display. Get agreement on the version that will be read, and confirm who will receive any resulting summary.

Use the group coaching ground rules template to develop the working agreement. Keep the agenda usable: it should tell members how to participate, not bury the real process beneath a long list of promises the host cannot enforce.

Open with updates that fit the purpose

During minutes zero to three, state the purpose, the two presenters, the timing and how to pass or request a pause. Confirm any relevant change to the agreement. Explain what will be documented and whether recording is proposed; do not surprise members by activating it after sensitive discussion begins.

Give each member up to two minutes: “What changed since we met, and what would be useful today?” They can report a relevant development, make a bounded request or pass. A metric is optional. Customer names, personal financial exposure or an employee’s private circumstances are not admission tickets to a worthwhile update.

Use a visible timer and a respectful cue. “We have thirty seconds left; what should we carry into the case?” is more useful than abruptly cutting someone off. If an update opens a larger issue, ask whether it belongs in their case or an appropriate later conversation.

In the fictional meeting below, host Leila facilitates six independent practitioners: Amina, Rohan, Bea, Chen, Dev and Eva. They meet on 4 November 2026 from 10:00 to 11:30 London time. All six attend, can open the text agenda and have agreed to the format and minimal group notes. They choose no recording and retain the option to request a pause. Eva chooses to pass on an update, leaving that time unused rather than creating an obligation to fill it.

Run each thirty-minute member case

Five minutes to frame. Invite the presenter to state the question, relevant context and contribution they want. Restate the question and ask whether it is accurate. If the case expands into several decisions, let the presenter choose one that can be usefully explored in the available time.

Ten minutes to clarify. Ask for information before recommending a solution. “What has the customer actually requested?” seeks a fact. “Why don’t you insist on a meeting?” introduces a proposed answer. The facilitator can acknowledge the idea and reserve it for the options segment if the presenter wants options.

Ten minutes to explore. Ask permission to move into ideas or relevant experience. Members should distinguish something they tried from a universal rule. State assumptions, limitations and relevant commercial relationships. The presenter can reject an idea, ask for further questions or change the kind of contribution they need.

Five minutes to review. Ask what was useful, what remains unknown and what the presenter chooses next. An enquiry, a deliberate pause or no new action can be an appropriate result. Read back the agreed note and check it. A peer’s persuasive suggestion does not become the presenter’s commitment unless they actually choose it.

For more detail on a single focused case, see the coaching hot-seat facilitation guide. This agenda preserves a full process for each presenter and a separate resource exchange, instead of allowing unbounded advice to consume the entire meeting.

First case: discover what a customer means by updates

Amina, an illustrator, provides this completed brief: “A customer asked for better updates during a four-week project. I am considering a weekly video call but do not know what information they are missing. I have sent work when a draft was ready, without a regular status message. I want clarification questions and possible update formats. Please retain only my final enquiry, with no customer identity or draft images.”

At 10:15, she reads the approved version. During framing, Leila checks whether the question is “How do I make the customer accept a call?” Amina corrects it: she wants to understand what useful updates would contain before choosing a channel. Leila repeats that revised question and Amina confirms it.

Chen: Why don’t you put a weekly call in the contract?

Leila: That is one possible option. First, what do we need to understand?

Bea: What did “better updates” mean in the actual request?

Amina: They asked when they would next need to respond. I assumed they wanted to see me working.

Dev: Do you know whether they need work-in-progress images or just dates and decisions?

Amina: I haven’t asked. The images may create another review round.

The clarification exposes an assumption rather than a difficult customer. Amina knows the customer has requested more notice of response dates; she does not yet know the preferred channel or detail. Nobody displays the actual customer correspondence or offers a diagnosis of the relationship.

At 10:30, Amina agrees to hear options. Bea describes her own short written update, while noting that her customers and projects differ. Chen offers a scheduled call for complicated decisions. Eva suggests asking the customer which information is missing before choosing either format. Leila gives Amina time to compare rather than asking members to vote.

Amina chooses the enquiry first. Her proposed message is: “I want to make the updates useful. Would a Friday note covering completed work, the next step and any response date meet your need? Is there something else you need to see, or would a call help?” She will send it through the existing authorized project channel.

During the final five minutes, Leila reads the proposed group note: “Amina will ask the customer which update information and format would help, then report what she learns if she wishes.” Amina approves it. The customer has not yet agreed to Friday updates, and the group does not record that an arrangement has already been made.

Second case: reduce preparation without guessing what members need

At 10:45, Rohan presents a different question. He runs short professional-development workshops and has sent an eighteen-page preparation PDF before a session. Three attendees told him they did not know which parts mattered. He wants help making the preparation clear while preserving a useful starting point for the workshop.

His approved brief excludes attendee names and responses. He requests questions followed by options. During clarification, Bea asks what attendees must bring. Rohan says he only needs one ordinary work situation they want to discuss; the PDF contains much more background than that task requires.

Dev begins explaining how Rohan should advertise the workshop. Rohan says that is not his present question. Leila redirects the group to preparation and acknowledges the correction. This matters: protecting the agenda includes protecting the presenter’s chosen purpose, even when another member is enthusiastic about a different problem.

In the options segment, Rohan compares retaining the whole PDF with a marked required section, making all background optional, and replacing required reading with two short text prompts. He selects the prompts: “What ordinary situation would you like to explore?” and “What would make discussion of it useful?” Attendees can use a generalized example or say they prefer to discuss it privately.

He chooses to try the instructions with one willing former attendee before using them in the next workshop. The agreed note records the test, not a claim that the shortened preparation is already clearer. Leila reads it back, Rohan approves it and the second case closes at 11:15.

Exchange resources and introductions with real permission

From 11:15 to 11:25, members offer relevant resources rather than reopening both cases. An offer should identify what it is, why it might help and any relevant interest. A paid service recommendation should not be disguised as independent experience. The presenter remains free to decline.

Bea offers Amina a blank example of her own status-note headings, with no customer information. She owns the template and agrees that Amina may adapt it for this project. Amina accepts. Bea sends the promised version afterward, and Amina confirms receipt; the resource exchange has an actual completed output.

Dev offers to introduce Rohan to a facilitator he knows. Rohan says he does not need that introduction for this test. Dev accepts the refusal and shares no contact details. An offer is not a mandate to network, and declining it should not be framed as resisting help.

Chen separately asks Eva whether she would welcome an introduction to a public-speaking organizer. Eva agrees to receive a short description first. Chen later asks the organizer; the organizer declines because their programme is full. Chen tells Eva, and no contact details are exchanged. The completed action is obtaining and communicating a refusal, not “delivering an opportunity.”

Keep other possible follow-up bounded. If two members want a peer check-in, agree the channel, frequency, topic and option to stop. Joining the mastermind does not make a member responsible for monitoring another person’s finances, health or business compliance.

Close on time and send the agreed record

At 11:25, each member has up to thirty seconds to name a takeaway, chosen next step or pass. Six turns take at most three minutes. Eva again passes. Leila uses the final two minutes to confirm 18 November’s next meeting, the two willing next presenters and where members can find the approved notes.

The host does not turn the close into six compulsory public commitments. Rohan has chosen a test, Amina an enquiry, and another member may simply have gained a useful distinction. Nor does a high-energy close create evidence that anyone has already improved their business.

Afterward, Leila sends the agreed, minimal summary to the six intended members through their established client channels. Amina spots a mistake: the first version says she will “start Friday updates.” Leila corrects it to the approved enquiry and sends the correction to the same audience. All six acknowledge the corrected record. The customer’s answer still belongs in later follow-through.

Leila also asks one process question: “Did the timing and participation options let you contribute as intended?” Five members respond. Four found the structure usable; Rohan says the interruption during his case was frustrating despite the repair. Eva does not respond. Leila retains that mixed feedback and the missing response without calling it unanimous satisfaction.

Review the actual follow-through at the next meeting

On 5 November, Amina sends her enquiry. The customer chooses a brief Friday written note and asks for a clear response date when a decision is needed. They do not want a routine video call. Amina confirms the arrangement rather than inferring acceptance from silence.

Her 6 November note states: “The composition draft is complete. Next I will prepare the colour version. Please confirm the preferred palette by Tuesday; without that answer, the colour work remains pending.” The customer acknowledges it. On 13 November, Amina reports that the palette reply is still outstanding and asks again through their agreed channel. The update routine has not removed that dependency.

Rohan’s former attendee agrees to the small instruction test and reads the two prompts. They can identify the required preparation but interpret “ordinary situation” as a request for a full client case. Rohan adds: “A few sentences are enough; omit names and confidential details.” The same reader checks the revision and correctly describes what is requested. The next workshop has not yet occurred.

At the 18 November opening, both presenters report these actual observations within their ordinary two-minute turns. They decline another full case for now. The later meeting’s remaining agenda is separate from the ninety-minute meeting described above; it is not extra time hidden in the original allocation.

Amina keeps the agreed updates while the palette decision remains pending. Rohan keeps the revised prompts pending a real workshop trial. Leila carries forward a clearer redirection cue after Rohan’s feedback. None of these observations establishes a financial return or that the new host cue has already solved interruptions.

Keep commercial and personal information within suitable boundaries

Business peer groups need a process for competition-sensitive discussion. Australia’s ACCC industry-association guidance addresses risks from sharing sensitive information and recommended pricing, including exchanges through an intermediary. This is Australian guidance, not a legal assessment of every mastermind or a rule that applies identically in every country.

Use qualified advice for the group’s actual membership, countries and activities. Do not collect future competitor prices, agree customer allocations or ask a confidentiality promise to make an unsuitable discussion acceptable. Excluding obvious direct competitors alone is not a complete assessment.

If a member proposes a shared minimum-price schedule, stop that discussion and keep it out of the group record. Redirect only to an appropriate general process question, such as what information a business needs to evaluate its own costs independently. Do not turn the redirection into coordinated pricing instructions.

The same principle of purposeful disclosure applies to personal material. A case about an employee’s health or a customer dispute may need another setting and qualified support. A useful mastermind does not require members to expose information that the peers cannot appropriately handle.

Set up the agenda workflow in Coachful

Start with the actual client-group roster and intended session audience. Create the group session, finish the required scheduling steps and confirm the relevant members can access its details. Check series versus single-date scope before adding people: recurring group-session rosters can extend across upcoming dates that retain that audience.

Create the blank agenda and original case brief as resources. Deliberately deliver preparation to the intended active clients, then confirm access. Review private submissions as facilitator preparation, and obtain the presenter’s approval before reading an agreed version to the group. Resource creation alone does not establish delivery or consent to display an answer.

A submitted form’s Coach review is private to the authorized coach team; Reviewed or Follow up does not send that note to the member or put it in the response PDF. Communicate actual feedback separately. Likewise, completing a client Task records follow-through work, not another person’s acceptance of a proposed introduction or arrangement.

Check any community space’s audience before using it for shared takeaways. The demo image illustrates a community feed, not verified membership of Leila’s fictional group. Client groups, private submissions and community visibility serve different purposes. Leila’s agreed summaries use the established client channels, with only the approved content shared.

Review recording and recap arrangements before the meeting. Session recaps send automatically by default; approval controls and relevant Session Type overrides affect review before sharing. Agree the intended recipients and content before promising confidentiality or a reviewed summary. Explore Coachful’s features around those actual requirements.

Frequently asked questions

What if only one member wants a case?

Agree a revised process, such as one full case and a useful general question, or a shorter meeting. Do not pressure someone to provide material solely to fill the timetable.

Should members have to give advice?

No. Clarification, relevant experience, an idea or a pass can each be appropriate. Ask the presenter what contribution they want and separate professional advice from ordinary peer suggestions.

How should we rotate cases fairly?

Publish the available slots and voluntary rotation, keep a simple record and discuss adjustments. Fairness includes usable notice and the ability to decline, not merely assigning names to a calendar.

How do we know whether the agenda worked?

Check actual timing, whether presenters chose useful outputs, agreed-record accuracy and members’ feedback. Review later action separately. Attendance, enthusiasm or one success story cannot establish the format’s general effectiveness or return on investment.