Technicians
Loading...
Detailed Strike & Deduction Report
Callback Analysis
Key: how to read this page
Role: where the visit sits in the machine's story
- BOC first visit: the visit that started it. A manager judges it.
- MOC middle visit: a visit with others before and after it. A manager judges it too.
- EOC latest visit: the return trip itself. It is the evidence the machine came back, so there is nothing to judge. These rows are faded.
CSWO: did this visit cause the next one?
- Yes this visit led to the return. These are the real callbacks, our most important measurement. A Yes is not automatically the tech's fault: the Primary Cause says who or what was responsible.
- No the machine came back for an unrelated reason.
- N/A nothing to judge: the latest visit, or a record that is not a repair, like a pickup.
Reading the table
- Alternating bands group one machine. A color change means a different serial number.
- Click any row to open the full chain for that machine.
Weekly Closed WOs
- Click Get last week's report while signed in to WaterDesk in this browser. It returns the Sunday to Saturday week before today, so do it Monday or Tuesday morning, before the Service Manager meeting.
- Drag that file into the box. Processing takes a minute or more; keep this tab open until it answers.
Forwarding the WaterDesk email to marketing@hydr8.us with the file attached still works too. Use one or the other; doing both is harmless.
Callback Analysis
Weekly Cause Report
Counts are human verify/correct events made during this week, deduped to the latest state per WO. A verification that leaves the AI first pass unchanged counts; an unverified Saturday first pass does not. This summarizes review activity, not a matured KPI for the WO week.
| WO | Company | Serial | Close Date | Role | CSWO | Reviewer | Tech | Primary | Conf. | Secondary | Model | Location |
|---|
Loading callback data...
My Callback Performance
Loading your performance...
First Call Resolution
Final, matured weeks only — a week appears once its full 60-day repeat window has passed.
Loading FCR...
Reference
Definitions and taxonomies used by this dashboard
How the callback system works
When a machine needs service again within 60 days, its visits form a repeat chain, also called a cluster. The system follows each one through six steps:
- Find. Every night the system looks for machines (serial numbers) that needed service again within 60 days.
- Suggest. Empire reads the WO notes and suggests a cause, and whether the earlier visit caused the return.
- Decide. A manager reviews every suggestion and makes the final call. Only a person's decision counts.
- Count. A confirmed callback counts once, in the week the manager decided it.
- Learn. Empire learns from every manager correction, so its suggestions improve over time.
- Review. Each month Eric reviews each tech's confirmed Tech Faults, with a link to every WO.
Weekly rhythm: upload the Weekly Closed WOs report, then decide every row before the weekly Service Manager meeting.
Why a No can still have a known cause. CSWO asks only whether this visit caused the next one. Often we know exactly what did, for example the customer shut off the water. That is recorded as the Primary Cause (Customer), and CSWO is still No, because the visit itself was not the cause. A planned next visit, like a scheduled service, is also No.
The orange dot (●) next to a role in the table means take another look: the machine came back again after that row was reviewed.
Caveats: read the numbers with these in mind
- The numbers show the trend, not exact counts. The system has known gaps: notes that leave things out, serial number mistakes, data from the moment the tech closed the WO, and rules that are still being improved. Each week's count has some error in it. But the errors are roughly the same from week to week, so the direction is real: if callbacks keep falling over several weeks, service is improving. With so few callbacks, one decision can swing a single week's % a lot, so read several weeks together before drawing a conclusion.
- Under construction. The rules are still being improved. When a rule changes, the trend has a break at that date, so compare weeks before and after a change carefully.
- Numbers move as decisions are made. A week's tiles keep changing until a manager has decided every row. A callback decided today counts this week, even if the visit was weeks ago.
- Only as good as the WO notes. Empire and the managers judge from what the tech wrote. If the notes leave something out, such as a phone call or a customer conversation, the call can be wrong.
- Only repeat visits within 60 days count. A machine that comes back after 61 days starts a new chain.
- Machines are tracked by serial number. A wrong or missing serial number can hide a repeat visit, or link two unrelated ones. The weekly SN check catches most of these.
- The data is a snapshot from when the tech closed the WO. The dashboard reads the WaterDesk completion email sent the moment a tech closes a WO. Anything changed in WaterDesk after that, such as a corrected service type, notes or serial number, only reaches the dashboard when the Weekly Closed WOs report is uploaded. Until then, some visits from the last days of the week may be missing or out of date. Coming: the WaterDesk API will let the dashboard read WOs directly, with much fresher data.
- More callbacks can mean better detection. In the early months, counts may rise because the process sees more, not because the work got worse.
- Before 10/29/2026, verdict dates are estimates. Older callbacks count in the week of the visit. From 10/29 on, they count in the week the manager decided.
- Agreement is only meaningful if managers really check. A Confirm without a real look raises agreement and teaches Empire the wrong lesson.
Dashboard tiles: full definitions
- Total Service WOs: work orders closed this week that could turn into a callback, and the base for the % on Manager Confirmed. Excludes logistics (Delivery, Shipment, Backorder Delivery, Backorder Shipment), lifecycle work that cannot fail a fix (Pick-up, Product Pickup, Refurbish, Removal and Disposal) and ruled duplicates. Counted by close date. Sourced from WaterDesk completion emails, corrected by the weekly report.
- Manager Confirmed: work orders a person decided CSWO = Yes, counted once per work order, in the week the decision was made, whatever the visit's date. Empire's unreviewed Yes does not count. The % divides by Total Service WOs.
- Left to Adjudicate: rows a person still has to decide: no one has saved or confirmed them, or CSWO is still blank. Empire's first pass never clears a row. Administrative / Closure rows count until someone confirms them. EOC rows and repaired rows are left out. The Left to Adjudicate button and the cluster card use the same rule. "New visits by SN" counts return visits (2nd or later on the same machine within 60 days) that closed this week, not counting pickups, refurbishes and removals.
- Root Cause Agreement: of the rows a person reviewed this week where Empire suggested a Primary Cause, the share where the Primary still matches Empire's. The Secondary is not compared. Rows carried forward from an earlier week's decision are not counted again.
- CSWO Agreement: of the rows a person reviewed where Empire suggested Yes or No, the share where the CSWO still matches Empire's.
Savings & ROI
What the accountability system saves Hydr8, in dollars, against locked baselines.
Loading savings model...
KPI Savings Ledger
Improvement Targets (annualized)
Automation Labor Savings
Callback Rate History (context)
Model Assumptions (locked)
Scheduling
Assign jobs to techs by skill, history, and area. Recommendations are decision support — WaterDesk remains the schedule of record.
Loading scheduling board...
Find the right tech for a job
Open work orders
Auto-fed each day from the WaterDesk Open WOs report email. A WO that drops out of the daily report disappears from this list on its own. "Seen" counts daily reports since first sighting; high counts and red ages are the disposition backlog.
- Click Get today's report. You must be signed in to WaterDesk in this browser; the file lands in your Downloads.
- Drag that file into the box above (or click the box and pick it). The queue below refreshes in a few seconds.
A successful refresh updates the Last updated line below with your name and the time. Refresh any time of day; this queue should always be as-of-now.
Tech capability board
Tom's 0-10 ratings, with what Empire has observed in parentheses (jobs closed in that category, last 6 months). Caused-callback rate is adjudicated CSWO only.
Logistics
Delivery, shipment, and backorder fulfillment, tracked separately from Service metrics.
Loading logistics...