Ride-Hailing App Development

Ride-Hailing Driver Import and Export: Templates, Company Changes, and Document Top-Ups

Hiring a batch of drivers one row at a time is slow. Later you still have to move a driver to another company, or collect a document that did not arrive with the first file. Ptaxi’s ride-hailing app documents driver import, filtered export, company change, and document supplementation on the admin driver list.

This article stays on those list actions. Driver verification already has its own post. Treat review as a related step, not a retell. This is not a fleet-management walkthrough.

What import and export actually do

Import Drivers is a bulk import for fast onboarding. Driver data must follow the import template. That is the whole contract in the list. The list does not name the template columns, the required fields, or the file-format rules. Do not brief a column list as a product fact. Open the template in a demo, write down the actual headers, and train import against that file. A clean import is only as clean as the template. Bad rows still need a human to fix.

Export Drivers lets customer service export driver data, filtered by search criteria. Use this when you need a working copy of a subset of the roster, not as a nightly HR feed. The list does not document scheduled export, an HR-system sync, or automatic roster updates. Do not invent those.

The driver list itself is the place these actions sit. Staff can view all drivers and open driver details, including account info, login logs, registration logs, related orders, driving records, and performance evaluations. The row actions that belong in this article are company change and document supplementation. Account suspension or reinstatement and push notifications sit on the same record as neighboring actions. Do not turn suspension or push into the center of the talk.

The tradeoff is speed against cleanliness. A template import is the documented way to get a hiring batch onto the list without typing every row. It does not, on the facts we have, validate the roster into a finished, verified fleet by itself. Plan for a review pass after the file lands, and keep export as a filtered snapshot rather than an integration you have not seen.

Staff should treat the list as the system of record for the roster row, not as a finished onboarding file. After an import, open a few driver details and look at what actually landed. Account info, login logs, registration logs, related orders, driving records, and performance evaluations are the documented detail groups. A new import will not have much history yet. That is the point of opening the record. You are checking that the row exists and that the fields you expected from the template are there, without inventing a column list in the briefing.

A hiring wave is also a good time to decide who is allowed to import and who only exports. The list names customer service as the role that can export, filtered by search criteria. It does not say whether import is limited to the same role. Confirm permissions in a demo. Then keep the operating rule simple: import a small batch first, export the same filter to see what you got, and only then load the rest of the file.

Company change and document supplementation sit on the driver record

After a driver is on the list, the work is not finished. Company change moves a driver from one company to another. The list confirms the action. It does not describe a workflow wizard, a transfer history tab, or an automatic reassignment of open trips. In a demo, change a test driver to a second company and write down what else updates — orders, login, payouts — without promising those side effects until you have seen them.

Company change matters because a hiring batch is easy to land in the wrong place if the template work is sloppy, or because a driver later needs to move. The documented fix is the company-change action on the driver record. Use it as a correction tool and as a planned transfer tool. Do not brief a bulk company-change import the list does not describe. The import is for driver data that follows the template. The company change is a list action after the row exists.

Document supplementation is the other list action that matters after import. A bulk file can create the roster row. It does not replace the documents that verification still requires. Staff can top up documents on the driver record when something is missing or has expired. The list does not spell out which files this action accepts, or whether it bypasses verification review. Confirm that in a demo, then keep supplementation as a desk path for a missing upload, not as a second onboarding product.

This is also why verification cannot be skipped in the briefing. A missing Vehicle Operating License, Commercial Insurance Policy, or Driver Qualification Certificate will still have to be collected. Document supplementation is how staff add files on the admin record. The driver can still apply and upload from the driver app, and administrators still approve or reject. Keep those three named documents in the script. If a buyer asks about other licenses, say the list names these three and confirm any others in a demo.

Account suspension, reinstatement, and push notifications are on the same driver row. Mention them as neighboring actions. This article is about getting drivers onto the list in bulk, moving them between companies, and collecting missing documents.

Verification is a related step, not this walkthrough

