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. Silently overwriting one person’s work is the worst outcome, since nobody finds out until the record is needed and it is wrong.
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. 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.