Dashboards by role: technicians
A Fair Technician Scorecard on ServiceTitan Data: Five Numbers and the Arguments They Start
Post a ranking in the shop and you will hear about it by 7:15. Some of the complaints will be right. Here is a technician scorecard built on your ServiceTitan data that answers the fair ones before anyone raises them.
November 12, 2026 · 10 min read
The short answer
A fair technician scorecard shows close rate, opportunity job average, revenue per hour, recalls and memberships sold for each technician, using ServiceTitan's own definitions, with the count behind every rate and comparisons only between like job types and business units. Each number opens its job list. DataCram builds one on your ServiceTitan data starting at $575, with hosting from $55 a month.
On this page
- The ranking goes up on Monday. The complaints start by 7:15.
- Five numbers per technician, each with ServiceTitan's rule attached
- A legacy report whose Close Rate is really a conversion rate
- Six rules that keep a comparison between technicians honest
- Exports, adjustment invoices and the 31-day wall
- Who sees which row, and why it matters
- Price, permissions, and shops that should fix settings first
The ranking goes up on Monday. The complaints start by 7:15.
Every service manager has watched it happen. The leaderboard goes up. The top name belongs to the technician who ran tune-ups in a new subdivision all month. Near the bottom is the one sent to every no-heat call in the oldest part of town, where the answer was often a part, not a system. The bottom technician is not wrong to be angry, and the manager knows it. A scorecard that ignores the mix of work does not measure skill. It measures dispatch.
ServiceTitan has scorecards, and they are useful. Its Technician Scorecards article, as read in November 2026, describes scorecards by business unit division with Overview, Lead Generation, Memberships, Productivity and Sales tabs, and notes that "Account configuration is required to use this feature." A Release Hub note published April 30, 2026 describes Day In Review, which sends technicians a personal summary at the end of each day.
A custom scorecard is for the company that wants the comparison fair, the definitions visible and the jobs behind every number one tap away. It is one of the role dashboards we build through our custom dashboard service, reading your own ServiceTitan account through the API.
Five numbers per technician, each with ServiceTitan's rule attached
Each column on the scorecard carries the rule ServiceTitan uses for it, quoted from ServiceTitan's help center (read November 2026), or our own rule, labeled as ours where ServiceTitan publishes none. The explainer pages in this section go deeper on each.
| Number | Definition used | One tap opens |
|---|---|---|
| Close rate | ServiceTitan's formula divides the "count of closed opportunities" by the "count of sales opportunities"; a closed opportunity is a completed job whose sold estimates meet the sold threshold (close rate guide) | Every opportunity that did not close, with estimate amounts |
| Average ticket | Opportunity job average, which ServiceTitan calls "the ServiceTitan primary metric for average ticket" (average ticket guide) | The jobs in the average, largest first |
| Revenue per hour | ServiceTitan lists a Revenue Per Hour column; we did not find its formula, so the scorecard prints the one we agree with you (revenue per hour guide) | Jobs with revenue and hours side by side |
| Recalls | Jobs ServiceTitan's glossary calls a fix for "a persisting issue from a previously completed job," counted only when marked as recalls (callback rate guide) | Each recall beside the original job |
| Memberships sold | Memberships Converted: membership opportunities "that resulted in a membership sale or renewal" | Membership opportunities, sold and not sold |
Sources: the sold threshold article, the dashboard business metrics article, the Business Unit Performance template and the glossary. Two fine-print items matter. A membership counts on ServiceTitan's dashboard only if it is "sold or renewed on an invoice." And revenue on a technician's line is split-adjusted: by default, the glossary says, the whole split goes to the first technician assigned. A helper on a two-person install shows no revenue unless someone sets the split.
A legacy report whose Close Rate is really a conversion rate
This is the trap behind the loudest argument. In ServiceTitan's current definitions, close rate and conversion rate are different numbers. Its troubleshooting article, as read in November 2026, says Close Rate is "Exclusive to sales and estimates" and Conversion Rate is "Exclusive to revenue and invoices." A comfort advisor selling replacements lives on the first. A technician running service calls lives mostly on the second.
The legacy Technician Performance Board uses the label differently. Its report guide calls its "Close Rate" the technician's "conversion rate within the report date range," computed as "([Jobs] - [Estimates]) / [Jobs]". In that report, "Estimates" means completed jobs whose invoices fell short of the sold threshold, not estimates at all. A manager reading the legacy board and a technician reading the current scorecard can both say close rate and mean two different things.

