Ground rules for meetings: Examples and a checklist

Ground rules for meetings define the behavior expected of everyone taking part, as this definition of meeting ground rules explains. For an event-company production review, workshop, or leadership meeting, make those expectations specific: how to contribute, challenge a proposal, share information, and confirm a decision. Choose rules the host can apply, explain exceptions before participation, and finish with a written decision record.

Key takeaways

• Choose participation rules from the meeting’s purpose, then ask participants to identify unclear or unworkable expectations.
• Separate permission to contribute from authority to approve changes.
• State what people may photograph, record, quote, or circulate before asking them to share sensitive information.
• Give every rule an owner, an exception path, and a response the host is prepared to use.
• Test an AI drafting step only after establishing a clear human-approved version of the rules.

Start with the purpose and each participant’s responsibilities

Priya Parker distinguishes inherited social expectations from temporary rules created for a particular gathering in The Art of Gathering: How We Meet and Why It Matters. Apply that distinction to event operations by asking what participants need to know for this meeting, rather than assuming they share the same professional habits. Write those expectations into the invitation and the host brief.

Start with a sentence such as: “We will review the proposed schedule changes and decide which are ready for production approval.” If that purpose is still unclear, use the questions in our guide to defining an event’s purpose before drafting participation rules. For a creative workshop, choose different expectations about when to introduce constraints and when to evaluate ideas.

Ask the people attending to review the draft against their responsibilities in the meeting. Ask a first-time participant which terms need explanation, and ask a returning participant which expectations differ from previous sessions. Ask the host what they will do when someone interrupts or challenges a decision. Ask anyone responsible for communications what material they expect to share afterward.

Assign responsibilities before the meeting. The host manages participation, the decision owner approves or declines proposals, and the record owner captures decisions and unresolved issues. One person may hold several roles, but name each responsibility separately. Invite everyone to challenge a proposal without implying that everyone has authority to approve it.

Use these seven ground rules as a starting template

The Conference Board’s guidance distinguishes broad aspirations, such as respect, from behavioral rules that describe specific actions. Follow that approach when adapting the template below. Ask participants to suggest changes before accepting it as the meeting’s agreement.

1. Review the current materials and disclose gaps

Name the document and version participants should review, such as the proposed run of show or open-issues list. Ask anyone missing information to say so before the relevant discussion. Keep “not reviewed,” “reviewed with concerns,” and “approved” as separate states in the decision record.

2. Keep one conversation and make room for a response

Ask participants to finish their point without starting a side conversation. Before returning to someone who has already spoken, invite contributions from people who have not yet responded. Offer a written contribution route, and allow people to pass rather than requiring an immediate public answer.

3. Challenge the proposal with a reason and a question

Ask participants to identify the assumption, dependency, or constraint behind an objection. A useful contribution might ask whether the proposed crew call accounts for the venue access window. Do not require a complete solution before accepting a concern, and ask the decision owner to acknowledge what still needs checking.

4. Check the connection before deferring a topic

Before moving an issue aside, ask how it affects the decision under discussion. The Conference Board warns that treating a contribution as irrelevant without testing that assumption can exclude information needed for the decision. If the group agrees to defer it, record an owner and a return point rather than leaving it on an unassigned list.

5. Follow the stated sharing and recording permissions

Specify whether participants may take photos, record audio, use a transcription tool, attribute comments, or circulate working materials. Define approved recipients and any permission process for wider distribution. Keep a participation instruction separate from a confidentiality guarantee, and have the appropriate owner review sensitive wording before publication.

6. Use devices for the task and declared operational needs

Ask participants to use devices for meeting materials, accessibility needs, and agreed operational coverage. For an on-call responsibility, agree on a discreet way to step out and return. Treat a device restriction as a choice to justify, rather than a default, and provide a private way to request an accommodation.

7. Confirm the decision, owner, and remaining conditions

Before closing an item, ask the decision owner to state whether it is approved, declined, or pending. Have the record owner read back the action, responsible person, and conditions that remain unresolved. Never treat a suggestion, an unchallenged statement, or silence as recorded approval.

Introduce the rules before the production review starts

Use a production-review pattern to put the template into practice: a proposed schedule change needs input from production, creative, account leadership, and venue coordination. Frame the meeting around the change and its dependencies. Use the example to work out who contributes and approves the change, then adapt those responsibilities to your own meeting before sending the invitation.

Before sending the invitation, prepare a short participation agreement alongside the decision materials. Include the purpose, required preparation, decision owner, sharing permissions, and exception contact. Put any condition that could affect someone’s willingness to participate where they can see it before accepting.

Use this implementation checklist:

• Name the exact decision or output expected from the meeting.
• Link the current materials and identify anything still awaiting verification.
• Publish the rules wherever participants receive the meeting instructions.
• Assign the host, decision owner, record owner, and exception contact.
• Prepare a neutral intervention for each rule the host intends to enforce.
• Keep an approved copy of the rules with the final meeting record.

