Per tag
Preservation follows the equipment
Activities are applied to the equipment tags they protect, so every pump, motor, and vessel carries its own preservation history.
Preservation
Equipment sits for months. Prove it was looked after.
Deskely turns preservation into a live schedule: PWL templates applied to equipment tags, recurring routines with real due dates, offline execution on tablet, and a per-tag record that stands up at handover.
No credit card required · 14-day free trial
On time
Routines that schedule themselves
Routine period and routine days drive the next due date automatically. Nothing depends on someone remembering the interval.
Evidenced
Proof, not a tick in a spreadsheet
Each cycle is completed with answers and photos captured on tablet, attributed to the person who did the work.
The Problem
Preservation fails quietly, and you find out months later.
Equipment arrives early and then waits. Rotating machinery needs turning, instruments need desiccant, vessels need a nitrogen blanket — all on intervals that run for a year or more while the project is busy with everything else.
The routine usually lives in a spreadsheet owned by one person. When they rotate off, the file stops moving. Two versions start circulating, cycles get marked complete without evidence, and nobody can say with certainty which tags were actually preserved and which were simply ticked.
The bill arrives at commissioning: a bearing that has corroded, a motor that fails on first run, a vendor who declines the warranty claim because there is no dated, attributed proof that the preservation regime was ever followed.
How it works
One template, every tag, a schedule that keeps running.
The interval is a property of the record, not a reminder in somebody's calendar. Once a PWL is issued, the next cycle appears whether or not anyone remembered to schedule it.
01
Design the PWL template
Set the title, instructions, and attachments, define the preservation activities and their acceptance criteria, add the required sign-off roles and their sequence, then publish the version.
02
Apply it to equipment tags
Select the tags in Tag Management and apply the template. Deskely generates a PWL per tag, so preservation history follows the equipment rather than a folder.
03
Set the schedule and issue
In PWL Management, set due date, end date, routine period and routine days, update key fields in bulk, then review and issue. Recurring cycles are created from there on.
04
Execute in the field, offline
Crews answer the activity questions and capture photos on tablet with no connectivity required. Anything that fails is raised as a punch against the tag on the spot.
05
Sign off and roll the cycle
Authorised users sign from web or tablet. The completed cycle is locked into the tag's history and the next due date is generated from the routine settings automatically.
Result
A preservation record per tag
Every cycle, its evidence, and its signatures are attached to the equipment they protected — ready for the vendor or the client.
In the Field
Preservation happens in laydown yards with no signal.
The tablet app is offline-first. The activity questions, the tag scope, and the photos taken during the round are held on the device, so a technician can work a full shift through a storage yard or a shut-down module and lose nothing.
Each activity is answered against its acceptance criteria, and a photo attaches to the specific activity it evidences rather than landing in a general camera roll. When something fails — a lost nitrogen blanket, a saturated desiccant, a seal that has let go — the technician raises a punch from inside the PWL, and the tag, category, photograph, and responsible party carry over automatically.
Once the device comes back into range everything syncs at once: the cycle is locked into the tag's history, the punch appears in the owner's list, and the next due date is generated from the routine settings without anyone updating a tracker.
Assurance
"It was preserved" has to survive a warranty dispute.
Preservation compliance in Deskely is a state the system maintains, not a claim made at the end of a long storage period. The rules below hold regardless of who ran the round or how long the equipment waited.
Every PWL is bound to an equipment tag, so preservation history travels with the equipment rather than a folder
Recurring cycles are generated from routine period and routine days — the next due date is never a manual entry
Overdue cycles surface against the tag, the system, and the responsible company instead of hiding in a tracker
Activity answers and photographs are attributed to the person who performed them, with date and time
Failures raise punches against the same tag, and the punch stays linked to the cycle that found it
Exports to PDF or Excel carry the same evidence the vendor or client reviewed in the system
When a vendor asks whether their equipment was maintained to specification during storage, the answer is a single record per tag: every cycle performed, the acceptance criteria met, the photographs behind them, the punches raised and closed, and the signatures that completed each round — produced in seconds instead of reconstructed from memory.
Business Outcomes
What this changes for your project.
Warranty claims that hold
A dated, attributed cycle history per tag is what a vendor asks for when equipment fails on first run. It exists before you need it.
No missed intervals
Due dates are generated from the routine settings on the record, so a rotation on a 30-day cycle does not depend on anyone remembering it.
Less rework at commissioning
Corrosion, moisture ingress, and seized shafts are caught during storage as punches, not discovered when the system is being energised.
Handover-ready evidence
Signed cycles, their photographs, and their punch history are already attached to the equipment they protect. The dossier assembles itself.
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.
