Commissioning software
Commissioning software that turns thousands of records into one defensible handover.
Deskely replaces the spreadsheet register, the scanned checksheet folder and the weekly consolidation job with a single system where status is derived from signed evidence — not typed in by hand.
The problem
Commissioning fails on paperwork, not engineering.
The engineering on a commissioning scope is rarely the hard part. The hard part is that a single subsystem certificate depends on hundreds of individual records being present, correct, signed and findable at the exact moment the gate is called.
The register forks
One master spreadsheet becomes a file per discipline, then per contractor, then a manual consolidation someone does over the weekend. Nobody is confident which copy is current.
Evidence detaches from status
The tracker says a check passed. The signed sheet proving it is a photo on a phone or a scan in a folder named after the day it was scanned.
Progress becomes a claim
Percentages are typed rather than derived, so reported completion reflects what people believe rather than what the signed records actually show.
The dossier is a project of its own
At handover someone must assemble thousands of documents in order and prove none are missing — work that routinely takes months and delays acceptance.
What you get
Every completions record type, on one relational model.
Tags, subsystems, ITRs, punch items, preservation routines, walkdowns and certificates are linked, so a milestone can only be issued when the evidence beneath it is genuinely complete.
Inspection & test records
A-ITRs, B-ITRs and C-ITRs raised against tags, completed on tablet, signed by the right role and stored against the subsystem they belong to.
Learn moreCommissioning procedures
Controlled step-by-step procedures with defined sign-off roles and enforced sequence, so a step cannot be skipped or back-dated.
Learn morePunch lists
Category A, B and C deficiencies raised with photos in the field, assigned, tracked and gated against the milestone they block.
Learn moreWalkdowns
Structured physical inspections against a subsystem boundary, with punch items raised directly from the walk rather than transcribed afterwards.
Learn morePreservation
Recurring routines on installed-but-idle equipment, with overdue tasks surfaced before they become warranty arguments.
Learn moreCertificates
Mechanical completion, RFSU and handover certificates generated from the underlying records, with the dossier assembled as you go.
Learn moreHow it runs
From tag register to signed handover, in one sequence.
- 01
Load the tag register
Import equipment lists and line lists, or let the AI parser extract tags straight from P&IDs and mark up the conflicts it finds.
- 02
Cut systems and subsystems
Assign every tag to the subsystem that will actually be started up, so progress reporting refers to something real.
- 03
Execute in the field
Crews complete ITRs, raise punch items and record preservation on tablet — offline, then synced when a connection returns.
- 04
Close the gate
Certificates become available when their prerequisite records are signed and blocking punch items are cleared. Nothing is issued on trust.
Side by side
Spreadsheets versus a completions system.
Almost every project starts in Excel and it works for the first few hundred records. Here is what changes once the record count runs into the tens of thousands.
| Aspect | Spreadsheets and scans | Deskely |
|---|---|---|
| Source of truth | Several files, versioned by filename, reconciled manually. | One database. Every record has one current state and a full audit trail. |
| Progress | Typed percentages that reflect judgement. | Derived from signed records. Reported completion equals proven completion. |
| Field work | Paper in the field, retyped in the office, with a latency of days. | Completed on tablet offline, synced on reconnect, visible immediately. |
| Evidence | Scans and photos stored separately from the tracker. | Attached to the record and carried through to the dossier automatically. |
| Gate control | A certificate can be signed while records are missing. | Certificates unlock only when prerequisites are actually satisfied. |
| Handover dossier | Assembled at the end as a separate, months-long exercise. | Assembled continuously and exportable at any point. |
What changes
One
register for tags, records, punch and certificates
Offline
field execution on tablet, synced when back in range
Live
progress derived from signed evidence, not estimates
Day one
dossier assembly starts with the first signed record
Before you shortlist
Estimate what your current process costs
Enter your tag count and record handling time to see the admin hours and cost in play — then book a demo against your own numbers.
FAQ
Questions about commissioning software.
Keep reading
Commissioning 101
The completions sequence explained end to end — systems, ITRs, punch, mechanical completion and RFSU.
Read moreCompletions software
How the completions record model works and why the subsystem is the unit that matters.
Read moreDeskely vs spreadsheets
An honest look at where Excel holds up on a completions scope and where it stops.
Read more