Mediator Support
One encrypted workspace for divorce mediators — from intake to signed agreement.
Mediator Support bundles the complete mediation case file: a parenting-plan wizard, alimony calculation to Dutch (Trema) standards, asset division, a care calendar and AI-moderated co-parent messaging. The mediator generates legal PDFs in their own branding; both parents get their own portal.
10
Parenting-plan wizard steps
3
Legal documents as PDF
AES-256
Client-side encryption
±38,500
Lines of TypeScript
What it does
Zero-knowledge case files
All personal data is AES-256-encrypted in the browser before it ever reaches the database. The server literally cannot read the case file — only anonymous metadata stays queryable.
Parenting plan in 10 steps
From custody and care split to social-media rules and relocation clauses; the wizard co-writes in legally sound language, with text variants per age bracket of the child.
Alimony to 2026 Trema standards
Three sequential engines: net disposable income (tax boxes and credits), child support via NIBUD tables, and partner alimony with net-comparison. Child support takes legal precedence.
Care calendar as a compliance engine
Dutch holidays, school vacations per region (derived from the postcode) and schedules like 2-2-5-5 — with a dashboard that puts the paper agreement next to the actual split, traffic-light deviations included.
Swap requests without escalation
Parents swap care days through a structured protocol with fixed reasons, a mandatory compensation date and expiry — deliberately designed to avoid free-text fights. Everything lands in an audit trail.
AI moderation of co-parent messaging
A Dutch regex layer plus an LLM assesses tone and intent, blocks escalating messages and proposes a constructive rewrite in 'I' language.
White-label branding
The practice's logo and colour scheme run through the entire app and through every generated document: parenting plan, mediation agreement and divorce covenant.
How we built it
Next.js 16 with React 19 and strict TypeScript; Firebase provides auth, storage and transactional mail. The app is deliberately almost fully client-side: the zero-knowledge model requires the key to never leave the browser.
The domain is modelled deeply rather than generically: care-discount thresholds, tax-credit phase-outs, vacation regions and age-based care schedules live as explicit rules across some 38,500 lines of TypeScript.
About 500 lines of deny-by-default Firestore rules, now covered by automated rules tests in CI. Payments and digital signing are ready as simulated flows for the next phase.
Why we built it
Mediators today juggle Word templates, separate calculation tools, WhatsApp and paper calendars. It is precisely the translation from paper agreement to daily practice that structurally breaks down.
Built with and for a Dutch mediation practice: one place where the whole case lives — and where parents never have to pay to access their own arrangements. The mediator is the paying party.
Need something like this in your company?