Resolving Two Offline Edits to the Same Asset Location
Handle conflicting offline asset updates with preserved observations, clear timestamps and human review instead of silently accepting the latest upload.
What should happen when two offline devices update the same asset differently?
Preserve both observations and route the conflict for review against the asset’s movement history and actual evidence. Distinguish capture time from upload time, then record the accepted current location and the reason. A later upload should not automatically erase an earlier observation that may describe a more recent physical event.
Two verification teams work without connectivity at adjacent sites. One records a generator in a store, while another observes it after a transfer. Their devices reconnect in the opposite order. If the system uses upload order as physical chronology, the register can move the generator backwards. Acceptance testing should expose this behaviour before a live fieldwork exercise.
Capture enough context to understand the conflict
Each observation should retain the asset identifier, observed location, verifier, capture time, device reference and sync time. Include an observation identifier that remains stable when an upload is retried. Where device clocks may be unreliable, record that uncertainty rather than treating every timestamp as equally dependable.
Preserve the original offline submissions even if the system maintains only one current location. The current record and observation history serve different purposes. Without the history, a reviewer cannot tell whether a location changed legitimately, a team selected the wrong room or a delayed upload overwrote a more recent physical observation.
Define a review rule before deployment
Agree which conflicts can be resolved automatically and which require a person. Identical repeated observations may be safely consolidated under a tested rule, but differing locations or identifiers generally deserve attention. Identify who receives the conflict and what evidence they should compare, such as transfer receipts or direct follow-up with the site.
Test a scenario with two devices, different capture times and reversed upload order. Also test a clock set incorrectly and a retry of the same observation. Use test assets in an authorised environment. Record the observed behaviour and compare it with the intended rule instead of accepting a demonstration that never creates a real conflict.
Publish the accepted state with its explanation
After review, record the selected current location, reviewer, decision time and supporting movement or observation references. Retain rejected or superseded observations with their reasons. A record can be current and still show that an earlier observation was valid for a previous point in time.
Report unresolved conflicts separately from ordinary unsynced work so supervisors know what requires judgement. Give the field team a way to see whether its submission was accepted, duplicated or held for review. This prevents repeated recapture driven by uncertainty and makes the handover between fieldwork and data administration much more reliable.
Practical Example
Illustrative example: device A observes generator G-32 in Store One at 08:00. It moves under a recorded transfer, and device B observes it at Site Two at 11:00. Device B uploads at noon; device A uploads at 16:00. The reviewer uses the transfer and capture evidence to retain Site Two as current while preserving the Store One observation as valid earlier history. Upload order does not determine physical movement.
Action Checklist
- 1.Store observation identifiers and both capture and upload timestamps for offline submissions.
- 2.Retain conflicting source observations instead of overwriting them without a trail.
- 3.Test reversed upload order, duplicate retries and an incorrect device clock.
- 4.Assign a reviewer for location conflicts that require movement evidence.
- 5.Show field users whether their submissions were accepted or held for review.
For an offline workflow with explicit conflict handling, explore Asset Management Software.