MSP Client Health Score Template: 8 Signals, Weights, and What Each Band Triggers

A client health score is one number per managed client that tells the vCIO who needs attention this month, built from signals the MSP already collects.

Every MSP has a gut feel version of this. The service manager knows which client keeps calling about the same printer. The account lead knows which owner stopped answering email. The billing person knows who pays on day 58. Those three people rarely sit in the same meeting, so the client that is quietly leaving looks fine to each of them separately.

This template puts those signals in one row. It covers eight signals, a 100-point weighting, three bands, and what each band triggers. Copy it, change the weights, and run it once a month.

The eight signals

Pick signals you can pull without a research project. If a signal takes an afternoon to gather, it will be skipped by month three.

The weights add up to 100. They lean on the signals a client feels every week (service and sentiment) and the signals the vCIO controls (engagement, standards, roadmap). Payment and renewal get less weight because they tend to move last. By the time a client pays late, the decision to leave is often already made.

Score each signal green, yellow, or red

Each signal earns its full weight when green, half when yellow, and zero when red. Three levels is enough. A 1 to 10 scale per signal just starts arguments about whether something is a 6 or a 7.

Use the client's own baseline for ticket volume. A 200-seat dental group and a 12-person law firm will never share a normal, and comparing them to each other just tells you which one has more people.

Notice the red condition on tickets includes "near zero." A client that stops opening tickets has not always run out of problems. Sometimes they hired an internal IT person, found a cheaper shop, or gave up asking. Silence from a client that used to be loud deserves a phone call.

For sentiment, use what you already run. If you survey with SimpleSAT, the SimpleSAT integration post shows how those CSAT and NPS responses land on the mapped client in Scopable. If you do not survey at all, score this from escalations and ticket notes for now, and say so in the row.

Turn the total into a band

Add the points. Then sort:

Add one override: certain events put a client in At risk regardless of the total. The decision maker you work with leaves. The client sends an RFP or asks for a copy of the contract. An executive escalation lands on the owner's desk. A strong score with one of those events is a strong score that is about to change.

The thresholds are a starting point. After two or three months, look at which clients you were actually worried about and check whether the bands caught them. If not, move the weights, write the new version and date in the template, and keep going.

Bring the client baseline into the QBR

Keep assessments, compliance posture, agreements, and roadmap items on one client record, then build the review from it. Free plan, no credit card.

Start for free

What each band triggers

A score with no action attached is a dashboard nobody opens. Each band needs an owner, a deadline, and a message.

The Watch call is the one MSPs skip, and it is the cheapest one to make. "We noticed your team opened twice the usual tickets about the line-of-business app this month. Here is what we found and what we changed." That call takes ten minutes and tells the client somebody is paying attention.

For At risk, the QBR churn signal post covers the recovery conversation when the client has stopped showing up. Bring the owner of the MSP in early. A client deciding whether to leave wants to hear from the person who can change things.

A worked example

Here is a made-up 40-seat accounting firm, scored in the week before its fall QBR:

The client looks happy on the surface. Surveys are good and the managing partner shows up. The score still lands in Watch because the repeat print error and the open renewal sit underneath.

The fix is cheap: get an engineer on the root cause of the print error this week, and put the renewal on the QBR agenda instead of letting it surprise everyone in month eleven. The MSP renewal calendar template helps set that renewal date early enough to matter.

When the score lies

A score is a sorting tool. It will be wrong in predictable ways, so plan for them:

• One signal swamps the rest. A single bad week (a ransomware scare, an office move) can push ticket volume red and drag a healthy client into Watch. Look at the row before you call anyone.
• New clients have no baseline. The first 90 days after onboarding are noisy. Score new clients but mark them as onboarding, and do not compare their ticket trend until they have a few months of history.
• Seasonal businesses spike on schedule. Accountants in tax season and schools in August will look sick every year. Compare against the same period last year when you have it.
• Quiet is ambiguous. Low tickets plus missed QBRs plus no roadmap is a client drifting away. Low tickets plus good surveys and an approved project is a client whose environment is in good shape. The total cannot tell them apart. The row can.
• The weights reflect your MSP. A security-heavy shop might weight standards drift higher. A shop that sells a lot of projects might weight roadmap momentum higher. Change it on purpose and write down why.

The 10-minute monthly review

Run it in the same meeting every month, with the service manager, the vCIO or account leads, and whoever owns billing:

1. Refresh the eight signals for every client. This should be mostly copy and paste from systems you already have.
2. Sort by band, then by score within the band.
3. Review only the clients that changed bands since last month and every At risk client.
4. Assign each one an owner, a date, and a next action from the band table.
5. Check last month's actions. Did the call happen? Did the score move?

Ten minutes works when the data prep happens before the meeting. If the meeting turns into gathering numbers, fix the prep. The QBR prep system post covers building a baseline that refreshes on its own schedule.

Copy the client health score row

Paste this into the client record or a shared sheet, one block per client:

Client:
Seats:
Score date:
Template version:

1. Ticket volume trend (15):    Green / Yellow / Red    Points:
2. Repeat issues (10):          Green / Yellow / Red    Points:
3. Client sentiment (15):       Green / Yellow / Red    Points:
4. QBR engagement (15):         Green / Yellow / Red    Points:
5. Standards drift (15):        Green / Yellow / Red    Points:
6. Roadmap momentum (10):       Green / Yellow / Red    Points:
7. Renewal position (10):       Green / Yellow / Red    Points:
8. Payment behavior (10):       Green / Yellow / Red    Points:

Total:
Override event (if any):
Band: Healthy / Watch / At risk
Change since last month:
Owner:
Next action and date:
Notes (what the total does not show):

The notes line matters more than it looks. When a client leaves anyway, that is where the postmortem will find out whether the signal was there.

Where Scopable fits

The health score tells you which client needs attention. The QBR and the roadmap are where you act on it.

Scopable's vCIO and QBR workflow keeps the client baseline on one record: assessments, compliance posture, agreements, opportunities, and roadmap items. QBR sections can draw on that data, so a Watch client's QBR starts from what changed and the decisions the client still has to make, instead of a blank deck. The score and the band call stay with your team. Scopable carries the context and the follow-up work, including the roadmap items and quotes that come out of the meeting.

If you are pricing the advisory time this takes, how to price vCIO services covers that math. For the broader account management practice, see MSP vCIO account management.