Desk booking, wayfinding, air-quality dashboards and mobile credentials are converging into a single tenant app across Australian corporate fitouts. Tenants judge these apps on convenience; the fitout team's real job is upstream of the interface — occupancy sensing that's actually reliable, API access to systems that were never designed to be queried by a mobile app, and a cabling design that treats the tenancy as a data platform rather than a floor of desks.
Occupancy Sensing: Choosing the Right Sensor for the Right Question
Workplace apps ask two different occupancy questions that get conflated far too often: "is this specific desk free right now?" and "how busy is this zone generally?" Under-desk power or capacitive sensors answer the first question reliably — they detect a laptop or monitor drawing current, which correlates well with actual desk use and avoids the false-positive problem of PIR sensors, which miss a stationary person typing at a keyboard. Zone-level density questions are better served by WiFi/BLE-based counting or ceiling-mounted people-counting sensors, which aggregate across a neighbourhood of desks rather than claiming per-desk accuracy they can't deliver. Specifying the wrong sensor type for the question — commonly, PIR sensors bought for desk booking — is the single most common reason workplace apps lose tenant trust in their first six months.
API Integration: Where the Real Engineering Sits
A workplace app's desk-booking and wayfinding features are relatively simple software; what makes the platform genuinely useful is its integration with access control, HVAC zone data and the tenancy's identity provider. This should never be a direct network-layer connection from the app's backend into building controllers. The defensible architecture is a scoped API layer — most modern access-control platforms expose this via OSDP-based edge controllers or a vendor REST API — through which the app can request mobile credential issuance and read door events, without ever holding network-layer access to the panels themselves. Identity federation (SSO via Azure AD or Okta) should sit in front of this, so mobile credentials inherit the tenant's own employee lifecycle management rather than the building maintaining a parallel, and inevitably stale, user database.
- Budget one PoE-fed sensor node per 8-12 desks in a typical open-plan floor for occupancy and environmental (CO2/temperature) monitoring.
- Specify BLE beacon or WiFi RTT infrastructure separately from the data network if indoor wayfinding accuracy below 3-5 metres is required — standard WiFi AP density alone is rarely tight enough for turn-by-turn indoor navigation.
- Route access-control API integration through a scoped, rate-limited gateway rather than direct panel access, with the app vendor holding read/issue permissions only — never write access to door schedules.
- Confirm data residency for the app's backend platform against the tenant organisation's own compliance requirements — many workplace-app vendors default to offshore hosting that large Australian occupiers will want reviewed at lease negotiation, not after go-live.
Design takeaway: The workplace app itself is rarely the hard part of the project. Specifying the right sensor for each question being asked, and a scoped API gateway rather than direct system access, is what determines whether the platform is trusted by IT and security teams — not just liked by end users.
Multi-Tenant Buildings Add a Governance Layer
In a multi-tenant Australian office tower, the workplace app usually sits at two levels: a landlord-operated base-building app (lift call, visitor management, amenity booking) and tenant-specific overlays for desk booking and internal wayfinding. Getting the data-sharing boundary right between these two layers — what the landlord's app can see about a tenant's occupancy, and vice versa — is a commercial and legal question as much as a technical one, and should be resolved before the ELV and cabling design is locked in, since it directly affects where sensor data terminates and who administers the underlying gateway.
Frequently Asked Questions
What sensor type gives the most reliable desk occupancy data?
Under-desk power or capacitive sensors give the most reliable binary occupied/vacant signal for booking systems, since PIR sensors miss stationary occupants and WiFi/BLE-based counting is better suited to zone-level density than individual desk state.
Does a workplace app need direct network access to the access-control system?
No, and it shouldn't get it. The safer pattern is a scoped API integration — typically via the access-control vendor's OSDP or REST layer — that lets the app request credential issuance and read door events without being granted broader network-level access to controllers.
How much extra cabling does a workplace experience rollout need?
Budget one PoE drop per 8-12 desks for occupancy and environmental sensors in a typical open-plan Australian fitout, plus dedicated drops for wayfinding kiosks and any BLE beacon infrastructure used for indoor positioning.