I’ll send the spreadsheet.
May add detail, but not authority, scope, or reader fit.
PRACTICAL GUIDE / MSP REPORTING TEAMS
Keep the QBR strategic. Make the material claim answerable.
A client does not need a new portal to question one number in a report. They need a clear reviewed explanation of the claim that affects the decision in front of them.
Use the no-data starter kitTHE REPORT PROBLEM
A QBR is not a data dump.
A good quarterly business review helps a client decide what matters next. Concise does not need to mean unanswerable: when a material SLA, ticket, patch, backup, or asset-risk claim is challenged, an MSP needs a support path as deliberate as the claim itself.
Log into the portal.
May offer broad access but lose the specific QBR context.
Trust the report.
Keeps the meeting concise but leaves a reasonable question unanswered.
Here is the approved support.
Preserves the report and makes source, scope, reader, and review visible.
PUBLICATION DECISION
The five fields behind an answerable claim.
If a team cannot state these fields, the missing ingredient is usually not a link. The claim may be vague, source may not be ready, scope may be too broad, or no one may have made the delivery decision.
Claim
What exact sentence, number, or chart result can the reader reasonably question?
“SLA attainment was 97.4% in Q2.”Source
Which reviewed structured source or mapping gives that claim meaning?
A reviewed ticket export with client, period, severity, and SLA rules recorded.Scope
What is the smallest approved support set that answers this reader’s question?
Included rows, exclusions, denominator, period, and calculation note—not every ticket ever created.Reader
Who is the evidence intended for?
A named client executive or a defined recipient condition.Review
Who approved the claim, source context, evidence scope, and delivery condition?
The accountable vCIO, account manager, or designated reviewer.WORKED FIXTURE-DATA EXAMPLE
An SLA percentage needs more than a chart screenshot.
The sample uses fixtures, not a customer deployment. The exact service agreement, source configuration, and client context determine an MSP’s actual reporting rules.
WHERE TO START
Choose the claims that change a client decision.
These are question patterns, not universal calculation definitions. The service agreement, client context, and system-of-record rules still determine what a metric means.
SLA attainment
Which tickets count, what did you exclude, and what period and time zone apply?
Tickets resolved
Does this mean tickets closed, requests completed, or incidents resolved—and for which client entities?
Patch compliance
Compliant with which policy and version? Which assets are offline, unsupported, or excepted?
Backup verification
Does “verified” mean job success, a restore test, or another approved check?
Assets at risk
Which lifecycle, warranty, risk, or exception rule produced the list?
COMMON QUESTIONS
Answer the question without widening the data boundary.
Does every QBR metric need a separate evidence view?
No. Begin with material claims that are regularly challenged or drive a client decision. The aim is not to turn every report into a portal; it is to make a selected claim answerable when it matters.
Can a PDF chart alone be treated as the evidence source?
Not reliably. A defensible path needs a reviewed structured source or documented mapping that explains the result, scope, calculation, and approval behind the chart.
Should a client receive the complete operational export after challenging one metric?
Only if the broader release is appropriate for the reader and question. A material QBR question may need a narrower approved support set, while an authorized audit may justify more detail.
What does RipoDoc replace?
RipoDoc sits beside systems that produce reports. It does not replace a PSA, RMM, BI platform, general client portal, or the MSP’s review responsibility.
NO-DATA NEXT STEP
Start with a claim you can name.
Use the starter kit to decide whether one real report claim has a clear source, scope, reader, reviewer, and delivery boundary. Do not paste customer data, credentials, report files, PHI/ePHI, or sensitive operational details into a public form.