Every long-running CNM relationship ends up with some version of a written or spoken agreement, even if nobody ever calls it that. What varies enormously is the content: a hierarchical couple who opened up after a decade of marriage needs different clauses from a non-hierarchical polycule that formed organically, and both need different clauses again from two people managing a relationship across a time zone. There's no universal template, and treating one relationship's agreements as a checklist for another is a reliable way to import problems that were never yours to begin with.

What follows are annotated example clauses drawn from real patterns in CNM relationships, organised by the relationship shape they tend to serve. Each comes with a plain explanation of the concern it's actually addressing, because a clause copied without understanding its purpose tends to either miss the point or outlive its usefulness. Before writing anything down, it's worth understanding the difference between a clause that reflects a genuine, jointly-held agreement and one that's really a rule dressed up in agreement language, covered in detail in our guide to agreements vs rules in open relationships. That distinction is the frame underneath everything below.

A note before the examples: none of this is a legal document template, and nothing here should be treated as a contract with legal force. If your situation touches cohabitation, marriage, or shared property, an agreement between you and your partners is a relational tool, not a substitute for independent legal advice from a solicitor.

What makes a clause worth keeping

Not every clause below will suit every relationship, and a few are presented with the tension left visible rather than resolved, because the honest version of most CNM agreements has some tension in it. A clause is worth keeping if it does three things: names a genuine concern rather than a hypothetical one, was actually agreed by everyone it binds rather than imposed by whoever felt most anxious, and specifies what happens when circumstances change. Clauses that fail the third test tend to calcify into the kind of rules that don't survive contact with reality.

Hierarchical relationships

In hierarchical polyamory, one relationship, usually a marriage or long-term nesting partnership, has an acknowledged priority over others in specific, named ways. The clauses that work best here make the hierarchy explicit rather than leaving it as an unstated assumption that outside partners discover the hard way.

Disclosure before a new connection becomes physical

Before things become sexual with someone new, I'll tell you who it is, roughly how it started, and give you the chance to ask questions before it goes further. I won't ask permission, but I will give you the information in time for it to be useful.

This clause distinguishes disclosure from veto. The primary partner isn't being asked to approve the connection, they're being given enough runway to flag something, a chaotic ex, a mutual friend who complicates things, a documented bad history, while it's still useful information rather than retrospective commentary. The timing detail matters: too early and it kills the freedom to explore low-stakes connections; too late and the disclosure loses any practical use it had.

Time and priority commitments, named explicitly

Weeknights are reserved for our household unless we agree otherwise in advance. Major life events, the holidays we've always shared, family occasions, get first claim on the calendar. Outside relationships get real time too, but scheduling conflicts default to the household unless we actively decide otherwise.

This clause protects the nesting relationship's logistics without pretending the outside relationship doesn't deserve real time. Vague commitments to prioritising the primary relationship tend to produce resentment on both sides: the primary partner feels it's not honoured in practice, and the outside partner never learns what they're actually entitled to. Naming the actual defaults turns an abstract hierarchy into something both partners and metamours can plan around.

Influence instead of veto

If either of us has a serious concern about the other's outside relationship, we'll raise it directly and expect it to be taken seriously. Ending that relationship because of the concern is a decision the person in it makes, not a right the other person holds unilaterally.

This is the version of hierarchy that avoids the sharpest criticism of veto power: it gives a nervous partner a real channel for concerns without giving them unilateral control over someone else's relationship, including one belonging to a person they've never met. Couples who start with a nuclear veto, "I can end it, no discussion", often walk it back once an outside partner they actually respect is the one it would apply to.

A shared health and safer-sex baseline

We test for STIs every three to six months, sooner after any higher-risk contact, and share results honestly. Barrier use with outside partners is the default; any change to that gets discussed before it happens, not after.

Testing cadence should track actual risk rather than a fixed calendar; three to six months sits within the range sexual health services generally recommend for people with multiple partners, with retesting sooner if a specific exposure warrants it. What the clause is really doing is converting an anxiety, what if you bring something home, into a concrete, checkable practice, which tends to settle the anxiety more effectively than a promise ever could.

Non-hierarchical and kitchen-table structures

Kitchen-table and other non-hierarchical structures reject the idea that one relationship gets named priority over others. The agreements that work here focus less on ranking and more on how the network communicates and makes decisions that affect more than one relationship.

No ranking language, explicit autonomy

No relationship in this network is designated primary or secondary. Each of us decides independently how much time, depth, and commitment we want with each partner, without needing anyone else's sign-off.

This clause is doing definitional work as much as practical work, stating the structure so nobody defaults back to escalator assumptions under pressure. Non-hierarchical polyamory doesn't mean relationships are identical in practice; a newer connection will naturally look different from a ten-year one. It means the difference is a fact about the relationship, not a rule imposed on it from outside.

Metamour introductions are offered, not required

New partners are welcome at group gatherings once things feel established, generally after a few months. Meeting isn't mandatory for anyone, and declining an introduction isn't treated as a red flag.

Kitchen-table culture puts real value on metamour relationships, but conflating that value with an obligation to be close with people you didn't choose tends to produce forced warmth nobody actually wants. This version protects the option to build kitchen-table relationships without turning meeting a metamour into a checkbox that has to happen by a certain date.

Shared decisions for shared risk

