Vouch

Know which sentences someone still stands behind.

Vouch is a document editor for the people who sign off requirements, instructions and research. Every sentence shows who wrote it. Every sign-off covers the text exactly as it reads, and expires on its own the moment a word changes.

Request access See how it works

requirements / Report export Changes are saved as you

Report export

  1. A team lead can export any report they can see.
  2. The export contains exactly the rows shown on screen, with the filters applied.
  3. Exports are offered as CSV, Excel and PDF.
  4. An export is limited to 50,000 rows.

Marek Nowak vouched for this text on 8 Oct.

His signature covers every sentence above, exactly as it reads.

Change any word in the document.

Approvals cover pages and diffs. The text keeps moving.

A team can now write more in a week than it can read in a month, and a growing share of it is written by models. Writing is no longer the scarce thing. Knowing what has been checked is.

Today a requirement signed off in March and quietly edited in June still looks as trustworthy as the day it was signed. Or the whole page drops back to draft, and someone re-reads all of it to find one changed number.

What other tools approve, and what an edit does to it
ToolWhat is approvedAfter a one-word edit
Pull requestsA diff, when it was mergedThe approval stays on the old change. Checking today's line means following its history back, line by line.
Wiki page approvalThe whole pageThe page goes back to “in progress”, and all of it is reviewed again.
Verified pagesThe whole page, for a periodNothing changes. Verification runs on time, not on what the text says.
VouchThe text, sentence by sentenceThat sentence is marked as changed since the sign-off. The other sentences are still exactly what was signed.

Three small rules carry the whole product.

A sentence is a line, and a line has an author.

Vouch keeps one sentence per line and records who wrote each one. A person who fixes one word gets one line under their name, not a reformatted page.

A vouch is a signature over the text.

It records who, when, and a fingerprint of the document's text. Change one word and the fingerprint no longer matches, so the vouch shows as stale by itself.

Unvouched is the default.

A sentence nobody has stood behind is shown as exactly that. Nobody has to remember to withdraw an approval.

The life of one sentence

  1. Written

    A person or an agent writes it. Saving records it under the writer's own name.

  2. Vouched

    Someone qualified reads the document and presses Vouch. Their name, the time and the fingerprint go into the file.

  3. Edited

    Anyone changes it later. The vouch shows as stale at once, and the sentence is marked.

  4. Reviewed

    The reviewer reads only the marked sentences, as signed and as they read now, and vouches again.

The review sheet in Vouch: three sentences changed since Marek vouched, each shown as signed and as it reads now, with who changed it, and a button to vouch for the text as it reads now.
Review changes. Only the sentences changed since your vouch, as you signed them and as they read now, with who changed each one. Minutes instead of a full re-read.
The provenance view in Vouch: each line of a document with who wrote it and when, newer lines warmer, and the lines changed since the last vouch marked.
Provenance. The same document with who wrote each line and when. Click a line to see everything it has said, newest first.

For the people who know whether a claim is right

Clinical writers, product managers, reviewers and auditors work in rendered documents. Engineers and AI agents work on the same files in git. Neither has to learn the other's tools.

WhoWhat they do in VouchWhat they never have to do
Writer or domain expertWrites and edits documents as formatted text, and vouches for what they stand behindLearn Markdown, git, branches or pull requests
Reviewer or approverReads only what changed since their last vouch, then vouches againRe-read the whole document, or compare versions by hand
AuditorSees who wrote each sentence and who stands behind itRebuild authorship from commit logs and chat
EngineerWorks on the same files with their own toolsCopy text between a wiki and the repository
AI agentWrites and saves under its own name, on behalf of the person running itPass as a person. An agent can never vouch.

Git underneath. Nobody on the review side sees it.

  • Saving is the whole of version control: one change, under your name, shared with the team automatically.
  • No branches, no merges, no conflict screens. If two copies ever disagree, Vouch says so in words and merges nothing.
  • The editor never rewrites a file. Opening and saving without typing changes nothing, and changing one word changes one line.
  • Documents stay plain Markdown files in your own repository, readable without Vouch.
  • Projects group repositories, some read only and some read and write, with the people who may use them.

What it is not

  • Not a wiki. It does not compete on pages, templates or databases.
  • Not a git client. People who use git keep using it.
  • Not a quality management system. It records evidence such a system can use, and claims nothing more.
  • Not for every document. It is for the ones where a wrong sentence costs something.

Vouch is in early access.

Sign in with your GitHub account and ask for access. Tell us what you would use it for, and we will let you in.

Request access