6 ways to automate vehicle key handovers

#1 - The basic check-in

Who it's for: Small teams sharing one or two vehicles, where a quick written record of who had the van and in what state is all that is needed.

What it is: A vehicle key handover is a short record filed the moment a shared vehicle passes from one driver to the next. This version is five steps on a phone: name the vehicle, name the outgoing driver, name the incoming driver, type the mileage off the dashboard, and pick a rough fuel state. Each handover is one stamped record, so the history of a vehicle is the list of completions over time.

In practice: Take a four-van courier firm. When the early driver passes a van to the late driver, the late driver opens the canvas, types the registration, names both drivers, reads the odometer, taps "Half" for fuel, and submits. Server timestamp captured. The next morning the same van changes hands again. Three handovers in two days, all on a phone, no clipboard in the glovebox that goes missing the week you need it.

Why it works: The record is the proof. The handover itself does not have to change. What changes is that there is now a time-stamped entry naming both drivers and the mileage at the exact point the keys moved. If a dent appears or the tank comes back empty, the manager can see which driver held the vehicle across that window, instead of guessing from a rota.

Steps included:

• 1 text input (vehicle)
• 1 text input (outgoing driver)
• 1 text input (incoming driver)
• 1 number input (mileage at handover)
• 1 single-choice step (fuel state: Full, Three quarters, Half, Quarter, Below quarter)

#2 - With written guidance

Who it's for: Fleets where vehicles pass between many drivers, and the walk-around needs to be the same whoever is taking the keys.

What it is: The basic check-in plus two guidance panels woven through the canvas. One panel sits at the top and tells the incoming driver what to check before they accept the vehicle: new dents or scrapes, tyres, lights, fuel, warning lights on the dash. The other sits lower down and tells the driver what to do if the vehicle is not fit for the road. A new driver on their first shift runs the same check as someone who has driven the fleet for five years, without anyone briefing them in person.

In practice: Take a regional groundworks contractor with eight pickups moving between sites. A pickup that was on a muddy site yesterday is handed to a driver heading to a client meeting today. The top panel prompts the incoming driver to walk around it first, so a cracked light cluster gets spotted before the vehicle leaves the yard. The lower panel tells them that if they find a low tyre or a warning light, they do not drive it: they log it on a maintenance fault report and call the duty manager. The walk-around stops drifting between drivers, and problems get caught at the handover instead of on the hard shoulder.

What it adds to the basic check-in:

1. A "what to check before handing over" panel at the top, listing the walk-around: dents and scrapes, tyres, lights, fuel, warning lights.
2. A "if the vehicle isn't fit for the road" panel that tells the driver to stop, log the fault, and call the duty manager rather than drive it.
3. A consistent walk-around across every driver, so the check does not depend on who happens to be taking the keys.

Why it works: Written guidance sits inline at the moment the driver is about to accept the vehicle. The incoming driver reads the walk-around prompt right before they type the mileage, not in an induction pack they skimmed months ago. It is on the screen at the moment of the task, every single handover.

Steps included:

