Chapter 6 - Textbook

Boundary work in facilitation operates across three distinct domains, each with its own risk profile and its own set of bright lines — the limits that cannot be crossed regardless of participant preference or contextual pressure.

Within each boundary domain, there are bright lines — limits that cannot be adjusted regardless of participant request, contextual pressure, established rapport, or the facilitator's belief that an exception is warranted in this case. Bright lines are not negotiated during the Touch Contract. They are stated clearly as non-negotiable parameters of the facilitation relationship.

• Physical bright lines: Sexual touch in any form, at any time, under any framing. Touch that is maintained against a participant's expressed or behavioral withdrawal. Touch during active sexual transference without immediate halt and supervision escalation.
• Emotional bright lines: Romantic or sexual relationship with a current participant. Personal financial transactions of any kind. Accepting significant gifts. Social relationship that began during or after facilitation, within the timeframe specified in the facilitator's boundary policy.
• Digital bright lines: Sharing unencrypted participant information across any channel. Social media friendship with current participants (policy-dependent, but generally a bright line). Communications that would not be appropriate in a session — at any time of day or night, in any channel.

The purpose of naming bright lines explicitly is not to create defensiveness — it is to make the discussion of boundary clarity a normal part of professional identity, not a topic that only surfaces when something has gone wrong.

Every facilitator should have a written boundary policy — a clear, plain-language statement of what participants can and cannot expect from the facilitation relationship across all three domains. This document is shared with participants as part of the intake and consent process. It is not a legal disclaimer — it is a communication of professional structure that helps participants know what the relationship is before they are in an altered state and potentially less able to evaluate it. The boundary policy is a portfolio artifact in this module.

The Touch Contract is a specific, explicit, revisable agreement about what physical contact — if any — is welcome during a session, under what conditions, initiated by whom, and revisable at any moment. It is separate from the general session consent conversation. It must be conducted before each session. A Touch Contract from a previous session does not carry forward.

The Touch Contract is not a waiver. It is not a form signed at intake that covers all future contact. It is not implied by the participant's general willingness to be in the room with you. A participant who says "yes, I'm comfortable with touch" has told you something useful — and nothing more. The specific conversation — what kind of touch, where, when, and how they signal they want it to change — still needs to happen.

Colorado regulation specifies six required elements for the Touch Contract conversation. These are not optional enhancements — they are the minimum for a compliant consent dialogue:

• (1) Participant-directed preferences — the facilitator opens genuine space for the participant to define their own relationship with touch: "I want to understand what feels right for you specifically — not in general, but in the context of this kind of work." The facilitator does not present a menu and ask the participant to check boxes. The participant defines the terms.
• (2) Grounding touch options — the facilitator explains specifically what is available: a hand on the shoulder, forearm, or upper back. For each, the participant indicates yes, no, or "only if I ask." Nothing beyond these areas is within scope, regardless of participant request.
• (3) Capacity limitations post-ingestion — the facilitator explains directly that after the medicine is ingested, the participant's ability to communicate and revoke consent may be limited. The standard stated clearly: if there is any ambiguity in the moment — if the participant cannot clearly confirm a yes — the default is no touch. A participant who is unresponsive, frozen, or unable to communicate is not consenting. This must be stated before ingestion, when the participant can fully receive it.
• (4) Co-facilitator option — the participant is offered the genuine option to request a co-facilitator or second person present for any part of the session. This must be presented as a real option, not as a procedural disclosure. "Some participants prefer to have a second person in the room — that's completely available to you and changes nothing about the quality of care you receive."
• (5) Recording option — the participant is informed that some participants choose to have a video recording made of the session, for their own later review or as an additional protection mechanism. Consent to record requires its own explicit agreement and documentation.
• (6) Opt-out mechanism and default — the participant is told the specific signal they can use at any point: "You can say 'no touch,' 'stop,' or just move away — and I'll honor that immediately without asking for an explanation. And if you want no touch at all throughout the session, that is a completely valid outcome of this conversation." No touch is always the default when there is any ambiguity.

During a session, if a moment arises where supportive touch might be helpful: offer it explicitly, don't apply it. "I'd like to put my hand on your shoulder — is that okay?" is correct. Moving closer and placing a hand is not, even if the Touch Contract was agreed earlier. The offer is what keeps the agreement active — it gives the participant a real decision point at the real moment, not just a pre-session abstraction.

