Practitioner resources

Running One Document-Prep Workflow Across Multiple States

Practice Efficiency7 min readUpdated 2026-06-14

Yes, one document-first intake can serve every state your firm works in. The workflow stays the same in each one: collect the client's own documents once, pull the data, and fill the required forms. Two things change per state. First, the jurisdiction unit you file under (counties in California, Colorado, Nevada, Texas, and Utah; judicial districts in Connecticut). Second, the required packet, including each state's financial disclosure form. Build the intake around the documents a client already has, and the same staff motion produces a correct packet in California, Colorado, Connecticut, Nevada, Texas, or Utah.

One document-first intake can feed packets across six states. The per-state work is the jurisdiction unit and the required forms. The workflow itself stays put.

The through-line: intake is the same, packets differ

Most firms treat a new state as a new process. In practice the intake is identical. A client arrives with the same kinds of documents in every state: a tax return, pay records, account statements, and the basic facts of the marriage. The data you extract from those documents is the data the forms need, regardless of where the case is filed. The differences live downstream, in which forms make up the required packet and in how each state names its jurisdiction unit. Once you separate the stable part (the document-first intake) from the variable part (the packet), running several states stops feeling like running several firms.

Variable one: the jurisdiction unit

The first thing that changes per state is the unit you file under. California has 58 counties, Colorado 64, Nevada 17, Texas 254, and Utah 29. Connecticut is the outlier; it has no counties and files by 13 judicial districts instead. Your intake should capture the client's location once and map it to the correct unit for the filing state. For the five county states, that is a county lookup. For Connecticut, the same location field resolves to a judicial district. The data you collect does not change; only the routing does.

Variable two: the required packet and its financial form

The second variable is which forms the packet requires, and the clearest example is the financial disclosure. Every state asks the spouses to lay out income, expenses, assets, and debts, but each one uses a different document. California uses the Income and Expense Declaration (FL-150). Colorado uses the Sworn Financial Statement. Connecticut uses the Financial Affidavit. Nevada uses the Financial Disclosure. Utah uses the Financial Declaration. Texas takes a different path and relies on required disclosures rather than a single statewide financial form. The income, expenses, and account data your intake already captured map into whichever of these the case needs. One set of extracted figures can feed any of the six destinations.

Residency and timing shape your client advice

State rules shape what you tell a client about eligibility and timing, and they vary widely. State residency before filing runs 6 months in California and Texas, 12 months in Connecticut, 91 days in Colorado, and 6 weeks in Nevada; Utah tracks residency at the county level. County residency is 90 days in California, Texas, and Utah, with no separate county requirement in Colorado or Nevada, and Connecticut filing by judicial district. Waiting periods before a divorce can finalize also differ: about 6 months in California, about 91 days in Colorado and non-waivable, about 90 days from the return date in Connecticut, about 60 days from filing in Texas, about 30 days in Utah, and none in Nevada. Treat any waiting period as a floor; the actual time to finalize usually runs longer. None of this alters how you prepare documents; it shapes the guidance you give around them.

Response deadlines and support models for the responding side

When your firm represents the responding spouse, the clock and the math both change by state. The response deadline is 30 days from service in California and 21 days in Colorado, Nevada, and Utah. In Texas the answer is due the Monday following 20 days after service, so plan for roughly three weeks rounded to the next Monday. Connecticut anchors to the return date rather than the service date, so handle its timing as a date-driven item rather than a fixed day count. Child support models differ too. California runs a guideline calculation on both parents' net incomes adjusted for parenting time. Colorado, Connecticut, and Utah use income shares. Nevada applies a percentage of the paying parent's gross income scaled to the number of children, and Texas applies a percentage of the paying parent's net resources scaled to the number of children. The same income data your intake captured feeds each of these models.

What this means for staffing and throughput

Because the heavy lifting sits in intake, adding a state is mostly a configuration question. Your staff learns one document-first motion: gather the client's records, confirm the facts, and review the filled packet. The per-state knowledge that used to live in a single specialist's head becomes the form mapping above. A team comfortable with one state can take on a neighboring one without a new playbook, because the steps a person performs are unchanged. The packet contents and the jurisdiction routing differ underneath, while the work the staff member does looks the same in all six states.

Where to confirm the local specifics

Court fees, local cover sheets, and filing logistics still vary by location, and the authoritative source is the state itself. Each of the six states publishes an official self-represented filing resource, and that page is where you confirm current fees, required attachments, and any local rules before a packet goes out. Use the document-first intake to produce a correct, complete packet, then check the filing details against your state's official self-help filing resource so nothing local is missed at the counter.

Common questions

Do I need a separate intake process for each state?
No. The document-first intake is the same in every state. Clients bring the same kinds of records (a tax return, pay and account documents, and the basic facts of the marriage), and the data you pull from them feeds the forms wherever the case is filed. What changes per state is the required packet and the jurisdiction unit. The intake itself stays put.
How does the financial disclosure map across states?
Each state uses its own financial document, but the underlying data is the same. California uses the Income and Expense Declaration (FL-150), Colorado the Sworn Financial Statement, Connecticut the Financial Affidavit, Nevada the Financial Disclosure, and Utah the Financial Declaration. Texas relies on required disclosures rather than a single statewide financial form. The income, expense, asset, and debt figures captured at intake map into whichever of these the case needs.
What actually differs when I add a new state?
Two things. First, the jurisdiction unit: California, Colorado, Nevada, Texas, and Utah file by county, while Connecticut files by one of 13 judicial districts. Second, the required packet, including the state's financial disclosure form. The residency rules, waiting periods, response deadlines, and child support models also differ and shape the guidance you give a client, while the document-prep steps your staff performs stay the same.
How should I handle response deadlines when representing the responding spouse?
Track them per state. The response is due 30 days from service in California and 21 days in Colorado, Nevada, and Utah. In Texas the answer is due the Monday after 20 days from service, so plan for about three weeks rounded to the following Monday. Connecticut is anchored to the return date rather than the service date, so treat it as a date-driven item rather than a fixed count and confirm the date for each case.

Keep reading

The forms, handled.

Upload documents. Get completed, court-ready forms. We’ll show you.

Show me

Paxora provides document preparation software for legal practitioners. Paxora is not a law firm. This resource is for informational purposes only.