Ferdis Flow explores job dispatch and field handovers for service crews travelling between locations.
The problem to solve
A schedule says where to go. A field handover must also say what access, equipment and completion evidence the visit requires.
The proposed approach
Put access instructions beside the job scope. Close a visit with observations and unresolved work, not just a completed label.
Working with the example
Site A
The sample records “Access confirmed” as context and “08:00” as its state. In a real field operations process, the source and responsible role should be checked before acting on that state.
Site C
The sample records “Equipment check” as context and “11:30” as its state. In a real field operations process, the source and responsible role should be checked before acting on that state.
Site B
The sample records “Handover pending” as context and “15:00” as its state. In a real field operations process, the source and responsible role should be checked before acting on that state.
This preview shows the product direction. It has no account system, integrations or live record storage.
Try the sample ↗