A shop owner on Monday morning at 7:42 a.m. opens their phone, checks two numbers, and decides whether last week was good or bad. The two numbers are revenue per truck (RPT) and dispatch yield. Every other metric in the shop — booking %, MPR, financing close, recall %, average ticket, GLSA ROAS — feeds into those two or trails behind them. The 2026 baselines per Built on Tenth, Level CFO, and MarginPlug published research: shop baseline $1,600-$2,400/day for residential service trucks; top-quartile target $2,800-$3,500/day for service trucks; $2,500-$4,000/day for replacement trucks; $5K+/day for commercial replacement. Average residential service ticket lands $450-$600. Dispatch yield (revenue per call routed) at baseline shops is $580-$640; top-quartile shops run $720-$820. The gap between baseline and top-quartile across both metrics is where the 12-18% dispatch yield lift from L3 Ch3 Lesson 1's configuration and Lesson 2's re-dispatch loop converts into owner-visible margin. This lesson is the ops manager's playbook for building the AI-supported daily dispatch-yield report — the one-page scorecard the owner reads in 4 minutes Monday at 7:42 a.m., the report cuts that surface the lift, the AI-assembled commentary that translates the numbers into trades English, and the 60-day lift target of 12-18% the report defends across quarters.

RPT and Dispatch Yield as the Paired Metrics

The owner reads two numbers Monday morning. RPT is the daily output per truck: total revenue closed by a tech over the day. Dispatch yield is the per-call output: revenue per call routed by the dispatcher. The two metrics measure related but distinct things; both matter because they reveal different operational levers when they diverge.

RPT at top-quartile $2,800-$3,500/day for residential service trucks reflects the compounding effect of every shop discipline: dispatch routes the right call to the right tech, the tech executes the kitchen-table close, the financing pivot lands, the membership pitch attaches, the average ticket lifts. RPT is the integrated outcome. Dispatch yield isolates the routing decision: revenue per call independent of how many calls the tech ran. A 7-truck shop running $720 dispatch yield × 6 calls/truck/day × 7 trucks = $30,240/day total revenue = ~$4,320/truck/day RPT (above top-quartile). A 7-truck shop running $580 dispatch yield × 6 calls/truck/day × 7 trucks = $24,360/day = ~$3,480/truck/day RPT (around top-quartile floor). The metrics paired show the lever (dispatch yield) and the outcome (RPT).

The 2026 RPT bands per Built on Tenth, Level CFO, and MarginPlug published research the ops manager defends to the owner: shop baseline $1,600-$2,400/day for residential service trucks; top-quartile target $2,800-$3,500/day. Replacement trucks $2,500-$4,000/day top-quartile target. Commercial replacement $5K+/day. Average residential service ticket $450-$600. Dispatch yield baseline $580-$640 per call; top-quartile $720-$820 per call. The gap between baseline and top-quartile is the lift the configuration plus loop captures over 60 days.

RPT by Truck Type

The ops manager reports RPT segmented by truck type because the bands differ by truck role. Residential service trucks (typical mix of tune-ups, repairs, diagnostic calls, occasional replacement quotes) run shop baseline $1,600-$2,400/day; top-quartile $2,800-$3,500/day; the gap is $1,100/day per truck. Replacement trucks (Comfort Advisors or replacement-specialist techs running primarily replacement quotes and installs) run higher with baseline $2,200-$3,000/day; top-quartile $2,500-$4,000/day; the gap is more compressed. Commercial replacement trucks run $5K+/day at top-quartile with much higher variance based on project pipeline. The ops manager reports each band separately so the owner sees lift by truck role.

The Monday Morning Scorecard: One-Page Format

The Monday morning scorecard is one page. The owner reads in 4 minutes between the truck cab and the office door. The scorecard's structure: header row with shop name and date; six summary metrics; three commentary lines; one open question. AI assembles the page from ServiceTitan / Sera / Housecall Pro FSM data overnight; the ops manager edits the commentary lines and the open question Sunday evening; the owner reads Monday at 7:42 a.m.

Six Summary Metrics

