Operational Guide to Property Operations Software

A regional asset manager we worked with last year had a familiar problem: her quarterly board pack showed rent roll, occupancy percentage, and service charge recovery — and none of it explained why two structurally identical properties in her portfolio performed 30% apart on tenant retention. The lease data said both buildings were fine. The buildings themselves disagreed. What was missing wasn't another financial report. It was operational data: who actually enters, when, where they go, and how that behaviour maps to the leases she was pricing.

That gap is exactly what property operations software should close. Not another dashboard duplicating your ERP, but a layer that converts physical activity in your buildings into numbers you can defend at a lease negotiation or a capex review.

What "operational" actually means in a property context

Most software sold under this label handles work orders, tenant tickets, and preventive maintenance. Useful, but reactive. The higher-value layer sits underneath: continuous measurement of how the asset is used. For a shopping centre, that's footfall by entrance, floor, and daypart. For a multifamily building, it's amenity usage — how many residents actually use the gym you're about to renovate for €200,000. For mixed-use, it's the flow between components, which determines whether your retail podium is genuinely fed by the offices above it or merely adjacent to them.

Once that measurement layer exists, three operational decisions become evidence-based rather than negotiated:

• Cleaning and security scheduling. Staffing to actual traffic curves instead of fixed rotas typically reveals hours of paid coverage during near-empty periods.
• Lease pricing and renewal strategy. A unit delivering high footfall exposure justifies a different rate per square metre than one on a dead corridor — and you can now prove which is which.
• Capex prioritisation. Renovation budgets follow the zones where measured utilisation is high and satisfaction is low, not the zones a walkthrough happened to notice.

The tenant conversation changes when you both see the same data

Retail landlords know the annual ritual: the tenant claims the centre delivers no traffic; the landlord claims the tenant fails to convert it. Without shared data, the renewal becomes a poker game. With entrance-level and zone-level counting, both sides see delivered footfall against the tenant's own capture rate. Tools like Vemco's VemTenant and VemLease were built for precisely this exchange — giving tenants their own traffic view while the asset manager keeps the portfolio picture. In practice, the conversation shifts from "your centre is dying" to "my capture rate dropped 2 points after the food court reconfiguration" — a claim that can actually be investigated and fixed.

Turnover-based rent structures depend on this even more directly. If a percentage-rent clause references traffic or sales density, the counting behind it needs to survive an audit. That is why accuracy claims matter more here than in marketing analytics: reputable providers contract a minimum accuracy — Vemco commits to at least 96%, typically reaching 98–99% where lighting, layout, and visitor behaviour allow — rather than quoting a flat number that no sensor achieves in every doorway.

A practitioner's warning: staff traffic will poison your baseline

Here is the detail almost every first implementation gets wrong. In a mid-sized centre, employees, cleaners, contractors, and delivery drivers can account for a meaningful share of daily entrance counts — and they cluster at opening, closing, and shift changes, exactly when visitor traffic is lowest. Left unfiltered, they inflate your quiet hours and flatten your traffic curve, which then corrupts every staffing and cleaning decision built on top of it. Staff-exclusion algorithms exist for this reason; insist on them at procurement, and validate them during the pilot by manually counting a shift change against the system output. If your vendor cannot explain how they separate staff from visitors, you are buying a people counter, not property operations software.

Evaluation criteria that separate real platforms from repackaged sensors

When you shortlist vendors, four criteria predict whether the system survives beyond year one:

• Sensor independence. Portfolios accumulate hardware over acquisitions and refurbishments. A platform locked to one sensor brand forces rip-and-replace; a sensor-agnostic one — Vemco's software works with Xovis 3D AI sensors, Milesight, Hikvision, and AXIS, among others — lets you standardise the data layer while the hardware varies by building.
• Deployment control. Institutional owners increasingly require private cloud or specific hosting jurisdictions for anything touching building data. Ask before the contract, not after the security review.
• ERP and BI integration. If traffic data cannot land in the same warehouse as your rent roll, someone will export CSVs by hand for the next five years. That someone will resign, and the reporting will stop.
• Zone-level and space-level granularity. Whole-building counts answer almost no operational question. You need corridor-level and space-level views — the problem modules like VemSpace address — because the decision is never "is the building busy" but "is level 2 west worth its service charge allocation".

Sequencing the rollout so finance stays on your side

Do not instrument the whole portfolio at once. Pick one asset with a live commercial problem — a renewal cycle in the next twelve months, a contested service charge, a renovation decision — and deploy there first. Run the pilot for a full quarter so you capture at least one seasonal swing. Then present the finding in financial terms: hours of security coverage reallocated, the rent uplift defended with delivered-traffic evidence, the amenity investment redirected. That single, concrete result funds the portfolio rollout far more reliably than a technology business case ever will.

Expect the first two months of data to surprise you, and expect some of the surprise to be measurement noise — miscounted entrances, unfiltered staff, a sensor angled wrong over a revolving door. Budget calibration time. The asset managers who treat the first quarter as data validation, not decision-making, are the ones whose numbers hold up when a tenant's lawyer questions them.

If you are weighing property operations software for a specific asset or across a portfolio — whether the immediate problem is tenant negotiations, staffing costs, or capex prioritisation — talk to Vemco Group about a scoped pilot. Bring the building plans and the commercial question you need answered; we will tell you honestly what the data can and cannot prove. Start the conversation at vemcogroup.com/contact-us.