If the participant declines or withdraws from touch at any point — verbally, by moving away, or through clear body language — stop immediately and do not offer again in that session unless the participant explicitly reinvites contact. A participant who says "yes" in the Touch Contract and "no" in the moment has updated their consent. The current communication supersedes the prior agreement, always.

Document the Touch Contract conversation in the session note: what was offered, what was agreed (including if the participant declined all touch), and any specific preferences or conditions stated. If touch was used during the session — document what, when, how it was offered, and that consent was confirmed in the moment. A brief note is sufficient: "Touch Contract reviewed — participant agreed to grounding hand contact on shoulder if offered. At approx. 2:40pm, facilitator offered hand contact on shoulder, participant nodded agreement, contact maintained 2 minutes."

Not all boundary events are equivalent, and conflating them produces both under-response (treating violations as crossings) and over-response (treating normal facilitation as a boundary issue). The actual curriculum uses four levels of severity — not a simple crossing/violation binary — because the correct response is proportionate to the classification:

• A — Bright-Line Violation: A clear breach of a non-negotiable limit. No ambiguity about classification. Examples: sexual touch of any kind; misrepresenting scope or outcomes to a prospective participant; sharing participant information without consent. Response: immediate halt, mandatory supervisor contact, regulatory reporting evaluation. Not repairable through apology alone.
• B — Violation: A serious breach that causes or risks significant harm — but may have some contextual ambiguity. Examples: initiating contact that exceeds the Touch Contract even in response to participant behavior; dual relationship that exploits residual power; post-service social contact before the required waiting period. Response: supervisor contact required, possible reporting obligation, documentation, serious professional consequence evaluation.
• C — Crossing: A minor, inadvertent, or situationally ambiguous departure from the established boundary — typically unintentional and not causing significant harm. Examples: adjusting a pillow without asking; holding a hand briefly outside the Touch Contract in response to participant distress; responding to a message outside stated communication hours. Response: the repair protocol — acknowledge, apologize, reaffirm the standard, document, bring to supervision.
• D — Not a Boundary Issue: Normal facilitation behavior that may superficially resemble a boundary event but does not constitute one. Examples: brief purposeful self-disclosure that normalizes participant experience without centering the facilitator; adjusted fee documented clearly in the service agreement. Response: no action required, though the classification itself may be worth reflecting on.

The key distinguishing question between B and C is not intent — it is whether a bright line was breached and whether the event caused or risked significant harm. The key distinguishing question between C and D is whether the event actually departed from an established boundary, or simply looked like it might have.

Repair is the facilitator's professional obligation when a crossing has occurred. The goal is not to eliminate the crossing from the record — it is to restore the participant's sense of safety, reestablish the boundary clearly, and document the event and the repair honestly. A repair done well often results in a stronger professional relationship than one where nothing ever needed repair. A repair done poorly — defensively, minimally, or not at all — damages trust in ways that compound over time.

Every facilitator needs a clear, written communication channel policy — shared with participants at intake — that specifies which platforms are used for what purposes, what the response timing expectations are, and what falls outside the bounds of appropriate facilitator-participant communication regardless of channel. This is not bureaucracy. It is the digital equivalent of the boundary policy: a professional communication of what the relationship is before the participant is in an altered state and potentially less able to evaluate it.

Minimal-data documentation means capturing only the information required for safe, effective facilitation — and capturing it in ways that minimize exposure. In practice this means: no substance specifics in session notes (note "participant consumed the natural medicine" — not dosage, compound, or source); no identifying session content in unsecured channels; no participant photographs or recordings without explicit written consent; no retention of communications beyond the policy-specified period; and no sharing of participant information across platforms, even with the participant's casual approval in a text message. Secure, encrypted storage for all documentation. For facilitators operating in CO or NV, the regulatory requirements for documentation security are specific — know them before your first session.

The digital boundary most commonly tested is social media. The general standard: current participants are not social media connections. Former participants require a policy-defined waiting period before any social connection is appropriate. Content posted to professional accounts must meet the same standards as any other public-facing communication — no clinical claims, no outcome guarantees, no jurisdiction misrepresentation. Content that is appropriate in a friend context (personal opinions, political positions, lifestyle content) requires judgment about whether it serves or undermines participant confidence in the professional relationship.

An important related point: what you post publicly, as a facilitator, is part of your professional profile. Participants will read your social media before, during, and after the facilitation relationship. Content that reads as appropriate in a personal context may read differently when viewed by someone who is in an altered-state vulnerability relationship with you. The standard is not perfection — it is professional awareness.