Completions software
Completions software built around the subsystem, because that is what actually gets handed over.
Construction is organised by area and discipline. Completions is not — it is organised by the functional systems that get started up. Deskely models that re-cut properly, so progress, punch and certificates all refer to the same thing.
The problem
The re-cut from areas to subsystems is where projects quietly go wrong.
Every physical tag has to be assigned to the subsystem that will be started up. Get it right and reporting is meaningful. Get it wrong and every downstream number is misleading — usually discovered during the walkdown that was supposed to be a formality.
Tags land in the wrong subsystem
Boundaries cut through functional loops, so a subsystem reports complete while part of the loop it depends on is untested.
Registers drift apart
The engineering tag list, the ITR register and the punch list each maintain their own version of the same equipment, and they stop agreeing.
MC is declared on judgement
Mechanical completion is called because the schedule needs it, not because the underlying A-ITRs and Category A punch are demonstrably clear.
Handover packs are rebuilt from scratch
The dossier is compiled at the end from folders and email attachments, and every missing signature becomes a search.
What you get
One relational model from tag to certificate.
Master data sits at the base, execution records sit on top of it, and certificates read from both. Change a tag's subsystem and everything that depends on it updates with it.
Tag and subsystem master data
A controlled register of tags, systems and subsystems with change history, so the completions scope has one authoritative definition.
Learn moreITR library and execution
Templated inspection and test records assigned by tag type and discipline, executed and signed against the specific tag.
Learn morePunch register with categories
Category A items block the milestone; B and C are carried with visibility. The gate logic is enforced, not remembered.
Learn moreMC and RFSU certificates
Certificates generated from the records beneath them, with the prerequisite list visible before you attempt to issue.
Learn moreAI project population
Build the tag, subsystem and ITR structure from EPC documents in days instead of months of manual data entry.
Learn moreRole-based signing rights
Who can sign what, on which record type, is configured per role — and every signature carries a name, role and timestamp.
Learn moreHow it runs
The completions sequence, enforced end to end.
- 01
Define the scope
Systems, subsystems and every tag assigned to the subsystem it will be commissioned within.
- 02
Reach mechanical completion
A-ITRs signed, walkdown complete, Category A punch cleared — then the MC certificate becomes available.
- 03
Pre-commission and commission
Flushing, loop checks and function tests recorded as B-ITRs against the same tags and subsystems.
- 04
RFSU and handover
Ready-for-start-up issued against proven records, and the dossier exported with everything already in order.
Side by side
A tracker versus a completions model.
The difference is not features. It is whether the relationships between tags, records, punch and certificates are enforced by the system or held in someone's head.
| Aspect | Tracker spreadsheets | Deskely |
|---|---|---|
| Scope definition | Tag list, ITR list and punch list maintained separately. | One master register that every record and certificate references. |
| Subsystem changes | Re-mapping is a manual find-and-replace across several files. | Change once; dependent records and progress follow automatically. |
| MC readiness | Assembled by hand into a status meeting slide. | A live prerequisite list showing exactly what is outstanding. |
| Signatures | Wet ink on paper, scanned and filed later. | Captured with name, role and timestamp on the record itself. |
| Dossier | Compiled at the end from folders and inboxes. | Continuously assembled and exportable per subsystem at any time. |
What changes
Subsystem
the unit of progress, punch and certification
Enforced
prerequisites before any milestone is issued
Traceable
every signature carries name, role and timestamp
Exportable
handover dossier available at any point, not just the end
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 completions software.
Keep reading
Mechanical completion explained
Where MC ends, pre-commissioning begins and RFSU sits — with the evidence each stage needs.
Read moreMaster data
The controlled tag and subsystem register everything else in the project references.
Read moreCommissioning software
The full commissioning workflow, from tag register through to signed handover.
Read more