Site work
WOs
Work Orders
Work orders as activities against tags, systems, or locations — raise, evidence, and close in one queue.
A work order in completions is usually “go do this on that tag”. The activity engine already does that. Add a Work Order activity type on the project, give it a short code, attach procedures, and the raise wizard, My Work, field capture, and Data Hub treat it like the rest of the register.
There is no separate WO approval chain, cost module, or ERP connector. Numbering follows activity numbers and the labels you apply. If you already have a CMMS, this is the completions-side record, not a replacement.
One queue, your type name
Completions teams already live in My Work. A work order that appears there, with a tag target and evidence, gets done. A work order that lives in a fourth register does not. Configure the type; keep the engine.
What it does
- ✓Define a Work Order activity type with your short code and description
- ✓Issue work orders against tags, subsystems, or documents
- ✓Attach procedural checklists for steps, evidence, and sign-off
- ✓Assign to field users and queue them in My Work
- ✓Track status from open through in progress to completed or rejected
- ✓Capture photographic evidence on steps and at raise
- ✓Relate work orders to hierarchy nodes for system-level visibility
- ✓Link to required attributes and readiness if the project gates raise on incomplete tags
- ✓Export work-order registers through Data Hub
Highlights
- • Same activity engine as punch and preservation
- • Field capture and desktop closeout stay on one record
- • Type is project-configured — not a hidden second product
- • No ERP or cost integration on this path
Demo
Demo video coming soon
See the rest of the platform, or talk to us about a demo.