After a driver applies for affiliation verification, backend administrators review the driver’s details and approve or reject. The same review supports editing driver and vehicle information. That path is already covered in driver onboarding and verification. One pointer is enough.

Document settings under business modules belong in the same short pointer. During driver verification, required uploads can include a Vehicle Operating License, a Commercial Insurance Policy, and a Driver Qualification Certificate. Do not add other document types. Do not treat the import template as a substitute for those uploads. Import gets the row onto the list. Verification still reviews the person and the vehicle, and those three documents are the ones the list names.

The driver app is where a driver applies and uploads. This article stays on the admin import, export, and list actions. If you need a contrast in a demo, open the driver-app verification form for a minute, then return to the admin list.

Fleet list is a different screen

Fleet List is a different screen. Staff can view and manage the fleet, bind fleet members, and view fleet totals, fleet drivers’ income, and order data. If a buyer asks whether import is “fleet management,” say no, then stop. Do not turn this page into a fleet training.

What not to promise on driver import

Do not invent template column names, required-field lists, or file-format rules. The list requires the import to follow the template. Confirm the actual columns in a demo.

Do not invent HR-system sync, automatic roster updates, driver-app self-import, or tag-based auto-assignment of imported drivers. Do not claim import auto-approves verification or skips the three named documents. Do not describe a passenger-facing or driver-facing import. Export is a filtered customer-service export, not a scheduled integration.

A short ops checklist before you brief the app

Keep this to one page.

  • In admin, open the import template. Write down the actual columns. Import a small test batch that follows the template, and a second batch with a bad row, so you can see what still needs a human review.
  • Export a filtered subset of drivers. Note the search criteria you used. Do not brief a scheduled feed.
  • Open a driver record. Run a company change to a second test company and write down what you see.
  • Use document supplementation on a driver who is missing an upload. Keep the required verification documents to Vehicle Operating License, Commercial Insurance Policy, and Driver Qualification Certificate.
  • Point at verification review as the approve-or-reject step, including the option to edit driver and vehicle information. Do not retell the onboarding post.
  • If useful, open Fleet List for one sentence of contrast, then leave it.

If a script starts promising an HR sync or a self-serve driver import, cut it back to a template file, a filtered export, a company change, and a document top-up on the admin list.

Close

Ride-hailing driver import is a template-based bulk load for fast onboarding, with a filtered export when customer service needs a working copy of the roster. After the row exists, staff can change the driver’s company and supplement documents on the same list. Verification review remains a related step, with three named uploads during verification.

That is enough to brief a hiring batch. It is not enough to sell an HR sync, a self-serve driver import, or an auto-assignment rule the list does not describe. Look at the driver list on the ride-hailing app product page. If you want a walkthrough, ask for a demo and bring a template file, one company change, and one missing document.

Frequently asked questions

What does ride-hailing driver import actually require?

Import Drivers is a bulk import for fast onboarding, and the driver data must follow the import template. The list does not name the template columns, the required fields, or the file-format rules. Operators should confirm the actual columns in a demo and train import against that file. A clean import is only as clean as the template; bad rows still need a human review.

Can customer service export only some of the drivers?

Yes. Export Drivers lets customer service export driver data, filtered by search criteria. Use this when you need a working copy of a subset of the roster. The list does not document a scheduled export, an HR-system sync, or automatic roster updates. Do not invent those.

After import, how do staff move a driver or collect a missing document?

On the driver list, staff can perform a company change and document supplementation, along with account suspension or reinstatement and push notifications. Company change and document supplementation are the list actions this article focuses on. The list does not describe a transfer wizard or say that supplementation bypasses verification review. Confirm those details in a demo.

Is driver import a substitute for verification review?

No. After a driver applies for affiliation verification, backend administrators review the driver’s details and approve or reject, and they can edit driver and vehicle information. During verification, required uploads can include a Vehicle Operating License, a Commercial Insurance Policy, and a Driver Qualification Certificate. Import gets the row onto the list. Verification remains a related step, already covered in its own post.

Related articles

Talk to our team about your platform

Tell us your market and business model. We will reply with a feature plan, a demo of the apps and a quote.