Building fleet software: make handovers clear for the next person

A vehicle can be physically present while its allocation is still uncertain. A repair can be completed while approval to return the vehicle remains outstanding. These distinctions matter because different people rely on the same event to make different decisions. A tool that compresses them into one reassuring status can create more questions than it answers.

For builders exploring Sparrow Mobility Labs, handovers offer a concrete place to study how information, physical work and responsibility come together.

Name what is being handed over

Start with the object and the decision. Is someone transferring vehicle custody, confirming a completed inspection, accepting a delivery or authorising an expense? Those are different events even when they happen close together. Write each in ordinary language before choosing labels for a screen.

Identify who initiates the handover and who can accept it. Clarify what evidence the receiving person needs. A photograph may show condition, but it does not by itself establish acceptance, an approved cost or a settled disagreement. The record should help people understand exactly which question has been answered.

Show the next action, including exceptions

A useful status leads somewhere. If an inspection is incomplete, the next person should know what is missing and who can supply it. If a handover is disputed, show that it remains unresolved rather than forcing someone to choose an inaccurate completion state. Let a coordinator distinguish a delay from a refusal or a missing record.

Test ordinary exceptions early: a participant loses connectivity, a document arrives later, a vehicle changes, or an earlier entry needs correction. Keep the explanation attached to the relevant event so another shift does not have to reconstruct the conversation.

Preserve the boundary of responsibility

Information shared between an operator, workshop and asset owner should reflect their different roles. A workshop may report that a repair is finished; an authorised person may still need to approve return to service. The asset-owner perspective helps expose where an operating update and an ownership decision differ.

The World Bank’s PPP risk-allocation framework asks which party can manage a particular risk. In product design, that is a useful prompt to confirm responsibility before automating a notification or approval. Software should make an agreed arrangement easier to follow.

Test understanding across both sides

Show a sample handover to the sender and receiver separately. Ask each what happened, what remains open and what they would do next. If their answers differ, revise the record before adding more features. A visually tidy interface can still leave the essential decision ambiguous.

Then observe the whole handover in a permitted test, including the time spent outside the tool. Repeated phone calls or copied messages may reveal a missing detail. Keep the design focused on completing the work with an understandable record, rather than collecting every possible field.