Clear words. Working documents.

Start with a contract, an offer letter, or a privacy notice. Our business library pairs clear legal writing with fillable questions and a lawyer’s review. Twelve new business templates join our letters and government forms. Navigator connects each answer to the document it belongs in.

Explore the templates ↗Follow the format ↓
agreement.md
---
kind: agreement
title: Sample agreement
prompts:
  delivery: How should notices arrive?
choices:
  delivery:
    email: By email
    post: By post
questionnaire:
  BEGIN: { _: custom_single_choice__delivery }
  custom_single_choice__delivery: { _: END }
  END: {}
# … workflow and other metadata
---

## I. Notices

Delivery method: {{custom_single_choice__delivery}}.
YAML Frontmatter+Markdown body

Many sources. One working format.

Markdown in the middle.

Email, conversations, questionnaires, and documents supply the material. A lawyer confirms the facts and scope. Notation brings the text and its structure together so the work can be read, checked, revised, and rendered.

  • Conversations

    Email, text messages, and discussions supply facts for confirmation.

  • Questionnaires

    Typed questions gather the answers a template needs.

  • Word documents

    Managed import projects supported document structure into notation.

  • Markdown templates

    Authored prose and Frontmatter declare the document and its process.

Notation pen

Computable legal format

Markdown + Frontmatter

  • Word revisions

    Supported edits return to the original package with tracked changes.

  • Typst

    The Typst rendering engine typesets Markdown into PDFs, with the document's layout, headings, and page numbering.

  • Government forms

    Declared field mappings fill the issuing agency's PDF.

  • Browser previews

    Read the document and explore its questionnaire before running it.

One file. Four connected parts.

A template is the blueprint. Bind it to a respondent and a Project, and it becomes a running Notation with answers, review, and a history.

  • Metadata

    Frontmatter names the document and the rules that govern its structure.

  • Questionnaire

    Typed questions collect answers. Prompts supply wording; choices name the available options.

  • Workflow

    Explicit steps describe how the work advances and where a lawyer makes the decision.

  • Body

    Readable prose carries headings, clauses, and placeholders that resolve from the answers.

Plain text. Precise checks.

Navigator's Rust rule engine checks declared kinds, required fields, question types, placeholders, and workflow structure. The CLI and editor use the same rules.

  • Check the project

    navigator project gate validates the repository's Markdown, YAML, and notation contracts together.

    Read the rule reference

  • Preview a file

    navigator notation preview opens a local browser preview of a template and its questionnaire.

    Learn to author a notation

  • Check as you type

    navigator-lsp shows diagnostics and hover explanations in your editor, using the rule engine behind the CLI.

    Read the Frontmatter guide

Every notation kind

Every value S103 accepts, generated from the same source the gate validates against — a definition, its category, and the structural rules bound to it.

  • letterCorrespondence

    A letter the firm sends on the client's behalf

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • filingFiling

    A document filed with a government body

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • willInstrument

    A last will and testament

    • N123 — Depth-1 sections must be numbered with Roman numerals (`I.`, `II.`, …), and the body must open with its own `# ` title.
  • trustInstrument

    A trust instrument

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • directiveInstrument

    An advance health-care or durable financial directive

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • agreementInstrument

    A private agreement (employment, contractor, LLC operating)

    • N123 — Depth-1 sections must be numbered with Roman numerals (`I.`, `II.`, …), and the body must open with its own `# ` title.
  • pleadingCourt paper

    Court paper filed with a court (complaint, motion, brief)

    • N123 — Depth-1 sections must be numbered with Arabic numerals (`1.`, `2.`, …), and the body must open with its own `# ` title.
  • onboardingCorrespondence

    The engagement that opens a matter — one instrument or a bundle

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • offboardingCorrespondence

    The firm-signed letter that closes a matter

    • N123 — Depth-1 sections must be numbered with Roman numerals (`I.`, `II.`, …).
  • memoCorrespondence

    An analytical work product (a review memo or opinion)

    • N117 — Every `custom_text__*` state must be allowlisted, and a memo's allowlist carries no section role: the question presented, the analysis, and the recommendation are body prose the attorney writes at `lawyer_review`, never questionnaire state.
  • eventContent

    A public event page (web/content/events/)

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • postContent

    A published blog post (web/content/blog/)

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • workshopContent

    A public workshop / teaching page (web/content/workshops/)

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • githubEngineering

    An engineering intake notation that opens a GitHub issue or pull request (templates/github/)

    • N119 — The questionnaire may declare only the engineering-intake field grammar; a `github` notation binds to no respondent and never reaches lawyer review.
  • review_queue_workbenchMatter dashboard

    A matter dashboard: a filterable item rail, a detail pane, and a per-item status

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • verifier_split_viewMatter dashboard

    A matter dashboard: drafted assertion beside the source page, both marked

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • matter_status_consoleMatter dashboard

    A matter dashboard: workstream state, key dates, and the principal's decisions

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • docket_deadline_boardMatter dashboard

    A matter dashboard: dated rows with hard/soft classification and calendar export

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • document_workbenchMatter dashboard

    A matter dashboard: a draft body with phrase-anchored comments

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • authority_libraryMatter dashboard

    A matter dashboard: authorities with citation, holding, quote, and position

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • discovery_cockpitMatter dashboard

    A matter dashboard: numbered request/response pairs with objection tracking

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • hearing_consoleMatter dashboard

    A matter dashboard: ordered stages with argument points and anticipated questions

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • deliverable_packageMatter dashboard

    A matter deliverable: a linear handoff page of inclusions, exclusions, and files

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

  • engagement_billing_recordsMatter dashboard

    A matter dashboard: engagement letter, invoice, and prebill review

    No kind-specific structural rule beyond the shared Markdown checks every file gets, regardless of kind.

Explore the templates

Correspondence

Instrument

Filing

Court paper