Have you ever walked out of a quarterly review with your IT provider, looked at the slide deck, and realized you could not prove a single thing it claimed? That is the question we hear most often from owners and operations leaders who have sat through years of these meetings. The charts looked healthy, the ticket counts went down, and yet nobody could tell them whether last quarter's backups would actually restore or who at the provider still had administrator access to their network.
An MSP quarterly business review should include evidence, not just metrics: proof of who at the provider can reach your systems, a documented restore test, a patch and vulnerability exception list, an asset lifecycle view, an incident and alert summary, a check on documentation and credential custody, and a roadmap tied to budget. If your provider cannot produce those artifacts, the meeting is a presentation, not a review.
Why most MSP quarterly business review advice misses the point
Most guidance on the MSP quarterly business review is written for providers, and it shows. Vendor playbooks treat the QBR as a retention and upsell tool: review last quarter, present a roadmap, reinforce the relationship. A typical provider-side guide frames the meeting around reviewing the past quarter and pitching a roadmap for the next one. Nothing wrong with that, but it measures how busy the provider was, not how exposed you are.
Here is the take that changes how you run the meeting: ticket volume, response times, and uptime percentages are the least useful numbers in a QBR. They tell you about service quality, which you already feel day to day. What you cannot feel is whether the controls you are paying for actually work. A provider can hit every service level target while a former technician's account still has domain admin rights and your backup job has silently been skipping a file share for two months.
We cover the service-level side in detail in our guide to holding your MSP accountable with SLA metrics and contract red flags. This article is about the other half of the meeting, the half that most SMBs never ask for: the evidence package.
Why does the QBR matter more than it used to?
Because your provider is now one of your largest risk surfaces, and regulators and attackers both know it. Verizon's 2025 Data Breach Investigations Report found that third-party involvement in breaches doubled to 30%. An MSP is the most privileged third party most small businesses have, with remote access to every endpoint and server it manages.
Government guidance has been specific about what customers should verify. The joint advisory from CISA, NSA, FBI, and allied agencies, Protecting Against Cyber Threats to Managed Service Providers and their Customers, tells customers to require visibility into the provider's "presence, activities, and connections" on customer networks, to ensure MSP accounts are "properly monitored and audited," and to require MFA on all MSP accounts used to access customer environments. That is a list of things you can only confirm with evidence, and the QBR is the natural place to collect it.
For some businesses this is not optional. The FTC's Safeguards Rule, which according to the FTC's compliance guide covers non-bank financial businesses such as mortgage brokers, tax preparation firms, and collection agencies, requires covered companies to oversee service providers by "periodically assessing your service providers based on the risk they present and the continued adequacy of their safeguards," according to 16 CFR 314.4. The same section requires a written report to leadership at least annually that addresses service provider arrangements. Four documented QBRs a year make that report straightforward. Four slide decks with no evidence do not.
What should be in an MSP quarterly business review?
A useful QBR covers seven evidence areas, each backed by an artifact you can keep and compare against the next quarter. The table below is the vetting checklist we recommend bringing into the room. Use it with your current provider, and ask any prospective provider to show you a redacted sample QBR report that covers the same ground before you sign.
| QBR area | Evidence to ask for | Red flag |
|---|---|---|
| Provider access review | A list of every MSP account and tool with access to your environment, MFA status for each, and accounts disabled this quarter | "We'd have to pull that" or a list that never changes despite staff turnover |
| Backup and restore testing | Date, system, and result of at least one actual restore test, plus measured recovery time | Only job success rates, with no restore ever performed |
| Patch and vulnerability exposure | Patch compliance by device group and a written exception list with owners and dates | A single percentage with no list of what is unpatched or why |
| Asset and lifecycle status | Device inventory with warranty and end-of-support dates for the next 12 months | Unsupported systems discovered only when something breaks |
| Incidents and alerts | Summary of security alerts, what was investigated, and notification timing against your contract | "No incidents" with no alert data behind it |
| Documentation and credential custody | Confirmation that network diagrams, admin credentials, and runbooks are current and accessible to you | Documentation that lives only in the provider's tools or one technician's head |
| Roadmap and budget | Named projects with dates, cost ranges, and the business reason for each | The same "continue monitoring" language every quarter |
Provider access review
This is the item SMBs skip most often and the one that matters most. Every RMM agent, remote access tool, and admin account the provider uses is a door into your business. The CISA advisory's first tactical recommendation is to "identify and disable accounts that are no longer in use." Ask for the list, ask who left the provider's team this quarter, and confirm their access is gone. The same discipline applies to non-human identities; our AI Lab piece on ghost agents and the AI offboarding gap explains why service accounts and automation identities are now the ones most often forgotten.
Backup and restore testing
A green backup dashboard tells you a job ran. It does not tell you the data comes back. CISA's #StopRansomware Guide is direct about this: maintain offline, encrypted backups and "regularly test the availability and integrity of backups in a disaster recovery scenario." Your QBR should show at least one real restore per quarter, rotated across critical systems, with how long it took. If you want to go further, our guide to disaster recovery testing strategies for business leaders covers how to scale tests from a single file to a full failover.
Patch exposure and lifecycle
A 96% patch compliance figure sounds great until you learn the remaining 4% includes the accounting server. Ask for the exception list, and ask whether anything on it appears in CISA's Known Exploited Vulnerabilities Catalog, which tracks flaws attackers are actively using. Pair that with a 12-month lifecycle view so hardware and operating system replacements show up in the budget before they show up as an emergency.
How should you use the QBR to vet an MSP?
Use it as a test of whether the provider can produce evidence on demand. Send the checklist two weeks before the meeting and ask for the artifacts to be included in the pre-read. A provider with mature operations will already have most of this in its reporting; one without it will either scramble or push back. Either response tells you something about how they run your environment the other 89 days of the quarter.
When you are evaluating a new provider, the QBR is one of the best due diligence tools available, because it shows you what ongoing oversight will look like rather than what the sales process promises. Ask for a redacted sample report from a client of similar size. Ask who runs the meeting. If the answer is an account manager with no technical lead in the room, the meeting will default to the relationship conversation and the evidence will never get examined.
Watch for a few patterns over two or three quarters, because a single thin meeting can be an off quarter while a trend is a signal:
- Artifacts arrive late, are verbal only, or are different in format every time, which makes quarter-over-quarter comparison impossible
- The same exceptions and open risks reappear with no remediation date or owner
- Restore tests are always "scheduled for next quarter"
- The provider access list never changes, even though you know their staff has turned over
For the scoring side of this, the MSP reliability scorecard for SMBs pairs well with the evidence checklist above. The scorecard tells you whether service is reliable; the evidence tells you whether your risk is controlled.
Who should attend from your side?
At minimum, the person who owns the business risk and the person who owns the budget, which in many SMBs is the same owner or COO. If you are in a regulated industry, include whoever handles compliance or your cyber insurance renewal. The evidence package feeds directly into insurer questionnaires, and our article on providers that help SMBs prove controls are real explains why underwriters increasingly want artifacts rather than yes/no answers.
Keep the evidence. A shared folder with each quarter's artifacts becomes your audit trail, your insurance evidence, and, if you ever change providers, your proof of what the environment looked like and what was handed over. If you need a simpler starting point for the conversation, our list of questions to ask your IT provider every quarter is a good warm-up before you move to the full checklist.
How Securafy approaches the QBR
We build the QBR pre-read around the same evidence areas in the table above, and we bring technical staff who can answer for each one: the current list of Securafy accounts and tools with access to your environment, the quarter's restore test results, the patch exception list with owners and target dates, and the lifecycle forecast that feeds your budget. The point is that you leave with artifacts you can file, compare next quarter, and hand to an auditor or underwriter without asking us to rebuild them.
Where clients have internal IT staff, we split the evidence by ownership so each side signs off on its own controls. That shared view is what keeps the QBR from becoming a status report and turns it into a working risk review.
Where To Go From Here
Take the checklist into your next review and ask for the artifacts in advance. Whether your provider delivers them or not, you will know far more about your actual risk than any uptime chart could tell you.
If you want to see how evidence-based QBRs fit into a full managed service, review Securafy's managed IT and cybersecurity plans.
If you would rather talk through your specific environment first, book a strategy call with Securafy and we will walk through your current provider reporting, the gaps in your evidence, and what a useful quarterly review should look like for your business.
By Rodney Hall
Join The Conversation
Have a question or perspective on this topic? Add it below.