Design an exception lane for health score that stops safely

The operational risk around health score

The risk around health score is not that staff forget a task; it is that the record can look complete even when the QBR packet was never checked against the health dashboard. The cost shows up later as a reopened case, an unexplained health score freshness change, or a correction that takes longer than the original task. A useful rule is simple: no health score closes until the QBR packet is attached and the destination record shows the approved change. The control should also cover the quiet case: an item that sits open because nobody knows who owns the next step. The October 28 control note for Customer Success Managers should name the health score source, the owner, and the next review time.

In customer success, health score often begins as a small favor from support lead, which makes it easy to skip the evidence that would let someone else reconstruct the decision. If the destination record is wrong, the team may send a correct-looking update while support lead still sees the old value in the onboarding tracker. The control should make the health score path readable from the request, the escalation record, the named owner, the decision, and the confirmation in the onboarding tracker. The risk is highest when the onboarding tracker looks current but the escalation record behind it was never opened. At Customer Success Managers, keep the escalation record attached to the health score case and record the escalation age observation date.

Evidence map for health score

The evidence map should show the minimum needed for a reviewer to answer who asked, what source was used, who approved, and what changed. The reviewer should be able to open the escalation record from the case without searching a personal drive or asking for a screenshot. If the escalation record is incomplete, the safest next step may be to pause health score rather than fill the gap with a plausible assumption. If the escalation record contains personal or confidential data, use the approved access path and record only the reference in the queue. The October 28 evidence trail for health score should show the source version and the account executive decision.

The evidence map should show the minimum needed for a reviewer to answer who asked, what source was used, who approved, and what changed. Attach the renewal risk memo to the case, label its version or date, and record the field in the support desk that it supports. Use a separate reason code for conflicting evidence so the pattern can be reviewed without reading every message. The evidence map should show which fields are required, which are conditional, and which may be marked unavailable. For this October 28 pass, Customer Success Managers should record which health score exception was paused and who released it.

Record the usage report and the time it was observed, because a later screenshot cannot prove what the record said when the first action was taken. For recurring health score work, use the same usage report type and the same field labels so a sample can be compared across owners. Keep an exception note that explains which value was used, which was rejected, and why; a later reviewer should not have to infer the choice from the final number. The team should test one health score case each week by reconstructing it from the evidence map alone. The health score review at Customer Success Managers should state whether the usage report was current on October 28.

Decision rights for health score

For customer success work, the safest split is preparation by the operator and judgment by the accountable owner, with both actions visible in the support desk. The boundary should be visible to the requester as well, so a request for health score does not become a promise the operator cannot keep. For repetitive health score work, use a standing approval only when its scope, limits, and review date are written down. For high-risk health score work, require a second reviewer who is not the person who prepared the packet. On October 28, Customer Success Managers should compare the health score queue count with the reopen rate denominator.

A handoff transfers ownership only when the receiving role acknowledges the health score and the next action; an unread message is not a handoff. If the operator discovers that the request falls outside the approved scope, pause the work and route the scope question before touching the QBR template library. The approval record should point to the usage report that was reviewed, not only to the request that started the work. The approval record should not be a forwarded thread with ten replies; summarize the decision and link the evidence. The October 28 health score note should distinguish a missing usage report from a confirmed negative.

Daily workflow for health score

A short morning pass should identify missing usage report, stale approvals, and items that crossed a time zone without acknowledgment. If the operator touches the QBR template library, record the before-and-after value and the approval that allowed the change. The end-of-day review should show what was completed, what is blocked, who owns the next step, and which usage report is still missing. Use a queue view that shows owner, age, next action, and missing evidence in one screen. At Customer Success Managers, record the October 28 health score correction and link it to the original source.

The daily health score routine should begin with a queue count by owner and age, not with the easiest request in the inbox. Use the escalation age field to flag a possible exception, but do not let the flag replace the evidence review. Use the final queue count to test the day’s escalation age; a lower count achieved by hiding open items is not progress. Use the same health score status values across owners so the daily count means the same thing to everyone. The customer sponsor decision on health score should be dated October 28 and linked to the onboarding plan.

Open the health score queue in the CRM and mark every item with the current owner, the next action, and the time it is due. At mid-day, check the health score items that have no next action; those are the ones most likely to age silently. Record any correction made during the day and link it to the original health score record. A case with no next action should be treated as an exception even if its status is marked in progress. For the October 28 sample, Customer Success Managers should include one health score case that crossed owners.

Exception handling for health score

Use separate reason codes for missing onboarding plan, conflicting source, wrong health score, expired approval, unavailable CSM, and an outage in the renewal forecast. Keep the escalation in the health score case so the response is visible to the next reviewer. A stop is not a failure of service; it is the control working before the error reaches CSM. Reason codes should be short enough to use at the queue and specific enough to route the case to the right owner. The October 28 health score close should name the destination field, the approver, and the renewal risk lead time check.

Do not let an exception close because the requester stopped asking; keep the case open until the evidence or the decision is resolved. Keep the escalation in the health score case so the response is visible to the next reviewer. When the request conflicts with policy or the approved scope, the operator should route it rather than negotiate a workaround in the queue. A stop-work decision should be visible to the requester so they know why the health score work is paused. At Customer Success Managers, the October 28 health score review should name the backup owner and the coverage window.

Use separate reason codes for missing QBR packet, conflicting source, wrong health score, expired approval, unavailable account executive, and an outage in the health dashboard. Send the exception to the named owner with the QBR packet attached and a specific question, not a general request to review. Record the stop time, the reason, and the release decision so the delay can be reviewed without guessing. Keep a separate escalation log for items that required account executive, so response time can be reviewed. The October 28 health score exception log should show the reason code, owner, and release decision.

Close and verify health score

The close condition should name the field, the expected value, the approver, and the time of the final check. Use a second reviewer for high-risk health score closures, and record the review even when the result is accepted. If the update fails or the requester disputes the result, reopen the health score case and link the new evidence to the original record. If the final value differs from the approved value, record the variance and the person who accepted it. For the October 28 audit walkthrough, Customer Success Managers should be able to open the health score note from the case.

Use the same close definition for routine and exception cases so the onboarding milestone completion does not improve by redefining completion. When the QBR packet is sensitive, record the approved reference and the access location rather than copying the content into the queue. Close the reopened case only after the destination record and the requester confirmation agree. If the destination is a downstream team, keep the health score open until that team acknowledges receipt. The October 28 health score recovery test should record the restore point and the onboarding milestone completion result.

Review cadence for health score

Include a case where the owner said no or asked for more evidence; those decisions show whether the boundary is working. Track health score freshness with a clear denominator and a review owner; a count without context is not a control. If the gap is caused by an unavailable CSM, add a backup decision path rather than letting the health score queue wait indefinitely. Review at least one case handled by a backup owner and one that crossed a time zone. For the October 28 review at Customer Success Managers, log the health score check with the QBR packet and the health score freshness result.

A useful sample includes a routine close, a reopened case, a missing escalation record, and a handoff that crossed a shift. Review the exception mix each month; a rising missing-evidence count may be an intake problem rather than an operator problem. When the same gap appears twice, change the intake field, the approval rule, or the onboarding tracker permission instead of repeating the coaching. When a measure improves, check whether the definition, the sample, or the queue mix changed. The October 28 control note for Customer Success Managers should name the health score source, the owner, and the next review time.