How to Write an FLR Contract (What to Include)
An FLR or D/s contract isn't legally binding and it isn't meant to be. Its real job is much simpler: turning a set of verbal understandings into something written down that both people can point back to when memory gets fuzzy or expectations start to drift.
Before you write anything
Have the actual conversation first. A contract should document an agreement you've already reached out loud -- it shouldn't be the format you use to negotiate it for the first time. If either partner is discovering a term for the first time while reading the draft, back up and talk it through before it goes on paper.
What a solid contract usually covers
- Roles -- who holds what authority, and specifically over what (this is the part people skip, and it's the part that causes the most confusion later)
- Scope -- is this 24/7, scened, or somewhere in between? Does it apply everywhere, or only at home?
- Hard limits -- anything that's off the table entirely, stated plainly, no ambiguity
- Soft limits -- things that need extra care, a slower pace, or advance discussion before they happen
- Structure -- chores, rituals, check-ins, or whatever routine elements you're actually using
- Consequences -- if you're using them, what they are, and just as importantly, what they are not (consequences should never touch hard limits or safety)
- The safety clause -- how either partner pauses or stops things, and confirmation that this requires no permission from anyone
- Review date -- when you'll revisit the whole document, not just wait for something to break first
The one clause that overrides everything else
Every real contract needs an unconditional way out -- a safeword, a stop mechanism, whatever you call it -- that works regardless of points, rules, or how "in the middle of things" you are. If a contract doesn't have this, it isn't a consent framework, it's just a list of demands. This is also exactly why Keyholder's Emergency Stop can't be gated, disabled, or made to require approval -- a contract on paper and a contract enforced by an app should both honor the same principle.
Keep it a living document
The couples who get the most out of a contract treat it as something they revise, not something they sign once and forget. Set an actual date to review it -- monthly is common early on, quarterly once things settle -- and treat that review as routine maintenance, not a sign something's wrong.
Ready to build the dynamic instead of just talking about it?
Get Keyholder