The six summary metrics on the scorecard, in order: (1) Average RPT trailing 7 days vs. trailing 30 days, broken out by truck type (service / replacement / commercial). (2) Average dispatch yield trailing 7 days vs. trailing 30 days. (3) Top-quartile target gap (current RPT minus top-quartile target, by truck type). (4) Override rate trailing 7 days vs. trailing 30 days with trend direction. (5) Configuration regression flags (number of vendor-release-note issues open, number of skill-tag drift flags). (6) Cross-functional handoffs delivered (marketing data, service manager data, installation coordinator data — count by delivery vs. expected).

Three Commentary Lines

The three commentary lines translate the metrics into trades English. Line 1: what moved (e.g., "Dispatch yield up $42 trailing 7 vs. 30, driven by 4 high-value re-dispatch decisions including Tuesday Bel Air $14K close"). Line 2: what stalled (e.g., "RPT on replacement trucks flat — Marco's install crew lost 2 days to supplier-delayed lineset shipment; recovery this week"). Line 3: what changed in configuration or override discipline (e.g., "Quarterly skill-tag refresh completed Friday; Jose promoted to premium close-rate band; rookie moved to mid band; configuration re-locked"). AI drafts the commentary from the underlying data; the ops manager edits for voice and shop-specific context.

One Open Question

The open question is the owner's decision-or-direction call for the week. The ops manager poses one question per week, ideally one that the owner is the only person who can answer. Examples: "Marco's install-rule-bend pattern continues — recommend hiring a second lineset specialist this quarter or accepting the install delay risk?" "Bel Air zip is producing 3-4 high-value calls/week from CallRail Conversation Intelligence sentiment data — recommend increasing GLSA bid weight in Bel Air or holding?" "Override rate on time-window flexes climbing 11% to 14% — recommend re-training CSR on window setting or accepting the trade-off for routing efficiency?" One question; one decision needed from the owner; the ops manager's recommendation included with reasoning.

Building the AI-Supported Daily Dispatch-Yield Report

The Monday scorecard is the owner-facing artifact; the underlying engine is the AI-supported daily dispatch-yield report the ops manager pulls every morning at 7 a.m. The daily report is granular — by tech, by call type, by zip code, by call source — and surfaces the patterns the Monday scorecard summarizes into commentary lines.

Data Sources Feeding the Report

The data sources feeding the dispatch-yield report: ServiceTitan / Sera / Housecall Pro FSM for closed tickets (call revenue, tech assignment, call type, equipment, customer history, originating CSR booking); CallRail Conversation Intelligence for call source and sentiment; ResponsiBid for estimate-stage data on three-option presentation; Wisetack / GreenSky / Synchrony for financing approvals and close rates; Hatch for nurture-sequence touch data; the dispatch AI's own override log from the configuration and loop. AI aggregates across data sources overnight via API integrations; the ops manager validates the data freshness daily before running the report.

Report Cuts the Ops Manager Pulls Daily

The named report cuts the ops manager pulls every morning: (1) Dispatch yield by tech trailing 7 / 30 / 90 days, sorted by gap to top-quartile. (2) Dispatch yield by call type, showing where high-value calls are landing and which call types are under-monetizing. (3) Dispatch yield by zip code, surfacing Bel Air / metro / suburban / rural patterns for marketing handoff. (4) Override rate by category trailing 7 / 30 / 90 days, showing learning trajectory. (5) High-value re-dispatch decision log trailing 7 days — every decision that moved $3,900+ of incremental margin (Bel Air-pattern decisions). (6) Configuration regression alerts — any vendor-release notes from the last 7 days flagging settings the shop owns.

AI-Assembled Commentary

The AI generates draft commentary on each report cut overnight using the system prompt the ops manager wrote during configuration. Commentary structure per cut: what changed, why it changed (link to a specific decision or pattern from the override log), recommended action (configuration adjustment, dispatcher training, marketing handoff, owner question). The ops manager edits for accuracy, voice, and shop-specific context — typically 5-12 minutes of editing per daily report. The AI's draft is 80% of the final commentary; the ops manager's edit is the 20% that converts AI output to operational voice.

The 60-Day Lift Target

The 12-18% dispatch yield lift target from L3 Ch3 Lesson 1's configuration and Lesson 2's loop manifests in the scorecard across 60 days. The ops manager defends the target trajectory week by week so the owner sees the lift accumulating rather than skepticism building from week 3 silence.

Weeks 1-2: Baseline and Shadow

