GX-13 · Testing and certification
Device results that accumulate into certificates, certificates sealed against a hash chain and verifiable by QR, and a handover pack that assembles itself out of what the job already holds. Nothing auto-completes, and nothing auto-signs.
Included in every subscription · Seven days free · No card required
Shot T1
Testing tab on a task, the right form for that device type
2400 × 1350
Test forms
Every task carries a Testing tab, and the form it renders is the one that belongs to that device type. Templates are versioned and frozen the moment they are published, and a result pins the version it was captured against — so a form that changes next year does not quietly rewrite what an engineer recorded last year.
Shot T2
Test template editor, fields and fail conditions
1600 × 1000
Shot T3
Certificate gather step — what goes on it, beside what is still untested
1600 × 1000
Certificates
The step that earns this feature is the one that gathers. It puts everything that will go on the certificate beside everything that has not been tested, and gives the untested the same weight as the selection. A screen that only listed the passes would let somebody certify a system with forty untested devices and never mention it.
Verification
Each issued certificate hashes its own content together with the hash of the last one your organisation issued. Edit a sealed certificate and its own hash breaks. Remove one, or reorder them, and the links either side break. Scan the QR and the verification page says so.
Shot T4
Public certificate verification page reached from a QR scan
1600 × 1000
Shot T5
O&M pack contents with the gap report beside it
1600 × 1200
Handover
By the time a job finishes, almost everything a handover pack needs is already in it: the drawings, the asset schedule, the test results, the issued certificates, the product data, the maintenance intervals. This is assembly, not capture — which is exactly why nobody else does it automatically.
Where we stop
Certification is signed by a competent person who carries the consequence. A software company is not that person, and building as though it were would be the easiest way to get somebody hurt.
01
No seeded form, certificate or handover pack asserts that an installation complies with, is approved under, or is certified against any standard. A test sweeps every seeded string for exactly that language and fails the build if it finds it.
02
The declaration on a certificate is your organisation's own words. Nothing here supplies default text. The most it will do is offer your own previous wording back to you.
03
Nothing completes itself and nothing signs itself. A responsibility statement is printed on both the certificate and the handover pack, because whose name is on it matters more than how it was produced.
13 · Testing and certification
Included in every subscription, from the first day of the trial.
13
Test templates
A seeded catalogue across five trades, plus your own, versioned and frozen at publish.
Testing on the task
The right form for the device type, on the task, captured where the work is.
Defects
Raised from a failed result, and standing between the system and a certificate.
Certificate builder
Gather, review the gaps, choose the signatory, declare, issue.
Signatory gate
Qualifications required by the certificate type, checked in date on the day.
Sealed PDF
A sequential reference, a snapshot of the results, and a responsibility statement.
Hash chain
Each certificate chained to the last your organisation issued. Tampering shows.
QR verification
A public page your client can check without an account or a login.
Compliance dashboard
Readiness and renewal banding across the project, so nothing lapses unnoticed.
O&M pack
Twelve sections compiled from the job, with every gap named rather than hidden.
Get started
Capture the results as the work happens and the certificate is a formality, not a fortnight. Put one system in it and see what the pack looks like when it writes itself.