Preflight check runner
Works down ten delivery checks on one file before it leaves your desk.
Follow practical guides, run the checks in your own browser, and know the limits before you commit to a tool.
Get StartedEach one runs in the tab you already have open. No account, no upload, and a table you can export before the tab closes.
Works down ten delivery checks on one file before it leaves your desk.
One row per claim, with the place in the source that should carry it.
One row per agreed task, with owner, due date and the timestamp behind it.
Compares an original and a rewrite and reports what moved in the wording.
Start with the job. Find the guide, the workflow and the checks that help you finish it.
Missing conditions. Changed dates. Confident conclusions. Learn to spot the small changes that make a big difference.
Check an AI summaryEvery claim in a summary needs a location in the source. Here is a repeatable way to mark them.
Section-by-section work costs a little more time and removes most rewrites.
A warmer sentence should not quietly become a new deadline.
The notes are a claim about the meeting. Here is how to test that claim.
If a row cannot be closed by someone else, it is not an action item yet.
A handoff pack is judged by whether a new owner can act without asking you.
The file your audience opens is the exported one. Check that file.
Scaling the canvas is the easy part. Re-flowing the content is the work.
Format choice is one decision. Dimensions and loading behaviour decide the rest.
Consistency is a written rule set, not a remembered style.
Every material sentence in the brief should point back to a source register row.
The follow-up is finished when someone else can act without asking what was decided.
Both workflows end with a record someone else can pick up: a source register or a checked action list.
Every number on this site arrives with the document or the file behind it, and a page that measured nothing publishes no score.