Each tool runs entirely in your browser, keeps no copy of what you paste, and reports Pass, Fail, Not checked or Unassigned — never a score.
This column holds the four browser tools that stand behind the guides and workflows. It is not a directory of software and not a comparison: each page takes one piece of work and hands back a table you keep. Use the preflight runner for a file that is about to be delivered, the claim ledger for a summary whose claims need a location in the source, the action register for notes that have to become tasks with owners and dates, and the commitment diff for an original and a rewrite that must not drift apart.
If something is already open on your desk, take the tool that matches it. If you want the reasoning before the rows, the Start here section below points to the guide each tool grew out of, and every tool page carries a worked example, the fields it asks for and the one decision it refuses to make.
What this column is not: a score, a grade, a ranking or a recommendation, and nothing here reviews or measures a product. The states a row can end in are the whole output, and they are set out below.
An assistant drafts the summary, the email, the deck or the notes, and a person still has to check it, tidy it and hand it over. Each of these four pages does one part of that job for a named piece of work: no account, no upload, no sign-in.
Works down ten delivery checks on one file before it leaves your desk: dimensions, licences, links and dates, the smallest text at viewing size, transparency, and a copy kept in the release folder.
Turns a summary or an AI draft into one row per claim, with the place in the source that should carry it, a state for the row, and a field for what the source actually says.
Builds a register from meeting notes or a transcript: one row per agreed task, with the deliverable, an owner, a due date and the timestamp in the recording where it was agreed.
Compares an original and a rewritten version of the same text and reports only what its published word lists can name: obligation wording, conditions, dates, deadlines and amounts.
Fictional walkthrough, invented for this page: an assistant drafts a six-page onboarding pack for a new client, and somebody has to get it out of the door. Every name, date and amount below is made up.
None of that is a verdict. Each tool leaves a row in a state a colleague can read, and a file you can print, copy or export before the tab closes.
Each page below is the worksheet version of a longer method. Read the guide when you want the reasoning; open the tool when you want the rows.
Still deciding what to use? Browse all guides, take the research brief workflow from source documents to a checked draft, or read how we check a page before it goes up.
This is an index of the pages on this site that discuss each product; it is not a tool.
No. Each tool holds its rows in the open tab only: no cookies, no local storage, no request that carries them off the page. Closing the tab discards them, so export, copy or print before you leave. If your browser blocks JavaScript entirely, the same ten preflight questions are still readable in the downloadable export checklist.
Because ToolVerity publishes no invented numbers. A row ends in Pass, Fail, Not checked or Unassigned, and a tool may count how many rows sit in each state. That count is as far as it goes: no percentage, no grade, no ranking and no product recommendation.
Runs entirely in your browser. Nothing you type or paste is sent anywhere.
