Polyamory Agreement Template for Neurodivergent Partners
Standard relationship agreements fail neurodivergent people in predictable ways. They're vague where we need specificity, flexible where we need structure, and silent on the things that actually derail our relationships. Here's a template built around how ND brains work — with concrete sections you can actually use.
What This Template Covers
A neurodivergent-friendly polyamory agreement template uses specific, literal language instead of vague intentions. This guide walks through five template sections: communication protocols, time & energy allocation, boundary definitions, conflict resolution procedures, and review schedules — each with fill-in-the-blank examples you can adapt directly.
Why Standard Agreements Fail Neurodivergent People
Most polyamory agreements start with good intentions and end up in a drawer. For neurodivergent people — especially those with ADHD, autism, or both — the failure is structural, not motivational. Standard agreements break in three specific ways.
They rely on implicit understanding
The phrase "check in when you need support" assumes both partners can reliably detect their own needs in real time and initiate a conversation about them. For many autistic people, that detection is delayed or unreliable — the emotional processing comes hours or days after the event, not in the moment. By the time the need is clear, the window for "natural" check-in has long passed.
ADHD creates a different version of the same problem: impulsivity and emotional intensity can make needs feel urgent and obvious in the moment, then invisible an hour later. An implicit agreement to "communicate needs" doesn't specify when, how, or in what format — which means it doesn't actually function as an agreement at all.
They use language that means different things to different people
"Be available for me emotionally" can mean anything from daily text check-ins to a phone call within 24 hours of a hard event to just not canceling plans last minute. For neurodivergent people who process language literally, an agreement that doesn't define its terms isn't a shared understanding — it's a shared hallucination of one.
They ignore executive function entirely
Standard agreements assume that knowing what you're supposed to do is sufficient to do it. For ADHD brains, there's a well-documented gap between knowing and doing — especially for tasks that are ambiguous, emotionally loaded, or lack an external deadline. An agreement to "bring up grievances before they become resentments" requires the exact executive function skills (initiation, timing, emotional regulation, working memory) that ADHD compromises.
The agreement fails not because the person doesn't care, but because the agreement was designed for a brain that works differently.
What a Neurodivergent-Friendly Agreement Requires
A well-designed ND relationship agreement has four qualities that standard templates lack:
- Specificity over flexibility. Every section names concrete behaviors, not vague intentions. "I will text my capacity number each morning before 10am" is an agreement. "I'll try to communicate my needs" is a hope.
- Defined terms. Words with emotional valence — "available," "support," "overwhelmed," "space" — are explicitly defined within the agreement so both partners are working from the same dictionary.
- Sensory and capacity sections. Standard agreements address communication and intimacy but skip sensory needs, processing time requirements, masking recovery, and variable capacity — the exact factors that most affect neurodivergent relationship functioning.
- Built-in revision cadence. A static agreement becomes outdated as relationships evolve and life circumstances change. ND agreements should include scheduled review dates as part of the document itself, not as a future task to remember.
The template below is a starting framework, not a finished document. Every section contains fill-in prompts — things you and your partner(s) answer together to create your specific agreement. The goal is a document you can actually reference during conflict, not a statement of ideals that sits unread.
Not Sure Where Your Relationship Needs the Most Structure?
Our free 5-minute relationship quiz identifies the gaps in your current agreements — and which sections of this template to prioritize first.
Take the Free Quiz →Template Section 1: Communication Protocols
This section is the most commonly underdefined — and the most consequential. It covers how partners communicate in different states, not just when things are fine.
Daily Check-in Format
We agree to share a daily capacity signal by [time, e.g., "9am"] via [method, e.g., "text message"]. Our capacity scale is [e.g., "1–10, where 1 = crisis/unavailable and 10 = fully resourced"].
A signal of [number] or below means I need [what, e.g., "no initiated conversations, just acknowledgment"]. Partners agree not to interpret a low signal as rejection or withdrawal of care.
Preferred Communication Channels
- For logistical coordination: [e.g., "shared calendar + text"]
- For emotional content: [e.g., "voice call or in-person only — not text"]
- For conflict or difficult topics: [e.g., "written message first, then scheduled call within 48 hours"]
- For urgent needs: [e.g., "phone call; if no answer, one follow-up text; no more"]
Response Time Expectations
During standard hours ([e.g., "9am–9pm"]), I will respond to non-urgent messages within [e.g., "4 hours"]. During low-capacity periods, I will send an acknowledgment within [e.g., "24 hours"] and give a realistic response timeline.
Silence for more than [e.g., "12 hours"] during a known conflict means: [e.g., "I am overwhelmed and need time; it is not abandonment"].
Processing Time
When I say "I need time to process," that means I will return to the conversation within [e.g., "24–48 hours"] with a specific time to reconnect. It does not mean the topic is dropped.
For more context on building communication systems that work with neurodivergent processing styles, see our guide on neurodivergent relationship communication.
Template Section 2: Time & Energy Allocation
This section is the one most poly agreements skip entirely — and the one most likely to cause resentment when left undefined. Time and energy aren't the same thing; this template tracks both.
Baseline Time Commitments
We agree to a baseline of [e.g., "one in-person date per week + one async check-in mid-week"]. Changes to this baseline require [e.g., "48 hours' notice except in emergencies"].
Solo time (no partner contact) is a non-negotiable part of my schedule. I need [e.g., "at least two evenings per week"] of unscheduled time for recovery. This is not rejection; it is operational infrastructure.
Sensory and Recovery Needs
My sensory needs that affect relationship availability include: [e.g., "low-noise environments for emotional conversations; no scented products when I need to be emotionally present; no unexpected touch during re-entry from social events"].
After high-stimulation environments (work events, crowded dates, large social gatherings), I need approximately [e.g., "12–24 hours"] of reduced social contact before I can engage relationally at full capacity.
Masking Recovery
When I have spent significant time masking in professional or social settings, I may need [e.g., "several hours of low-demand time before I am available for emotional conversation"]. This does not mean I don't want to connect — it means I need to refill before I can give.
Capacity Overflow Protocol
When I am over capacity and a partner needs connection, our agreed approach is: [e.g., "I will offer a 15-minute check-in now + schedule a full conversation within 48 hours, OR offer async written support if real-time is not possible"]. Partners agree this is an acceptable response, not a rejection.
For a full framework on tracking capacity across relationships, see our guide to polyamory capacity planning for neurodivergent partners.
Template Section 3: Boundary Definitions
Boundary agreements fail most often because they use the word "boundary" to mean many different things simultaneously. This section separates three distinct categories and defines each explicitly.
Hard Limits (Non-Negotiable)
Hard limits are behaviors that are not subject to negotiation, circumstance, or partner persuasion. They require no justification.
My current hard limits include: [list explicitly — e.g., "no unprotected sex with new partners without mutual discussion", "no overnight stays at a metamour's home during our scheduled connection weekends", "no canceling our weekly date with less than 24 hours notice except for emergencies"]
If a hard limit is crossed, the agreed immediate response is: [e.g., "pause the situation, have a same-day conversation to assess impact and next steps"]
Soft Limits (Negotiable With Process)
Soft limits are things I have concerns about but am open to discussing if my partner wants to revisit them. Revisiting a soft limit requires: [e.g., "advance written notice of the request, my explicit agreement to have the conversation, and no decision made in the same session it's raised"]
My current soft limits include: [list]
Preferences (No Limit, But Matters to Me)
These are things that aren't limits but that I'd like partners to be aware of and factor in when possible: [e.g., "I prefer knowing about dates in advance even when not required; I appreciate a heads-up if a metamour is visiting a space I also use"]
Boundary Language We Use
In our relationship, the phrase "I need space" means: [define it]. The phrase "I'm overwhelmed" means: [define it and what response it requires]. The phrase "I'm not available right now" means: [define timeframe and follow-up expectation].
Template Section 4: Conflict Resolution Procedures
Neurodivergent people often experience conflict differently: the emotional dysregulation can be more intense (ADHD), the processing can be slower (autism), the triggering can be easier (RSD), and the recovery can take longer. An agreement that assumes neurotypical conflict patterns will fail in these moments.
Initiating a Conflict Conversation
Either partner can request a conflict conversation using this format: [e.g., "I have something I need to talk through. Can we find time in the next 48 hours? It's about [topic], it's [urgency level], and I estimate I need about [time]."]
The receiving partner will respond with a proposed time within [e.g., "24 hours"]. If that's not possible, they'll explain why and offer an alternative timeline.
During a Conflict Conversation
We agree to these ground rules: [e.g., "one person speaks at a time; no interrupting; either partner can call a 20-minute break without explanation; no decisions made when either person is visibly dysregulated"]
If emotional dysregulation escalates, the agreed pause signal is: [e.g., "a raised hand or the word 'pause'"]. This triggers a [e.g., "20-minute"] break with a specific return time. Calling a pause is not ending the conversation.
After a Conflict
After a significant conflict, we agree to a follow-up check-in within [e.g., "72 hours"] to confirm resolution and assess whether anything needs to be written into our agreement. The format for that check-in is: [e.g., "brief written exchange before any call"]
We do not consider a conflict resolved until both partners have explicitly stated they feel complete. Silence after a difficult conversation does not equal resolution.
RSD and Interpretation Protocols
If a partner interprets something as rejection or criticism, they agree to check that interpretation before responding to it. The check looks like: [e.g., "stating the interpretation out loud — 'I'm reading this as X — is that accurate?' — before acting on the feeling"]
The receiving partner agrees to answer that check directly and specifically, not defensively.
Template Section 5: Review Schedule
The single most common reason relationship agreements fail over time is that they're treated as a one-time conversation. Relationships change. Capacity changes. What worked in your first year may need updating in your third. Scheduled reviews turn a static document into a living one.
Regular Review Cadence
We will review this agreement every [e.g., "3 months"], scheduled in advance on: [e.g., "the first Sunday of the month following the 3-month mark"]. Reviews are non-negotiable standing appointments, not optional check-ins.
For each review, both partners will prepare written notes in advance covering: (1) what's working well in the agreement, (2) what isn't working or needs updating, (3) any new needs or circumstances to address.
Triggered Reviews
Either partner can request an unscheduled review when: [e.g., "a significant life change occurs (new job, health event, new partner, major shift in living situation), when the same conflict occurs more than twice, or when either partner feels the agreement no longer reflects how the relationship is actually working"]
A triggered review request will receive a scheduled time within [e.g., "one week"].
Version History
Each reviewed agreement includes a date and brief summary of what changed. This creates a record of how the relationship has evolved and prevents retroactive disputes about what was agreed when.
Current version: [date] — [brief summary of major items in this version]
Turn This Template Into a Living Agreement
NeuroRelate's living agreements feature lets you and your partner(s) fill in, store, and revisit your agreement together — with built-in review reminders and version history. No more agreement in a doc you can't find.
Take the Quiz to Get Started → See a Demo FirstHow Living Agreements Handle This Differently
The template above works as a Google Doc or printed sheet. But there's a structural limitation to static documents: they don't update themselves, they don't send reminders, and they don't adapt when circumstances shift.
This is exactly the problem that living agreements — dynamic, tracked, revisable relationship documents — are designed to solve. And it's particularly relevant for neurodivergent partners whose capacity and needs change more variably than standard agreement models assume.
What changes with a dynamic agreement system
| Challenge | Static Template | Living Agreement |
|---|---|---|
| Review cadence | Relies on both partners remembering | Scheduled reminders, automatically surfaced |
| Capacity changes | Requires a new conversation and doc update | Capacity signals tracked and visible to partners in real time |
| Conflict history | Memory-dependent, often contested | Resolution notes tied to specific agreement sections |
| Version tracking | Manual, usually forgotten | Automatic — every update is dated and diff'd |
| ND-specific needs | Present only if you remembered to include them | Structured sections for sensory needs, capacity, masking recovery |
NeuroRelate's living agreements feature was built specifically around this use case. Rather than one conversation that produces one document, it's a structured, ongoing system where agreement sections can be updated individually, review dates are built in by default, and capacity signals from both partners inform what sections need attention.
For the broader context on what makes relationship agreements work long-term in poly relationships, see our foundational guide to relationship agreements for polyamorous couples.
Ready to Build an Agreement That Actually Works?
Take the free relationship quiz to see where your current agreements have gaps — then use NeuroRelate to build a living version that adapts as your relationships evolve.
Take the Free Quiz → Explore the DemoKey Takeaways
- Vague language is the most common agreement failure for ND partners — replace "communicate when stressed" with specific trigger + action language.
- Five template sections cover the essentials: communication protocols, time & energy, boundary definitions, conflict resolution, and review schedules.
- Build in a review schedule from day one — quarterly is standard, plus a trigger for any major life change.
- Conflict resolution procedures need to be written before the conflict happens — scripted steps are available when executive function is low.
- Living agreements handle ND needs better than static contracts because they're designed to be updated, not enforced.