What firms ask before they switch.

Take the tour: seven screens of a real project, no account, nothing you can break. It puts a finished job next to one that's still running, so you can see a complete package beside an unfinished one.

The tour is a look-only walk-through. The sandbox is the same demo workspace with the controls live, and it resets when you leave. The trial is your own workspace with your own data, never reset — the real thing from the first minute.

A firm name, your name, a work email and a password of at least twelve characters. No card. You agree to the terms on behalf of your firm, and we keep a record of which version you agreed to.

One project with one machine, its real document requirements, and one open check waiting on evidence — day one of an actual job. Then you import your own: rooms, people and machines from CSV, or add them one at a time.

Bring in your rooms, people and machines from spreadsheets, then open Take over a job. It lists every document each machine already owes, you check the last firm's paperwork against it, and whatever's missing becomes your chase list.

Yes. The field app holds what you capture — steps, photos, clock-ins, deficiencies — on the device and sends it once it has signal, under the same rules as everything else. If something is refused (a reading out of range, say), it comes back on that item instead of disappearing.

A step that cannot be passed on somebody's word. It names what has to be captured — a photograph, a reading inside a range, a signature, a document — and the check stays open until that exact thing is attached.

A required step is still missing its proof, or the check needs signing off by someone who didn't do the work. It tells you how many steps are left. Everyone gets the same answer, administrators included.

No. The rule doesn't care who you are; nobody can close an unfinished check, and that's tested, not just promised. It's what makes a closed check worth something a year later.

Add a correction: a new entry, with their name and the time on it, on the open check, saying what it fixes. Nothing is edited in place, and closed evidence is never rewritten.

From templates: a named, ordered list of steps for a kind of work, written once in your own procedures' language. Ours cover the common kinds of work; you add your own. Every machine of a type inherits them.

Yes. Each asset carries its L0–L5 level. A level can't move on until the proof the template names is in, and passing a level earns a physical colour tag for the machine.

As deficiencies: a severity, who's responsible, a due date and a days-open clock. One can't close without a photo of the fix and the name of whoever checked it. When the same problem keeps showing up, it becomes an NCR with a corrective action.

A live list of what's done and what's missing, from day one — each machine's requirements come from its equipment type, so the package starts at 0% already knowing what it needs. Every closed step lands in it automatically; nothing to assemble at the end.

Yes. The owner signs into a portal and sees the register, its gaps, the deficiencies raised against their building and the evidence behind every closed check. They don't see the firm's rate cards or approval queue.

The firm offers the finished site inside the platform. The owner accepts under named terms, and the site — machines, checks, evidence, warranties, maintenance routines — moves to the owner's own workspace. The firm keeps its sealed history of the work.

Then nothing changes: the firm keeps the project, the owner keeps the portal, and the site stays active in whichever months it has open checks.

The firm keeps it as an archived project for as long as it is a customer. If the firm's plan ends, the ninety-day export window applies like any other data.

It is tamper-evident, so it cannot be quietly altered; it is exportable, so it is not hostage to us; and it follows the site to the owner, so it does not end at turnover. Warranty windows count down on it and maintenance runs on it.

The platform is $495 a month, with unlimited people and every module. On top of that, each project costs $495 in any month it has an open check. Past four projects the price drops: projects 5 to 8 are $445, 9 to 12 are $395, and every one after that is $345. Pay yearly and you get two months free: $4,950 for the platform, $1,950 for the branded workspace. Projects are always billed monthly. Start with a 30-day trial, or pay from day one. Firms we approve can pay by invoice, net 30.

A project with at least one open check in a given month — open one on the 1st or the 31st, it counts either way. On hold with nothing open costs nothing that month; closed projects are archived free, for as long as you're a customer.

Yes, on every plan including the trial. Your office, your field crews, your subcontractors, the owner — per-seat pricing quietly decides who gets an account, and the people it leaves out are usually the ones holding the evidence.

Your colours and logo appear on every screen in every plan, including sign-in. The branded-workspace add-on — $195 a month on top of the platform fee, or $1,950 a year — puts the whole workspace on a domain you own (qa.yourfirm.com): turn it on from your plan page, set the hostname, add one DNS record. "Powered by Veristep" stays on the signed-out screens.

An owner who mandates Veristep across firms and sites is priced under a program agreement — projects, sites, years, an MSA and a DPA — since they're buying for the whole job, not a seat for themselves. The firm price is the floor, not the ceiling.

