QA Flow - the quality module
Prove the work was right, the first time and two years later
Inspection and test plans your team designs, tolerances the app refuses to let you pass, hold points the main contractor signs by email, and an audit trail that can be shown to have not been edited. Your quality record is your payment record.
Your quality record is your payment record
Retention is released against evidence, and defect claims are defended with it. A folder of photographs nobody can date, taken on a phone that has since left the company, is not evidence. A hash-chained record with capture timestamps and a signature from the person who inspected it is.
Everything in QA Flow
Forms your team designs - not ours
Every trade's inspection plan is different, so you build your own: tasks with photo requirements and recorded readings, with hold and witness points wherever your plan demands them. Start blank or clone a trade template and edit it.
Tolerances the app enforces
Give any reading an acceptance range and the app polices it. Out-of-range readings are flagged as they are typed and can never be passed - they are recorded as failures, with a non-conformance report pre-filled with the reading, the limits and the step it came from.
Room by room, on real project structure
Set up each project's levels and rooms, or import the whole schedule from a CSV. Apply a form to any set of rooms in one action and watch coverage build.
Runs on site - even with no signal
Operatives work through steps in enforced order on the phone; photos carry their capture time and a fingerprint. In basements and cores everything queues offline and syncs in order when coverage returns.
Hold points the main contractor signs by email
Submitting a hold point emails a link showing every completed step, reading and photo since the last one. They approve or reject with one click - no account, no app, no licence. The form pauses until they respond.
Witness points that protect programme
Where the contract only requires that the contractor be given the chance to inspect, serve notice instead of stopping: same evidence link, plus a notice period you set. Work carries on and the point releases automatically if the clock runs out, with the served notice on the record.
It chases, so you do not
Sign-off requests unanswered after 3, 7 and 14 days are re-sent automatically with a fresh link; unsigned method statements are chased at 5 and 10 days. Managers get a weekly digest of everything outstanding. Nothing rots quietly.
Issue records with the clock running
Send any query, submittal, non-conformance, inspection or handover to the main contractor for a formal response. Each send carries a contractual reply period, shows as overdue when it lapses, and chases itself - so you hold a timestamped record of exactly who was notified and when.
Method statements with tracked signatures
Upload versions per project, pick who must sign and what signing demands - name, date, read-and-understood, drawn signature. Everyone gets a personal link; you see sent and signed at a glance.
Handover manual, compiled to one PDF
Build the client's operations and maintenance manual: cover letter, works done, products used, manufacturer details, cleaning and maintenance, warranties and technical specifications - one branded document.
Evidence-grade exports, provably untampered
Every form exports as a branded PDF ending with a record-integrity certificate: the state of the audit chain plus a SHA-256 fingerprint for every photo. Proof the record was not doctored after the fact.
Cross-project analytics
Completion and room coverage per project, re-work counts drawn from the audit trail, photo volumes, open non-conformances - and a live list of sign-offs sitting with main contractors, oldest first.
The full quality register
Non-conformances with severity, disposition and close-out; standalone inspections; queries, submittals and handover acceptance; snagging lists; calibration and subcontractor-approval registers. Every record type carries the same hash-chained audit trail and its own branded export.
Set the reply period from your contract. The AS 4000 family fixes superintendent response periods; the Security of Payment Act fixes the payment schedule window separately.
How it works on site
- 1
Build the form once
Your inspection plan as a sequence of tasks and hold points - photo rules, readings and sign-off parties included.
- 2
Apply it to rooms
Import the room schedule, tick the rooms, apply. One form per room, tracked to completion.
- 3
Work through it
Operatives complete steps in order on their phone, offline if they have to. Photos land capture-timestamped against each step.
- 4
Sign off and hand over
Hold points go to the main contractor by email; completed rooms export as branded PDFs, straight into the handover manual.
Pricing - in the plan, or added to VariationFlow
Every QA feature is in VariationFlow + QA Flow. On VariationFlow you can add it for the difference, and cancel it without cancelling anything else. It is not part of Builder.
Charged monthly alongside your subscription. No setup fee, no minimum term on the add-on.
Prove quality. Protect handover.
The record you wish you had is the one you have to build before you need it.