Weeks 1-2 show baseline metrics from the L3 Ch3 Lesson 1 calibration: dispatch yield $580-$640, RPT $1,900-$2,200/day per truck, override rate not yet established. The scorecard reports the baseline and the calibration progress. Owner reads "baseline captured, shadow-mode comparison running."

Weeks 3-4: Board-Leading Transition

Weeks 3-4 show the transition to board-leading mode. Dispatch yield climbs $30-$60 (3-8% lift) as the loop captures early reshuffle opportunities; override rate establishes at 12-18% with one-line documented reasons; daily end-of-day reviews running. The scorecard reports "loop live, early lift visible, override discipline establishing." Owner reads the trajectory; ops manager points to the specific high-value re-dispatch decisions driving the early lift.

Weeks 5-8: Lift Accumulation

Weeks 5-8 show the lift accumulating to 8-12% — full lift typically lands at day 60 because the model needs the additional weeks to learn shop-specific patterns. Dispatch yield trails 7-day at $640-$720; RPT at $2,200-$2,500/day per service truck. Override rate trajectory dropping from 15% week 4 to 12-14% week 8. The scorecard reports "lift on trajectory; configuration tightening." Owner reads the accumulating numbers and starts considering capital deployment (next truck purchase, Comfort Advisor hire, marketing budget expansion).

Day 60: The 12-18% Lift Lands

Day 60 the full 12-18% dispatch yield lift lands. Dispatch yield at $700-$760 against $580-$640 baseline. RPT at $2,500-$3,000/day for service trucks. Override rate stabilizing 10-13% on declining trajectory. Configuration locked; quarterly refresh scheduled. The scorecard reports "60-day target hit; configuration locked; quarterly refresh on calendar." Owner reads the achievement; ops manager translates into annual revenue impact (~$425K-$575K margin contribution at a 7-truck $5M shop) and frames the next 90-day quarter (compounding effect, cross-functional expansion to ride-along scorecard and RC&D triage).

The Friday Recap and the Monday Scorecard Relationship

The Friday recap from L3 Ch6 Lesson 3 (Service Manager Weekly Review territory in the program structure) feeds the Monday scorecard. Friday afternoon the service manager runs the 25-minute Friday review with cross-functional handoffs (marketing on named-request data, installation coordinator on crew composition, ops manager on configuration and override patterns). The output of the Friday review becomes the source data for the Sunday-evening AI scorecard assembly. By Monday at 7:42 a.m. the scorecard reflects the full week's operational signal.

The scorecard's commentary lines often reference the Friday review's findings: "Friday review surfaced 4 install-rule-bend overrides — recommend crew-capacity hire decision this week." "Marketing handoff produced Bel Air zip pattern — recommend GLSA bid adjustment this week." "Configuration drift detected on skill-tag accuracy — off-cycle refresh deployed Saturday; daily monitoring this week." The Friday review is the input; the Monday scorecard is the output; the daily reports are the working layer.

This cadence — daily reports, Friday review, Monday scorecard — turns the dispatch AI's operational data into a structured weekly rhythm the owner consumes in 4 minutes and the ops manager runs in 8-12 hours of structured weekly work. The ops manager's role architecture across L3 Ch3 (Lessons 1, 2, 3) builds the chassis, runs the engine, and presents the dashboard. The owner sees the result; the workflow runs the lift.

Reading the Scorecard Against 2026 Baselines

The 2026 baselines per Built on Tenth, Level CFO, and MarginPlug research provide the comparison frame the owner reads against. Without baseline comparison, the numbers float in isolation; with baseline comparison, the scorecard tells the owner whether the shop is closing the gap or holding behind the curve.

The ops manager labels every metric on the scorecard with the 2026 band: "RPT residential service trucks $2,650 (shop baseline $1,600-$2,400; top-quartile target $2,800-$3,500) — ABOVE BASELINE, $250 GAP TO TOP-QUARTILE FLOOR." "Dispatch yield $696 (baseline $580-$640; top-quartile $720-$820) — TOP OF BASELINE, $24 GAP TO TOP-QUARTILE FLOOR." "Average residential service ticket $498 (band $450-$600) — MID BAND." Three lines per metric: current value, 2026 band, status (below band / in band / top of band / above band / gap to next tier).

