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.xmlwith 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
omitAttorneySignatureBlockfor orders and declarant-signed forms)
A PR that clobbers any of that frame fails CI. This is enforced, not aspirational.
Generating a form
- Open the matter
- Go to Pleadings → New pleading
- Pick the form (e.g.,
FL All Family 140 Parenting Plan) - Review the pre-filled fields pulled from the matter spine
- Answer the form-specific questions the matter data doesn\u2019t cover
- Click Generate
- 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 104checklistLoop(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.