the checklist tells a driver what. somebody still has to show them where.
every partner app has a list of onboarding steps with ticks next to them. it tells a new driver what's left. it rarely helps them do it, and that gap is where first orders get lost.
by shritupdated 6 min read

tl;dr (too long, didn't read)
a driver app's onboarding is already a checklist: documents, verification, training, kit, first order. it's good at showing what's left and bad at showing how to do it.
checklists in general don't get finished much. Userpilot's benchmark puts average completion around 19%, with a median near 10%. short walkthroughs a user starts themselves do much better, about 67% in Chameleon's data, and over 70% at 3 to 4 steps.
use both. keep the checklist short and honest about waits, and make each item open a short walkthrough, spoken in the driver's language, on the screen where the work happens.
two tools that get confused for each other
an onboarding checklist is a list of tasks with ticks. upload your licence, add your bank account, finish training, collect your kit. in most partner apps it's the home screen until the driver is approved.
a guided walkthrough is a sequence of steps that points at the actual screen. tap here, now hold the licence inside the box, now press submit. it moves with the driver and then gets out of the way.
people talk about these as if you'd pick one. but they answer different questions. the checklist answers "what do i still have to do?" the walkthrough answers "where is that, and what do i press?" a new driver has both questions, often within the same minute, and usually in Hindi rather than in the English the app was written in.
what the checklist does well, and where drivers stall
the checklist earns its place in a driver app. there really are six or seven things that have to happen before a first order, and a driver who can't see them will assume they're done when they aren't. a list with ticks gives the first few days some shape.
the trouble starts when a driver taps an item. in most apps one of two things happens. either it opens a form and leaves them there, or it opens a status that says "under review". a Borzo Play Store review from september 2026 complains that the "same approval message appears again and again". a MagicFleet reviewer is stuck on "manual training order not reviewed yet". the checklist knows something is pending. it doesn't tell the driver whether they're supposed to do something or wait.
the general numbers back this up. Userpilot publishes benchmarks from its customers, and across 188 products the average checklist completion rate was 19.2%, with a median of 10.1% (source). that's SaaS, not driver apps, but the lesson carries. a list of tasks assumes the person knows how to do each task. the whole reason they're new is that they don't.
what the walkthrough data says
walkthroughs have their own failure mode. the classic version fires on first launch and shows everyone the same nine screens. in driver apps the equivalent is the training video. one Rapido captain's review of the training video is "Playing In Loop Again And Again". that's what happens when explanation is long, automatic and the same for everyone. we wrote about this in why product tours break.
but the same data that condemns long, automatic tours is kind to short ones people start themselves. Chameleon published numbers from its customers' tours (source):
| kind of tour | completion |
|---|---|
| click-triggered (the user started it) | about 67% |
| time-delay triggered | about 31% |
| 3 to 4 steps | over 70% |
| 7+ steps | about 16% |
put those next to the checklist numbers and a pattern shows up. guidance gets finished when it's short and when the person asked for it. a training video is long and nobody asked for it. a four step walkthrough of the document camera, started by the driver tapping the item they're stuck on, is short, and somebody asked for it.
when to use which
the checklist is the right tool for the parts of onboarding that are about waiting or about order. verification, kit pickup, slot approval. a driver can't speed these up, but they can be told what's happening and what comes next. a good checklist item for a wait says what's being checked and roughly how long it takes, so nobody reinstalls the app thinking it's broken.
the walkthrough is the right tool for the parts the driver does with their own thumbs. taking a document photo that won't be rejected, adding a bank account, going online, accepting an order, collecting the customer's OTP. nobody needs a list for those. they need someone to point, and to say it in a language they think in. a 2023 Borzo survey found 84% of couriers use a local language while delivering, and 82% wanted one inside the app.
and some steps need neither, because the problem is operational. a joining fee, a deposit, a slow queue, a zone with no orders. no list and no walkthrough fixes those, and it's better to say so than to pretend.
how the two fit together
the setup we'd recommend is simple to describe. keep the checklist short, only the steps without which a driver can't take an order. mark the waits as waits. then make every item the driver acts on start a short walkthrough for that task, instead of dumping them on a form. the checklist says what. the walkthrough shows where. the driver starts each one, so you get the completion rates of guidance people asked for.
the most important walkthrough is missing from most checklists: the first live order, when a driver has a customer waiting and has never pressed these buttons before. an approved driver can quietly give up right there, and it's where being shown each tap matters most.
this is what heytappr does inside Android partner apps. it highlights where to tap and talks the driver through each step in Hindi first, then regional languages, right on the screen they're on, until they finish a first order. every step is shown on screen too, so it works on mute. it only speaks guides your team wrote and approved, and your ops team edits them from a dashboard without an app release. if a release moves a button, heytappr flags the broken step. it ships as an Android SDK.
if you measure this, measure per item. "onboarding completion" as one number hides everything interesting. you want to know which item drivers abandon, and whether the walkthrough attached to it gets finished. an item with a long wait and a lot of drop-off is an operations problem. an item drivers start and then drop halfway is a walkthrough with a confusing step. heytappr's funnel from signup to first job shows you which is which.
see it in your product
fifteen minutes: heytappr answering a real question by walking a user through a real interface, out loud.
questions people ask
Do onboarding checklists work in driver apps?
They help drivers see what is left before their first order, but they rarely show how to do each step. They work best when short, when waits are labelled as waits, and when each item opens a short walkthrough on the right screen.
Onboarding checklist vs guided walkthrough: which is better for drivers?
They do different jobs. The checklist shows what is left; the walkthrough shows where to tap and what to press. The strongest setup is a short checklist where each action item starts a short, spoken walkthrough in the driver's language.
What is a good onboarding checklist completion rate?
Userpilot's SaaS benchmark across 188 products found an average of 19.2% and a median of 10.1%. For a driver app, the number that matters is how many drivers complete a first order.
How many steps should a guided walkthrough have?
Three or four. In Chameleon's data, 3 to 4 step tours complete over 70% of the time, while tours with 7 or more steps fall to about 16%.
go deeper
keep reading
- why new delivery drivers quit before their first order
- why new drivers never open your help section
- your driver app's ai shouldn't write its own answers
- how to write guide steps a new driver can follow by ear
- in-app guidance on android, for the apps drivers use
spotted something out of date? tell us and it gets fixed.