Scorecards
What it's for
Scorecards is how each technician is performing — jobs closed, revenue, first-time fix, callbacks. It exists so a coaching conversation starts from the same numbers both people can see, rather than from an impression.
Reach it from Scorecards in the sidebar, at /scorecards. The page opens
on "Pick a technician from the list to see their full scorecard."
Tabs
The index has no tabs. A technician's own scorecard has Trend and Jobs, covered on the technician scorecard.
Panels and controls
- Search finds a technician — "Search techs…".
- Filters narrow what you are looking at, each with a count: All, First-time fix, and Callbacks. Callbacks is the one that matters most: a return visit is the single clearest signal that something did not go right the first time.
- The job table shows #, Job, Date, Outcome, and Value, so a number on the scorecard can always be traced back to the jobs behind it.
- Picking a technician opens their full scorecard.
Numbers here are snapshots taken per period, so a scorecard read today for last month shows what last month actually was rather than being recomputed against today's data.
What it accepts
The screen takes no input beyond its search and filters.
How to configure it
- Job costing settings decide how revenue and margin per technician are worked out.
- Dashboard settings decide the default period.
- Branches scope which technicians a branch-limited user can see.
Who can see it
This screen sits behind the Scorecards area.
Owners and office managers can open it. Dispatchers and technicians cannot — a technician sees their own scorecard in the field app, not the whole team's. The gate is checked on the server, not just hidden in the sidebar, so a direct link does not get around it.
The full role matrix is on Roles & permissions.