Oryn ships Washington State mandatory forms as first-class citizens of the product. Every form is generated from your matter data onto pleading paper, with the line numbers, header frame, vertical text box, and signature block a court expects.

What “pleading paper fidelity” means

Every bundled template retains:

  • header1.xml with line numbers 1\u201325
  • The VML Text Box 1 shape that holds the vertical bar
  • The court-specific caption block
  • The attorney signature block (suppressible via omitAttorneySignatureBlock for orders and declarant-signed forms)

A PR that clobbers any of that frame fails CI. This is enforced, not aspirational.

Generating a form

  1. Open the matter
  2. Go to PleadingsNew pleading
  3. Pick the form (e.g., FL All Family 140 Parenting Plan)
  4. Review the pre-filled fields pulled from the matter spine
  5. Answer the form-specific questions the matter data doesn\u2019t cover
  6. Click Generate
  7. Review the resulting .docx (or PDF export)

Under the hood

Oryn uses docxtemplater with custom helpers:

  • paragraphLoop(key, indentTwips) for repeated paragraphs (children, exhibits, findings)
  • tableWithRowLoop({ loopKey, columns }) for tables like prior search actions in FL 154 or service attempts in FL 104
  • checklistLoop(key) for documents-served checklists in FL 107

All three shipped in the forms sprint that added 49 forms across 10 packs.

Firm-custom templates

You can upload your own templates alongside the mandatory forms. Custom templates follow the same data-binding conventions (Mustache-style placeholders resolved against the matter record) so they mix cleanly with bundled forms.

Last updated: 2026-04-21 \u2190 All articles