Designated Driver Apps

Designated Driver Performance Stats: Daily, Weekly, and Monthly Orders and Earnings

A designated-driver conversation often starts with a simple question. The driver wants to know how the week looked. The desk wants to know who accepted work, who rejected it, and what income looks like. If those answers live in a chat thread, you will argue from memory. Ptaxi’s designated driver app documents two related views for that work. In the driver profile, performance stats let the driver view earnings, or transaction flow, and accepted-order data by day, week, or month. In admin data statistics, performance stats let staff view statistics on drivers’ accepted orders, rejected orders, and income.

Those screens report what already happened. They do not, in the list, pay a bonus, rank a fleet, or replace a payroll tool.

Say the tradeoff before you brief the team. If drivers only have the today dashboard, weekly questions go back into a group chat, and the desk reconstructs a shift from memory. If you oversell the admin screen as a discipline product, someone will invent a penalty, a lockout, or a prize the list does not attach to these figures. Train the views as reports. Write any bonus or coaching rule as your policy, after you have looked at the actual columns.

The home snapshot is not the weekly report

The driver home dashboard shows today’s hours, today’s accepted orders, service score, and today’s earnings. That is a shift snapshot. It is useful when a driver goes online and wants a quick read on the day so far.

It is not the performance-stats module. The dashboard is dated “today.” Performance stats are the place to switch between day, week, and month. If you brief them as one screen, a driver will look for last week’s figures on the home tile, or a supervisor will treat a today score as a monthly review.

Service score appears on that home snapshot. It does not appear in the documented performance-stats row. Keep it where the list puts it. Do not invent a formula for the score in this article, and do not fold it into the day-week-month stats as if it were a documented column there.

The home screen also holds other operational tools — going online or offline, the heat map, the order pool — that are not performance reports. This article leaves those tools alone, including appointment changes already covered elsewhere. The only reason to mention the dashboard here is to stop people from mixing a today tile with a period report.

Driver performance stats: day, week, or month

Under the personal center, performance stats let the driver view earnings / transaction flow and accepted-order data by day, week, or month.

Two objects sit in that sentence, and you should name both in training. One is money movement, written as flow or earnings. The other is accepted-order data. The driver can look at those by a day, a week, or a month. That is the documented scope.

The list does not say whether the money figure is gross receipts, income after commission, or a wallet balance change. Treat it as a recorded flow, not as a tax document or a payout instruction. The list also does not say whether accepted-order data is a count, a list, or both. It does not mention rejected orders on this driver-app row, and it does not mention a completion rate, an attendance score, or a bonus flag. In a demo, open the module, switch day, week, and month, and write down the columns you actually see. Then stop.

If a driver asks “what did I refuse this week?,” do not promise that answer lives here. Rejected-order statistics are documented on the admin screen. Confirm in the build whether the driver page also shows a reject figure. If it does not, tell drivers that a refuse question goes to a supervisor who can open admin stats.

Passenger ratings are a different profile item

Drivers also have a passenger ratings entry in the personal center. There, the driver can view, by day, week, or month, the scores from service orders and accepted-order data.

The period switch looks familiar, which is why people mash the two screens together. Do not. Performance stats are flow and accepted-order data. Passenger ratings are scores plus accepted-order data, on a separate row. You can tell a driver that both screens offer day, week, and month. You should not tell a buyer that star ratings are a documented metric of the performance-stats module.

If your company wants a combined review that includes scores and earnings, that is an ops habit you design. It is not a single documented report. Open both screens in training, and keep them on separate lines of the checklist.

Admin performance stats: accepted, rejected, and income

Under data statistics, admin performance stats let staff view statistics on drivers’ accepted orders, rejected orders, and income. That is the desk view, and it is broader than the driver-app row in one important way: rejected orders are named here.

Use that when a supervisor is reviewing a shift pattern, not when you are selling a discipline product the list does not describe. The screen lets you see accept, reject, and income figures. It does not, in the list, recommend a penalty, lock a driver out, or write a warning letter. If your company already has a coaching rule for repeated rejects, keep that rule in your ops manual and use this screen as the source of the numbers.

The same statistics area also includes other modules: passenger stats, driver stats, order stats, and invitation stats, each with their own totals and, where the list says so, related charts. Those are neighbors. They are not this module. Invitation stats belong to a referral activity, not to performance stats. If you need company-level access rules for who can open these screens, use the role and company model already described in admin roles and company permissions. The performance-stats row itself does not publish a filter list. Confirm in a demo which drivers a given admin login can actually see.

