Ready
Readiness computed, not claimed
A certificate turns ready when its ITRs, walkdowns, A punches, and prerequisite certificates actually allow it — not when someone says the system is finished.
Certificates
A system is complete when the record says so, not when the meeting says so.
Deskely computes certificate readiness from the work underneath it — ITRs, walkdowns, punches, and prerequisite certificates — so G03 to G08 are issued against evidence instead of optimism.
No credit card required · 14-day free trial
G03–G08
Your project's standard
Certificate types and their scope follow the standard configured for the project, whether that is subsystem and discipline, subsystem, system, or project level.
Traceable
Every signature accounted for
Linked ITR and punch tabs, required fields, attachments, versions, and reissues sit on the certificate itself for audit at any point.
No. 01 · The problem
Certificates get signed on a status nobody can verify.
Mechanical completion is the moment a project stops being a construction scope and starts being an asset. It should be the most evidenced decision on the job. In practice it is usually the least: a percentage from a construction tracker, an ITR count from a second spreadsheet, and a punch list emailed on Tuesday.
None of the three agree, and none of them are linked to the underlying records. So the certificate is prepared against the most optimistic number, walked into a completion meeting, and signed on the understanding that the outstanding items are "small".
Then the client's representative opens the punch list and finds category A items on the same subsystem. The certificate comes back, the start-up sequence is re-planned around it, and from that point every certificate you present is treated as a claim to be audited rather than a record to be accepted.
No. 02 · How it works
Readiness is a calculation, not an opinion.
Every certificate sits on top of the ITRs, walkdowns, punches, and certificates that must precede it. Because those are records in the same system, the gate opens by itself the moment the work underneath is genuinely done.
01
Step 01Set the standard and scope
The project's certificate standard defines which types exist — G03, G05, G06, G07, G08 — and the scope each is generated against: subsystem and discipline, subsystem, system, or project.
02
Step 02Certificates generate against the scope
Deskely creates the certificates for every subsystem and system in the project automatically, so the register is complete from day one rather than built as you go.
03
Step 03Readiness is computed continuously
Required ITRs completed, required walkdowns completed, linked category A punches cleared, and prerequisite certificates completed. Until all four hold, the certificate is not ready for issue.
04
Step 04Issue and complete sign-offs
Configure the required sign-offs, issue the certificate to move it In Progress, then fill required fields, add attachments, and collect signatures in the web app. Force issue exists for when the project genuinely needs it.
05
Step 05Complete, reissue, or reopen
A completed certificate can be downloaded, reissued, reopened, or partially completed as the project changes, with versions retained so nothing overwrites the record that was accepted.
✓
SealedA certificate the client can check
The ITRs, punches, fields, attachments, and signatures behind the certificate open from the certificate itself.
No. 03 · Project control
"What is stopping this system?" answered in one screen.
The certificate register shows every subsystem and system in the project with its current state — ready for issue, in progress, completed, or blocked — filtered by certificate type, system, or discipline.
Where a certificate is blocked, the register says exactly why: the outstanding ITRs, the walkdowns not yet done, the category A punches still open, or the prerequisite certificate that has not been completed. Each of those opens directly from the certificate through its linked ITR List and Punch List tabs, so the completions meeting works from the record rather than from three competing reports.
That changes the conversation. Instead of arguing about whether a system is finished, the team works a short, specific list of blocking items — and when the last one closes, the certificate becomes ready without anyone updating a status field.
No. 04 · Assurance
A certificate is a legal position, so it has to be defensible.
Handover moves care, custody, and liability. The rules below hold on every certificate in the project, regardless of schedule pressure or who is in the room.
Readiness is derived from required ITRs, required walkdowns, linked category A punches, and prerequisite certificates — never from a manual status field
Certificates are generated against the project's configured scope, so no subsystem or system is quietly missing from the register
Issue stays disabled until the required sign-offs are configured, and force issue is a deliberate, recorded action
Every signature carries the user, the role, and the timestamp that produced it
Reissue and reopen retain previous versions, so the record a client accepted is never overwritten
Linked ITR and punch tabs let a reviewer verify the certificate against the work without leaving it
When a client asks what a certificate was issued against, the answer is the certificate itself: the ITRs and walkdowns behind it, the punches that were cleared to release it, the fields and attachments completed on it, and the signatures — in order, attributed, and timestamped — that accepted it.
No. 05 · Business outcomes
What this changes for your project.
Completion status you can trust
Readiness is derived from the underlying records, so the register is the same number in the site meeting, the client review, and the board report.
Fewer rejected handovers
Blocking items are visible before the certificate is presented, so certificates go into a completion meeting to be signed rather than to be argued about.
Start-up planned on facts
When you can see which systems are genuinely ready and what holds the rest, the start-up sequence is planned against reality instead of forecast percentages.
A dossier that is already built
Signed certificates, their linked ITRs and punches, their attachments and versions are all attached to the scope they certify and download on demand.
FAQ
Frequently asked questions.
Related Modules
Works seamlessly with other modules.
Commissioning Procedures
Design, publish, and execute controlled commissioning procedures with structured sign-off flows.
Preservation
Manage Preservation Work Lists with interval tracking, due-date management, and field evidence capture.
ITR Checksheets
Build templates with sections and steps, issue checksheets, and execute on tablet with evidence capture.