Even the current template carries three versions: Close Rate, Close Rate Rolling and Close Rate As Of, per ServiceTitan's Technician Performance template article. The close rate guide works through ServiceTitan's own January example, where one estimate reads 0% under one version and 100% under another. Our scorecard picks one version, names it on the column header and keeps it, so the number a technician saw in March means the same thing in June.
Six rules that keep a comparison between technicians honest
The rules below lean on ServiceTitan's own definitions, as read in November 2026, plus the habits that stop a scorecard turning into a grievance.
- Compare like with like. Replacement sales against replacement sales, service calls against service calls, inside one business unit. Mixing them ranks job mix, not skill.
- Show the count beside the rate. A 60% close rate on five opportunities and one on fifty are different facts. Small samples get a flag, not a rank.
- Check the sold threshold. ServiceTitan warns that "With a $0 sold threshold, conversion rates are always 100%," and suggests setting it "a minimum of $1 over your dispatch fee." Thresholds are set per job type and changes apply retroactively, so the scorecard notes when one changed.
- Respect No Charge jobs. On ServiceTitan's dashboard, a No Charge job "cannot decrease" a close or conversion rate, and recall and warranty jobs are No Charge by default. Nobody is marked down for going back to fix a colleague's work.
- Credit splits. Two technicians on one install should not read as one hero and one zero. Set splits in ServiceTitan and the scorecard reads them.
- Compare a technician with their own past. Last quarter against this quarter is often the fairest view of all.
What you will not find is an outside yardstick. We will not print an industry close rate or a target ticket beside anyone's name. We have no sourced figure to offer. Besides, section 3.4(29) of ServiceTitan's API Terms of Use, in the version dated April 15, 2026, bars anyone from deriving "benchmarks, industry reports," trend data or similar works from API data. Your best technician's last quarter is a better target than a number from a stranger's slide deck anyway. Our Insights post on scorecards that coach instead of shame shows how to adjust each close rate for the calls a technician was handed.
Exports, adjustment invoices and the 31-day wall
ServiceTitan's scorecards have two limits worth knowing, both from the Technician Scorecards article as read in November 2026. First: "you can export the information to an XLSX file if the date range is less than 31 days." A quarter of scorecards means at least three exports and a spreadsheet to stitch them together. Second, by default the scorecards leave adjustment invoices out of revenue, while the legacy board's Job Avg "Includes adjustment invoices," per its report guide. Two revenue figures for one technician can both be right.
Business units add a third wrinkle. Each scorecard is a business unit division, and its metrics follow each invoice item's business unit, which by default is the job's rather than the technician's. So a technician "can appear on different scorecards," as the article puts it. A plumber who swaps a water heater on an HVAC job turns up in two places, with part of the month on each.
A custom scorecard reads the same records through ServiceTitan's API and shows a quarter or a year on one screen, with the adjustment rule printed on it. It does not need a permanent copy of your data to do that. ServiceTitan's API Terms cap the time API content may be kept at 24 hours, with exceptions the terms and documentation spell out, and they do not settle whether a derived number counts as content, so we design for the strict reading and ask you to confirm what your agreement permits. The API data page explains the mechanics.
Who sees which row, and why it matters
The technician
Their own five numbers, their own job lists and their own trend. Not a leaderboard. The point is where they stand against their own last quarter, not where they rank.
The service manager
Every technician, grouped by job type and business unit, with counts and small-sample flags. This is the coaching view.
The owner
The same rows, plus revenue and the tiles they roll up into on the owner dashboard. Pay stays off the screen unless you put it there.
The ride-along
One technician, one week, every opportunity with the options presented. This is where the scorecard stops being a number and becomes a conversation in the truck.
The arguments will still happen. The difference is that they happen about the work, with the job list open, instead of about whose spreadsheet is right. That is also the point of the monthly numbers review: we sit with the service manager, look at what moved and why, and leave with two or three things to try. The general manager dashboard carries the follow-up lists that come out of it.
Price, permissions, and shops that should fix settings first
Pricing for a technician scorecard begins at $575 for the build and depends on complexity (as of November 2026). A fixed written estimate comes first, always. Five columns for one business unit land near that floor; several units, ride-along views and per-person permissions raise it. Hosting runs from $55 a month under our hosting and maintenance plan, and the ServiceTitan API connection is live the day we start. ServiceTitan's Developer Portal, on its integration paths page read in October 2026, ties customer-built apps to the "Works or Ent Plus package," so check your agreement first.
DataCram is a San Antonio, Texas web studio that has built for the web since 1999, working with companies around the country over phone and video, with a shared project page for each build. DataCram has no affiliation with ServiceTitan. If you are replacing ServiceTitan's field app rather than reading its data, the technician web app is the page to read. The build itself sits under our web app development service. Read about us, or call (210) 346-0848 with a copy of the leaderboard that started the last argument.
Questions owners ask about ServiceTitan dashboards and numbers
Five cover most of it: close rate on sales opportunities, opportunity job average, revenue per hour, recalls, and memberships sold. Show the count behind each rate, compare technicians only on like job types and business units, and let each number open its job list. Add replacement leads generated if your technicians set appointments for comfort advisors.
Because the label means different things in different places. As ServiceTitan's help center read in November 2026, current close rate counts sold estimates on sales opportunities, while the legacy Technician Performance Board's Close Rate is an invoice-based conversion rate. The current template also offers Rolling and As Of versions. A scorecard should name the version it uses.
Group them by job type and business unit before comparing, show the number of opportunities beside every rate, flag small samples, and make sure splits and sold thresholds are set. Then compare each technician with their own previous quarter as well as with peers. A ranking that mixes tune-ups and no-heat calls measures dispatch, not skill.
Not from the scorecards themselves. ServiceTitan's Technician Scorecards article, as read in November 2026, allows an XLSX export only when the date range is less than 31 days. A custom scorecard reading the same data through the API can show a quarter or a year on one screen, within ServiceTitan's API rules and your agreement.
That is your call, and the build follows it. Many managers show each technician their own numbers and trend, and keep side-by-side comparisons for coaching conversations, where the job lists are open and the context is in the room. A posted leaderboard tends to reward whoever got the easiest calls.
It starts at $575 to build, depending on complexity (November 2026 pricing), with a fixed written estimate up front and hosting from $55 a month. The ServiceTitan connection goes live the same day. Reading the scorecard together each month is what the numbers review is for, from $575 a month with no long contract.
Keep reading
- The number that starts argumentsServiceTitan Close Rate: Why One January Can Read 0% and 100%, and Which Version Belongs on Your ScreenHow ServiceTitan counts close rate, why the legacy board's Close Rate is really conversion, and how a sold threshold rewrites history. A worked example.
- Dashboards by role: ownerA ServiceTitan Owner Dashboard for 7:45 a.m.: Eight Numbers, Each With Its List Behind ItThe eight numbers a home service owner checks before 8 a.m., read from your ServiceTitan account, each defined and one click from its list. From $575.
- Module: technician web appA Technician Web App on the Phone Already in Their Pocket: Jobs, Photos, Signatures, Payments and an Honest ScopeA field technician web app: jobs, photos, notes, signatures and payments on the tech's own phone, with an honest first-version scope. From $575 to build.
- The build, in fullA Custom ServiceTitan Dashboard for One Role, With the List Behind Every NumberA custom ServiceTitan dashboard for one role: written definitions, a visible refresh time, lists one click away. From $575, hosting from $55 a month.
- Once a month, out loudThe Monthly ServiceTitan Numbers Review: What Moved, Why It Moved, and What Changes on MondayA monthly numbers review for ServiceTitan owners and managers: what moved, why, and what to do next. From $575 a month, no long contract, honest about fit.
- Dashboards by role: GMThe General Manager Dashboard for Home Services: Today, This Week, Every Business UnitA GM dashboard on ServiceTitan data: capacity, booked work, unsold estimates, recalls and receivables, today and this week, by business unit. From $575.
- Everything in ServiceTitan DashboardsSee the section
From the Insights desk
- Local Services Ads vs. Google Search Ads for Plumbers and ElectriciansLocal Services Ads charge when the phone rings; Google search ads charge when someone clicks. How each one bills, screens and ranks plumbers and electricians in 2026, what the move to Performance Max changes, and where the first dollar should go.
- The Estimate You Already Wrote Is the Cheapest Lead You Will Get This MonthAn unsold estimate is a lead you have already paid for in full. Why estimates go cold, what Jobber, Housecall Pro and ServiceTitan already do about it, what automation cannot do, and a follow-up rhythm that does not nag.
Get a scorecard your technicians will accept
Tell us how many technicians you run, which business units, and what you rank them on now. A person at DataCram replies with a proposed set of columns and, if you ask, a fixed written estimate.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.