Skip to main content

How We Build Legal Templates

Templates on Forms Legal name the statute they rely on where one applies, are checked by a structural validation script when they are added or changed, and show the date their text was last edited. The templates are written and maintained by the Forms Legal editorial team, and no individual document has been reviewed by a lawyer. This page describes exactly what our process does — and what it does not do.

The Build Pipeline

Templates move through four stages:

  1. 1

    Statute Research

    We identify the primary statute, regulations, and leading case law that govern each document type in its jurisdiction. References include section numbers, not just act names — for example, "Employment Act 1968, Cap. 91, s. 2" for Singapore or "Mietrechtsgesetz (MRG) § 14" for Austria. Research focuses on official government sources: legislation.gov.uk, Légifrance, Gesetze im Internet, eCFR, the relevant Commonwealth legal databases.

  2. 2

    Drafting

    Templates are drafted from the statute research above, using the clauses the cited statutes call for. The result is a structured DocumentTemplateV2 object — field schema, clause text with {{fieldName}} markers, and metadata — that feeds the site's wizard and preview.

  3. 3

    Structural Validation (validate-all.py)

    We run our validation script over templates when they are added or changed. The script checks structure and consistency: every {{marker}} has a matching field and vice versa, select and radio options have labels, field names and section IDs are unique, conditional fields point to real questions, the document metadata is complete, and a statute named in the page description also appears in the template text. We fix the errors it reports. The script does not judge whether the law is stated correctly or is still in force.

  4. 4

    Provenance Tracking (doc-provenance.json)

    Every published template's last-modified date is derived from the git history of its source file, not set manually. The date visible on a document page ("Template last modified: YYYY-MM-DD") is the real git commit timestamp of the most recent change to that file. This provenance record is rebuilt on every deploy, so a date can only advance when code changes — it cannot be fabricated forward. Dates shown before 18 May 2026 were not verification dates: until then every page showed the current day as its “reviewed” date.

What This Pipeline Does Not Do

No individual lawyer review

No practising lawyer has reviewed any individual template. Our templates are statute-referenced reference documents, not legal advice. The validation script checks structure and consistency; it cannot substitute for professional legal judgment about a specific transaction.

reviewedBy not yet active

The codebase contains a gated reviewedBy feature that would display a named reviewer on each document. That feature is not currently activated: no templates have a human reviewer assigned, and we will not display reviewer attribution until genuine individual reviews are completed. The maintainer line on each document page is not a legal-review claim.

Laws change faster than we update

We do not continuously monitor every legislature, and nothing in our process detects on its own that a cited statute was amended or repealed after our last edit. We rely on reader reports and periodic re-research to catch these. Legal changes we have recorded are listed, with dates and official sources, in our legal changes log (/legal-changes). If you find an outdated reference, the fastest correction path is the error-report link on the document page, or email below.

Reporting an Error

If you find an inaccuracy — an outdated statute, a missing required clause, a wrong jurisdiction — email [email protected]. Confirmed corrections are applied to the live site, re-run through validate-all.py, and logged with the exact git commit in our public Corrections Log.

Open Dataset

A machine-readable subset of the templates is mirrored as an open dataset on Hugging Face under CC-BY-4.0, so anyone can inspect the template text and reuse it.