Back to Blog
Blog

What happens when two people make conflicting changes while offline?

What happens when two people make conflicting changes while offline?

When two people work offline on the same job, there is a real chance they both record something for the same step, and the system needs a clear rule for…

When two people work offline on the same job, there is a real chance they both record something for the same step, and the system needs a clear rule for what happens when they both sync. This comes up more often than people expect, since crews often split a long job between them, a supervisor may check a step that an operator has already completed, and a device that sat in a pocket all shift without signal can come back hours later with entries nobody else has seen yet.

Silently overwriting one person’s work is the worst outcome, since nobody finds out until the record is needed and it is wrong. Many simple sync systems use a last write wins rule, where whichever device syncs most recently replaces whatever was there before, and on a step that records a pressure reading, an isolation point or a sign off that can erase the only evidence that the work was done properly, with the person whose entry vanished having no idea it happened until an audit or an incident review goes looking for it.

A good offline system keeps both entries with who made them and when, flags the conflict to someone who can resolve it and never quietly throws away field data. In practice that means the step shows both values side by side with the names, device times and any photos or comments attached, and a supervisor or the job owner picks the correct one or records why both are valid, so the final record keeps the history of the disagreement along with the answer.

For safety critical steps, it is also worth designing the job so that only one person owns a given step at a time, which removes most conflicts before they happen. Assigning steps or sections to named people before the crew goes out of signal, and making it obvious on the device who owns what, means two people rarely end up recording the same thing, and when they do it stands out as unusual rather than routine.

It also helps to test conflict handling before a rollout by deliberately putting two devices in airplane mode, completing the same step differently on each and syncing them, since that shows very quickly whether the system behaves the way the site expects. The same test is worth repeating after software updates, and the people who will resolve conflicts should know where flagged entries appear and how quickly they are expected to deal with them.