FamilyLawPath is the front door to a family law firm. It listens, repeats back what you said in your own words, and shows you where you are on a path that most people walk without ever being shown a map. A person from the firm calls you.
Every screen has a leave button in the same place. Pressing it closes this site immediately and replaces it. Escape twice does the same thing.
These are the stages a family matter usually moves through. They are typical. No date is attached to any of them, because nobody can honestly tell you when a court will do anything.
What the software can tell you is which stage you are standing in, and what the firm is waiting on. That is the part people are never told.
In your own words, once. Typed or spoken. Nothing is a form field until it has to be.
Stage 01At a time you said is safe for you. Text only, if that is safer.
Stage 02A retainer agreement, in writing, with the scope of the work stated in it.
Stage 03Applications, answers, financial statements. Prepared by the firm, reviewed with you.
Stage 04Most matters resolve before trial. That is a statement about the system, not about yours.
Stage 05Two lines, in your words, before anything else. Not a summary and not advice. If it got it wrong you correct it, and it uses your correction.
Before it asks anything about the matter. A window you choose, or text only, or no contact at that number at all.
Orders, agreements, statements — photographed with your phone, whenever you are ready. You can keep going without any of it.
Not paused politely while a chat window keeps talking. Stops. The screen changes to shelter and crisis numbers for your region, and the matter questions do not come back until you say to bring them back.
There is no celebration anywhere in that part of the product. No progress bar, no green flash, no sound. It is the one place where taking the encouragement out is the whole design.
It is a constraint, not a policy. The matter questions are not reachable while a flag is open. There is no screen in the product that routes around it.
Intervals govern re-routing, not a clock. If a flagged file is not acknowledged inside an interval, it re-routes to the next operator. No callback time is ever quoted to a client.
Stages are typical and dates are never shown. The path tells you where you are standing. It does not tell you when anything will happen, because that is not knowable.