Ask how the IT company will keep each property supported while headquarters maintains visibility and control. Have it explain who owns tenant-impacting incidents, how local access and vendor work are coordinated, what building records it keeps, and how it reports unresolved issues. Require clear approval boundaries and a named owner for every handoff.
In This Article
- Who owns an incident that crosses IT and building operations?
- How will support work when the property manager is not onsite?
- What property records should headquarters be able to retrieve?
- How should tenant access and building security changes be approved?
- What should headquarters review beyond ticket counts?
- Frequently Asked Questions
Who owns an incident that crosses IT and building operations?
A tenant reporting a failed conference-room connection might be dealing with a carrier outage, a tenant network issue, a building-managed switch, or a service handled by another vendor. Ask who keeps the issue moving while the cause and responsible party are being established.
Have the provider walk through an incident from the first report to confirmed restoration. Ask who receives the report, what details are recorded, who contacts the property manager, and who keeps the tenant informed. The process should prevent the tenant from being passed between the landlord, IT provider, carrier, and tenant's own support team without a clear owner.
Clarify where landlord responsibility ends and tenant responsibility begins. A provider should confirm ownership and authorization before changing a tenant's network, building controls, cameras, or access system. Sharing a closet or network path does not, by itself, give a provider permission to make changes.
Four handoff details to document: first contact, decision owner, vendor escalation, and next update.
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 captures what a useful support experience should deliver: a clear explanation, a practical next step, and attention to preventing a repeat.
The handoff matters as much as the fix.
How will support work when the property manager is not onsite?
Multi-state support depends on coordination as much as travel. Ask which issues the provider can diagnose remotely, which require someone onsite, and how it arranges building access, escorts, after-hours entry, and vendor arrival with the property team.
Ask for the escalation route when the usual property contact is unavailable. The provider should explain what information it needs to proceed, who can approve access or a change, and how it records a decision made by phone. A documented process is more dependable than a verbal workaround known to one employee.
Discuss field coverage in terms of the actual properties you own or manage. GDS Technology serves multi-location organizations nationally, with offices in Norcross, Georgia and Carmel, Indiana. Ask any provider how it handles a building outside its routine field coverage, including whether it uses authorized local vendors and who verifies their work.
Before dispatch, agree on how onsite work will be scoped. For cabling, riser, or surveillance work, identify the area involved, building permissions, tenant coordination, expected documentation, and any specialist who needs to participate. GDS provides riser management services and structured cabling and low-voltage services. Confirm the scope for each project rather than assuming all site work is included.
Test the process with a realistic scenario: a shared network room is inaccessible, a tenant is waiting, and the property contact cannot be reached. Ask what the provider can decide, what requires approval, and how it keeps the issue visible while waiting. A useful answer names roles and communication steps, not just a promise to coordinate.
A remote diagnosis helps only when the next local action is clear.
What property records should headquarters be able to retrieve?
Ask for records that let a new technician understand a property without relying on the memory of the person who installed or last supported its systems. For each site, identify the equipment and services in scope, service providers, support contacts, system owners, access constraints, and known dependencies. Mark unverified details as open questions rather than presenting them as confirmed facts.
For commercial properties, include infrastructure that can affect tenant operations: internet demarcation points, shared network rooms, riser pathways, cameras, access control, and tenant-facing communications systems that are part of the agreement. Record who owns each system and what approval is required before work begins.
Ask how records are updated after a tenant buildout, equipment replacement, move, or provider change. A contact list naming a former property manager or a floor plan that omits a new pathway can send a technician to the wrong place or delay authorization. Define who reports changes and who checks that the updated information is usable.
Ask whether a technician who has never visited the building can find the right room, contact, and system owner from the records. Shared infrastructure should be clearly distinguished from tenant equipment. That distinction helps avoid unauthorized changes and makes responsibility easier to establish when multiple vendors are involved.
GDS supports commercial real estate technology through technology services for commercial real estate. Ask any prospective provider to show a sample site record with sensitive information removed and explain how it tracks gaps, conflicting details, and items that still need validation.
Current records shorten diagnosis and help prevent avoidable repeat visits.
How should tenant access and building security changes be approved?
Ask how access requests are authorized, recorded, and closed. A request to add a tenant employee, contractor, or property staff member should identify the approver, affected system, requested access level, and end date when access is temporary. The provider should follow the approval process the property has established rather than treating every forwarded email as authority.
Separate technical support from security decisions. Property leadership should define who may view camera footage, issue credentials, or approve retention and disclosure practices. Put the IT provider's permissions and responsibilities in writing, especially when a system spans properties or is managed by a third party.
Ask what happens when an employee leaves, a vendor changes, or an account may have been compromised. Clarify who can disable credentials, who confirms the change, and where the action is recorded. Ask whether temporary construction staff and service vendors use the same workflow or need a separate approval path.
GDS provides business video surveillance systems. For each building, confirm which cameras, recording components, and support tasks are included. Supporting a camera network does not automatically give a provider authority to decide who can review recordings or how footage may be used.
Access control is a governance process, not just a login task.
What should headquarters review beyond ticket counts?
Ticket volume alone does not show whether properties are becoming easier to support. Ask for reporting on recurring incidents, aging work, third-party dependencies, blocked changes, and sites with incomplete records or unclear ownership. Each measure should help headquarters decide what to do next.
Agree on consistent definitions across locations. "Resolved" should mean the reported service is working again and the affected party has been informed, not merely that a ticket was reassigned. For recurring problems, ask the provider to distinguish immediate restoration from follow-up investigation and record any unresolved dependency.
Keep building-specific exceptions visible. A medical office, law firm tenant, and general office property may have different system owners, privacy requirements, or operating windows. Consistent reporting should make status easier to compare without forcing every building into the same technical design or approval process.
Ask to see how a repeat issue would appear in a report. If several properties report similar connectivity failures, headquarters should be able to see what has been checked, whether the likely cause is shared or site-specific, and who owns the next investigation. The report should support a decision, not simply lengthen a list of open tickets.
GDS offers managed IT services. Ask the provider to define reporting cadence, covered locations, escalation contacts, and any response targets in the proposal or service agreement. Do not assume those terms from a general service description.
Use this short checklist when comparing providers:
- Who owns the incident and keeps tenants and property leadership updated?
- Who authorizes access, changes, and third-party dispatch?
- What site records are maintained, and who updates them?
- How are local field work and vendor results verified?
- What recurring issues, delays, and open dependencies will headquarters see?
Useful reporting makes ownership visible before a small issue becomes a portfolio-wide pattern.
Looking for local help? We've covered this for Norcross.
Frequently Asked Questions
Can one IT provider support properties in several states from a headquarters?
Yes, if the operating model separates central coordination from local authorization and field work. Ask how remote diagnosis, property-manager communication, vendor dispatch, and onsite access fit together. Confirm which locations and tasks are covered, and how the provider handles a building that needs a local specialist outside its routine field coverage.
What should a property owner ask about tenant technology support?
Ask who owns the tenant relationship during an incident, where landlord responsibility ends, and how the provider confirms authority before changing shared or tenant-owned systems. Also ask how updates reach the tenant and property manager. Clear boundaries and communication reduce duplicate work and help prevent requests from stalling between vendors.
How can headquarters compare IT support across different buildings?
Use common definitions for issue status, aging work, repeat incidents, vendor dependencies, and documentation gaps. Keep each building's systems and approval requirements visible instead of treating differences as noise. Ask the provider to connect every reported pattern to an owner and next step, so headquarters can prioritize without assuming each property needs the same remedy.
What should a multi-state IT support agreement spell out?
It should identify covered properties and systems, how to report issues, who can authorize access and changes, and how onsite work is coordinated. Ask it to define escalation contacts, reporting cadence, and any response targets in plain terms. Confirm how exclusions, third-party dependencies, and work outside routine field coverage are handled before service begins.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.