YakForms
YakForms Manager · Forms estate control plane

Your forms estate should not depend on filenames, shared folders and institutional memory.

YakForms gives every form a durable identity, maps every dependency, validates every change, and turns production deployment into a reproducible, reversible release.

Runs in your tenancy or ours. No runtime replacement required.

claim-notice-FNOL.xdp 2 to review
UUID
4f2a…c19e
Revision
r41
Depends on
6 fragments · 2 schemas
In release
2026.09.2
Sheet 01 · The problem

Filenames are not identity

A large form estate is a few thousand PDFs and XDPs spread across a content repository, a build server and three people's memories. Nobody can answer the four questions that matter: which version is live, what it depends on, who approved it, and what happens if the renderer changes.

  • Two files named final_v3 that are not the same form.
  • A fragment edited once, breaking eleven forms silently.
  • An approval that lives in an email thread from 2021.
  • A renderer upgrade nobody dares schedule.
Sheet 02 · What it does

One record for every form you are responsible for

Sheet 03 · Identity

A UUID per form. Paths become aliases.

Import the estate once and every asset gets an identity that survives renaming, re-foldering and repository migration. Each save is an immutable revision with its own digest, so "which version" stops being a matter of opinion.

Name Alias UUID
claim-notice-FNOL /claims/fnol/final_v3.xdp 4f2a…c19e
renewal-pack-motor /motor/renewal.pdf 91bd…7a03
address-block /shared/addr.xdp 08c7…4412
Sheet 04 · Validation

Findings block the release, not the customer

Every revision is validated on ingest — structure, scripts, submit targets, fonts, accessibility. A critical finding stops the release gate. Anything you knowingly accept becomes a recorded waiver with an owner and an expiry, not a silent pass.

  • Critical XFA-204 Submit target resolves outside the allowed host list
  • Warning A11Y-011 3 fields have no accessible name
  • Info FONT-002 Embedded subset missing 2 glyphs used by the Welsh variant
Sheet 05 · Dependencies

Know what a fragment breaks before you change it

Fragments, schemas, stylesheets and images are tracked as real edges. Open any asset and the impact set is already computed, so a shared address block stops being a change nobody is willing to make.

address-block.xdp 11 dependents

claim-notice-FNOL Validated
renewal-pack-motor Validated
benefits-election Needs revalidation
bereavement-claim Needs revalidation

+ 7 more in the impact set

Sheet 06 · Releases

An exact set of revisions, or an exact rollback

A release is an immutable manifest of revision digests. Deploy it to an environment, and if the renewal pack misprints on a Friday afternoon, roll back to the manifest that worked — not to whatever the share drive held at the time.

Version Status Manifest
2026.09.2 Deployed 418 assets · sha 7c1f…
2026.09.1 Superseded 417 assets · sha 2ab9…
2026.08.4 Superseded 411 assets · sha 55de…
Who runs on YakForms

Built for estates where a form is a legal document

Start with an estate assessment

Point YakForms at a copy of your repository. You get an inventory, a dependency graph and a validation report for the whole estate — before you commit to anything.