Before hiring an MSP, ask who owns each technology responsibility, how incidents are handled, what documentation you receive, and how the provider plans for outages, security, vendors, and future investments. For commercial properties, the answers should protect building operations, reduce tenant disruption, and give your team clear accountability.
In This Article
- Does the provider understand the technology in our building?
- Who takes ownership when several vendors are involved?
- How will the MSP reduce cybersecurity risk without disrupting operations?
- What happens during an outage, and how will we recover?
- Will the MSP help us plan technology spending instead of reacting to failures?
- What should we confirm before signing an MSP agreement?
- Frequently Asked Questions
Does the provider understand the technology in our building?
A property can look well maintained while its technology infrastructure tells a different story. Telecom rooms may contain unlabeled switches, old carrier equipment, camera recorders, access-control panels, building-system gateways, and cabling installed during prior tenant improvements.
Ask how the MSP begins discovery. A credible answer should cover network equipment, MDF and IDF rooms, carrier demarcation points, riser pathways, wireless equipment, cameras, access control, remote access, and the systems that depend on them.
The purpose is not to turn every discovered asset into an immediate project. It is to establish what exists, who relies on it, where the risks are, and which issues require attention first.
For a multi-tenant building, ask the provider to separate landlord-owned systems from tenant-owned systems. The property may own common-area Wi-Fi, the riser, surveillance, access control, and core network equipment, while tenants own their applications, workstations, and internal networks.
Shared systems need clear boundaries. Without them, a tenant outage can become a long series of calls between the property manager, carrier, cabling contractor, security vendor, and IT provider.
Ask what documentation you will receive after discovery and how it will stay current. Network diagrams, equipment inventories, carrier records, access ownership, vendor contacts, and escalation details should be usable when a problem occurs, not buried in an old email thread.
Key figure: 1 documented owner should be assigned to every shared building system.
Takeaway: Choose an MSP that starts with the actual condition of the building rather than a generic technology checklist.
Who takes ownership when several vendors are involved?
Commercial property technology problems rarely stay within one vendor's scope. Slow access control may involve a controller, switch, internet circuit, cabling issue, or vendor configuration. Each party may see only its own piece of the problem.
Ask, "When the carrier, access-control vendor, camera vendor, cabling contractor, and building engineer are involved, who coordinates the investigation?" The provider should explain who gathers evidence, communicates updates, tracks next steps, and confirms resolution.
Your property team should not have to become the unpaid dispatcher for every vendor. A capable technology partner can organize the technical facts, identify dependencies, and keep the responsible parties focused on the same outcome.
Ask what information the MSP collects before escalating an issue. Useful details include affected areas, device names, circuit identifiers, timestamps, recent work, error messages, and the operational impact on tenants or building staff.
That preparation matters because it prevents the familiar cycle of one vendor referring the issue to another. A vague report such as "the internet is down" gives every party room to avoid ownership.
Ashlee, a commercial real estate client, described the value of accountable follow-through this way: "GDS Technology answers every question we throw at them and actually follows through to solve it. You get real answers, not deflection, and the problem gets fixed, not just talked about. They make it easy to bring them anything and walk away with a result."
Ask whether support updates identify the next action, responsible party, expected update, and closure criteria. A closed ticket is not a result if a recurring problem remains unexplained or nobody owns the permanent fix.
Takeaway: Your MSP should coordinate the work across vendors instead of simply forwarding requests.
How will the MSP reduce cybersecurity risk without disrupting operations?
Cybersecurity in a commercial property begins with knowing what is connected. Cameras, access-control systems, intercoms, networked printers, Wi-Fi, building-management gateways, and remote vendor connections all create operational dependencies that need defined ownership.
Ask how the provider identifies devices, user accounts, remote access methods, software updates, backup needs, and network boundaries. The answer should focus on reducing avoidable exposure and improving visibility, not on promising that any environment can be completely risk-free.
Ask how suspicious activity is handled. Who is notified first, what information is preserved, how are affected systems isolated, and how does the provider avoid unnecessary disruption to building operations?
The provider should be able to explain that process in plain language before an incident happens. If the answer depends entirely on technical jargon, it may not give property leadership the clarity needed during an urgent situation.
Property teams that maintain tenant records, employee records, or electronic payment processes should also ask which obligations apply to their own operations. Requirements depend on contracts, data handled, systems in scope, and the organization's role in protecting that information.
A serious MSP will identify where discovery is needed rather than making a blanket compliance promise. Review cybersecurity services for commercial operations and ask how the proposed controls connect to your specific systems and responsibilities.
Takeaway: The strongest security conversation connects technology controls to operational risk, ownership, and a clear response process.
What happens during an outage, and how will we recover?
Utility disruptions, carrier failures, equipment problems, and human error can interrupt building operations with little notice. The question is not whether every interruption can be prevented. The question is whether the team knows what is affected, who makes decisions, and how work resumes.
Ask the MSP to explain the difference between backup and recovery. A backup is a copy of data or configuration. Recovery is the tested process for restoring the services the organization needs, in the order it needs them.
A backup that cannot be located, restored, or validated does not solve an operational outage. The recovery discussion should include both business information and the systems that support building operations.
Ask which systems are included in planning. Depending on ownership and vendor arrangements, that may include property-management data, shared files, communications, accounting records, cloud services, network configurations, access-control administration, and camera-system records.
Request an understandable recovery sequence. It should identify decision makers, priority services, vendor contacts, technical dependencies, communication expectations, and where documentation is stored when normal systems are unavailable.
Ask how the plan is reviewed after a major change, such as a carrier move, tenant improvement project, acquisition, or infrastructure replacement. Changes that are not documented can invalidate an otherwise sound recovery plan.
Use the discussion to evaluate data backup and recovery services. The goal is to make recovery responsibilities visible before an outage makes those questions urgent.
Takeaway: A provider should describe recovery as a tested business process, not merely a storage feature.
Will the MSP help us plan technology spending instead of reacting to failures?
Every building has a technology history. Equipment ages, carrier agreements change, tenant improvements add cabling and devices, and a single telecom closet can accumulate infrastructure from several ownership or management cycles.
Ask what the MSP includes in a technology roadmap. A useful roadmap identifies known equipment, lifecycle concerns, support-status issues, documentation gaps, ownership questions, and potential capital priorities.
The roadmap should help your team distinguish urgent stabilization work from improvements that can be budgeted and scheduled. It should not be a sales list of equipment replacements without a clear operational reason.
Ask whether recommendations are tied to outcomes. "Replace the switch" is incomplete. A stronger recommendation explains what the switch supports, the consequence of failure, whether landlord or tenant systems are affected, and what documentation will be updated after the work.
For riser and carrier questions, ask how the provider documents access, demarcations, available pathways, carrier coordination, tenant handoffs, and changes made during tenant buildouts. Those records support faster decisions when a tenant needs service or a carrier must access the building.
Ask who retains ownership of documentation, administrative access, configurations, and vendor records if the relationship changes. The property organization should be able to retrieve and use its own operating records without starting discovery over again.
Review riser management services if carrier governance and tenant connectivity are part of your selection criteria.
Takeaway: A capable MSP turns inherited technology into an asset that can be documented, governed, and budgeted.
What should we confirm before signing an MSP agreement?
Before selecting a provider, ask for the agreement in plain language. Review what is included, excluded, billed separately, and dependent on third parties. Do not assume every device, site visit, project, emergency request, or after-hours issue is covered the same way.
- Ask which users, systems, devices, and property locations are in scope.
- Ask how requests are submitted, prioritized, escalated, and communicated.
- Ask what response and resolution expectations are written into the agreement.
- Ask what documentation, administrative access, and records your organization receives.
- Ask how onsite work, projects, structured cabling, carrier coordination, and emergency requests are authorized.
- Ask how recurring issues are identified and how corrective recommendations are presented.
- Ask how the relationship transitions if property ownership, management, or vendors change.
Ask for discovery before accepting a fixed scope that does not account for the building's actual condition. Unknown infrastructure cannot be responsibly governed as if it were a standard office network.
For ongoing support expectations, review managed IT services and use it as a starting point for defining the support model your property operations need.
Takeaway: The agreement should make responsibilities visible wherever landlord, tenant, carrier, and vendor systems meet.
Frequently Asked Questions
What should a Norcross commercial property manager ask an MSP first?
Start by asking how the provider will inventory the building's network, telecom rooms, risers, carrier handoffs, cameras, access control, and remote connections. Then ask who owns each system and document. This shows whether the provider can assess the property as infrastructure rather than treating it like a standard office.
How do I compare managed IT providers for a multi-tenant building?
Compare providers by their discovery process, documentation standards, vendor-coordination approach, cybersecurity process, recovery planning, and agreement clarity. Ask each provider to explain how it separates landlord, tenant, carrier, and vendor responsibilities. The strongest answer connects technical work to tenant impact, operational continuity, and informed capital planning.
Should an MSP manage access control, cameras, and cabling?
An MSP can add value when those systems depend on shared networks, power, telecom rooms, credentials, carriers, or vendor remote access. Ask what the provider manages directly, what remains with specialist vendors, and who coordinates incidents. Clear responsibilities matter more than claiming one party handles every technology component.
How quickly should an MSP respond to a Norcross business outage?
Ask the provider to define response expectations in writing, including how urgent requests are prioritized, who communicates updates, and when escalation begins. The right timeframe depends on the affected service and agreement scope. What matters is a documented process that keeps decision makers informed and work moving toward restoration.