FLR Contract: What to Include and How to Write One

An FLR contract is a written agreement between partners that defines the structure, rules, and expectations of their Female Led Relationship. A female led relationship contract isn't a legal document. It's a relationship tool — a shared reference point that transforms verbal agreements into something concrete, reviewable, and harder to forget.

Most Female Led Relationship dynamics start with conversations. Conversations are necessary but insufficient. Memory drifts. Expectations shift. What both partners "agreed to" three months ago becomes two different versions of what was discussed. A contract solves this by putting everything in writing.

Why Write an FLR Contract

Clarity

The act of writing forces specificity. "I lead and you follow" becomes "I assign tasks on Monday mornings with deadlines; you complete them and submit proof." The gap between those two statements is where most FLR conflicts live.

Alignment

Writing a contract together reveals mismatched expectations before they cause problems. If one partner imagines Level 2 authority and the other imagines Level 4 — terms explained in our guide to D/s dynamics — that gap surfaces during the writing process, not three months later during an argument.

Accountability

A written agreement is harder to gaslight or reinterpret than a memory. When both partners signed the same document, "we never agreed to that" becomes a factual question, not an emotional one.

Evolution Tracking

Contracts change over time. Version 1 reflects where you started. Version 5 reflects how you've grown. Having written records of your dynamic's evolution is useful for reflection and for resolving disputes about what was agreed when.

What to Include in an FLR Contract

1. Roles and Identities

Define who holds which role and what those roles mean in your specific dynamic:

• Dominant/Leader: Name, chosen title (if any), areas of authority
• Submissive/Supporter: Name, chosen title (if any), areas of service and deference
• Dynamic type: FLR level, scope of authority, kink inclusion

Example:

[Name] serves as the Dominant partner with authority over household management, financial decisions, task assignment, and behavioral expectations. [Name] serves as the submissive partner, committing to follow the structure outlined in this contract.

2. Rules and Expectations

This is the operational core. Document the rules that govern daily life:

Household rules:

• Specific chores with deadlines and standards
• Meal planning and preparation responsibilities
• Home maintenance expectations

Behavioral rules:

• Communication protocols (greeting rituals, check-in requirements, response times)
• Permission requirements (purchases, social plans, decisions)
• Conduct expectations (tone, language, deference in specific contexts)

Service expectations:

• Ongoing acts of service (coffee preparation, errands, personal care)
• Special occasion responsibilities
• Proactive service expectations (anticipating needs without being asked)

3. Rituals and Routines

Document the rituals that maintain daily rhythm:

4. Task Framework

Define how tasks work within the dynamic:

• Who assigns tasks (dominant only, or can the submissive propose?)
• How tasks are communicated (app, text, verbal)
• Deadline expectations
• Proof requirements (photo, text confirmation, none)
• How missed tasks are handled

5. Consequences and Rewards

Document the accountability system:

Consequence tiers:

• Tier 1: Verbal acknowledgment and recommitment
• Tier 2: Written reflection (100-300 words)
• Tier 3: Assigned consequence (lines, restriction, extra tasks)
• Tier 4: Serious conversation about the dynamic's direction

Rewards:

• Point system for consistent task completion
• Earned privileges (choice of activity, special time together)
• Verbal acknowledgment and praise
• Milestone celebrations (streak achievements, contract anniversaries)

6. Boundaries and Limits

This section is non-negotiable. Every contract must include:

• Hard limits: Actions that are never acceptable, regardless of context (see power exchange for couples for more on negotiating limits)
• Soft limits: Actions that require specific discussion and consent before proceeding
• Safe words: A word or signal that immediately pauses the dynamic
• Emergency protocol: What happens if either partner needs to completely exit the dynamic temporarily
• Areas excluded from the dynamic: Aspects of life where the hierarchy doesn't apply (parenting, career, health decisions)

7. Chastity Terms (If Applicable)

If chastity is part of your dynamic:

• Maximum session duration before mandatory review
• Check-in frequency during sessions
• Emergency release protocol
• Conditions for earning release
• How chastity integrates with the task/consequence system
• Physical safety requirements

8. Communication Protocols

How partners communicate about the dynamic:

• Regular check-ins: Daily mood check, weekly review, monthly assessment
• Issue escalation: How to raise concerns without undermining the dynamic
• Pause protocol: How to signal "I need a break from the dynamic" without guilt
• Renegotiation process: How to propose changes to the contract

9. Review Schedule

The most important section for long-term sustainability:

