Guide · British Columbia
Selecting a managed service provider in British Columbia: a structured evaluation process
Choosing an MSP is a multi-year decision that touches every employee and most of your data. This guide sets out a practical selection process for BC organizations, from defining requirements to scoring proposals, reviewing the contract and switching without disruption.
- Published
- 8 min read

On this page
Key takeaways
- Define requirements and must-haves before you meet providers, so the evaluation is driven by your needs rather than the best presentation.
- Use a simple weighted scorecard covering scope, service delivery, security practices, geography, communication and commercial terms.
- BC organizations should ask how a provider handles personal information and where data is stored, and get legal advice on their own obligations.
- Read the agreement for term, renewal, price changes, liability, data ownership and exit assistance before you sign.
- Plan the transition from your current provider carefully; access, documentation and timing matter more than speed.
A six-step selection process
1. Define the requirements
Document users, devices, locations, critical systems and current pain points. Separate must-haves, such as support for your Microsoft 365 tenant or on-site work at a particular site, from nice-to-haves.
2. Build a shortlist
Identify three to five providers whose focus matches your size and industry. Ask peers in similar organizations who they use and what they would change, and check whether each provider genuinely serves your locations.
3. Share a consistent brief
Send each provider the same written brief and invite questions. A provider that asks thoughtful questions about your environment is showing you how they will work.
4. Hold structured meetings
Use the same agenda for each conversation and include the people who will actually work with the provider, not only leadership.
5. Score written proposals
Evaluate proposals against your scorecard rather than gut feeling, then discuss the scores as a group to surface concerns.
6. Check references and the contract
Speak with existing clients of a similar size, ideally ones the provider has onboarded recently, and review the agreement in detail before signing.
A weighted scorecard you can adapt
Assign each category a weight that reflects your priorities, score each provider from one to five, and multiply. The categories matter more than the exact numbers.
Scope fit
Does the proposal cover your users, devices, cloud services and sites explicitly? Are exclusions clear and reasonable for an organization like yours?
Service delivery
How are requests logged, prioritized and escalated? What response targets are committed in writing, and how will you see whether they are met?
Security practices
Which security tasks are included? How does the provider secure its own tools and staff access to your systems? How would it handle a suspected incident?
Geography and on-site work
Can the provider reach each of your sites when physical work is needed, at what cost, and with what lead time?
Communication and planning
Who is your primary contact? How often are reviews held? Is there a roadmap process? Can the provider communicate in the languages your team prefers?
Commercial terms
Total first-year cost, onboarding fees, minimum term, price adjustment clauses, and how out-of-scope work is quoted and approved.
Considerations specific to British Columbia
British Columbia is large, and organizations with more than one location can span very different geographies: an office in the Lower Mainland, a branch in the Fraser Valley, a team in the Okanagan or a site on Vancouver Island reached by ferry. Remote support works the same everywhere, but on-site work does not. When you score geography, be specific about which sites need physical support and how often, and ask each provider how they handle locations outside their regular travel area.
Privacy is another consideration. Private-sector organizations in BC generally fall under the province’s Personal Information Protection Act, and some activities may also involve federal privacy law or sector-specific rules. An MSP cannot take on your legal obligations for you, but it can support privacy-aware operations: controlling who has access to systems, keeping records of administrative actions, and being clear about where data and backups are stored. Ask each provider to describe these practices, and consult a qualified adviser about what your organization specifically needs.
Finally, consider time zones if you have staff or clients outside the province. Support hours are normally stated in Pacific time, so teams in Alberta or further east may start their day before the help desk opens. Raise this during evaluation rather than discovering it after onboarding.
A consistent agenda for provider meetings
Using the same agenda with every provider makes the conversations comparable and keeps them focused on your needs.
- Ask the provider to summarize your environment and priorities back to you, to test whether they read the brief
- Walk through a recent real problem and ask how they would have handled it, step by step
- Ask who would be your day-to-day contact and who handles escalations
- Ask them to describe their onboarding plan and the first ninety days in practical terms
- Discuss how they would handle each of your locations, including any outside their regular travel area
- Ask what they would want to change in your environment first, and why
- Close by confirming what their written proposal will include and when you will receive it
Contract clauses to read carefully
Have someone with commercial or legal experience review the agreement. These are the clauses that most often cause friction later.
- Term and renewal: initial length, automatic renewal and the notice required to end it
- Price adjustments: whether and how fees can change during the term
- Scope changes: how adding or removing users, devices and sites is priced and when it takes effect
- Service levels: response targets, how they are measured and reported, and what happens when they are missed
- Data and credential ownership: confirmation that documentation, configurations and admin accounts belong to you
- Exit assistance: what the provider will do to hand over to you or a new provider, and at what cost
- Liability and insurance: limits of liability and the provider’s own insurance coverage
- Subcontracting: whether any work is performed by third parties, and where
Switching providers without disruption
Secure your own access first
Before giving notice, confirm that your organization holds working administrator credentials for Microsoft 365, domain registration, firewalls and key applications.
Time the notice period
Align the end of the old agreement with the new provider’s onboarding so there is overlap rather than a gap in support.
Request documentation in writing
Ask the outgoing provider for network diagrams, asset lists, licence records and backup details, referencing the exit terms in your agreement.
Remove old tools and access
Once the new provider is in place, make sure the previous provider’s remote access agents, accounts and API connections are removed.
Getting useful references
Ask to speak with clients of a similar size and industry who joined within the last couple of years. Ask them how onboarding went, how problems are communicated, and what they would change about the service, rather than whether they are happy overall.
Frequently asked questions
Do we need a formal RFP to select an MSP?
Most small and mid-sized organizations do not need a formal procurement process. A written brief, a consistent meeting agenda and a simple scorecard give you most of the benefit with far less effort. Public bodies and some nonprofits may have procurement rules they must follow.
How long does it take to select and onboard a new MSP?
It depends on your size, complexity and notice period with your current provider. Selection can take a few weeks; onboarding involves discovery, access transfer and tool deployment, and the provider should give you a timeline in their proposal.
Should the cheapest proposal win?
Only if it covers the same scope with comparable service and security practices. Compare total first-year cost including onboarding and expected out-of-scope work, and weigh it against the other categories on your scorecard.
Can an MSP make us compliant with BC privacy law?
No provider can make your organization compliant on its own; compliance depends on your policies, practices and legal obligations. A provider can support privacy-aware operations through access control, logging and clear data-location practices. Seek advice from a qualified privacy or legal professional.
Related services
Products and packages
Service areas
Add us to your shortlist
Send us your brief or book a consultation. We will ask questions about your environment and respond with a written scope you can score alongside other proposals.
