One template
Thousands of tags
Design an ITR once, apply it across every tag that needs it, and issue the whole scope in a single action.
ITR Checksheets
Every inspection, recorded once and properly.
Deskely turns your ITRs into live checksheets: designed in the web app, issued against tags in bulk, executed offline on tablet with evidence attached, and closed with sequenced sign-off that stands up at handover.
No credit card required · 14-day free trial
Offline
Built for the field
Checksheets execute on tablet in tank tops and machinery spaces with no signal, then sync when the device is back in range.
Signed
Not just ticked
Every record carries sequenced, role-based sign-off and an attributed audit trail the client can accept at handover.
The Problem
The work gets done in the field. The record gets lost on the way back.
A technician signs a paper checksheet at 09:40. It travels in a folder to the site office, waits for a scanner, gets filed under a slightly wrong tag number, and reappears three weeks later when someone asks whether the loop was actually tested.
In between, nobody can answer the only question that matters: what is complete right now. Progress is rebuilt every week from spreadsheets that were accurate on the day they were exported. Photos live on phones. Signatures live on paper. A checksheet marked complete with a missing torque value is only discovered during handover review, when the crew that performed the work has demobilised.
The cost is not the paper. It is the rework, the duplicated walkdowns, and the certificates that cannot be issued because the evidence behind them cannot be produced.
How it works
One template, one issue action, one live record.
The lifecycle is deliberately linear. Every checksheet in the project can be traced back to the template version it came from and forward to the signature that closed it.
01
Design the template
Build the ITR once in the web app: sections, tables, checkboxes, numeric fields with tolerances, dates, and image capture. Set the sign-off roles and their sequence, then publish a version.
02
Apply it to the scope
Select the tags the ITR applies to — by system, subsystem, discipline, or location — and Deskely generates one checksheet per tag, correctly referenced from the start.
03
Issue in bulk
Review phase, scope, and paper flags, then issue hundreds of checksheets in a single action. Each one lands in the right crew's work list.
04
Execute offline on tablet
Crews answer the questions where the work happens, attach photos and readings, and raise a punch on the spot when something fails. No signal required.
05
Sign in sequence
Each authorised role signs in order, from web or tablet. Nothing can be signed out of turn, and every signature is bound to the evidence present at that moment.
Result
A completions record that is always current
Progress, outstanding scope, and evidence are the same dataset — not a weekly reconstruction of one.
In the Field
Designed for a tank top with no signal and gloves on.
The tablet app is offline-first, not offline-tolerant. The full work list, the checksheets, and the previously captured evidence live on the device. A crew can walk into a machinery space for six hours, complete forty checksheets, and never notice that connectivity dropped.
Evidence is captured at the point of inspection rather than reconstructed afterwards. Photos attach to the question they answer. Numeric readings are validated against the tolerance defined in the template, so an out-of-range value is caught while the technician is still standing at the equipment.
When something fails, a punch is raised against the tag from inside the checksheet — with the photo, the category, and the responsible party already attached — instead of being written on the back of a drawing and typed up later.
Assurance
A signature is only worth the evidence behind it.
Completion in Deskely is a state the system can defend, not a checkbox someone ticked. The rules below are enforced by the platform rather than by the diligence of whoever happens to be reviewing that week.
Sign-off roles execute in the sequence defined on the template — nothing can be signed out of turn
A checksheet cannot be closed while mandatory questions or required evidence are outstanding
Numeric answers are validated against the tolerance range set by the engineer who built the template
Every signature records who signed, in what role, from which device, and against which template version
Amendments after sign-off are versioned and attributed, never overwritten in place
Exports to PDF or Excel carry the same evidence the client saw in the system
The result is a completions dataset that survives scrutiny: when the client asks why a system was accepted, the answer is a record with the readings, the photographs, the punch history, and the signatures attached — produced in seconds rather than reconstructed from folders.
Business Outcomes
What this changes for your project.
Schedule
Checksheets are issued in bulk the day the scope is defined, and closed the hour the work is done — not the week the paperwork catches up.
Visibility
Completion by system, subsystem, discipline, and contractor is live. Progress reporting stops being a weekly spreadsheet exercise.
Quality
Missing evidence and out-of-tolerance readings are blocked at the point of capture, where a fix costs minutes instead of a return trip.
Handover
The dossier assembles itself. Every signed record, photo, and punch history is already attached to the tag it belongs to.
FAQ
Frequently asked questions.
Related Modules
Works seamlessly with other modules.
Punch Lists
Create, assign, and close out punch items with photo evidence and real-time status tracking.
Commissioning Procedures
Design, publish, and execute controlled commissioning procedures with structured sign-off flows.
Master Data
Manage tags, systems, subsystems, documents, and personnel that power every module.
