AI Rotating Facilitation Rehearsal: Practice the Handover

As of 2026-10-23 · The AZET team. Written by the AZET team as a creative reference exercise for fun and practical exploration. All examples are hypothetical, not evidence of AZET product capabilities. This is the article reference date, not a current product verification date.

“I am handing over the speaking queue, not the choice of ending. Two people are waiting, and the group has not agreed to extend this round.” That is the handover line in a fictional story circle. It names the unfinished process without giving the incoming facilitator permission to settle the story.

This rehearsal uses three participants developing an imaginary tale about a wandering lighthouse. Each person facilitates one short round. No finished story is required; the artifact is a short script showing how authority changes hands.

Give the facilitator a narrow mandate

For this exercise, the group agrees that a facilitator may maintain the speaking queue, restate the current task, and call the planned pause. They may propose a process adjustment, but the group must accept it. They may not select the ending, rewrite another person's contribution, or describe silence as agreement.

The facilitator remains a contributor, but labels a personal suggestion before making it: “Speaking as a participant, I prefer the lighthouse to stay.” After that contribution, they return to the queue. The label distinguishes a preference from a direction without requiring the person to abandon their creative interest.

Rehearse the switch, including the awkward moment

Use three imaginary people: Ada, Rowan, and Ellis. Ada facilitates the opening round about the setting. Rowan then facilitates the round about the obstacle. Ellis takes the final round about possible endings.

At the first switch, Ada has an unanswered suggestion about moving the lighthouse inland. Rowan likes it and says, “Since I am leading now, let's use Ada's version.” Pause the rehearsal there. Rowan has treated control of the process as control of the content.

A repaired exchange could read:

Ada: The inland idea is still a proposal. Ellis is next in the queue.

Rowan: Understood. I now hold the queue. Ellis speaks next; afterward, we can decide how to compare the proposed obstacles.

Ada: I am returning to a participant role and will wait for my turn.

Carry process state across the boundary

At each handover, transfer four pieces of information: the active task, the next speakers, the remaining round boundary, and any unresolved process request. Do not add a recommendation about which idea should win unless it is clearly presented as a participant's view.

Suppose Ellis has asked for a quiet writing interval, but the group has not considered that request. Ada passes it to Rowan as “writing interval proposed; not agreed.” Rowan can bring the proposal to the group. Reporting it as “we are doing silent writing next” would convert a pending request into a decision during the switch.

The incoming facilitator should acknowledge the transfer in their own words. That gives the outgoing person a chance to correct a missing queue entry before stepping back. The handover ends when the incoming facilitator has accepted the process state, not merely when the timer sounds.

An exact prompt for a practice script

The following prompt specifies a hypothetical AI writing exercise. Read and rehearse any draft before using it with people:

Write a fictional rehearsal for Ada, Rowan, and Ellis in a story circle.
Story topic: a wandering lighthouse. Facilitation rotates in that order.
Allowed authority: maintain the speaking queue, restate the active task,
and call the planned pause. Process changes require group agreement.
Facilitators cannot choose story content or treat silence as consent.
Create two handovers. At the first, Rowan accidentally claims authority
to select an obstacle. At the second, include an unresolved request for
quiet writing. Show a brief correction and an explicit acceptance of
the queue at each switch. Label personal creative suggestions.
Keep disagreement possible. Do not invent a unanimous story decision.
End with three observer checks about authority, not personality.

A draft that ends with everybody enthusiastically accepting the same ending misses the rehearsal's purpose. Leave a content disagreement unresolved so observers can examine whether the process remains usable without creative agreement.

Observe verbs and interruptions

Ask an observer to underline verbs such as choose, require, accept, propose, and record. Compare each one with the facilitator's mandate. “I propose another minute” and “I require another minute” assign different authority even when spoken gently.

Track interruptions at the switch. If the outgoing facilitator keeps answering every process question, the role may have rotated in name only. Rehearse one clean response: “Rowan holds the queue now.”

For a second attempt, change the interruption rather than memorizing the first script. Let a participant ask for an immediate content vote. The incoming facilitator should identify whether that process was agreed, then handle the request within the same boundaries.

FAQ

Should the incoming facilitator inherit the previous person's preferences?

No. They inherit the agreed process state. Creative preferences remain attributed contributions, including any preference held by the person now facilitating.

What if someone does not want a facilitation turn?

Offer a rehearsal observer role or postpone their turn. Record the changed order explicitly so the next switch does not depend on an assumption that everyone accepted.

Can the group change the facilitator's authority midway?

Yes, by making and accepting an explicit process change. State what changed and when it applies. Do not infer expanded authority from a facilitator's confident wording.

The maker introduction labeled E1, dated October 3, 2026, described an assistant and an early-access waitlist. This role rehearsal is an editorial exercise, not a demonstrated AZET function or an update to that dated description.

For interest in AZET and its waitlist, visit azet.io.