Most family law mediation in this country still runs synchronously. Two people, a mediator, and a clock. That format works when both parties can be in the same room at the same time. It fails when they cannot, which is more often than the legal profession admits. Family Law mediation tools on LawSensai run the same structured conversation async, with HMAC magic-link invites, calculator anchors, and impasse detection.
This post walks through the async track, the calculator anchors, and how impasse detection surfaces when the parties are actually stuck.
What Family Law mediation does
The mediation product is the structured negotiation layer for divorce, separation, custody, and support matters. It does not replace a mediator on every case. It gives parties a way to move through the standard mediation agenda async, capture positions and proposals, and surface the points where outside help is needed.
The product runs three core tools. The async invite system with HMAC magic-links. The calculator anchors that tether proposals to math. The impasse detector that flags stuck issues for escalation.
The async invite system
The initiating party sets up the matter. The other party receives an HMAC magic-link invite by email or text. The link is signed and time-bounded. It opens to the mediation surface for that specific matter and that specific party.
Neither party needs a LawSensai account before the first session. The magic-link grants scoped access. Each party answers the same structured prompts and records their position on each agenda item. The system shows each party what the other said only after both have answered, which removes the first-mover anchoring that warps live negotiations.
The invite system uses HMAC because the threat model includes someone forwarding a link to a third party. HMAC signing means only the intended party can use the invite, and revoking is one click.
The agenda the async track records
The async track moves through the standard family law mediation agenda. Parenting time and decision-making. Child support. Spousal support if applicable. Division of marital assets. Division of marital debts. Tax positions. Insurance. Future review triggers.
For each agenda item, both parties record their position, their reasoning, and any specific number tied to the position. The system stores the positions side by side. The parties see the comparison once both have answered.
Calculator anchors
The biggest failure mode in family law negotiation is proposals that drift from the math. A spousal support number invented in the room may have no relationship to either party's actual income. A parenting time split may not match the support calculation the state will actually apply.
The calculator anchors fix that. When a party proposes a child support amount, the system runs the state-specific child support model against the inputs both parties have entered. The proposal appears next to the calculated number. The party can still propose whatever they want. They cannot pretend their proposal is the math.
The same anchoring runs for spousal support guidelines where the state has them, asset valuations where both parties have entered the asset, and tax allocation where the system can compute the effect.
Impasse detection
Impasse detection flags the points where the parties are actually stuck, distinct from points where they simply have not gotten to agreement yet. The detector looks at three signals.
Proposal gap. The parties' last proposals are far apart and have not moved in recent rounds. The detector measures both absolute gap and movement velocity.
Reasoning divergence. The parties are not arguing about the same thing. One party is talking about parenting time and the other is talking about decision-making. The detector flags the agenda mismatch so the parties realize they are on different topics.
Calculator divergence. The parties are not using the same inputs in the calculator. One party entered an income figure the other disputes. The detector surfaces the disputed input.
When the detector flags impasse on a specific item, the system suggests the next step. That can be sharing additional documentation through the Document Vault, bringing in a live mediator, or routing the contested issue to an attorney through Attorney Match.
Spanish language support
The mediation product runs in Spanish. The invite, the agenda, the calculator output, and the impasse alerts are localized. Bilingual matters can have each party operate in their preferred language.
Safety, audit, and prompt injection defense
Every mediation step is recorded in brain_decisions. The audit-log hash chain captures the agenda position, the calculator inputs, and the proposals. Support can reconstruct a session after the fact.
The Settlement Composer that turns the mediation output into a draft agreement runs through a guardrail scan. The scan checks for prompt injection in the parties' free-text reasoning. The detector treats injection attempts as a safety event and surfaces them rather than letting them flow into the draft.
Attorney involvement
The mediation tools do not replace attorneys. They give parties a structured way to identify what they agree on and what they do not. Many parties use the tools to narrow the issues before bringing the remaining contested items to attorneys or to a live mediator. Some parties use the tools to reach full agreement and then have attorneys review the draft from the Settlement Composer before signing.
Common misreads we see new users make
Misread one: thinking the calculator anchor is binding. It is not. It is a reference number. The state's court will calculate child support under the state's official model when an order is entered. The anchor tells you what that calculation is likely to produce given the inputs both parties have entered.
Misread two: assuming impasse means failure. Impasse on a single item is normal. The detector flags it so you can address that item specifically rather than letting it block agreement on items you actually agree on.
Misread three: sharing the magic-link. The link is single-party. Forwarding it does not work because the HMAC binds it to the intended party's identity at issuance.
Practical next steps
Step one: start a mediation matter at lawsens.ai/family/mediation. Pick the agenda items you want to address.
Step two: send the HMAC invite from lawsens.ai/family/mediation/invite. The other party receives the signed link and can respond on their own time.
Step three: when the mediation reaches agreement, run the Settlement Composer at lawsens.ai/family/settlement to produce the draft agreement for review.
How Family Law mediation connects to the rest of LawSensai
The mediation tools are the negotiation layer of the Family Law product. The Document Vault stores supporting documents under signed-URL access scoped by RLS. The Child Support Calculator provides the state-specific math the calculator anchors call. The Settlement Composer drafts the final agreement once the parties reach agreement. The Court Date Tracker holds session dates and any review hearing the parties schedule. Aggregate mediation outcomes and safety findings are published at lawsens.ai/trust/family.
This post is informational and is not legal advice. The mediation tools structure a conversation. Final agreements and court orders are legal documents you should have an attorney review.
Read more
- lawsens.ai/product/family-mediation
- lawsens.ai/trust/family
- lawsens.ai/trust
- lawsens.ai/help/magic-link-invites
- lawsens.ai/product/child-support-calculator
- American Bar Association family law mediation overview at americanbar.org
Last verified: 2026-04-09.