From sign-up to a running QA operation, in ten steps.
This is the walk a firm takes from its first login to a company where the field runs on evidence, the paperwork writes itself, the AI assistants chase what is missing, and the invoice comes from proof. Every step here runs on the thirty-day trial.
In the order you will actually do them.
A twenty-minute setup call at sign-up covers the first five with you; the rest is the job running.
Sign upStep 1
Your firm gets its own workspace — your name, your logo, your colours — separated from every other firm's and protected. Ten AI assistants are already on the roster. Minutes, nothing to install, no card.
Invite your peopleStep 2
Everyone lands with a login and exactly the tools their job needs: a technician gets scanning and checklists, a project manager gets the dashboard, the schedule and the approvals, the office gets billing and security. Team members are unlimited, subs and the owner included.
Set up the jobStep 3
Project, buildings, rooms, and every machine from a template — each born with a QR code and its complete list of required documents. "How complete are we?" has a real answer from minute one, because the register knows what is owed, not just what showed up.
Capture the designStep 4
Design-phase QA: requirements get a feasibility and testability check, disciplines sign off on the record, and any shortfall becomes an approved deviation with its residual risk written down. The front of the record, before a shovel moves.
Build your formsStep 5
Supervisors define what gets collected — the steps, the proof each one needs, the allowed ranges — with no developer and no deploy. Put any form on a weekly or monthly cadence and it opens itself when it falls due.
Run the fieldStep 6
Scan the sticker, follow the steps, capture the proof. A torque reading out of range is refused on the spot. Problems get logged with a photo, a severity and a clock nobody can stop; pin them straight on the drawing.
Advance the tagsStep 7
Each machine climbs the L0–L5 commissioning levels, earning its physical colour tag — red, yellow, blue, green — one signed, evidence-gated step at a time. A level cannot be claimed; it has to be earned.
Let the AI assistants workStep 8
They chase missing paperwork, classify deficiencies, draft the daily and weekly reports, keep the closeout package current, and watch ETAs and warranties — and stop at the approvals queue before anything consequential goes out. A named person decides.
Bill from proofStep 9
Rate cards price the work; quantities fill from closed cases and recorded hours; one click pushes the assembled invoice into your own QuickBooks. Every line traces to a signed, evidence-gated step.
The QuickBooks push is for customers — on a trial the invoice assembles but does not leave.
Close out and hand overStep 10
The closeout package has been assembling itself since day one; at turnover it names exactly what is missing until nothing is. The owner accepts inside the record and the site moves to them. After handover the record keeps living: warranty, maintenance, years of scan-and-see history.
Exports and downloads switch on when you upgrade; everything else runs in full on the trial.
Bring a job that is halfway done.
Add each machine at its real phase and import the previous 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, and the package starts from where the job actually is.
One generator, from the order to its next life.
Twelve stages, one QR code — who acts at each, what the AI assistants do on their own, and the proof each stage needs before the record can move.