The list also does not say that admin stats include a live leaderboard, a download button, or an automatic bonus when a threshold is hit. Ranking campaigns exist as a ride-hailing marketing tool. They are not this designated-driver statistics module. Do not import them.

What not to promise from a stats screen

Do not treat star ratings as a documented metric of performance stats; ratings are a separate profile item. Do not promise a completion rate, an attendance score, or an automatic bonus generated by these figures. Do not sell a live leaderboard, and do not brief a ride-hailing ranking campaign as if it lived here. Do not tell a driver that the home dashboard is the weekly report, or that service score is a performance-stats column. Do not invent a payroll export, a formula for transaction flow, or a rule that rejected orders appear on the driver app just because they appear in admin. If you need those behaviors, confirm them in a demo, then write them as your procedure.

A short ops checklist for drivers and the desk

Keep this to one page.

  • On a driver account, open the home dashboard and name the today snapshot: hours, accepted orders, service score, and today’s earnings.
  • Open performance stats in the personal center. Switch day, week, and month. Write down the earnings / flow figures and the accepted-order data you actually see.
  • Open passenger ratings as a separate screen. Note that it also offers day, week, and month, and that scores are not a performance-stats column.
  • In admin, open data statistics > performance stats. Confirm you can see accepted orders, rejected orders, and income.
  • Ask a refuse question from the driver side. If the driver page has no reject figure, show where that answer lives in admin.
  • Do not attach a bonus, a rank prize, or a payroll file to either screen in the training script.
  • If more than one company is in scope, confirm which drivers an admin login can see, using the role model you already trained.

If a script starts promising a leaderboard or a bonus paid by this module, cut it back to the period views you can actually open.

Close

Designated-driver performance questions come in two places. The driver can open a profile module and view earnings and accepted-order data by day, week, or month. The desk can open admin performance stats and view accepted orders, rejected orders, and income. The home dashboard remains a today snapshot, and passenger ratings remain a different screen.

That is enough to stop arguing from a chat history, if you train the screens as they are. It is not enough to sell a bonus plan, a completion-rate product, or a live ranking board. Look at performance stats in Ptaxi’s designated driver app. If you want a walkthrough, ask for a demo and bring one driver’s week and one reject question, then open the driver period view and the admin stats side by side.

Frequently asked questions

What can a designated driver see in performance stats?

In the driver profile, performance stats let the driver view earnings, or transaction flow, and accepted-order data by day, week, or month. That is the documented scope of this module. Rejected-order figures are documented on the admin performance-stats screen, not in this driver-app row. Confirm in a demo whether any reject count also appears on the driver’s own stats page.

Is the home dashboard the same as performance stats?

No. The driver home dashboard is a today snapshot: today’s hours, today’s accepted orders, service score, and today’s earnings. Performance stats are a profile module for day, week, or month views of earnings and accepted-order data. Do not train the dashboard as a weekly report, and do not treat service score as a documented metric inside the performance-stats module.

What does the admin performance-stats screen include?

Under data statistics, performance stats let staff view statistics on drivers’ accepted orders, rejected orders, and income. Other statistics modules — passenger, driver, order, and invitation stats — are separate. The list does not say these figures automatically issue a bonus, build a live leaderboard, or export a payroll file. Confirm layout and filters in a demo.

Are passenger ratings part of this performance-stats module?

No. Passenger ratings are a separate profile item. There, the driver can view, by day, week, or month, the scores from service orders and accepted-order data. You can mention that screen so staff do not go looking for stars inside performance stats. Do not treat star ratings as a documented metric of the performance-stats module, and do not import a ride-hailing ranking campaign into this view.

Related articles

Designated Driver Admin Roles: Own-Company Data vs Subordinate Companies

A group that runs several designated-driver companies cannot give every branch the same back-office view. Admin roles separate data permissions — own company only, or own company and subordinate companies — from operation permissions that control which features a backend administrator can use. Company records and staff accounts sit in the same permission area. This is a procurement question about who sees which books, not a slogan about enterprise access.

· 7 min read

Designated Driver Account Managers and Referral Rewards

Night-time designated-driver volume often comes from a person, not a billboard: a venue host, a regular rider, or a driver who brings a friend. The product has an account-manager path for promoters and a separate invite-and-earn campaign tool. If you never configure a campaign, the refer-and-earn screen is only a download link.

· 7 min read

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.