Choose an IT provider for a commercial real estate business by checking whether it understands the building as well as the office: its network, telecom rooms, risers, access control, cameras, building systems and tenant boundaries. Ask how it will assess the environment, define responsibilities, coordinate support and document security and lifecycle decisions. A good fit makes ownership clear and helps keep property operations moving.
What should an IT provider learn before recommending changes?
A provider should begin by learning what is installed, where it sits, who owns it and what depends on it. In a property, the user count rarely describes the whole technology estate. A switch may connect cameras, access-control panels, tenant services, a building management system gateway or other equipment with different owners and consequences if disrupted.
Ask how the provider would document MDFs and IDFs, cabling, risers, carrier demarcations, network equipment, wireless coverage and the systems attached to each segment. A useful record goes beyond a device list. It helps property staff distinguish landlord infrastructure from tenant equipment, vendor-managed systems and carrier services.
Find out how discovery becomes a decision plan. Which findings need attention soon? Which can remain in service with better documentation or monitoring? What is approaching end of support, and what evidence supports that conclusion? A sound assessment separates observed conditions from assumptions and explains the operational effect of each finding.
For a portfolio, check whether the provider can use a consistent inventory and documentation approach across properties without assuming every building is identical. Equipment generations, ownership structures and tenant arrangements may differ. The goal is a comparable view of risk and lifecycle, not a forced uniform design.
Ask what access the provider needs to complete discovery and how it will handle gaps in inherited records. Clarify whether property staff, tenants or vendors must supply information, and how unresolved questions will be tracked. This prevents unknowns from quietly becoming assumptions in a later project.
Ask for three connected records: an asset inventory, a dependency map and a responsibility matrix.
Discovery should produce records the property team can use. If nobody owns the diagram, the diagram is probably wrong.
How can you tell whether support fits a building, not just its users?
Ask the provider to walk through a realistic incident: cameras stop responding after a network change, a tenant reports connectivity trouble, or a carrier handoff is down. Listen for questions about scope, affected systems, access permissions, recent changes and the right vendor contacts. A useful response starts with diagnosis and coordination, not a premature promise about the fix.
Clarify what the provider supports directly and what remains with the property, tenant, carrier, security integrator, building systems contractor or another vendor. Those boundaries should appear in the service agreement or operating documentation. Ask who opens and tracks third-party cases, who updates property staff, and who confirms service is restored across affected systems.
Responsiveness is more than an advertised response time. Ask how incidents are classified, how escalation works outside ordinary business hours, what updates the property team receives and how unresolved vendor dependencies are handled. Compare the answers with the proposed agreement, including exclusions and services that require separate approval.
Commercial property support can involve both remote troubleshooting and on-site work. Ask what conditions trigger a site visit, how access to telecom rooms is coordinated, and what information technicians record afterward. If the provider cannot explain how it avoids undocumented changes, the next outage may begin with another round of discovery.
Ask how routine maintenance, planned changes and urgent incidents are distinguished. A provider should explain how it communicates work that may affect tenants or shared building services, and how it records the result. Make sure the process accounts for authorization: the *** requesting a change may not be authorized to approve it for the property.
Therese, a commercial real estate client, said, "Brian clearly explains what is happening and shows you ways to help prevent the issue from happening again. He is great to work with." That is a useful standard for communication: explanations should clarify the cause and help the property team understand prevention steps.
Choose a support model that makes ownership and escalation visible. Clear handoffs keep building issues from becoming a chain of disconnected vendor tickets.
What cybersecurity questions matter for connected property systems?
Ask the provider to identify which building and business systems are connected to the network, who can reach them remotely, and how that access is approved, limited and reviewed. Include cameras, access control, building-system interfaces, tenant services and vendor support connections where they are in scope. Do not assume a system is isolated because it has a separate controller or vendor.
Ask how networks are separated by purpose and ownership, how administrative accounts are controlled, and how changes are documented. The provider should explain its approach in plain terms and show how it would verify the design against the property's actual equipment and service responsibilities.
Probe incident readiness. Who contacts the property team if suspicious activity affects a building system? What evidence is preserved? How are the system vendor and internal stakeholders brought into the response? What recovery decisions belong to the property owner? Ask for incident-response responsibilities and escalation contacts in writing rather than relying on informal assumptions.
Also ask how backups and recovery planning apply to relevant systems, and which party is responsible for each configuration, record or data set. A backup claim is useful only when scope, retention, access and restoration responsibilities are clear. Recovery planning should account for the practical order in which services need to return.
Ask how the provider will handle vendor remote access when a project ends or a support relationship changes. Establish who approves access, who can revoke it, and how the change is recorded. Confirm that any security recommendations distinguish what the provider manages from what remains the responsibility of the property or a specialist vendor.
Cybersecurity review should connect to building operations, not stop at employee computers. The provider should help the property understand exposure and ownership without claiming that any assessment can guarantee security or compliance.
How should you compare proposals and long-term costs?
Compare scope before comparing totals. One proposal may cover only user support; another may include network management, cybersecurity, documentation, site visits or coordination with physical-system vendors. Put inclusions, exclusions, assumptions and separately billed work side by side. Confirm how the provider handles projects, after-hours requests, new properties and tenant-specific work.
Ask what drives the recurring fee and whether the model is based on users, devices, sites, service tiers or a defined combination. In a device-heavy property, a per-user count alone may not represent cameras, controllers, wireless equipment, network switches or shared infrastructure. Ask how those assets affect monitoring, support scope and lifecycle recommendations.
Request a clear explanation of one-time costs, ongoing services, equipment replacement assumptions and renewal terms. Ask which records or assessments are included, how often they are refreshed, and whether transition or onboarding work is priced separately. If the proposal uses an allowance or estimate, ask what could change it and how approval works before additional charges are incurred.
Use the same scenario to test each proposal: an access-control outage that may involve the network and a third-party integrator. Ask each provider who coordinates diagnosis, what is included, how progress is communicated and what would be billed separately. This reveals more than a comparison of package names.
Check whether the proposal explains how new sites, tenant changes and equipment additions affect the service. Ask what triggers a scope review and whether the provider will document the resulting change before work begins. This makes it easier to plan around portfolio changes rather than discovering later that a key responsibility was excluded.
Use this checklist to compare proposals consistently:
- Included services, exclusions and separately billed work
- Response commitments, escalation and vendor coordination
- Documentation, onboarding and site-visit scope
- Recurring fee drivers, renewal terms and approval for additional charges
A useful proposal makes the operating model and cost drivers understandable. Choose the plan that fits the building's obligations and exposes future decisions, not simply the shortest price sheet.
What evidence should you request before signing?
Ask for a sample, appropriately redacted service report or technology inventory so you can see how findings are recorded. Request an example of a network or system diagram, a change record and a recurring review format. These artifacts show whether the provider leaves behind usable information or keeps the operating picture in individual technicians' memories.
Check references that resemble your environment in relevant ways, such as multi-tenant operations, multiple properties or coordination among property staff and outside vendors. Ask the reference how the provider communicates, handles follow-through and explains recurring problems. Do not rely only on a list of supported products or a polished proposal.
Review the service agreement for response commitments, escalation, access controls, data handling, documentation ownership, termination assistance and transition responsibilities. Confirm who can authorize changes and how tenant, landlord and vendor responsibilities are recorded. Make sure the agreement's language matches what the sales discussion led you to expect.
Finally, ask what the first phase would establish and what decisions it would leave to the property team. A disciplined start should clarify the inherited environment, immediate operational concerns and longer-term lifecycle questions before it recommends broad replacement. Treat unknown infrastructure as a due-diligence finding, not a future surprise.
For additional context, review the commercial real estate technology services, riser management services and cybersecurity services relevant to your property's needs. Use those service descriptions as a starting point for questions about scope; confirm specific responsibilities and commitments in the proposal and agreement.
Evidence of clear records, credible references and written boundaries is stronger than a promise that everything will be handled.
Looking for local help? We've covered this for Carmel.
Related reading
Frequently Asked Questions
What does an IT provider need to know about commercial real estate?
The provider should understand how networks, telecom rooms, risers, carriers, access control, cameras, building systems and tenant services depend on one another. It should also distinguish landlord responsibilities from tenant and vendor responsibilities. Ask how those relationships will be documented and kept current, so property decisions do not rely on incomplete equipment lists or informal knowledge.
Should one provider manage every building system?
Not necessarily. Ownership and support can remain divided among property teams, tenants, carriers and specialist vendors. What matters is that responsibilities, escalation paths and shared network dependencies are explicit. Ask the IT provider which services it supports directly, which it coordinates with other parties, and how it records changes that may affect connected building systems.
How do I compare commercial real estate IT proposals?
Compare the included services, exclusions, response commitments, vendor coordination, site work, documentation, onboarding, project charges and renewal terms. Use the same building scenario to test each proposal and ask who owns each step. A lower total may reflect a narrower scope, so confirm how shared infrastructure and device-heavy systems are treated before selecting a provider.
What records should an IT provider maintain for a property?
Request an asset inventory, network and dependency diagrams, system ownership boundaries, carrier and vendor contacts, change history, lifecycle observations and incident escalation details. Agree who can access these records, who updates them after work, and how the property receives copies. Documentation should help staff make operating and capital decisions without depending on one person's memory.
