Controlled
One published version in use
Procedures are built from published CP templates, so the crew in the field is never working from a document somebody edited last night.
Commissioning Procedures
The procedure everyone runs is the one that was approved.
Deskely turns commissioning procedures into controlled records: CP templates built from structured sections, published once, executed against systems and subsystems, and signed in the sequence your project agreed to.
No credit card required · 14-day free trial
In sequence
Sign-offs in the right order
Roles and their order are configured on the template. A procedure cannot be closed out before the people who must witness it have signed.
Reportable
Register, report, export
Every procedure sits in a filterable register with status, remarks, generated reports, and Excel export for the client's review.
§1 The problem
A procedure in a document is only as good as the copy someone is holding.
Commissioning procedures are written carefully, reviewed by three parties, and then released as files. From that moment the control is gone: the procedure lives in a document management system, a mail thread, a shared drive, and a printout in a folder on the deck.
A step gets clarified during a pre-start meeting and marked up on one copy. A witness is added late and never makes it into the signature block. The register that is supposed to show status is a spreadsheet updated on Thursdays, so nobody knows on Monday which subsystems are actually procedure-complete.
The dispute comes at sign-off. The client asks which revision was executed, who witnessed the function test, and where the readings are. If those answers have to be reconstructed from emails and scans, the test gets repeated — with the crew, the vendor, and the witness all back on site.
§2 How it works
From an approved template to a signed, exportable record.
The procedure is a record in the system rather than a file in a folder. Its content, its scope, its status, and its signatures are all the same object, so the register never has to be reconciled against reality.
§01
Build the CP template
Give the template its details and a unique CP number, choose the section type, link the system, subsystem and scope, and attach the drawings and vendor documents the procedure depends on.
§02
Design the layout and publish
Lay out the procedure section by section in the CP designer — instructions, checks, steps, readings — then configure the sign-off roles and their order and publish the version for use.
§03
Issue against systems and subsystems
Published templates generate controlled procedures in the Commissioning Procedures register, scoped to the system or subsystem they belong to and visible to everyone with access.
§04
Execute with the plant in front of you
Crews work the procedure step by step, capture readings and photos as evidence, and raise a punch against the tag on the spot when something does not meet the acceptance criteria.
§05
Sign in sequence, report, export
Each role signs in the configured order. The register status updates live, procedure reports generate from the record, and the whole register exports to Excel for the client.
SEALED
One procedure, one truth
The executed steps, the evidence behind them, and the signatures that accepted them live on the same record as the procedure itself.
§3 In the field
Procedures are executed at the equipment, not at a desk.
The tablet app is offline-first. The steps, the acceptance criteria, the attached drawings, and the photos taken during the run are held on the device, so a commissioning engineer can work a module with no coverage and lose nothing.
Readings are entered where they are taken, and photographs attach to the specific step they evidence instead of landing in a general camera roll. When a step fails, the engineer raises a punch from inside the procedure — the tag, the step, the category, the photograph, and the responsible party carry over automatically, and the punch stays linked to the procedure that found it.
On sync, the procedure's status moves in the register, the punch appears in its owner's list, and the report reflects what was actually done. Nobody transcribes a marked-up printout into a tracker at the end of the shift.
§4 Assurance
"It was tested" has to hold up in front of the client.
Procedure control in Deskely is a state the system maintains, not a claim assembled at handover. The rules below hold regardless of who ran the test or how late in the shift it finished.
Procedures are generated from published CP templates, so a single controlled version is in circulation at any time
Every procedure carries a unique CP number and is scoped to the system, subsystem, and discipline it belongs to
Sign-off roles and their order are configured on the template — the sequence cannot be skipped or reordered in the field
Steps, readings, and photographs are attributed to the person who captured them, with date and time
Failures raise punches against the same tag, and the punch remains linked to the procedure that found it
Register exports and generated reports carry the same evidence the client reviewed inside the system
When the client asks which revision was executed, who witnessed it, and where the readings are, the answer is one record: the procedure as published, the steps as completed, the evidence behind them, the punches raised and closed, and the signatures that accepted it — produced in seconds instead of reconstructed from a mail thread.
Business Outcomes
What this changes for your project.
No revision disputes
One published template generates every procedure, so the version executed in the field is provably the version that was approved.
Witnesses in the right order
Sign-off roles and sequence are set on the template. A procedure cannot be closed before the parties who must witness it have signed.
Status you can act on
The register shows procedure progress by system and subsystem live, so readiness meetings run off the record rather than a Thursday spreadsheet.
Handover packs that assemble themselves
Signed procedures, their readings, photographs, and punch history export to report or Excel without anyone collating scans.
FAQ
Frequently asked questions.
Related Modules
Works seamlessly with other modules.
ITR Checksheets
Build templates with sections and steps, issue checksheets, and execute on tablet with evidence capture.
Certificates
Monitor project readiness and track prerequisites based on G-series certificate standards.
Punch Lists
Create, assign, and close out punch items with photo evidence and real-time status tracking.
