47 questions, answered short.

The tour: seven screens of a real project, no account, read-only. It crosses a finished job and a running one so you can see a complete package next to an incomplete one.

The tour is a read-only walk. The sandbox is the same demo tenant with the controls live, reset when you leave. The trial is your own tenant, with your data, never reset — a real customer workspace from minute one.

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 the acceptance is recorded with its version.

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.

Import the register (rooms, people, assets from spreadsheets), then run the adoption sweep: it lists every document each machine already owes, you reconcile the prior firm's manifest against it, and the gaps become the chase list.

The field app queues what you capture on the device — steps, photographs, clock-ins, deficiencies — and replays it through the same server rules when it has signal. A refusal (a reading out of range, say) comes back against the item rather than being dropped.

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 evidence, or the case needs independent acceptance by someone who did not do the work. The refusal names how many steps are left. It comes from a database trigger, so an administrator gets the same answer.

No. The triggers do not check who you are. A database superuser cannot close an incomplete case — the stress suite proves it. That is what makes a closed check worth something a year later.

Add a correction: a new, attributed, logged entry on the open case that references what it corrects. 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. Platform templates cover the common cases; you add your own. Every machine of a type inherits them.

Yes. Each asset carries its L0–L5 level; each level is gated by the evidence the template names, and passing a level earns a physical colour tag for the machine.

As deficiencies: severity, a responsible party, a due date, a days-open clock. One cannot close without a fix photograph and a named verifier. A pattern becomes an NCR with a corrective action.

A live list of what is done and what is missing, from day one. Each machine's requirements come from its equipment type, so the package knows on day one everything it will need and reads 0%. Every closed step lands in it as it closes; there is 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. Not 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, cases, evidence, warranties, maintenance routines — moves to the owner's own tenant. 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 append-only and hash-chained, 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.

$495 a month for the platform — unlimited people, every module, archive kept live — plus $495 per project in any calendar month that project has at least one open check. Annual on the platform only: $4,950, two months free.

A project with at least one open check in the month. Open a case on the first of the month or the last, it is an active month. A project on hold with nothing open costs nothing that month. A closed project is archived free for as long as you are 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.

An owner who mandates Veristep across firms and sites is priced under a program agreement — projects, sites, years, an MSA and a DPA — because they are buying for everyone on the job, not a seat for themselves. The firm price is the floor, not the number.

No. When you are ready, you ask to upgrade from your plan page; we set up the agreement; the moment it is signed, exports and the API switch on with everything exactly where it is.

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 — cases, evidence, assets, schedule — and no billing or security signals. Owners and clients see their own job through a portal. Subcontractors and vendors see only what concerns them. All of it enforced by the database, not the 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). Organization-wide enforcement for administrators is not switched on yet; it is on the readiness register 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 agents with first names and job titles — Document Control, Reporting, Closeout, Commissioning and so on. They are people in the data model, so their work is audited on the same terms as a human's. 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. A tenant's policy can tighten which tools an agent may use; the runtime refuses to unlock high-risk autonomy regardless of policy.

It carries an 'assisted' tag naming the agent and the person who decided. The activity log shows every run: inputs, tool calls, results and the approval that gated them.

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.

Row-level security on every table: each row carries its organization and project, and the database decides who may see it. A test suite runs the real migrations and queries as each person to prove an administrator reads zero rows of another tenant.

No. Events, sign-ins and security signals are append-only by trigger with no override, and each event is sealed with a hash of the one before it. Alter one and every later hash fails to verify — inside the platform or from 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 audit spine with its hash chain — 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. For ninety days you can export everything in bulk. Reactivate before then and everything carries on in place. After two notices the tenant is closed: files and access are removed; the append-only audit spine stays sealed and unreachable.

Alongside them. Firms usually keep the general contractor's platform for RFIs and drawings and run the commissioning record here because the enforcement lives here. CSV exports and the API are how the two talk; there is no native two-way sync 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 with a preview and a re-checked write. A Veristep archive re-imports the same way, so a workspace can be rebuilt from its own export.