Anything that affects the whole household, moving a new partner into a shared space, a change to our safer-sex baseline, a financial commitment involving more than one of us, gets discussed by everyone it affects before it's decided, not announced afterwards.

Non-hierarchical doesn't mean nobody's decisions ever require input from other people; it means the input requirement tracks actual shared risk rather than relationship rank. Two partners who don't live together and share no finances genuinely don't need to weigh in on each other's dating lives. A polycule that shares a home, a lease, or a testing pattern does need a mechanism for the decisions that touch everyone.

Long-distance CNM

Long-distance relationships introduce a specific set of practical questions that proximity-based agreements don't have to answer: how local partners factor in, how much contact is realistic between visits, and how visit time gets protected once it's genuinely scarce.

Local partners and travel disclosure

Local partners where either of us lives are part of normal life and don't need advance approval. When one of us is planning to see a local partner during a visit window, we'll say so while planning the trip, not as a surprise once we're there.

The clause exists because long-distance CNM concentrates a lot of emotional weight into short visit windows. Discovering during a rare in-person visit that time is being split with someone local can land much harder than the same information would in a relationship where you see each other every week. This isn't about restricting local relationships, it's about making sure visit planning happens with full information.

Communication cadence that survives time zones

We check in by voice or video at least twice a week, more if either of us wants it, and we don't let more than 48 hours pass without some form of contact under normal circumstances.

Distance relationships depend on communication infrastructure more than any other CNM structure, there's no shared physical space generating small, ambient contact, so it has to be built deliberately. The specific numbers matter less than having any explicit baseline; without one, gaps tend to open gradually and get reinterpreted as meaning something they don't.

Protecting visit time without isolating other partners

The first and last day of a visit are kept clear for us. Time with local partners during the rest of the visit is fine and doesn't need to be minimised, we're not pretending the other person's life pauses when we're in town.

This is one of the harder balances in long-distance CNM: visit time is genuinely scarce and worth protecting, but treating every visit as requiring the local partner to disappear entirely tends to produce quiet resentment in that relationship too. Naming a protected window rather than claiming the whole visit gives both relationships something real to work with.

Opening an existing marriage

Opening a marriage carries specific weight that opening a newer relationship doesn't: there's usually more shared infrastructure, housing, finances, sometimes children, more history to protect, and often more fear on both sides about what it means. Our guide to opening an existing relationship covers the broader process; the clauses below are the kind that tend to show up once a couple has actually started.

A deliberately slow start

We're starting with dating and flirting, no outside sex for the first three months, and we'll revisit that limit together rather than letting it expire silently or extend by default.

Time-limited restrictions that get explicitly revisited tend to work better than either permanent rules or vague, open-ended ones. The clause isn't claiming three months is the correct number for every marriage opening, it's making the limit conscious and giving it a built-in expiry that requires a real conversation rather than silent renewal or silent abandonment.

What stays private, what gets shared

Day-to-day details of outside relationships stay between the person and their outside partner unless something affects us directly. What we do share: whether we're seeing someone regularly, our safer-sex practices with them, and anything that would change our time or financial commitments.

Married couples opening up often default to DADT out of instinct, wanting to avoid painful detail, without examining whether it will hold up over time. This clause is a middle path: it protects genuine privacy, nobody needs a play-by-play, while keeping the categories of information that actually affect the marriage, health, time, money, non-negotiable.

Legal and financial safeguards

Opening our relationship doesn't change our legal or financial arrangements as a married couple. If either of us wants to formalise anything with an outside partner that touches property, finances, or parenting, we'll get proper legal advice before doing so.

This is the one clause here doing legal work rather than purely relational work, and it's worth being precise about what an agreement between partners can and can't do. A relationship agreement has no legal force; it won't affect a divorce settlement, a custody arrangement, or a property dispute. Anything with genuine legal stakes, cohabitation with an outside partner, changes to a will, parenting arrangements involving a third adult, needs a solicitor, not a clause in a document you wrote together. Our legal considerations guide and the wider piece on CNM and the law both go into where that line sits.

Review cadence: the clause most agreements are missing

The single most common gap across all four shapes above isn't any specific clause, it's the absence of a mechanism for revisiting any of them. Agreements written at the start of a relationship, or at the point of opening one, reflect what made sense to specific people at a specific moment. Revisiting them isn't a sign that the original agreement failed, it's what keeps an agreement from quietly becoming a rule that nobody remembers agreeing to.

A workable review cadence has two parts. The first is scheduled: a check-in every three to six months, treated as a standing appointment rather than something that only happens when there's a problem, where each clause gets a quick assessment, still working, needs adjusting, no longer relevant. The second is trigger-based: certain events, a new partner becoming more serious, a house move, a health scare, a change in job or income, warrant an unscheduled review regardless of where you are in the cycle.

What a review conversation should actually cover: whether each clause is still solving the problem it was written for, whether it's being followed in practice or quietly worked around, a strong signal that it needs to change, and whether anyone is holding onto a clause out of habit rather than genuine need. If a clause has already been broken, the process for handling that is different, working out what actually happened comes before deciding what changes.

None of the clauses above are meant to be copied verbatim. They're illustrations of what a genuinely negotiated agreement looks like when the underlying concern is named honestly rather than obscured by vague language. The version that will actually hold in your relationship is the one you and your partners write yourselves, in your own words, for the concerns you actually have, not the ones a stranger's example anticipated for you.