Taxi Driver Service Score: Why It Sits on the Home Dashboard

A taxi driver does not open a dissertation before the first offer. They glance at the home board and decide whether tonight looks workable. If that board hides the service score in a buried menu, coaches invent their own gossip about who is “in trouble.” If it shows a number nobody can explain, drivers treat the figure as decoration—or as a threat. Ptaxi’s taxi dispatch software puts service score on the same driver dashboard as today’s hours, today’s accepted orders, and today’s earnings. Admin business settings include a matching service-score rules configuration. This piece is about why those two surfaces sit where they sit, and what operations actually configures versus what a sales deck should never invent.

The taxi list does not publish a point formula. That absence is the point of the training, not a hole you fill with folklore.

Why the score sits next to hours, accepts, and earnings

The documented taxi driver home dashboard displays four kinds of “how is today going” data: today’s duration online or on shift, today’s accepted orders, service score, and today’s earnings (the source list names this as today’s turnover). Read that grouping as a coaching choice.

Typical pains this grouping is meant to blunt:

1. A driver finishes a long night, remembers the cash, and forgets how many jobs they actually took—or how the platform currently rates the work.
2. A supervisor argues about “attitude” with no shared figure on the screen the driver already watches.
3. Finance talks only about earnings while ops talks only about accepts, and nobody notices the score until a complaint explodes.
4. Night desks invent a fifth metric in a spreadsheet because the home board looked like a toy.

Hours answer *how long the shift has been*. Accepted orders answer *how much work was taken*. Earnings answer *what the register recorded today*. Service score answers *how the configured rules currently rate the driver’s service*. Keep the four sentences separate even though they share one card. A high-earning short shift and a long empty shift are different stories. The score is not a substitute for either.

Nearby home tools are easy to mash into the same lecture. They should not be. The taxi driver home also has a heatmap of how orders are spread across areas, a listening-status check that inspects network state, location permission, and go-online parameters, and go-online / go-offline to start taking work or rest. Those surfaces help a driver hear work and stand in a better place. They are not documented as inputs that compute the score. Pair heatmap coaching with heatmap and listening status so the board does not become one blurry “health” number.

What drivers see—and what they do not see

Say the dashboard sentence in launch workshops exactly as the list allows: the board shows today’s hours, today’s accepted orders, service score, and today’s earnings. Do not add a weekly trend chart the taxi list does not describe. Do not add a passenger-visible score badge on the hail screen unless your own build adds it. Do not promise that a low score auto-logs a driver off. The docs do not say that.

Drivers still need a written policy you own. The product gives them a number on the home board. It does not give them the arithmetic. If you show the number and refuse to say what your configured rules reward or punish, you will get the same question every Monday: “Why did my score move?” Answer that from your ops policy, not from a invented formula printed in a brochure.

The rest of the taxi driver home still matters around that board. Driver verification must pass before the person can take platform orders. Messages carry activity notes and system notices. The online list and the older order pool decide which unanswered passenger requests a driver may see. None of those replace the dashboard. A verified driver with a quiet pool still deserves an honest board. A busy driver with a mystery score will still open a ticket.

What admin actually configures

Admin business settings list service-score rules configuration among related taxi operating controls: one-tap order, online payment, cash payment, order simple flow, income freeze, driver accept range, scheduled-order acceptance, and reminder settings.

That list is a map of neighboring levers, not a claim that they all write into the score:

• One-tap order is a passenger ordering path. It is not a scoring engine.
• Online payment and cash payment decide how a finished taxi trip can settle. They do not invent tip lines or card processors the taxi docs do not include.
• Order simple flow is the shorter dial-a-ride path. Keep that story on dial-a-ride simple flow. Do not teach simple flow as a score shortcut.
• Income freeze holds order income until a freeze period passes before withdrawal. That is a wallet timing rule. Point people at income freeze and withdrawal review and come back to the score.
• Driver accept range sits next to a harder company-territory rule: a driver can accept only if pickup or drop-off falls inside the affiliated company. That filter belongs with driver accept range, not with score arithmetic.
• Scheduled-order acceptance and reminder settings answer whether scheduled work is allowed and how reminders are configured.

The service-score item on that list confirms there is a rules configuration surface. Demo it. Show that operations can configure score rules rather than hard-code tribal knowledge in a group chat. Then stop. The list does not publish thresholds, weights, recovery steps, or a “score below X cannot grab” switch. If a prospect asks for the formula, say you configure rules in admin and you write the policy in your own SOP. Do not invent a 100-point scale because it sounds familiar.

Ops tradeoffs to say out loud

• Hide the score and coach only on earnings: fewer dashboard questions this week, more “I never knew I was in trouble” fights after a complaint.
• Show the score and refuse to explain the rules: drivers invent their own math. Supervisors cannot defend a change.
• Show the score and publish a written policy that matches what you configured: more upfront training, fewer conspiracy theories.
• Pretend the score also controls accept range, freeze, or heatmap: the night desk flips the wrong switch when a number looks ugly.

Practical notes that match the surfaces:

• When a driver asks why the score moved, open the admin service-score rules with them and compare the policy you actually configured. Do not guess.
• When a supervisor wants “stricter quality,” change the documented rules surface—and the written policy—together. Changing only the speech does nothing on the board.
• When finance stares only at today’s earnings, put the other three dashboard figures on the same coaching card so a high-cash day is not treated as a perfect day by default.
• Do not punish a driver in a meeting for a formula nobody configured.

Realtime location still helps supervisors see who is online by company. It does not invent a score change.

What this is not

• Not a published numeric scoring formula, point table, or auto-ban threshold. Those are not in the confirmed taxi lists.
• Not a claim that taxi cancellations deduct a stated number of points. Other product lines document cancel-rule deductions in their own lists. The taxi list does not import that sentence here, so this article does not either.
• Not dispatch diffusion, company-range accept rules, or unused dispatch geofences.
• Not urban-versus-intercity commission, monthly cards, or meter bill confirm.
• Not WeChat mini programs, official-account booking, or local short-code packaging for overseas App buyers.
• Not named map vendors, tips, bank cards, or card processors.
• Not permission to skip passenger safety tools you enable elsewhere. Keep emergency claims to documented surfaces, separate from score training.

Launch sequence sales can repeat

1. Open the taxi driver home and point at the dashboard: today’s hours, today’s accepted orders, service score, today’s earnings. Name each figure once.
2. Open the heatmap and the listening-status check on the same home, then say they are not the score.
3. Open admin business settings and point at service-score rules configuration without reciting invented weights.
4. Walk the neighboring switches on that list—simple flow, income freeze, accept range, scheduled-order acceptance—so the buyer sees a row of levers, not one magic quality knob.
5. Ask the buyer to write, in one page, what their configured rules will reward or punish. If they cannot write it, they are not ready to show drivers the number.

If someone wants “just display 100 and never talk about it,” ask who answers the first driver who thinks the figure is random. That person is usually standing in the demo.

Soft next step

If your drivers already argue about a score they cannot find—or a score nobody can explain—put service score back on the home dashboard next to hours, accepts, and earnings, and open the admin service-score rules as a real configuration, not a rumor. When a lead can demo those two surfaces without inventing a formula the taxi docs do not give, you are ready to run taxi dispatch software without training the rank to guess what “quality” means tonight.