• Review frequency: Monthly for new dynamics, quarterly for established ones
• Review process: Both partners re-read the contract, discuss what's working, propose changes
• Version control: Date each version, keep prior versions for reference
• Sunset clause: The contract expires and must be actively renewed (prevents inertia)

10. Signatures and Date

Both partners sign and date the contract. This isn't about legal enforcement. It's about psychological commitment. The act of signing creates a shared moment of intentional agreement.

Sample FLR Contract Structure

Here's a template outline you can adapt:

FLR CONTRACT — Version 1.0
Date: [Date]
Review Date: [Date + 4 weeks]

SECTION 1: ROLES
- Dominant: [Name], [Title]
- Submissive: [Name], [Title]
- Dynamic Level: [1-4]
- Scope: [Domains covered]

SECTION 2: RULES
- Household: [List]
- Behavioral: [List]
- Service: [List]

SECTION 3: RITUALS
- Daily: [List with times]
- Weekly: [List with days]

SECTION 4: TASKS
- Assignment method: [App/verbal/text]
- Proof requirements: [Photo/text/none]
- Miss protocol: [Consequence tier reference]

SECTION 5: CONSEQUENCES & REWARDS
- Tier 1-4 consequences: [Details]
- Reward system: [Points/privileges/acknowledgment]

SECTION 6: BOUNDARIES
- Hard limits: [List]
- Soft limits: [List]
- Safe word: [Word]
- Pause protocol: [Process]

SECTION 7: CHASTITY (if applicable)
- Session parameters: [Details]
- Safety protocols: [Details]

SECTION 8: COMMUNICATION
- Daily check-in: [Time and format]
- Weekly review: [Day and process]
- Issue escalation: [Process]

SECTION 9: REVIEW
- Next review: [Date]
- Process: [Both re-read, discuss, propose changes]
- Renewal: [Explicit renewal required / auto-renew]

SIGNATURES
[Name] _____________ Date: _______
[Name] _____________ Date: _______

Writing Tips

Use Clear Language

Write like you're creating instructions, not poetry. "The submissive shall prepare the morning elixir with the devotion of a servant" is worse than "Make coffee by 7am, how she likes it."

The contract should be instantly understandable when referenced at 6am on a Tuesday. Plain language serves this goal.

Be Specific but Not Exhaustive

Cover the important rules and expectations. Don't try to legislate every possible scenario. A contract that's 30 pages long won't be read. Aim for 2-4 pages that cover the essentials and leave room for judgment.

Write Together

Both partners should contribute to the contract. The dominant may hold final approval, but the submissive's input ensures the rules are realistic, the boundaries are respected, and the structure is sustainable.

Start with a Draft Period

Write a draft contract and live with it for one to two weeks before signing. This trial period surfaces problems before they're formalized:

• Is the morning ritual actually achievable on workdays?
• Are the consequence tiers proportional?
• Are check-in times realistic given both schedules?

Include What's NOT Covered

Explicitly stating what falls outside the dynamic prevents scope creep:

• "Parenting decisions are shared equally and are not governed by this contract"
• "Career decisions remain individual"
• "Health and medical decisions are personal"

Common Mistakes

Writing a Contract That's Too Ambitious

A contract that requires 2 hours of daily rituals, 10 rules, and a complex consequence system will collapse under its own weight. Start simple. You can always add complexity in Version 2.

Treating the Contract as Permanent

A contract that hasn't been reviewed in six months is a dead document. Life changes. Dynamics evolve. The contract should keep pace.

One Partner Writing Alone

If the dominant writes the entire contract and presents it for signing, the submissive hasn't participated in the negotiation. Both partners should be involved in the creation process.

Skipping Boundaries

A contract without hard limits and safe words is missing its most important section. Structure without safety isn't structure. It's coercion.

No Exit Clause

Both partners should be able to exit or pause the contract at any time, for any reason, without penalty. This isn't a weakness in the document. It's what makes the consent genuine.

Digital Contract Management

Managing a contract on paper works, but digital tools offer advantages:

• Version history: Track changes over time
• Connected rules: Rules in the contract become tasks and rituals with automated tracking
• Review reminders: Scheduled notifications for review dates
• Shared access: Both partners can reference the contract anytime

---

A female led relationship contract is a conversation turned into a commitment. It doesn't create the dynamic — the daily practice does that. But it anchors the Female Led Relationship to something specific, reviewed, and shared. When the dynamic feels uncertain, when expectations drift, when either partner wonders "what did we actually agree to?", the contract is there.