Walkthrough · Track B

The attorney runs the whole show.
The case builds itself.

Client walks in with a folder — paystub, tax return, credit report, bank statements. Sarah opens her app, makes a case, drops the documents in. Minutes later: Ch 7 petition assembled, means test computed and explained, exemptions resolved, every creditor address verified. Later that week the court drops a docket and the case absorbs that too.

STEP 01 00:00

New case → Petition

Top bar, + New → New Case. Bankruptcy, individual debtor, Ch 7, district of choice. Saving creates the case and the first draft filing in one move — B 101 voluntary petition seated automatically.

New-case wizard at the petition step: Ch7 individual, district picker, draft filing about to seat B101

STEP 02 00:45

Pull data — paystub, tax, bank

Forms tab. Pull data opens the import tray — every source the firm's configured. Credit bureaus, paystubs, tax returns, bank statements, CSV. Each is a recipe: what it writes, where. Sarah drops three documents, each lands as one sourced entry on the case.

Pull-data tray open with paystub, tax-return, and bank-statement tiles highlighted

STEP 03 01:40

Credit report builds Schedule D

Pull data → Credit report. Trade-lines arrive as a list — balance, account, payment, address, type. Confirm, and the secured creditors slot straight into creditors[]. Schedule D fills itself, addresses normalized, account numbers redacted to the last four.

✓
          One write, every form
          The credit report writes to the schema once. Schedule D, the means test's secured-debt rollup, and the plan calculator's lien total all read the same keys — no copy-paste.
        

Form lens on Schedule D after credit-report import: four secured rows filled, source chip = credit-report

STEP 04 02:30

One click → 116 fields appear

Form lens on B 122A-1. Sarah flips the marital-status radio to married, filing separately. The whole Column B income block lights up gold and slides into place — visibility computed live from one binding, the cascade animated so you can see the dependency.

★
          The reveal
          Every conditional row on every form is just an expression on the schema. Edit the gate, watch the dependents arrive. No form-builder logic, no hidden if-then ladders.
        

Form lens on B122A-1 mid-cascade: marital status flipped, Column B income rows in gold reveal animation

STEP 05 03:15

Means-test verdict on the Overview

Overview tab. The verdict strip across the top carries one pill per calculator — Means Test PASS, Exemptions OK, Plan N/A for Ch 7. Click the means pill to land directly in the calculator with its explained worksheet open.

Overview tab with verdict strip showing PASS / OK / N/A pills for the three calculators

STEP 06 03:55

Why the verdict is the verdict

The means-test worksheet expands as a trace — each line is the expression with substituted values. gross_wages × 12 = $50,400, six-month lookback averaged, household-size step-down applied, median compared. Every input traces back to its source document.

∑
          Auditable math
          When opposing counsel asks "where did this number come from?" you point at the worksheet. Inputs, expression, output — one panel. The court file can defend itself.
        

Means-test TraceDisclosure expanded with substituted values and per-line sources

STEP 07 04:30

Exemption resolver, asset by asset

Property tab. Each asset row shows available vs claimed; the resolver picks the right statute per asset and tells you where the value comes from. A trace expands for each row — homestead cap, wildcard remainder, federal vs state choice — same explained-worksheet shape as the means test.

Property tab exemption resolver: per-asset rows with available/claimed columns and a trace open on the homestead

STEP 08 05:00

Schedules built — the real PDF

Forms → PDF lens. The real fillable PDF for Schedule D, populated. The focused field on the page maps back to a schema key in the rail; click a row in the rail and the highlight jumps to the box. Same data, third projection.

PDF lens on Schedule D page 1, focused on a secured creditor row with the rail showing the source key

STEP 09 05:40

Petition ready to file

Court → Filings. The Ch 7 group expands — petition, schedules A/B through J, SOFA, means-test forms — each leaf populated from the schema, the pre-flight rail showing readiness across the packet. Download merged PDF, sign, file.

Court → Filings with the Ch7 group expanded and the pre-flight readiness rail on the right

STEP 10 06:15

Court drops a docket. Case absorbs it.

A week later, Court → Docket. Paste the docket PDF and the parser turns it into typed entries: §341 meeting set 2026-06-12, response deadline 2026-06-19. Each entry auto-creates a deadline on the calendar and a question thread on Manager — nothing to retype, nothing to forget.

Court → Docket after import: entries list with deadline pills and a question thread chip on each row

Same engine; different door. Pull-data is the deliberate path; docket-import is what the court hands you back.

The other directions.

Same case, same outcome — but starting from the client, or a guided tour of the chrome itself.

Chapter 13 from the portal → Get to know your case → Pricing

The attorney runs the whole show.The case builds itself.