IT for Property Management: Many Small Sites, No IT Staff Anywhere

Property management has an IT profile that does not fit standard templates: a head office, a long tail of small sites, staff who move between them, contractors who need temporary access, and physical systems — door entry, cameras, intercoms, lifts — that have become networked.

No individual site justifies infrastructure. Collectively they are a real estate of technology.

The organising principle: nothing lives on site

The single most useful decision is that no site holds anything that matters. No file server, no local application, no local directory, no data that exists only there.

Each site becomes: a connection, a firewall or router, a switch, access points, endpoints, and whatever physical systems the building needs. If any of it fails, the fix is a replacement unit, not a recovery.

That makes sites replaceable rather than precious, which is the only workable model when you have twenty of them and visit each twice a year.

Connectivity, sized honestly

A leasing office with three staff does not need a large circuit. It does need a reliable one, because when it is down the office cannot take applications or payments.

What works:

• business-grade connection, modest speed, with an SLA
• cellular failover — cheap, and it turns an outage into a slow day
• the router managed centrally, so configuration is pushed rather than visited
• the same model at every site, so a spare in the head office cupboard fits anywhere

Standardising the hardware across sites is worth more than optimising each one. One configuration, one spare, one set of instructions.

The physical systems are the hard part

Door entry, cameras, intercoms and lift phones are increasingly IP-based, and they arrive through construction and facilities projects rather than through IT. The consequences:

They appear on the network without anyone telling you. A contractor installs a camera system and plugs it into whatever port was available. Inventory regularly and ask facilities about upcoming works.

They are rarely patched. Embedded devices with old firmware and default credentials. Segment them onto their own network with no internet access and no route to business systems.

Vendor remote access is standard. The installer wants permanent access to support the system. Use a brokered, time-limited arrangement rather than a permanent tunnel with a shared credential.

Camera retention has legal implications. How long footage is kept, who can view it, and what happens on a request are governed by privacy law that varies by jurisdiction. Decide and document it; do not let the default setting on the recorder be your policy.

Lift phones and alarm lines often need analogue service. They cannot simply move to a cloud phone system. Identify them before any telephony migration, not during.

Staff who move between sites

Property managers work across several buildings. They need the same experience everywhere.

• Cloud-first applications, so the location is irrelevant
• Identity-based access, so a laptop works at any site without local accounts
• Wi-Fi with the same SSID and credentials at every site, so devices roam without intervention
• Mobile as a first-class device, because much of the work happens walking a property
• Offline tolerance for inspection and maintenance apps — basements and plant rooms have no signal

That last one is frequently overlooked. An inspection app that requires connectivity will be used on paper and typed up later, which is where data gets lost.

Contractors and temporary access

A constant feature of the sector, and a constant source of lingering access.

• Guest Wi-Fi isolated from everything, at every site
• Time-limited accounts with an actual expiry date, not a reminder to remove them
• Scoped access to the specific property and system
• A documented process for the handover when a contract ends — including who collects badges and keys

Resident and tenant data

Property management holds a lot of personal information: applications, credit checks, identity documents, payment details, maintenance requests describing the inside of people's homes.

That carries obligations:

• know which systems hold it and for how long
• retention schedules, because application records for unsuccessful applicants accumulate indefinitely by default
• access control so site staff see their property's residents, not everyone's
• a process for access and deletion requests
• secure disposal of paper, which is still abundant in this sector

The support model that fits

With many small sites and no local IT, the model that works is:

Remote-first. Everything manageable remotely — devices enrolled, network equipment cloud-managed, applications cloud-hosted.

A named person per site who is not IT but is the point of contact. They power-cycle things, let engineers in and report problems. Give them a one-page card with what to check first.

Scheduled visits rather than purely reactive ones. A quarterly pass that checks the comms cupboard, the spare stock and the physical systems catches the slow failures — a failed fan, a dusty cabinet, an unplugged camera — before they become outages.

Standard spares in head office. Router, switch, access point, a laptop. A courier is faster and cheaper than an emergency purchase.

The starting checklist

• Inventory every site: connection, equipment, physical systems, who the on-site contact is
• Standardise hardware and configuration across sites
• Add cellular failover where an outage stops business
• Segment physical systems; fix vendor remote access
• Confirm nothing business-critical exists only on a site
• Set retention for camera footage and resident records, and enforce it
• Put time limits on contractor access
• Stock spares centrally and document the swap procedure

The pattern is consistent: centralise everything that can be centralised, standardise what must be local, and make each site cheap to fix and cheap to lose.