A D/s relationship agreement can be a two-page operating manual or a 47-page document with numbered clauses and the general energy of a minor international treaty. Both can work. Only one of them is likely to get reread on a random Wednesday.
The best agreement captures the current version of your relationship in language both people understand. It records what you’re building, what each person can expect, where the limits are, how communication works, and how the whole thing changes when real life changes.
The writing process is usually more valuable than the finished document. It forces specific conversations before assumptions have a chance to dress up as facts.
This guide gives you an eight-part D/s relationship agreement template, a two-session writing process, and a 30-day review plan. You can make it formal, playful, romantic, clinical, or all four before lunch. The structure still works.
What is a D/s relationship agreement?
A D/s relationship agreement is a shared written reference for an agreed power exchange. It can define purpose, roles, scope, limits, rules, communication, accountability, privacy, duration, and review procedures.
It is not a replacement for current communication or consent. It records decisions and makes future conversations easier.
Some people call it a contract because the formality feels meaningful. Others avoid that word because it sounds legal or permanent. Use the name that fits, but put a plain-language sentence near the top:
This document records our current mutual agreements. Either person may pause an activity, withdraw consent, or request a review at any time.
The National Coalition for Sexual Freedom’s Consent Counts resources define consent around clear, informed, voluntary agreement and emphasize community education. Their materials are a useful authority alongside your own specific negotiation.
Is a D/s agreement legally binding?
Don’t treat a personal D/s agreement as a legally enforceable contract for sexual access, personal control, or consent. Consent remains current and can be withdrawn. A signature does not create permanent permission.
The NCSF Consent Counts FAQ also notes that its materials are informational and not legal advice. Laws vary by location, so consult a qualified local attorney if your document touches property, debt, tenancy, employment, medical decision-making, or another area with real legal consequences.
That doesn’t make the relationship agreement pointless. Grocery lists aren’t legally binding either, and they still prevent me from returning home with six interesting sauces and no dinner.
Who should write a D/s relationship agreement?
Write one if the conversation would help, not because you think serious dynamics are required to produce paperwork.
An agreement is especially useful when:
- You’re beginning a new power exchange and want to surface assumptions.
- The dynamic covers several areas of daily life.
- You’re long-distance and need clearer communication rhythms.
- You are revising a system that grew informally.
- One or both people process difficult conversations better in writing.
- You want a review date and change process that won’t depend on memory.
- Past misunderstandings reveal that your mental versions don’t match.
You may not need one when the structure is narrow, both people already communicate clearly, and writing would add more performance than clarity. A one-page summary can also be enough.
If the whole dynamic is new, read our guide to starting a D/s dynamic before turning every possibility into a clause.
Prepare before writing your D/s relationship agreement
Don’t open a blank document and negotiate live while one person types. That setup quietly gives the keyboard owner editorial power and encourages quick agreement just to keep the evening moving.
Do a short preparation round separately first.
Each person answers:
- What do I want this dynamic to feel like?
- What areas of life do I want included?
- What areas must remain outside it?
- What responsibilities am I willing to take on?
- What do I need when something goes wrong?
- What am I curious about but not ready to agree to?
- What would make me ask to pause the whole structure?
- What does a successful first 30 days look like?
Then compare answers. Mark three kinds of items:
- Aligned: You already want roughly the same thing.
- Discuss: You might agree, but details matter.
- Not now: There is no current shared yes.
“Not now” belongs outside the agreement. It can live on a future-discussion list without becoming a soft commitment.
Planned Parenthood’s guidance on talking with a partner about sex makes the basic point well: talk openly about likes, dislikes, and boundaries, and keep that communication going because preferences can change.
Use two writing sessions
Split the work so nobody agrees from fatigue.
Session one, 60-90 minutes: Purpose, scope, limits, communication, and pause process.
Session two, 60-90 minutes: Roles, rules, tasks, accountability, privacy, duration, and review.
Leave at least a day between sessions. Each person should read the draft alone before signing or adopting it. The gap catches clauses that sounded fine in the room but feel different without conversational momentum.
The eight-part D/s agreement template
Your agreement can be short. One or two paragraphs per section is enough for version one.
1. Purpose and shared vision
Begin with why you’re doing this. A purpose statement helps resolve future questions because it identifies the experience the structure is meant to support.
Prompts:
- What are we building together?
- What qualities do we want more of?
- What should this structure never cost us?
- How will we know it is helping?
Example:
We are creating a playful, structured D/s dynamic that helps us stay connected, follow through on shared goals, and explore an agreed power exchange. We want the structure to feel challenging, affectionate, and sustainable alongside work, health, family, and ordinary relationship responsibilities.
Avoid mission-statement fog such as “achieve our highest potential through complete devotion.” It sounds impressive and tells you nothing about Tuesday.
2. Roles, scope, and excluded areas
Name who holds which role and where that authority applies. Scope is the difference between “the tasker may assign tasks” and “the tasker controls everything,” which is not a detail you want left to interpretation.
Possible domains:
- Daily routines
- Task assignment and deadlines
- Clothing or presentation in agreed settings
- Spending within a defined category and limit
- Health-support habits
- Social plans
- Intimate or scene-based activity
- Sleep schedule
- Communication rituals
For each included domain, describe the authority being exchanged. Then list excluded domains just as clearly.
Example:
The tasker may assign up to five active personal-development or household tasks at a time and set reasonable deadlines. Employment decisions, medical care, relationships with friends/family, and personal funds outside the shared date budget remain outside this authority.
Specific exclusions aren’t a lack of commitment. They make the yes around included areas more legible.
3. Consent, limits, and pause mechanisms
This section should be impossible to misunderstand.
Include:
- Current hard limits
- Conditional or “maybe” activities that require separate negotiation
- Health, trauma, accessibility, medication, or injury considerations
- Safewords or stop signals where relevant
- A non-scene phrase for pausing the wider structure
- What happens immediately after a pause
- How and when the conversation resumes
Example:
Either person may say “pause the framework” at any time. Active tasks and accountability stop immediately. We will handle immediate care first and schedule a check-in within 24 hours unless the person requesting the pause asks for more time. A pause does not itself trigger consequences.
Write this while calm. A pause mechanism is much easier to use when nobody has to invent it during distress.
4. Rules, protocols, rituals, and tasks
List only the structure you plan to use during the first term.
- Rules state standing expectations.
- Protocols describe how an action happens.
- Rituals are repeated moments with shared meaning.
- Tasks are specific assignments with an endpoint.
Our guide to rules vs. protocols vs. rituals explains the distinctions in detail.
For each rule or protocol, write:
- The exact behavior
- Context and timing
- Exceptions
- Who tracks it, if anyone
- The response when it is missed
Example:
On weekdays, the taskee sends a morning check-in by 9am with today’s priority and any expected scheduling conflict. Weekends are optional. Illness, emergencies, and pre-agreed travel days are exceptions. If a check-in will be late, a one-line notice is enough.
Five clear expectations beat twenty aspirational ones. Version one should be easy enough to remember without carrying the agreement around like a field manual.
5. Communication and check-ins
Define where routine updates happen and how harder conversations happen.
Cover:
- Daily or weekly check-in rhythm
- Which channel is used for tasks versus urgent messages
- How extensions are requested
- How either person raises discomfort
- How conflict pauses work
- What feedback each role needs
- Whether important decisions must be confirmed in writing
Example:
We hold a 20-minute review every Sunday. Either person can add topics during the week. Difficult conversations happen by voice or in person when possible, not through a chain of increasingly haunted text messages. Either person may request a break and suggest a return time.
If you’re long-distance, our guide to maintaining a D/s dynamic across distance has more on asynchronous communication and time zones.
6. Accountability, repair, and rewards
Accountability should be defined before a miss, not improvised from disappointment.
Include:
- How completion is recorded
- How quality feedback works
- What counts as late, missed, or incomplete
- How context is considered
- Available repair actions
- Any demerit or consequence process
- Rewards, points, or recognition
- Behaviors that will never be handled as part of the game
Example:
Missed tasks are discussed before any consequence is assigned. We first determine whether the task was unclear, unrealistic, blocked by circumstances, or knowingly skipped. Repair should address the actual issue. Relationship conflict, consent decisions, health limitations, and requests to pause will not be converted into points or consequences.
The distinction between correction and repair matters. If a task was missed because the deadline was impossible, adding pressure won’t repair the design problem.
7. Privacy, records, and sharing
D/s agreements can contain intensely personal information. Decide what gets written down, where it is stored, and what either person may share.
Address:
- Who can access the document
- Whether screenshots or excerpts may be shared
- Rules for photos, videos, journals, and completion evidence
- Device security and notification previews
- What happens to shared records after the agreement ends
- Whether anonymized stories may be discussed with friends or community spaces
Example:
Neither person will share the agreement, task history, private messages, photos, or identifying details without specific permission for that instance. If the agreement ends, each person may keep their own written reflections but will delete intimate media at the other person’s request where legally permitted.
For app-based structure, review how the tool handles your information. SubTasks explains its approach on the privacy page.
8. Duration, revision, and ending
Every agreement needs a clean way to change or end.
Include:
- Start date
- First review date
- Regular review cadence
- How amendments are proposed and accepted
- Whether old versions are retained
- How either person can end the agreement
- What happens to active tasks and shared materials afterward
Example:
This version begins July 30 and runs as a 30-day trial. We review it on August 29. Changes require a clear agreement from both people and are recorded in the change log. Either person may end the agreement at any time by saying so directly. Ending the agreement stops active tasks and consequences without requiring a final performance or explanation.
An ending clause does not predict failure. It prevents ambiguity from becoming pressure.
Test every clause before you keep it
Run each clause through five tests.
The clarity test
Would both people agree on what this sentence requires? “Maintain a good attitude” fails. “Raise concerns directly during the weekly review or sooner if urgent” is clearer.
The reality test
Can this survive an ordinary hard week? If the protocol assumes unlimited time, energy, privacy, or money, rewrite it.
The reciprocity test
Power is asymmetric, but responsibility runs in both directions. What does the tasker owe in clarity, consistency, response time, care, and review? Write those obligations down too.
The pause test
Can either person stop or question the clause without the act of pausing becoming a violation? If not, the mechanism is unsafe and operationally useless.
The purpose test
Which part of the shared vision does this clause support? If nobody remembers why it exists, delete it or put it in the parking lot for later.
The agreement should be an aid to building trust through predictable structure, not a pile of impressive-sounding sentences.
Common D/s relationship agreement mistakes
Copying a template without translating it
Templates are prompts, not personality transplants. Delete sections that don’t fit, rewrite formal language, and add the boring operational details your life actually needs.
Writing only the taskee’s responsibilities
An agreement that lists one person’s duties and says nothing about the other’s clarity, care, consistency, and review obligations is incomplete. Authority creates work for the person holding it.
Treating curiosity as consent
“Maybe someday” does not belong in the active agreement. Keep a separate exploration list and negotiate those items when both people are ready.
Making exceptions feel like failure
Good structure handles illness, disability, travel, work crises, and family care. Define the minimum viable version and the communication path for days when the full version cannot happen.
Hiding disagreement with elegant wording
If one person wants financial authority and the other does not, better prose will not create alignment. Mark the domain “not included” and revisit it only if both people want to.
Skipping the review
A document with no review date slowly becomes either irrelevant or oppressive. Put the meeting on the calendar before adopting the agreement.
Your 30-day D/s agreement review
Treat the first term as a pilot. Thirty days is long enough to encounter real life and short enough that revision doesn’t feel distant.
Before the review, each person privately scores every major section:
- Green: Helpful and sustainable
- Yellow: Useful but needs adjustment
- Red: Stop or replace
At the meeting, discuss red items first. Then yellow. Green items need only a quick confirmation.
Ask:
- Which part created the most connection?
- Which expectation caused the most confusion?
- Where did the tasker need more clarity or consistency?
- Where did the taskee need a different level of challenge or support?
- Did the pause mechanism feel genuinely usable?
- Did any excluded area get crossed unintentionally?
- What should version two remove?
- What single addition would create the most value?
Keep a short change log:
| Date | Change | Reason | Review again |
|---|---|---|---|
| Aug. 29 | Morning check-in moved from 8am to 9am | Better fit with work schedule | Sept. 29 |
Changing a clause should feel normal. The document’s job is to describe a working agreement, not force the relationship to remain loyal to an old draft.
You can begin with the Designing Your Dynamic Task Kit or set up your structure in SubTasks once the two of you know what you want the tool to carry.
FAQ about D/s relationship agreements
Do we need a formal D/s contract?
No. A formal document can feel meaningful, but a short plain-language agreement works better for many couples. The value comes from specific negotiation, shared understanding, and regular review.
How long should a D/s relationship agreement be?
Version one can fit in two to five pages. It should be long enough to cover purpose, scope, limits, communication, accountability, privacy, and revision, but short enough that both people will reread it.
Can either person change the agreement?
Either person can propose a change. Changes to a mutual agreement require a fresh shared yes. Either person should also be able to pause or end participation without waiting for the next scheduled review.
Should we include safewords in the written agreement?
Yes, if safewords or stop signals are part of your practice. Also include a plain-language way to pause the wider relationship structure outside a scene and describe what happens immediately afterward.
What if we disagree while writing it?
Don’t average your answers into fake agreement. Keep the disputed item outside the active scope, record the question if useful, and return to it later. A clear “not agreed” is safer and more honest than an ambiguous clause.
How often should we review it?
Review the first version after 30 days. After the structure stabilizes, monthly or quarterly reviews may work. Review sooner after a major life change, repeated confusion, or a request from either person.
Write the document you will actually open again
A useful D/s relationship agreement is specific enough to guide behavior and flexible enough to admit that people change. It names the vision, defines scope, protects excluded areas, makes pauses easy to use, and gives both roles real responsibilities.
Keep version one shorter than your instinct. Schedule the review before you adopt it. Then use the agreement as a map for conversation, not a substitute for it.
The finished document may look less dramatic than the ceremonial contract you imagined. But if it helps both people understand the dynamic on a hard Wednesday, it is doing the job.