At source
Raised where the problem is
A failed ITR check, a walkdown finding, a preservation cycle, or a rejected procedure step becomes a punch on the spot — with the tag, photo, and context already attached.
Punch Lists
Every outstanding item, with an owner and a way out.
Deskely turns deficiencies into tracked records: raised in the field with photo evidence, linked to the tag and the record that found them, assigned to a responsible party, and closed out with verification.
No credit card required · 14-day free trial
Owned
Someone's name on every item
Category, priority, responsible company, and due date are set when the item is created, so nothing lands in a list nobody is accountable for.
Blocking
Category A holds the gate
Open A items on a subsystem keep its certificate out of Ready for Issue. Close-out is enforced by the system rather than negotiated in a meeting.
Tag 01 · The Problem
A punch list nobody owns is just a list of complaints.
Deficiencies are found everywhere — during an ITR, on a walkdown, in a preservation round, halfway through a commissioning procedure. They get written on a pad, photographed on a phone, and typed into a shared spreadsheet at the end of the shift, if at all.
By the time the list circulates, half the items have no tag, no category, and no responsible party. The photo that explained the problem is on a device belonging to someone who has rotated off. Two crews have raised the same item twice, and a third item was closed by someone with no record of what they actually fixed.
Close-out then becomes archaeology. Teams re-walk the plant to work out what is genuinely outstanding, contractors argue about whose scope an item belongs to, and the certificate waits on a number that changes every time the list is re-issued.
Tag 02 · How it works
From the moment it is found to the moment it is verified.
A punch in Deskely is a record with a tag, a category, an owner, and a history — created once, in the field, and carried through to a closure someone put their name against.
Step
Raise it at the point of discovery
Create the punch on tablet while standing at the equipment. Photograph the defect, describe it, and let the tag, system, and originating record attach themselves.
Step
Categorise and prioritise
Set the category and priority against your project's convention — category A items block completion, lower categories are cleared before or after handover as agreed.
Step
Assign the responsible party
Give the item an owner, a responsible company, and a due date. It appears in that party's list immediately rather than in a weekly circulation.
Step
Work it and record the fix
The owner moves the item through its lifecycle, adds comments, and attaches the evidence of what was actually done — not just a status change.
Step
Verify and close
Closure is verified against the evidence and attributed to the person who accepted it. The item stays linked to the ITR, walkdown, or procedure that raised it.
Result
A close-out list you can trust
What is outstanding, who owns it, and what blocks completion is one number that does not change between reports.
Tag 03 · In the Field
The item is written down while you are still standing in front of it.
The tablet app is offline-first, so a punch is created at the equipment with no connectivity required. The photograph is taken against the item itself, the description is written while the defect is in front of you, and the tag, system, and originating record attach automatically.
Category, priority, responsible company, and due date are set at creation, which is what makes the list usable later. There is no end-of-shift transcription step where context is lost, no photo stranded on a personal phone, and no ambiguity about which tag an item belongs to.
On sync, the item appears in its owner's list, contributes to close-out status by system and discipline, and — if it is a category A item — is immediately visible as something holding a certificate. Progress and closure are recorded on the same record, with comments and verification evidence attached.
Tag 04 · Assurance
"It's been fixed" needs a photograph and a name.
Punch close-out decides when a system can be certified, so it has to be evidenced rather than asserted. The rules below hold on every item, regardless of who raised it or how close the handover date is.
Every punch is bound to a tag and to the record that raised it — an ITR, a walkdown, a preservation cycle, or a commissioning procedure
Category and responsible party are set at creation, so no item enters the register without an owner
Photographs are attached to the item they evidence, both when it is raised and when it is closed
Status changes, comments, and closures are attributed with the user, date, and time
Open category A items keep the affected certificate out of Ready for Issue automatically
Filtered registers export to Excel or PDF, so contractors and clients work the same list you do
When a client asks what happened to an item raised three months ago, the answer is the item itself: where it was found, what it looked like, who accepted it, what was done, and who verified the fix — with the certificate it was holding released on the same record.
Tag 05 · Business Outcomes
What this changes for your project.
No disputed ownership
Responsible company and owner are recorded when the item is raised, so close-out meetings work the list instead of arguing about whose scope it is.
Close-out you can forecast
Outstanding items by system, discipline, and category are live, so you can see what genuinely stands between the project and its next certificate.
Fewer re-walks
Photographs and context are captured at discovery and at closure, so nobody walks the plant again just to confirm whether an item is still open.
Handover without a backlog
Category A items are cleared before certification by design, and the remaining items hand over as a documented, owned list rather than a surprise.
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.
Walkdowns
Run area-based verification walkdowns with integrated field discovery and punch creation.
Certificates
Monitor project readiness and track prerequisites based on G-series certificate standards.
