Plan coverage
Seven plan families, each under its own law
Division orders fail when language written for one system is filed in another - ERISA boilerplate in a COAP, a private-pension formula in a PERS order. The Preparer keeps each plan family on its own clause library, sourced from the documents the plans themselves publish and the regulations that bind them. The six federal-law families may be drafted for a decree entered in any state, with the drafter supplying that state’s marital-property framing; the Nevada PERS order is for a Nevada decree only.
Nevada PERS / JRS
PERS model order · NRS 286.6703 · NRS 125.155
Built on the model order in the official PERS divorce-benefits publication, with the NRS 286.6703 entitlement elements, the NRS 125.155 frozen-valuation recitals, and the retirement-option election tracked to the current text of NRS 286.590 - Options 2 through 8, where the aging model still says 2 through 7.
ERISA plans - defined benefit and defined contribution
29 U.S.C. 1056(d)(3) · IRS Notice 97-11
The sample QDRO language of IRS Notice 97-11 and the required contents of 29 U.S.C. 1056(d)(3), including the survivor alternatives and the shared-versus-separate-interest forms. Where the official sources deliberately provide no sample - the award formula itself - the clause is an original composition in the statutorily required determinable form, and labeled as such.
Military retired pay
DFAS sample language · 10 U.S.C. 1408
The DFAS sample order language verbatim with your case data in the slots - formula, hypothetical, and reserve-points awards - plus the frozen-benefit data recitals DFAS has required for divorces after December 23, 2016, and the SBP election machinery. What is out of scope is stated, never approximated.
Federal COAP, TSP, and IRA
5 CFR part 838 · 5 CFR 1653 · IRC 408(d)(6)
CSRS/FERS orders assembled from the codified model paragraphs of 5 CFR part 838 - the regime where ERISA-styled language causes OPM rejection - TSP orders from the current TSP model language under 5 CFR part 1653, and IRA division by transfer incident to divorce under IRC 408(d)(6), with the taxable-distribution trap warned in the draft.
Workflow
Four steps to a reviewable draft
- 01
Pick the plan type
Seven plan families, each with its own order document, qualification requirements, and clause set - the wizard shows what each is grounded in before you commit.
- 02
Caption and parties
Court, case number, parties, participant and alternate payee. Identifiers stay out of the order body: each system's official separate-transmission device carries them instead.
- 03
Make the elections
Survivor coverage, gains and losses, COLAs and subsidies, refund bars, award form - every legal fork is presented with its options and authority, and you elect. Silence never chooses.
- 04
Generate the draft
One request assembles the .docx in memory and streams it back on Nevada pleading paper - or, for a decree entered in another state, in a generic court format - ready to review and file. Nothing is stored, logged, or retained - when the download finishes, the data is gone.
Why trust it
Deterministic, sourced, and yours to elect
Every clause is fixed text traceable to its source in a per-clause manifest; the same case data always produces the same draft. The elections that carry legal consequence - survivor coverage above all, the omission Nevada law will not forgive (Henson v. Henson; NRS 125.155(3)) - are never defaulted for you: the wizard shows the fork, the authority, and the cost, and records what you chose. The draft leaves marked for attorney review, because that is what it is.
Questions
What attorneys ask
- Where does the order language come from?
- From each plan's official source: the PERS model order in the official PERS publication, IRS Notice 97-11 sample QDRO language, the DFAS sample order language, the codified model paragraphs of 5 CFR part 838, and the current TSP model language. Every clause is fixed, vetted text with variable slots, and a per-clause source manifest records the authority behind it. The few clauses the official sources deliberately leave unsampled are original compositions in the statutorily required form, labeled as such.
- Is anything stored?
- No. Your answers are sent once, over TLS, to a deterministic document service that assembles the .docx in memory, streams it back, and retains nothing - no storage, no content logging. If you want the inputs kept for the next session, that is a separate, explicit choice: an encrypted client matter your browser encrypts before anything is saved.
- Will the plan accept the order?
- Qualification always rests with the plan administrator and the court. The generated document is filing-ready - Nevada pleading paper for a Nevada decree, a generic court format otherwise - with no draft banner and no footer note, so the attorney's review is what stands between the download and the filing. The drafting tracks each system's stated requirements - 29 U.S.C. 1056(d)(3) contents, NRS 286.6703 elements, the DFAS recitals, the part 838 paragraph structure - and the Scrutinizer will check the finished draft against the same authorities before it goes out.
- Can I draft for a decree entered outside Nevada?
- For the federal-law plans, yes: ERISA QDROs, military USFSPA orders, CSRS/FERS COAPs, TSP RBCOs, and IRA transfer provisions follow federal plan law, and the wizard takes the state that entered the decree. You supply that state's marital-property framing (community property or equitable distribution) and the order recites the state and the regime you elected - nothing more. No Nevada statute or decision is recited for another state's decree, and no other state's authority is recited either; confirming the decree state's division law, caption, and local formatting rules is the drafter's work.
- What is out of scope?
- State retirement systems other than Nevada PERS - a decree from another state can carry the federal-law orders, but not that state's public-pension order. Also military members who entered service before September 8, 1980, and Chapter 61 disability divisions. The wizard says so instead of generating an approximation - a wrong order is worse than no order.
F-Law provides informational document-assembly tools, not legal advice, and creates no attorney-client relationship. Every draft is for review by counsel and is subject to acceptance by the plan administrator and the court. Sources: official PERS divorce-benefits publication; IRS Notice 97-11; DFAS sample order language; 5 CFR part 838; TSP model language; 29 U.S.C. 1056(d)(3); NRS 286.6703, 125.155; 10 U.S.C. 1408; IRC 408(d)(6).
