The register knows what every machine owes.
Required per machine, per phase: submittals, test reports, certificates, O&M manuals — 200-plus document types across ten categories. From day one the register lists what is required and not yet received, so the chase starts while the sub is still on site.
This is the documents part of Veristep: the register of what every machine owes, and the chase that keeps it moving.
This used to be a shared drive with two hundred folders, a submittal log in a spreadsheet that went stale the week it was built, and an inbox of RFIs nobody could say were open or already answered. Knowing what was missing meant opening every folder and checking by hand.
The register shows, per machine, what was required, requested, received, reviewed and approved — each move dated and attributed — so the completeness figure on the closeout package is the register itself, not a percentage someone estimated the night before the meeting because nobody had time to check every folder.
What changes on the job.
Catch the gap in week 2, not week 20
The register knows what is supposed to exist, not just what showed up — so a missing document is caught early, not at closeout.
Every log is real, not a spreadsheet tab
Master and equipment document registers: 200-plus document types across ten categories, required per asset per lifecycle phase.
Subcontractor documents, always current
The AI assistants keep chasing vendors so the register stays complete without a human reminder system.
Take over a job in the middle
Taking over a project another firm started? Add each machine at its real phase and import the previous firm's records — one at a time, a machine's backlog, or the whole register in one sweep. Attributed and dated, so nothing already inspected is re-inspected.
A free template of the register
Every document each machine owes, by phase, generated from the same defaults Veristep builds a project from. Excel or CSV, no account.
A document is required until it is reviewed, not until it is uploaded.
Each requirement moves required → requested → received → reviewed → approved, with a name and a date on every move. The completeness figure on the package is this register, not a percentage somebody typed.
Connect your own tools
Your systems can read and update the record, locked to your firm alone — the same as everywhere else.
Keys you control
You issue them, and you can take them back any time.
Read and write
Projects, assets, deficiencies and documents — so your other tools can see and update the record.
Locked to your firm
A key only ever reaches your own firm's records. Nobody else's are in reach.
Seven screens, live from a real job. No account.
Put one of your jobs in it.
Thirty days, no card, your whole crew, every feature. A workspace with a job already in it. Exports and downloads switch on when you upgrade.