No. The trial takes no card. When you're ready, pay by card from your Plan page — or, for a firm that needs a purchase order, ask to be billed by invoice — and everything switches on right where you left it: exports, downloads, the API. You can also skip the trial and pay from day one.

Anything that lets data leave: exports, report and file downloads, the public API, the QuickBooks push. Every feature is on; the record stays inside until you are a customer.

Administrators see the whole firm; technicians see the work — checks, evidence, assets, schedule — without billing or security alerts. Owners and clients see only their own job, via a portal; subs and vendors see only what concerns them. It's enforced underneath the app, not just hidden from a menu.

Yes. Admit them for their scope and they see the documents they owe and the equipment they supplied, and can upload against those requirements. They see nothing else.

Yes, as an option any person can turn on (an authenticator app, with a step-up at sign-in). Requiring it for every administrator across your firm isn't switched on yet; the readiness register lists it as opt-in.

Their relationship is ended; their access stops; everything they recorded stays attributed to them on the record. Offboarding never deletes evidence.

Yes. One identity, many relationships: an inspector who works for one firm and is a client contact for an owner switches between them, and each side sees only what its relationship allows.

Ten assistants with first names and job titles — Document Control, Reporting, Closeout, Commissioning and so on. They're logged and reviewed exactly the way a person's work is. They hold no credentials and claim none.

Low-risk legwork: chase a missing document, draft the weekly report, draft the closeout index, flag a stalled check. Anything consequential is written as a proposal and waits in the approval queue for a named person to approve, refuse or edit.

No. Your firm can limit which tools an assistant uses, but nothing risky goes through without a person approving it. That part isn't a setting.

It carries an 'assisted' tag naming the assistant and the person who decided. The activity log shows every run: what went in, what it did, what came out, and who approved it.

Gemini today, behind one interface; other providers are supported by configuration. The provider receives only the text of that draft. The provider and its terms are listed under subprocessors on the security page; we do not train models on customer data.

Database, files and authentication on Supabase in AWS us-east-2 (Ohio); the application on Vercel. Nothing is stored outside the United States.

Every record carries its organization and project, and access is decided at the record, not the screen. An automated test signs in as each kind of person and checks that even an administrator can't read anything belonging to another firm.

No. Activity, sign-ins and security alerts can only be added to — never edited or deleted, by anyone. Each entry is linked to the one before it, so any change shows up, inside Veristep or in the export.

No. The controls an auditor examines are built and most are proven by tests; the audit itself has not been scheduled. The readiness register says exactly what is proven, built, opt-in and not yet — including backups, pen test and SLA.

Yes, as part of a program or customer agreement. The terms of service and privacy policy are published and versioned; a program agreement adds the paper a procurement team needs.

Privately, to the contact in /.well-known/security.txt. Every report is investigated, and every access in Veristep — including ours — is on the audit trail.

Yes: one archive with every record as CSV — including the full audit trail — and every uploaded file, on demand, for customers. Plus specific exports: audit trail, COBie asset handoff, payroll hours, billable lines, schedule.

The workspace goes read-only, and nothing is deleted. You have ninety days to export everything in bulk — reactivate within that window and everything resumes in place. After two notices on day ninety, it is archived: unreachable but intact, every record and file kept for two years. Reactivating costs $495 once and restores everything exactly as it was. When the two years end, or sooner at your written request, the workspace closes: files and access are removed, and the audit trail stays sealed and unreachable.

No. An archived workspace is kept, unopened, for two years from the day it was archived. Ask to reactivate from your plan page; $495 once, the plan resumes from that day, and every record and file is exactly where you left it.

Alongside them. Firms usually keep the general contractor's platform for RFIs and drawings and run the commissioning record here, because this is where the rules actually hold. CSV exports and the API are how the two talk; there's no built-in two-way connection today.

Yes, for customers: rate cards price proven work, and the invoice is pushed to your own QuickBooks Online, with status read back. Veristep never holds a dollar. Payroll hours export as CSV for QuickBooks Payroll, Gusto or ADP.

A public API scoped to your organization by key: read projects, assets and deficiencies, and create deficiencies. Customers only; it is one of the things that switches on at upgrade.

Locations, people and assets from CSV — you see a preview first, and every row is checked again as it goes in. A Veristep archive re-imports the same way, so a workspace can be rebuilt from its own export.