A family law settlement agreement is the document a court will turn into an order. It governs parenting time, support, asset division, and the terms both parties have to live under for years. Producing a clean draft from a productive mediation should be routine. In practice it is where many cases fall apart. The LawSensai Settlement Composer is the drafting tool that turns mediation output into a draft agreement, with a guardrail scan that catches the issues that derail finalize.
This post walks through the inputs the Composer uses, the structure of the draft, and what the guardrail scan checks.
What the Settlement Composer does
The Composer reads the agreed positions from the Family Law mediation surface, pulls the calculator anchors for support amounts, pulls the asset and debt schedules from the matter, and drafts the settlement agreement section by section. The output is a draft suitable for attorney review and entry by a court.
The Composer is a drafting tool. It does not file. It does not sign. It produces the draft and leaves the rest to the parties and their attorneys.
The inputs the Composer uses
The Composer pulls from five sources inside your matter:
The mediation agenda outcomes. The Composer reads each agenda item the parties addressed and the position both parties agreed on. Items still in dispute are surfaced and not drafted until resolved.
The Child Support Calculator output. The calculator number anchors the support section. If the parties agreed on a different number, the Composer drafts the agreed number and notes the deviation from guideline so the agreement is honest about what was decided.
The spousal support analysis where the state has guidelines or schedules. The Composer uses the same anchor pattern as the child support section.
The asset and debt schedules. The matter holds the agreed list of marital assets and debts, the agreed valuations, and the allocation between parties. The Composer translates the schedules into agreement language.
The tax position the parties agreed to. Who claims the children for federal tax purposes. How tax-related deductions are split. The Composer drafts the tax section from the agreed positions.
The structure of the draft
The draft follows the structure most family courts expect. Parties and recitals. Parenting plan including decision-making and parenting time. Child support including amount, payment mechanism, and modification triggers. Spousal support including amount, duration, and modification triggers. Division of marital assets. Allocation of marital debts. Tax positions. Insurance. Dispute resolution and modification provisions. Signature blocks.
State-specific provisions are inserted where required. Some states require specific language for parenting plans. Some require specific allocation language for retirement assets. The Composer pulls the state-specific provisions from the same state rules library the other Family Law products use.
The guardrail scan
Every draft runs through the guardrail scan before the Composer marks it ready for review. The scan checks four classes of issues.
Prompt injection. The mediation surface accepts free-text reasoning from both parties. The scan checks for instructions disguised as facts, attempts to redirect the drafter, and any content that looks designed to manipulate the model. Detected injection is surfaced as a safety event and the affected content is quarantined.
Math drift. The scan compares the support numbers in the draft against the calculator output and the agreed numbers in the mediation surface. If the draft includes a number neither matches, the scan flags it. The same check runs for asset valuations and debt allocations.
Jurisdictional inconsistency. The scan checks that the state-specific provisions match the state of the matter. If the parenting plan language is from one state and the support model is from another, the scan flags it.
Missing sections. The scan checks that every section the agreed positions require has been drafted. If the parties agreed on a parenting plan but the draft is missing the holiday schedule, the scan flags the omission.
Any scan flag must be resolved before the draft can be marked final. The parties see the flag and the suggested fix.
What you see as the user
You see the draft with each section marked by source. Mediation outcome. Calculator anchor. Asset schedule. State-specific provision. You can edit any section. Edits are tracked.
You also see the guardrail scan results. Green sections passed clean. Yellow sections have a soft flag, often a suggestion. Red sections require resolution before finalize.
Spanish language support
The Composer runs in Spanish. The draft language, the scan flags, and the suggested fixes are localized. For bilingual cases, the Composer can produce parallel-language drafts where the state and the parties accept that format.
Attorney involvement
The Composer is built for attorney review. The draft is structured to be readable by counsel, with each clause sourced to the agreed input. Many parties run the Composer, then route the draft to attorneys at lawsens.ai/match for review before signing. Some attorneys use the Composer with their own clients as the drafting layer.
Safety and audit
Every draft is recorded in brain_decisions with the audit-log hash chain. The recorded data includes the inputs, the draft version, the scan results, and the resolution of any flags. Support can reconstruct any draft after the fact. Aggregate Composer usage and safety findings are published at lawsens.ai/trust/family.
Common misreads we see new users make
Misread one: thinking the Composer files the agreement with the court. It does not. The Composer drafts. Filing the agreement and entering the order are court processes that happen outside LawSensai.
Misread two: treating a yellow scan flag as optional. Yellow flags are not blocking but they are real. Read them. Many yellow flags turn into post-decree litigation if ignored.
Misread three: assuming the scan catches every drafting issue. The scan catches the four classes above. It is not a substitute for an attorney reading the draft. Both parties benefit from having counsel review before signing.
Practical next steps
Step one: complete the mediation track at lawsens.ai/family/mediation so the Composer has the agreed positions to work from.
Step two: run the Composer at lawsens.ai/family/settlement. Review each section against the source it cites.
Step three: resolve every red flag and address every yellow flag before marking the draft final at lawsens.ai/family/settlement/finalize.
How the Settlement Composer connects to the rest of LawSensai
The Composer is the drafting layer of the Family Law product. The mediation tools provide the agreed positions. The Child Support Calculator provides the support anchor. The Document Vault stores supporting documents under signed-URL access scoped by RLS. The Court Date Tracker holds any hearing date the entry of the order requires. Attorney Match routes the draft to counsel for review. Every step is logged in brain_decisions and the aggregate decision counts are published at lawsens.ai/trust/family.
This post is informational and is not legal advice. The draft is a starting point for attorney review and court entry. Treat the Composer as the drafting tool. Treat the attorney and the court as the authorities that turn the draft into a binding order.
Read more
- lawsens.ai/product/settlement-composer
- lawsens.ai/trust/family
- lawsens.ai/trust
- lawsens.ai/help/guardrail-scan
- lawsens.ai/product/family-mediation
- American Bar Association family law section overview at americanbar.org
Last verified: 2026-04-09.