Key takeaway
A customer success team can move quickly for weeks before one missing QBR packet turns a routine health score request into an investigation. Rework rises, health score freshness becomes hard to compare, and the line between an approved change and a helpful shortcut vanishes. Build the health score rule around exceptions, because that is where incomplete onboarding turns into cost. At Customer Success Managers, first decide whether the request creates a new health score or changes an open one. The CSM decision on health score should be dated November 2 and linked to the QBR packet.
In this article
The first weak link in health score
A customer success team can move quickly for weeks before one missing QBR packet turns a routine health score request into an investigation. Rework rises, health score freshness becomes hard to compare, and the line between an approved change and a helpful shortcut vanishes. Build the health score rule around exceptions, because that is where incomplete onboarding turns into cost. At Customer Success Managers, first decide whether the request creates a new health score or changes an open one. The CSM decision on health score should be dated November 2 and linked to the QBR packet.
Familiarity makes health score feel safer than it is: the same support lead asks again, and the check that protected the first request quietly disappears. The result is overpromised feature, followed by a question the record cannot answer without help from whoever happened to be online. The control is a readable chain: request, escalation record, named owner, decision, and the confirmed value in the onboarding tracker. If support lead cannot state the intended outcome, the health score request is not ready. For the November 2 sample, Customer Success Managers should include one health score case that crossed owners.
When health score work passes through three hands, the last person often receives a summary that omits the exception the first person already knew about. Rework rises, renewal risk lead time becomes hard to compare, and the line between an approved change and a helpful shortcut vanishes. Give every health score request an owner who can pause it when the evidence is not good enough. The operator should name the exact the support desk field that will change, not just the message that asked for it. The November 2 health score close should name the destination field, approver, and renewal risk lead time check.
A source map for health score
The source of truth may be a system, a signed document, or an approved message, but the team should pick one and stay with it. Keep the original escalation record and the corrected version together, with the reason and the approver. The exception note should say which value was used, which was rejected, and why. For confidential data, note the approved access path rather than copying content. At Customer Success Managers, the November 2 health score review should name the backup owner and coverage window.
Start the map by naming the the support desk field the health score action is supposed to change. When the renewal risk memo is absent, say absent; absent, unavailable, and confirmed negative are different facts. When the support desk and the renewal risk memo disagree, stop dependent work and record both values with their observation times. When a correction arrives, keep the original request and the new value in one history. The November 2 health score exception log should show the reason code, owner, and release decision.
A complete health score evidence set shows request, usage report, owner decision, action, and the resulting the QBR template library value. For sensitive usage report content, store it in the approved location and record only the reference in the health score case. When the QBR template library and the usage report disagree, stop dependent work and record both values with their observation times. Record the source identifier and extraction time for values from the QBR template library. For the November 2 audit walkthrough, Customer Success Managers should open the usage report from the case.
Running health score across a normal day
A handoff note names the open health score item, the next action, the owner, and the evidence still missing. When the request is unclear, ask one focused question and write the answer into the case. Track waiting time separately from working time; they point to different fixes. The morning check should confirm that the health score queue and the QBR template library show the same open items. At Customer Success Managers, keep the usage report attached to the health score case and record the health score freshness observation date.
A handoff note names the open health score item, the next action, the owner, and the evidence still missing. When the renewal forecast is unavailable, record the outage time and avoid promises that depend on the missing view. Use a short standard reply when returning an incomplete health score request. If the queue grows faster than it clears, report arrivals and completions, not only backlog. The November 2 evidence trail for health score should show the source version and the customer sponsor decision.
Before touching the CRM, the operator reads the request, opens the health score note, and confirms both describe the same change. When CSM changes the outcome mid-case, record the new instruction and recheck the health score note. Track waiting time separately from working time; they point to different fixes. The handoff note should be readable by someone who has not seen the case. For this November 2 pass, Customer Success Managers should record which health score exception was paused and who released it.
When health score does not fit the rule
If the destination value cannot be verified, the health score item stays open even if the client has been told it is done. A hidden exception teaches the wrong lesson: the queue looks clean, so the process looks healthy. Define a small set of codes: missing evidence, conflicting evidence, authority gap, system outage, client change. If the same exception is granted three times, open a process review. The health score review at Customer Success Managers should state whether the onboarding plan was current on November 2.
If the destination value cannot be verified, the health score item stays open even if the client has been told it is done. A queue with no exceptions usually has weak recording, not a perfect process. Set a review date so a temporary exception does not become the permanent process. A waiver without an expiry date is a permanent change nobody approved. On November 2, Customer Success Managers should compare the health score queue count with the QBR completion denominator.
A missing QBR packet, a conflicting the health dashboard value, and an unclear approval are different exceptions and need different codes. An exception that bypasses the health dashboard creates a second record that must be reconciled by hand. Review exception codes monthly; a rising count in one code points to a specific fix. When the exception is approved, restate the approved scope in the case. The November 2 health score note should distinguish a missing QBR packet from a confirmed negative.
A close that holds up
The final check is a comparison: request, health score note, approval, and the value now visible in the CRM. If the destination cannot be verified, the honest status is pending verification, not closed. Sample closes weekly for destination accuracy, not only speed. Do not close on a promise that the health score note will arrive tomorrow. At Customer Success Managers, record the November 2 health score correction and link it to the original source.
The final check is a comparison: request, QBR packet, approval, and the value now visible in the health dashboard. If the health score value is correct but the QBR packet is missing, the case is complete in fact and incomplete in evidence; record the difference. High-risk health score changes need a verifier other than the preparer. A close note that names the QBR packet is stronger than one that says the source was checked. The customer sponsor decision on health score should be dated November 2 and linked to the QBR packet.
A reopened health score case links to the original close so the history shows both decisions. When the same health score item closes twice, the second close references the first and explains the reopening. If a case closes with an exception, link the exception note in the close entry. If the destination value will change later, the case stays open until the change is visible. For the November 2 sample, Customer Success Managers should include one health score case that crossed owners.
The monthly health score check
Pick five cases, rebuild each from the record, and note where the reviewer needed outside knowledge. If the reviewer cannot access the health dashboard, the review measures access rather than quality. Keep the review to one page: sample, method, findings, decision, owner, next check. Keep the sampled case keys so the test can be repeated. The November 2 health score close should name the destination field, approver, and health score freshness check.
Compare the sample with escalation age for the same period; a gap is a definition problem. If the reviewer cannot access the onboarding tracker, the review measures access rather than quality. Close by confirming the next sample date is on the calendar. Keep the sampled case keys so the test can be repeated. At Customer Success Managers, the November 2 health score review should name the backup owner and coverage window.
Compare the sample with renewal risk lead time for the same period; a gap is a definition problem. A finding repeated across owners points to the the support desk setup or the health score definition, not to effort. Record the selection method, even if simple, so the sample can be defended. Five cases can find a broken step; they cannot rank owners. The November 2 health score exception log should show the reason code, owner, and release decision.
Common questions
Who owns the decision?
The named account owner keeps the decision and exceptions.
What evidence is kept?
Keep source, observation time, reviewer, correction, and next action.
Sources and context
Sources provide public context. Their inclusion does not imply endorsement of this site or a guaranteed business result.
Apply this to your customer journey
Define a support role with visible boundaries.
Bring one recurring workflow. We will help map the approved inputs, review owner, evidence, and escalation points.
Book a free consultation