From proposal to proof

Do not “roll it out.” Make it earn the right.

Courts are not software platforms, and families are not test data. FJP should move from criticism to expert review, then to a small protected test, and only then toward wider use if the evidence supports it.

The short version

Start with the pieces least likely to cause harm: clearer evidence histories, better-defined professional assignments, written reasons, cost tracking, and checks that orders were actually carried out. Test them in one willing setting. Keep what works. Change or stop what does not.

Four phases

A path from idea to accountable action

01

Challenge the draft

Find legal errors, safety hazards, blind spots, added burdens, and better alternatives.

Current phase
02

Build the working group

Bring together people whose duties and experiences differ. Record conflicts and disagreement.

03

Design a small pilot

Choose low-risk modules, one willing setting, clear measures, privacy rules, and reasons to stop.

04

Test, publish, decide

Report helpful, neutral, and harmful results. Expand only what earns evidence and trust.

Family-court triage is not merely theoretical: NCSC reported in December 2025 that twelve courts had been selected for a family case-management initiative using training, tools, triage, tracking, data coaching, and peer learning without requiring a wholesale system replacement. That does not validate FJP, but it shows a practical model for supported court change. S41

Largest obstacles

Resistance is information—if we ask what it is protecting.

1 · Different laws and local court structures

The obstacle: Family law is mainly state-based, and court rules, funding, staffing, records, and professional roles vary by place.

Constructive response: Build a common core with a state-specific legal map. Begin in one willing jurisdiction—such as an Illinois pilot site—and let local legal authority control.

2 · Safety and fairness could be made worse

The obstacle: A classification tool can miss danger, treat an unproven report as false, harden bias, or rush someone through a process they cannot safely use.

Constructive response: Keep people—not software—responsible for decisions. Begin with low-risk record and workflow tools. Use private safety screening, meaningful notice and response, independent review, and written stop rules.

3 · Courts are already overloaded

The obstacle: Even a good checklist can fail if it simply adds work to crowded calendars and understaffed offices.

Constructive response: Co-design with judges, clerks, attorneys, advocates, interpreters, and self-represented court users. Every new task should replace, combine, or prevent existing work—not merely sit on top of it.

4 · Trust is fractured

The obstacle: Parents, professionals, advocacy groups, and institutions may suspect that FJP favors one side, one profession, or one theory of family conflict.

Constructive response: Treat disagreement as part of the design. Publish conflicts of interest, objections, responses, corrections, unresolved risks, and the exact meaning of every endorsement. Participation must never imply agreement.

5 · Court data do not speak the same language

The obstacle: Courts use different labels and systems. Missing or inconsistent data can make comparisons misleading.

Constructive response: Start with a small data dictionary and map fields to existing national standards. NCSC’s open-court data standards are designed to improve consistency without requiring every court to replace its system. S22

6 · Family information is unusually sensitive

The obstacle: A better record could become a more efficient way to expose therapy notes, addresses, allegations, or a child’s history.

Constructive response: Collect the minimum necessary information. Separate identities from research data, limit access and retention, plan for correction and deletion, and test security before live use. NIST’s Privacy Framework supplies a general risk-management structure, not permission to collect more. S23

7 · Technology and vendors can become the new gatekeepers

The obstacle: Proprietary systems can lock courts into expensive tools, hidden decision rules, or contracts that make correction and exit difficult.

Constructive response: Require open data formats, independent testing, accessible exports, audit rights, clear ownership, incident duties, and an exit plan. Court technology must serve legal values throughout its full life—not merely at purchase. S42

8 · A pilot can “succeed” by measuring the wrong thing

The obstacle: Faster closure may hide unsafe agreements, unaffordable return to court, or unresolved harm.

Constructive response: Record the test plan before results are known. Pair speed with safety, fairness, cost, access, child stability, implementation, and necessary reopening. Publish neutral and harmful results, not only wins. S19

9 · Access can disappear behind professional language

The obstacle: A process designed by experts can exclude people who represent themselves, speak another language, have a disability, or cannot spend hours decoding instructions.

Constructive response: Test every form and explanation with actual court users. Provide plain language, qualified interpretation, translation, disability access, and more than one way to participate. Meaningful language access is part of court fairness—not a courtesy. S43

A useful mindset

Be ambitious about the outcome. Humble about the mechanism.

Invitation, not indictment

Many people inside courts are already trying to make an overloaded system work. Invite their practical knowledge without asking them to defend every failure.

Pilot, not proclamation

A proposal is not proven because it is detailed. Use a small test to find what the paper could not foresee.

Replace work; do not pile it on

Adoption becomes possible when a tool removes duplication, prevents avoidable hearings, or makes existing duties easier to complete.

Make critics part of the safety system

A strong objection is not disloyalty. It is an early warning delivered before a family pays the price.

Protect people before protecting the project

If evidence shows harm, inequity, or unmanageable burden, change the module or stop it.

Earn each next step

Attention earns review. Review may earn a pilot. Only good pilot evidence can earn wider advocacy.

Ways to help

You do not have to endorse FJP to improve it.

RoleWhat we would askWhat participation means
Independent reviewerFind legal, safety, ethical, research, or operational flaws.Review—not endorsement.
Subject-matter contributorImprove one defined module or safeguard.A credited contribution only with consent.
Research or pilot partnerExplore feasibility, measurement, governance, and participant protection.Exploration—not a promise to adopt.
Public advocateHelp explain the need for tested, family-centered reform.Support for the mission; expertise is described separately.
Names and logos need precise permission.

No reviewer, employer, court, university, funder, or organization should be displayed as a supporter unless it has explicitly approved that exact description.

First practical moves

What progress could look like before any live pilot

  1. Complete a plain-language and accessibility review with parents, professionals, and people who have never used family court.
  2. Create an Illinois legal crosswalk showing what can be done under existing law, what may require a court rule, and what may require legislation.
  3. Form an independent review group with balanced expertise and published conflict rules.
  4. Turn the Evidence Ledger and scoped-assignment concepts into non-production prototypes using fictional cases.
  5. Choose a minimum dataset, privacy plan, security plan, and independent evaluation design.
  6. Approach a willing court, university, legal-aid group, or court-administration partner to explore—not promise—a small pilot.
The goal is not to defeat resistance.

It is to separate the warning that improves the protocol from the inertia that merely protects the status quo.

Offer expertise or an objection