• 1 guidance note (what to check before handing over, and what to do if the vehicle isn't fit for the road)
• 1 text input (vehicle)
• 1 text input (outgoing driver)
• 1 text input (incoming driver)
• 1 number input (mileage at handover)
• 1 single-choice step (fuel state)

#3 - With a signature

Who it's for: Fleets where the handover needs a name against it, signed at the time by both drivers.

What it is: A signed handover is the basic check-in plus two signatures at the end: one from the outgoing driver and one from the incoming driver. The outgoing driver signs to confirm the condition they are handing the vehicle over in. The incoming driver signs to accept the vehicle in that condition. Both signatures attach to the same record as the mileage and fuel state, so the handover is a two-sided agreement rather than one person's note.

In practice: Take an electrical contractor with twelve vans shared across two depots. Every handover ends with both drivers signing the touchscreen: the driver handing over confirms the van is going across with a clean nearside panel and three quarters of a tank, and the driver taking it signs to accept exactly that. Three weeks later a scuff on the nearside panel turns into a question of who caused it. The manager pulls the handover record, sees the panel was clean and signed for by both drivers at that point, and knows the damage happened on the next driver's watch.

What it adds to the basic check-in:

1. A signature step for the outgoing driver, confirming the condition they are handing the vehicle over in.
2. A signature step for the incoming driver, accepting the vehicle in the condition described.
3. A two-sided agreement on the same record as the mileage and fuel state, so neither driver can later say they never agreed.

Why it works: The two signatures are what close the handover. The mileage and fuel state say what condition the vehicle was in. The signatures add: and both drivers agreed to it. With one driver signing to hand over and the other signing to accept, a later dispute has both names attached to the same condition at the same moment.

Steps included:

• 1 text input (vehicle)
• 1 text input (outgoing driver)
• 1 text input (incoming driver)
• 1 number input (mileage at handover)
• 1 single-choice step (fuel state)
• 1 signature (outgoing driver sign-off)
• 1 signature (incoming driver sign-off)

#4 - With photo evidence

Who it's for: Teams that want proof of the vehicle condition at handover, not just a typed mileage and fuel state.

What it is: The basic check-in plus a photo of the dashboard taken at the moment the keys change hands. The driver snaps the dashboard showing the odometer, the fuel gauge, and any warning lights, and the photo lands in the same record as the typed mileage and fuel state. The number and the picture back each other up, so a wrong digit or an optimistic fuel guess is easy to check against the shot.

In practice: Take a three-site care provider running a pool of cars for community visits. Cars move between staff across three towns, and the office never sees most of them in person. A carer taking a car for the afternoon snaps the dash before they pull away: 48,210 miles, half a tank, no warning lights. When the car comes back with a tyre pressure light on, the office pulls the last handover photo and sees the light was already on when the car left. The argument is over in a minute.

What it adds to the basic check-in:

1. A photo of the dashboard, capturing the odometer reading and fuel gauge at the handover.
2. A visual check on the typed mileage and fuel state, so a mistyped reading is caught against the picture.
3. A record of the vehicle condition at the exact point the keys moved, instead of a he-said-she-said later.

Why it works: A typed number is data. A photo of the dash is context. The two together survive a dispute in a way that either alone does not. The number is searchable and quick to read; the photo shows the real state of the vehicle at that moment. Captured on the same device, at the same time, neither can be reconstructed after the fact.

Steps included:

• 1 text input (vehicle)
• 1 text input (outgoing driver)
• 1 text input (incoming driver)
• 1 number input (mileage at handover)
• 1 single-choice step (fuel state)
• 1 photo of the dashboard

#5 - With Poppi checking the photo

Who it's for: Fleets where the dashboard photo gets taken but nobody reviews it. Multi-site operations where head office can't look at every handover photo, or where the person taking the photo is rushed and might not hold the camera steady.

What it is: A photo-checked handover is the basic check-in plus a photo of the dashboard that Poppi (AI) reviews the moment it's saved. Poppi answers one question about that photo, set by you: does the photo clearly show the odometer reading and fuel gauge? A single named spot is something an AI can actually judge, where a wide shot of the whole dashboard is not. If the answer is no, Poppi posts what it spotted to the team chat, so the photo gets retaken before everyone moves on.

In practice: A three-site property maintenance firm runs six vans across two shifts. The outgoing driver photographs the dash before handing the keys over. Poppi reads the photo: odometer clear, fuel gauge visible, all good. Verdict yes, and nothing changes. On a rushed afternoon the photo is blurry and the gauge is half cut off. Poppi answers no and posts the reason to the team chat ("The fuel gauge is not fully visible in the photo"). The driver retakes it right there while still on site, this time holding the phone steady.

What it adds to the basic check-in:

1. A photo of the dashboard that gets checked the moment it's saved, not just stored.
2. A team chat message with Poppi's reason the moment a photo fails the check.
3. The manager stops being the only person who ever looks at handover photos.

Why it works: The check happens in the seconds between the photo being taken and the driver leaving, the only moment a retake is still easy. A manager reviewing photos the next day can only record that the photo was poor; Poppi catching it at the moment of handover gets it fixed on the spot.

Steps included:

• 1 text input (vehicle)
• 1 text input (outgoing driver)
• 1 text input (incoming driver)
• 1 number input (mileage at handover)
• 1 single-choice step (fuel state)
• 1 photo of the dashboard
• 1 Poppi decision (judges the photo against your question)
• 1 Poppi action (posts to the team chat if the photo fails the check)

#6 - With an alert if the handover runs overdue

Who it's for: Fleets with a set handover deadline, where handovers must be logged within a time window and staff sometimes delay or skip filing them.

What it is: An overdue-handover alert is the basic check-in plus a Poppi (AI) action set to a deadline. If the handover record isn't completed by the time set, Poppi posts a message in the Pilla team chat so the outstanding handover gets filed before the window closes. It watches the deadline, so it catches the handover that got started but quietly abandoned, not just the one that never started.

In practice: Take a three-site property maintenance firm running six vans across two shifts. Handovers need to be filed within 15 minutes of the keys changing hands. On a busy day it's easy for the outgoing driver to hand over the keys and walk away before the form is filed. With this version, if a handover isn't filed within 15 minutes, the team chat gets a message, so the site supervisor catches the incomplete handovers that shift rather than discovering undefined vehicle conditions at shift end or the next morning.

What it adds to the basic check-in:

1. A message in the team chat if the handover isn't filed by the deadline
2. A catch for the handover that got started but abandoned, not just the one that was skipped
3. A record of when the handover should have been done, next to when it actually was
4. The manager finds out that shift, not from the next handover or end-of-day review

Why it works: The alert is tied to the deadline, so an incomplete handover raises its own hand. Nobody has to notice it's missing; the deadline does.

Steps included:

• 1 text input (vehicle)
• 1 text input (outgoing driver)
• 1 text input (incoming driver)
• 1 number input (mileage at handover)
• 1 single-choice step (fuel state)
• 1 Poppi action (posts to the team chat if the handover isn't completed by deadline)

How to pick the right version

You do not need to know how the canvas builder works to pick the right version. Every version here is the basic check-in plus one addition, so pick the additions your fleet actually needs.

Do other people run the handover?

If one or two of you share a vehicle and you both already know what to check, the basic check-in (#1) is enough. If the vehicle passes between many drivers, #2 adds guidance panels that spell out the walk-around on screen, so a new driver runs the same check as a veteran.

Does the handover need a name against it?

If knowing it was done is enough, skip this one. If you want who signed it off on the record, #3 adds a signature from both drivers.

Do you need photo proof of the vehicle condition?

A typed mileage says the work was done; a photo shows it. If you want visual proof of the dashboard at the handover, #4 adds a photo of the odometer and fuel gauge.

Does anyone actually look at those photos?

If a manager genuinely reviews every photo, #4's record is enough. If photos get taken and filed unseen, #5 has Poppi (AI) check each one as it's saved, and tell the team chat when something's wrong.

Does the handover need to be filed by a set time?

If handovers always get filed right away, the versions above are enough. If your fleet has a deadline and staff sometimes forget or abandon them halfway through, #6 posts a message to the team chat if the handover isn't completed in time.

Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps. That's how the product works anyway: every option here is one step added to the same check-in.

Related workflows

• 4 ways to automate maintenance fault reports
• 4 ways to automate damage reports
• 4 ways to automate job completion sign-offs
• 4 ways to automate delivery received logs
• 4 ways to automate lone worker check-ins

Conclusion

A vehicle key handover is a stamped record of both drivers, the mileage, and the fuel state, filed the moment the keys change hands. Every version above is the same basic check-in plus one addition: guidance, a signature, a photo, an AI check on the photo, or a deadline alert. Pick the ones your fleet needs and combine them in the playground.

More additions are coming in future refreshes, like pulling every site's handovers into one report. Those need more review time and will land separately.

→ Build your own vehicle key handover on Pilla.