A Voicify dental AI battlecard library with 20+ slot-aware artifacts and a trigger map that decides which artifact fires for which deal moment is still inert until something forces the rep to actually deploy the right card on the right signal in the field. That something is the weekly forecast call scorecard. The scorecard is the manager-facing one-page rubric that grades every open dental AI deal across four dimensions — slot-tag hygiene, activation cue compliance, override discipline, and signal-to-outcome correlation — and assigns a green, yellow, or red rating per deal per dimension. It is the enforcement layer the library and the trigger map both depend on. Without it, the system collapses inside two quarters into "use whatever battlecard feels right," and the slot-aware weighting built into every artifact in the library quietly stops mattering. This post is the field-facing build of that scorecard: the rubric, the data inputs, the running protocol, the coaching escalation path, and the failure modes that recur when teams try to skip the scorecard or run it without RevOps in the room.
TL;DR
Four dimensions, three colors, two minutes per deal. The forecast call scorecard grades each open Voicify dental AI deal on slot-tag hygiene, activation cue compliance, override discipline, and signal-to-outcome correlation. The manager grades, RevOps verifies against the activation log and the slot-flip log, the AE narrates and explains reds. Two reds in two consecutive calls escalates to a structured intervention. The scorecard reads from three RevOps-prepared inputs and writes one output: a per-deal grade that flows into the quarterly refresh meeting alongside win-loss themes and CSM field intel. Without the scorecard the trigger map is decorative; with it, the library's slot-aware weighting compounds into measurable win-rate lift.
Why the Scorecard Sits Below the Trigger Map and Above the Pipeline Review
The trigger map tells the rep which artifact to deploy in which deal moment. The artifact itself — the discovery brief, the demo script, the pilot scorecard, the CSM B-slot defense plan — does the work in the buyer-facing moment. The forecast call scorecard is the layer in between: the weekly check that the rep actually consulted the map and actually deployed the artifact when the signal fired. The pipeline review sits next to the scorecard and asks a different question — where is this deal and when will it close. The two reviews are complementary and most teams already run the pipeline review; the gap is the scorecard, and that gap is the reason 18-month-old battlecard libraries quietly stop mattering even though the rep certification rubric still passes everyone.
Skipping the scorecard is the single most common failure mode in dental AI sales systems that look fully built on paper. The library exists. The trigger map exists. The slot-flip log column is in CRM. RevOps wired the activation log. The rep certification check happens quarterly. And yet the slot-weighted variants of every artifact never actually fire in the field, because no one is grading whether they fire. The scorecard closes that loop. Two minutes per deal in the existing forecast call is the entire intervention.
The Four Dimensions and How Each One Is Graded
The scorecard grades four dimensions per deal. Each dimension gets green, yellow, or red. The grades roll up into a per-deal status that managers track week over week.
| Dimension | Green | Yellow | Red |
|---|---|---|---|
| Slot-tag hygiene | Slot tag set, updated within 14 days, consistent with last three buyer interactions | Slot tag set but stale (15-30 days) or one inconsistent interaction | No slot tag, or tag contradicted by two+ recent interactions with no flip log entry |
| Activation cue compliance | Trigger map artifact deployed within 48 hours of qualifying signal | Artifact deployed but later than 48 hours, or default artifact used when signal should have overridden | No artifact deployed on a signal that fired, or wrong-slot variant deployed |
| Override discipline | Override fired within 24 hours, logged to slot-flip log with reason code | Override fired but not logged, or logged without reason code | Signal fired, no override deployed, no log entry; or override deployed on noise without signal in CRM |
| Signal-to-outcome correlation | Activations correlate with stage advancement in the activation-log dashboard | Activations fire but stage advancement is flat — needs investigation | Activations fire and stage regresses or deal stalls — coaching required |
The four dimensions are deliberately not equal-weighted. Slot-tag hygiene and override discipline are non-negotiable — a red in either of those produces a red overall deal grade regardless of the other two columns. Activation cue compliance and signal-to-outcome correlation are diagnostic — they tell the manager what kind of coaching to apply, not whether the deal is in trouble on the system layer. A deal can be green on signal-to-outcome and red on slot-tag hygiene, and the manager treats it as a red deal that happens to be advancing despite the system gap, not as a green deal.
The Three RevOps Inputs Pulled Before the Call
The scorecard is unrunnable without three RevOps-prepared inputs in the room. RevOps pulls these the business day before the forecast call.
The slot-tag report. Every open deal, current A-or-B-or-unknown tag, last-updated date on the tag, and any entries in the slot-flip log since the previous forecast call. The report flags deals where the tag has not been touched in 30+ days and deals where the slot-flip log shows an entry that has not yet been reconciled into the tag — both of which trigger the slot-tag hygiene grade.
The activation log. Every battlecard artifact the rep claims to have deployed in the last seven days, tied to a deal ID, a signal note explaining what triggered the deployment, and a timestamp. The log is rep-entered but RevOps validates against email send-logs and CRM activity to flag claimed activations that have no corroborating system trace.
The signal feed. Every CRM-detected event that should have fired an override in the last seven days. The feed reads from five sources: the slot-flip log itself, the buying-committee contact additions for new-executive signals, the calendar plugin for competitor-demo signals, the deal discount field for pricing-escalation signals, and the call-note natural-language tagger for clinical-safety signals. The signal feed plus the activation log produces the reconciliation that drives the activation-cue-compliance grade.
The Two-Minute Per-Deal Protocol
Two minutes is the running budget per deal. The manager and AE walk the four dimensions in order, RevOps validates against the inputs, and the grade is set live in a shared scorecard tab open in the call. The protocol is deliberately tight because forecast calls that run long are forecast calls that get cancelled inside a quarter.
- Slot tag check (20 seconds). Manager reads the slot tag from the report. AE confirms or explains why the tag is what it is. RevOps flags any stale-tag or unreconciled-flip-log conditions. Grade set.
- Activation cue check (40 seconds). Manager asks "what signal fired since last week, which artifact did you deploy?" AE answers. RevOps reads the activation log entry and the matching signal feed entry. If the answer matches the trigger map's expected artifact for the stage-slot-signal combination, green. If the artifact fired late or the default fired when an override was warranted, yellow. If no artifact fired or the wrong slot variant fired, red.
- Override discipline check (30 seconds). Manager reads the slot-flip log entries for the deal in the last seven days. AE confirms reason codes. RevOps flags any signals that fired without a log entry. Grade set.
- Signal-to-outcome check (30 seconds). RevOps reads the activation-log dashboard for the deal — did the activations the rep deployed correlate with stage advancement, or did the deal stall after the artifact fired. Manager grades. AE explains any reds, especially red activations on otherwise green deals (most often a signal that the override fired on noise, not signal).
Two minutes is achievable when the inputs are pre-loaded. It is not achievable when RevOps is pulling reports during the call. The discipline is in the prep, not in the meeting.
The Coaching Escalation Path
The scorecard's authority comes from what happens when a rep keeps scoring red. The escalation path is three rungs.
One red. Coaching in the next 1:1, specific to the dimension. Slot-tag red gets a re-walk of the slot decision framework. Activation cue red gets a re-walk of the trigger map for the stage-slot combination in question. Override discipline red gets a re-walk of the slot-flip log protocol. Signal-to-outcome red gets a paired call-recording review with the manager.
Two reds in two consecutive forecast calls. Structured intervention. The rep is paired with a senior AE for two weeks of joint deal review on every open deal in their pipeline. The slot-tag and activation log entries for their deals get a fresh review by enablement against the rep certification rubric. Manager schedules a re-certification check at the end of the two-week intervention. The intervention is not punitive — it is the team's investment in catching a system-execution gap before it becomes a quota gap two quarters later.
Persistent red after the intervention. Treated as a fit issue, not a knowledge issue. The rep has demonstrated they either cannot or will not run deals through the system the team has built, and the manager escalates with HR. This rung is rare and explicitly so — the scorecard is designed as a system-health tool, not a performance management tool, and most reds are coached out within one to two weeks of the first flag. But persistent failure to use the system is itself a performance signal that managers cannot pretend not to see.
What Flows Out of the Scorecard Into the Quarterly Refresh
The scorecard is not just a weekly grade. Its accumulated grades over a quarter are one of the three inputs into the quarterly refresh meeting that retunes the entire library and the trigger map — the other two inputs are win-loss debrief themes and CSM field intel capture. The refresh reads the scorecard for two patterns specifically. First, dimensions where the team grades consistently red across multiple reps — this is a system gap, not a rep gap, and points to either an artifact that does not actually fit the deal moment it claims to fit, or an activation cue in the trigger map whose signal definition is too vague to detect cleanly. Second, dimensions where a small number of reps grade red while the rest of the team grades green — this is a coaching gap, and feeds the next round of manager coaching cadence investment.
The scorecard also flows into the coaching scorecard the manager themselves is graded against by their director. The two scorecards are related but not identical — the forecast call scorecard grades rep execution per deal, the coaching scorecard grades manager execution per rep. A manager whose reps score consistently red on the forecast scorecard while the manager scores green on the coaching scorecard is a paradox that the director-level review is supposed to catch.
Failure Modes: When the Scorecard Stops Working
Three failure modes recur. The first is RevOps absence — the manager runs the scorecard without RevOps in the room and grades from rep-claimed activations rather than reconciled activations. Inside three weeks, reps learn that claiming an activation is sufficient, and the activation log becomes performative. The cure is that RevOps presence is non-negotiable; if RevOps cannot make the call, the scorecard does not run that week and the manager flags it in the next forecast.
The second failure mode is grade inflation — managers default everything to green to avoid uncomfortable conversations, and reds accumulate only on deals where the AE is already known to be struggling. The cure is the director-level audit: the sales director samples five randomly selected deals from each manager's scorecard once a month and re-grades against the same four dimensions independently. Persistent grade inflation by a manager is itself a manager-performance signal.
The third failure mode is scorecard creep — the team adds a fifth dimension, then a sixth, and the per-deal time blows past two minutes. Inside six weeks, the forecast call is unbearable and the scorecard gets quietly dropped. The cure is that any new dimension must displace an existing one, and the team has to defend in the quarterly refresh why the displacement is worth it. Four is the working maximum and the scorecard's authority depends on keeping it at four.