How it works

From scope
to signed record.

Give it the scope, it drafts the RAMS. Brief the crew, they sign on the phone. The record can be filed at the point of work, and the commercial record can link back to that evidence. Four stages, in the order a job actually runs.

Set the job up

Create the company, add the first project, put the team on it. Everyone gets a role — operative, supervisor, manager, QS, admin — and what they can see follows the role. It runs in the browser on any phone, so there's nothing to install and nothing to roll out.

Projects, work packages and a project team — who's on the job, in what role, with what access
Works on any phone, nothing to install — the crew opens it in the browser and gets on with it
Equipment and plant register with PUWER, LOLER and PAT dates against each asset
Cost codes and an activity library set up once, then booked against every day after
Company document templates, so every job starts from the same place

Every plan covers a set number of projects and active workers — the caps are on the pricing page, not in the small print. It's quick to set up on purpose: the trial is seven days because a week is enough to see it working on a real job. See the plan limits →

Plan the work safely

Use authorised scope and supporting text to shape the first draft of safety paperwork. Unknowns remain evidence gaps; a competent person checks and changes it before any approval or issue.

AI can prepare a clearly marked first draft from the scope and evidence you provide; a competent person must check, amend and authorise it
Draft, review and approve in one place — every state change stamped with who and when
The crew signs on at the briefing, on a phone, at the point of work — not typed up afterwards
Revisions kept in full, so the version that was live on the day is still there
Permits carry valid-from and valid-to, the location and the issuer — superseded ones stay linked

AI allowances are stated, not implied: Starter includes 3 AI-drafted documents a month; Professional and above carry full AI authoring.

Prove it as it happens

Signatures, photos, hours and inspections can be recorded against the project as work progresses, leaving a linked evidence trail for review rather than a later reconstruction.

Inspection and test certificates signed on a phone at the point of work — hold and witness points included
Incidents captured with photos, witnesses, immediate actions and RIDDOR details on one record
Timesheets, plant hours and the site diary logged on the day — actual cost builds from them
Signs and checksheets queue through signal drops and sync when you're back in coverage
Expiry alerts at 30, 14 and 7 days for cards and documents — and the morning before a permit lapses

Get paid

The commercial record runs off the same system as the safety record, so the paperwork that proves the work is the paperwork that gets it paid for.

Payment applications built with gross, retention, previously certified and the amount due this period
Due date and final date for payment on the record, with certificates linked to the application they answer
Retention releases tracked, instead of quietly forgotten
CIS deduction rate and status carried on the application
NEC early warnings and compensation events logged as they arise — recorded rather than argued about later
The ITP pack exports as one handover document, with your logo on it

And when someone asks

“Can you show me the briefing record for the crew that was on site last Thursday?”

Here is the record, linked to the work and the revision that was briefed rather than reconstructed from folders and phones. The annual compliance check can then organise the same evidence against the SSIP Core Criteria for a competent person to review.

See it on your own job

Seven days, the current trial modules, no card. Use a sample before committing real records.