Designated Driver Document Requirements: Experience Checks and Extra Uploads

A designated-driver launch is not “anyone with a license, online tonight.” The first week usually fails in one of two ways. You ask for nothing and discover reviewers have no packet to reject. Or you ask for everything and the rank stays empty through Friday payday. On Ptaxi’s designated driver app, driver verification is explicit: the applicant fills in driver information, uploads document images, and can provide service only after review approves the file. During that application the driver must choose whether they have previously worked as a designated driver, then upload other materials. Whether those extra materials are mandatory is an admin business switch.

This piece is about that certification packet. It is not a rewrite of go-online balance reserve or health declaration. Those gates fire when a driver tries to go online. Verification is what lets them on the platform at all.

Why experience and extra documents get treated as one toggle

Designated driving is personal work in someone else’s car, often late, often after alcohol is already in the story. Buyers want a filter that sounds like “only pros.” Products that actually ship usually give you a declaration plus a document packet—not a magic years-of-experience API.

Typical pains this split is meant to blunt:

1. Recruiters promise “no paperwork” and reviewers later have nothing but a selfie and a phone number.
2. Compliance lists every conceivable extra file as required, then wonders why nobody finishes the form.
3. Ops hears “they answered the experience question” and treats that answer as an automatic pass or an automatic fail the list never described.
4. Night desks confuse a rejected verification file with a driver who simply cannot go online because the wallet reserve is short.

The experience question answers *what the applicant claims about prior designated-driver work*. The extra-materials switch answers *whether review is allowed to proceed without the rest of the packet*. Verification review answers *approve or reject*. Go-online rules answer *whether an already-approved driver may start a shift*. Keep those cards separate.

What the documented verification flow includes

Confirmed driver surfaces describe verification in one tight sequence. The driver fills in information and uploads document images. Once approved, the driver can use the platform to provide service. The same item adds the detail that matters here: during verification the driver must choose whether they have worked as a designated driver before, then upload other materials, and those other materials can be set as required or optional in the backend.

Say that sequence out loud. The experience field is a required choice, not a hidden scoring model. The lists do not say the admin can flip a switch that secretly rejects every “no prior experience” answer. Do not invent that gate. Reviewers can read the declaration and decide. If your city legally needs prior experience, encode that in review SOP and rejection reasons—not in folklore about an undocumented hard block.

The lists also do not name each extra file. There is no confirmed designated-driver checklist of operating permits or insurance policies in these documents. Do not import document names from another product line. Teach “other materials, required or not, as the admin sets them,” and show the actual upload fields in the demo build you are selling.

Admin verification review is where staff open the applicant’s details and approve or reject. That is the hard door. A completed form sitting in review is not an online driver. Train the desk to leave a reason when they reject, then send the driver back to upload rather than inventing a side channel over chat.

Admin switch: extra materials required or not

Admin business settings include an explicit control: whether other materials are required during driver verification. It lives with other designated-driver operating switches such as passenger-pay, driver-advance, offline collection via a driver-uploaded collection code, fixed-price pricing, accept limits based on wallet reserve, income freeze, and minimum mileage.

Treat the extra-materials control as an ops choice:

• Require extra materials when reviewers keep approving thin files you later regret.
• Leave them optional when you are opening a city and would rather review a smaller packet than wait on every attachment.
• Do not flip the switch mid-week without telling applicants already halfway through the form.

The same settings area also documents accept limits: a driver whose wallet is below the reserve cannot take orders, and you can require a collection code before they go online. Those rules protect settlement. They do not inspect documents. Point at go-online balance reserve when the complaint is “approved but cannot start a shift,” then return to verification when the complaint is “cannot get approved.”

Health declaration is another first-online-of-the-day upload, and the backend can turn it off. Useful, and already its own article. It is not a substitute background check.

After approval: supplements, imports, and the driver list

Verification is not the last time you will touch a file. The driver list lets admins change company, request document supplements, ban or unban, and push messages. Use document supplement when an approved driver is missing something you now need. Use a ban when the problem is conduct or risk, not a missing page. Mixing those two actions is how you create appeals you cannot explain.

Admins can also bulk-import drivers from a template. Import is a speed tool for onboarding records. It does not remove verification review, and it does not decide whether extra materials are required. If you import thin rows, reviewers inherit thin files. Fill the template as if a human will still open each packet.

Driver-side context that belongs in the same workshop, without stealing the plot: the heatmap shows busy areas plus counts of online drivers, drivers on a job, and drivers waiting to accept. That is useful after you have a reviewed rank. A beautiful heatmap over three unverified accounts is not a launch.

Ops tradeoffs to say out loud

• No extra materials required, no review discipline: faster sign-ups, weaker packets, harder incident reviews later.
• Every extra file required on day one: cleaner files, slower supply, more abandoned applications.
• Treating the experience answer as an automatic reject: not what the lists describe, and you will argue with applicants who answered honestly.
• Treating approval as the same thing as going online: approved drivers still hit reserve and collection-code rules when they try to start a shift.
• Required extras + honest review + separate go-online coaching: slower than a flyer that says “drive tonight,” and much easier to defend.

Practical notes that match the surfaces:

• In demos, complete the experience choice on purpose. Show both “have done this work” and “have not,” then show reviewers reading that answer.
• Toggle extra materials required and optional once each so the buyer sees the packet change.
• Reject one sample file and send it back, then approve another, so the door is visible.
• When someone asks for a named document list that is not on the designated-driver surfaces, say so. Do not invent one.

What this is not

• Not a confirmed hard block that secretly rejects applicants with no prior designated-driver experience.
• Not a named checklist copied from another mobility line.
• Not go-online wallet reserve, collection-code requirements, or daily health declaration.
• Not WeChat or official-account packaging for overseas App buyers.
• Not named map vendors, tips, bank cards, or card processors.
• Not SOS marketing. Keep emergency claims on documented passenger alarm surfaces, separate from certification.

Launch sequence sales can repeat

1. Open the driver app verification form. Fill information, choose the prior-experience answer, and upload the base images.
2. Open admin business settings and show other materials required on, then off.
3. Submit a file and walk verification review through reject and approve.
4. On the driver list, show document supplement next to ban and change-company so cleanup tools stay distinct.
5. Only then try to go online, and point at reserve or collection-code rules if the shift still will not start.

If a buyer wants “we’ll just let them drive and collect papers later,” ask who explains the first incident when the file still has no extra materials and review never happened. The documented path is submit, declare experience, upload what you require, then approve.

Soft next step

If your designated-driver rank is either unverified or stuck in an endless upload loop, set the extra-materials switch on purpose, teach reviewers to read the prior-experience answer, and keep verification review as the door to service. When a lead can demo that packet without inventing extra document names or mixing it with wallet reserve, you are ready to run designated driver software without training applicants to guess what “certified” meant.