What happened on site, stage by stage.

When a work order does not tell the whole story

A simple visit fits in one work order. A multi-day job with different crews at different times does not: mobilization happens on Monday, diagnosis on Tuesday, execution waits on a part, testing is witnessed by the customer.

A phase organizes that work into stages, each with its own start, end, pauses and people, and it can serve several work orders at once. The result is an execution log that writes itself as the work happens.

Stages named the way the field talks

Each stage is classified by the kind of work, which tells the manager exactly what is being tracked:

• Mobilization and demobilization — getting crew, tools and parts to site, then clearing the area, returning tools and disposing of waste.
• Diagnosis — finding out what is wrong before touching anything.
• Execution — the intervention itself.
• Testing and inspection — functional tests, commissioning and measurements, and inspection of the finished work.
• Handover — returning the asset to the customer, usually with a signature.

Every stage with its own clock, crew and evidence

Who paused it, why and when

Every status change on a stage writes an event to the operation log: created, started, held with a reason, resumed, finished, cancelled or reopened. “Who stopped the job and why” is answerable months later, without diffing spreadsheet versions.

A finished or cancelled stage is a record of what happened and is not rewritten: to change anything it is reopened first — and the reopening goes in the log too.

Templates for jobs that repeat

Jobs of the same kind follow the same stages. Phase templates keep the sequence of stages with their types and checklists, and a new phase created from a template starts out structured.

The stage in the hands of whoever is assigned

In the app, technicians see the phases they are assigned to, with stage and checklist progress, and start, pause and resume their stage from their phone. Managers follow everything in the dashboard's traceability screen.

Example: a compressor replacement, stage by stage

At mobilization, the crew records its arrival with tools and the part, and photographs the site before touching anything. Diagnosis confirms the fault and attaches the measurements. Execution is paused for two hours while power is isolated — the pause is recorded with its reason, and the stage clock stops.

During testing, the technician records the equipment running with photos and a checklist, and handover closes with the customer's and the supervisor's signatures. Weeks later, if someone asks why the job took two days, the answer sits in each stage's operation log.