At the opening, ask which instruction needs clarification before discussion begins. Ask a participant to explain the sharing rule in their own words, and ask the decision owner to confirm their authority. Revise unclear wording instead of treating a lack of questions as agreement.

During the review, invite each relevant function to name constraints before asking for approval. If a venue access question emerges, ask whether it changes the proposed schedule. When it does, record the dependency and leave approval pending until the responsible person verifies it.

At the close, read back the decision and unresolved conditions. Use the same wording in the follow-up record, with a link to the approved document version. If you need a separate check on how participants experienced the process, adapt the prompts in our guide to choosing meeting feedback questions.

Resolve exceptions without weakening the agreement

Avoid choosing between unrestricted participation and a rule so rigid that people cannot meet legitimate responsibilities. Guidance on meeting ground rules explicitly allows different expectations for different objectives and participants. Make those choices before the session wherever possible, including what qualifies for an exception and who can authorize it.

Permit task-related device use and agreed on-call coverage, and ask participants to step outside when taking unrelated calls. Offer both speaking and writing options so participants can contribute without having to disclose a private need. When setting discussion limits, explain how participants should raise a concern that must be checked before a consequential decision, even if the ordinary discussion time has ended.

Use a decision rule for enforcement: keep a rule only if the host can explain its purpose, describe acceptable behavior, handle a reasonable exception, and respond consistently to a breach. If any part is missing, narrow or rewrite the rule before publishing it. Apply that test to senior participants and sponsor representatives as well as everyone else.

Prepare the response as carefully as the instruction. For an interruption, pause and return the floor to the original speaker. For an unauthorized recording, ask for recording to stop, involve the designated owner, and follow the approved procedure without promising that every copy can be recovered.

Be especially careful with silence. A facilitation resource describes several possible meanings of silence, including reflection, confusion, resistance, and agreement. Ask for an explicit decision response, while allowing a participant to say they need more information before supporting a proposal.

Test AI for wording consistency, with a human owner

If you test AI, limit its role to drafting and checking whether the documents give consistent instructions. This test is separate from Parker’s gathering principles. Compare the invitation, host brief, opening slide, and follow-up template against one human-approved participation agreement. Keep approval of the rules and their enforcement with the host.

Start with generic materials and no live participant information. Ask the AI to flag conflicting sharing permissions, undefined approval roles, missing exception routes, and promises that exceed the approved agreement. Require each proposed edit to identify the conflicting passage and explain the ambiguity rather than silently rewriting every document.

Give the meeting owner responsibility for accepting or rejecting edits. Keep the approved version available for comparison, and require a fresh review whenever the meeting format or audience changes. For any proposed use involving operational information, use our production trust and claims boundary as a starting point for reviewing the exact data, permissions, retention, and permitted actions.

Before expanding the test, compare the AI-assisted review with a review done entirely by people to see whether it helps. Use comparable document sets and record the same observations for each approach. Do not judge the AI draft by fluency alone.

• Record contradictions found and whether a reviewer confirmed each one.
• Test whether readers can explain sharing permissions and decision authority accurately.
• Note repeated clarification questions and requests for exceptions.
• Check whether the host can apply every published rule using the prepared response.
• Record unsupported promises, unnecessary clauses, and edits the reviewer rejects.

Keep the AI step only if the review shows a useful improvement in consistency without unacceptable review burden or unresolved information-handling concerns. If a shared template and a human check meet the need, retain that simpler process. Stop the test if the owner cannot reliably identify the approved instructions.

Frequently asked questions

What are the 7 ground rules for effective meetings?

Use these seven as an adaptable set: review current materials, keep one conversation, challenge with reasons, check relevance before deferring, follow sharing permissions, agree on device use, and confirm decisions explicitly. Choose the wording with participants and name who will apply it. Treat this as a starting template rather than a universal standard.

What are good ground rules for a meeting?

Choose rules that describe observable behavior and serve the meeting’s purpose. For a production approval, specify how participants raise unresolved dependencies and who can authorize a change. For a workshop, specify how people contribute and when evaluation begins.

What are some good ground rules for sensitive discussions?

Start with explicit instructions about recording, attribution, note circulation, and permission to share outside the group. Allow participants to decline a question or request clarification. Ask the responsible owner to approve the wording, and avoid promising confidentiality beyond what the organization can support.

What are the 5 P's of meetings?

For this checklist, use purpose, people, preparation, process, and product as a planning aid. State why the meeting is needed, who contributes and decides, what they should review, how discussion will work, and what written output should remain. Use the participation rules to make the process understandable before people attend.

Choose one meeting and assign the host

Select one recurring production review or planning workshop and appoint an owner to revise its participation agreement. Ask that person to test the sharing instructions, exception route, and decision readback before adding any technology. Bring the approved agreement and its unresolved handoffs to a review of your event operations. We look at how your team runs an event and show you what we would make more efficient.