The status labeling is what converts the scorecard from a data report to a decision tool. "Below baseline" triggers an action question. "In band" triggers a quarterly review of whether the band itself is the right target. "Top of band" triggers a stretch question (what's the next tier?). "Above band" triggers a defense question (how do we sustain?). Owners read decisions, not data; the scorecard labels every metric as a decision frame so the 4-minute read produces action rather than acknowledgment.

The Scorecard as the Ops Manager's Product

The Monday scorecard is the ops manager's product. Configuration (Lesson 1) and loop (Lesson 2) are the work; the scorecard is the deliverable. Without the scorecard, the configuration and loop produce results the owner can't see; the AI value gets attributed to vendor magic and the ops manager's work is invisible. With the scorecard, every metric movement is attributed to a specific operational discipline the ops manager owns. The ops manager who builds the scorecard captures the credit for the lift; the ops manager who runs the loop without the scorecard watches their work get attributed elsewhere.

Comp typically follows the scorecard. The ops manager's variable comp shifts to scorecard metrics: dispatch yield trailing 30 days (~25%), RPT vs. top-quartile gap closure (~25%), override rate trajectory (~15%), recall rate decline (~15%), cross-functional handoff completion (~10%), configuration regression detection time (~10%). The scorecard becomes both the owner's dashboard and the ops manager's comp model. Aligned incentives produce sustained operational discipline; misaligned incentives produce one-quarter wonders.

By month 6 the scorecard becomes shop infrastructure. The owner reads it every Monday at 7:42 a.m.; the ops manager assembles it Sunday evening; the AI drafts the commentary overnight; the data flows from configuration and loop continuously. The chassis, engine, and dashboard work together as a profit-per-truck operating system. Year-end RPT lands at top-quartile $2,800-$3,500/day for service trucks because the scorecard kept the operational discipline visible across 52 Mondays. The ops manager who built the system across L3 Ch3 (configuration, loop, scorecard) is the ops manager whose shop hits the band the 2026 baselines defined — and whose owner reads two numbers Monday at 7:42 a.m. and decides whether last week was good or bad.

Key Takeaways

• RPT and dispatch yield are the paired metrics the owner reads Monday morning. RPT is the integrated outcome (revenue per truck per day); dispatch yield is the lever (revenue per call routed). 2026 RPT bands per Built on Tenth, Level CFO, and MarginPlug: shop baseline $1,600-$2,400/day for residential service, top-quartile $2,800-$3,500/day, replacement trucks $2,500-$4,000/day, commercial replacement $5K+/day. Average residential service ticket $450-$600.
• The Monday scorecard is one page, 4-minute read, six metrics plus three commentary lines plus one open question. AI assembles overnight from FSM data; ops manager edits Sunday evening; owner reads Monday at 7:42 a.m.
• Six summary metrics: RPT trailing 7 vs. 30 by truck type; dispatch yield trailing 7 vs. 30; top-quartile target gap; override rate trailing 7 vs. 30 with trend; configuration regression flags; cross-functional handoffs delivered.
• Daily dispatch-yield report drives the scorecard. Six named cuts: dispatch yield by tech, by call type, by zip code, override rate by category, high-value re-dispatch decision log, configuration regression alerts. AI-assembled commentary edited by ops manager in 5-12 minutes.
• 60-day lift trajectory: weeks 1-2 baseline, weeks 3-4 board-leading with 3-8% early lift, weeks 5-8 lift accumulating to 8-12%, day 60 full 12-18% lift lands. Override rate trajectory 15% week 4 to 10-13% day 60.
• 2026 baseline labeling on every metric: current value, band, status (below / in band / top of band / above band / gap to next tier). Status converts data report to decision tool; owners read decisions not data.
• Annual impact at a 7-truck $5M shop: ~$425K-$575K annual margin contribution from the 12-18% lift. The ops manager translates the scorecard's metric movements into the annual revenue picture for the owner's capital deployment decisions (next truck, Comfort Advisor hire, marketing expansion).
• Cadence: daily reports + Friday review + Monday scorecard. Daily is granular working layer; Friday is cross-functional handoff layer; Monday is owner-facing summary layer. Ops manager runs 8-12 hours of structured weekly work; owner consumes in 4 minutes.
• The scorecard is the ops manager's product. Configuration and loop produce the lift; the scorecard makes it visible. Without the scorecard the ops manager's work is invisible; with the scorecard every metric movement is attributed to a specific operational discipline. Comp follows the scorecard; aligned incentives produce sustained discipline.