For contractors and multi-engineer firms
Your QS should sign certificates
they have actually read
Certably gives the Qualified Supervisor a real review queue: the finished certificate, the board schedule, the observations and the photographs — then a signature, or a rejection with notes back to the engineer.
The problem
Pre-authorised signatures are not sign-off
The usual approach to remote sign-off asks the QS to flip a switch in settings, confirming in advance that they have checked certificates that do not exist yet. Their signature then appears on whatever engineers produce in the field.
The QS never sees the work
A blanket authorisation applies a signature to certificates nobody reviewed. If your scheme assessor asks what the QS actually checked before signing, there is no answer to give them.
Shared logins
Some enterprise licences require every engineer to sign in to the same Apple ID. One account, no way to tell who did what, and nothing to revoke when somebody leaves.
No record of the decision
A signature on a PDF proves a signature was applied. It does not show when it was applied, by whom, to which version of the certificate, or what was on screen at the time.
How Certably does it
A review queue, not a rubber stamp
-
01
Engineer completes on site
Certificate built offline as usual, then marked ready for review the next time there is signal.
-
02
It lands in the QS queue
The QS sees the full certificate — circuit schedule, test results, observations, photographs — on phone or iPad.
-
03
Sign or send back
Sign it, or reject it with notes attached to the specific observation that needs fixing. The engineer gets it straight back.
-
04
Issue with a record
The signed certificate goes to the client, and the review is logged: who, when, and which version they approved.
A login per engineer
Real accounts with real names. Add an engineer when they start, revoke them the day they leave, and know exactly whose work is whose.
An audit trail you can hand over
Every certificate carries its own history — created, edited, submitted, reviewed, signed or rejected, with names and timestamps. Export it for an assessment visit.
Shared customers and sites
One record per site across the whole firm. Whoever attends next opens the previous visit instead of starting from a blank address field.
Straight answer on your data
A firm workspace needs a server. Here is what that means.
On the sole-trader plans nothing leaves your device, and we say so plainly. A QS cannot review a certificate sitting on someone else's phone, so the firm plan syncs through a Certably workspace instead. We are not going to pretend otherwise.
What we will commit to: your data is held in the UK, encrypted in transit and at rest, isolated to your firm, and never sold, mined or used to train anything. You can export everything you have in a machine-readable format at any point, and if you leave we delete it on request.
Pricing
Pick a size and set it up yourself
Published prices, no quote, no discovery call. Choose the band that fits, put your firm's details in, and you are set up. If you outgrow a band you move up from inside the app.
No sales call
Prices are on this page. You do not have to speak to anyone to find out what it costs or to get started.
Add engineers yourself
Invite and revoke engineers from inside the app. Moving between bands is a button, not an email thread.
Cancel yourself too
One click, from your own account. No retention call, no 30 days notice, no form to request a form.