Pocket Concierge, Binding Terms: Auditing Resident Apps in Connected Blocks
Photo: U.S. Army USAG-RP by Keith Pannell, Public domain, via Wikimedia Commons
For a growing number of UK apartment schemes, the resident app is no longer a novelty layered on top of a concierge desk. It is becoming the desk. Access codes, visitor notifications, gym bookings, parcel collection, maintenance reporting and community notices may all sit behind a single login. That convenience is real, but it also creates a dependency that deserves scrutiny before a buyer exchanges contracts or a renter signs a tenancy.
The app is not simply a consumer product. In a connected building it can function as infrastructure: a gatekeeper to common parts, a record of building activity and a channel through which managing agents issue instructions. Approached in that light, it belongs in due diligence alongside the lease, the service-charge budget and the fire-risk assessment.
Why the app belongs in due diligence
Many scheme brochures present the resident app as a lifestyle benefit. The more useful question is whether the building can operate acceptably without it. If the front door, car park, bin store or parcel room depends on an app that requires a smartphone, a stable data connection and a working account, then the app is part of the building's operational model. Prospective residents should understand that model before they commit.
This is particularly important in new-build and converted blocks where traditional concierge hours have been reduced or omitted. A managing agent may describe the app as an enhancement, but residents can experience it as the only practical route to report a leak, book a lift-protection slot or receive a delivery. The distinction matters because essential services attract a higher standard of reliability and transparency than optional extras.
The audit should therefore begin with a simple mapping exercise. Ask which functions are app-only, which have a telephone or web fallback, and which are merely duplicated. Request a written schedule from the developer or managing agent. A verbal assurance that 'everything can be done at reception' is less useful than a documented fallback route, especially where reception hours are limited.
Mapping dependency before you commit
Prospective buyers and renters should test the app's role across five areas: access, bookings, parcels, maintenance and communications. For access, ask whether physical fobs or keys remain available and whether visitors can be admitted without a smartphone. For bookings, check whether amenity spaces can be reserved by telephone or email. For parcels, confirm what happens if a resident is unavailable and the app is offline. For maintenance, establish whether urgent repairs can be reported by phone. For communications, ask whether statutory or building-safety notices are also issued in writing.
A useful question is what happens during a connectivity failure. If the building's mobile signal is poor in the basement or the app relies on resident Wi-Fi that is not yet installed, the operational model may be weaker than the brochure implies. Buyers in particular should consider how these arrangements will be described in the lease or transfer documents, and whether any future change to the app provider requires leaseholder consultation.
Data sharing and the small print
The resident app will process personal data: names, contact details, visitor records, vehicle details, maintenance reports and possibly access logs. UK GDPR and the Data Protection Act 2018 still apply, but the practical question is who controls that data and for how long. The developer, managing agent, app provider and any subcontractors may each have a role.
Ask for the privacy notice and, where relevant, the data processing agreement. Look for clear retention periods, the lawful basis for processing, and whether data is shared with third-party service providers for analytics or marketing. Check whether residents can request a copy of their data and whether deletion is possible when they leave. A building that cannot explain its data flows in plain English is not necessarily acting unlawfully, but it is asking residents to accept an unusual level of opacity.
Accessibility is not an optional extra
A resident app that is difficult to use can exclude people with visual impairments, dexterity limitations, learning disabilities or limited digital confidence. The Equality Act 2010 places duties on service providers, and accessible design is also a practical requirement for a building that expects all residents to use the same platform.
Ask whether the app has been tested against recognised accessibility standards, such as WCAG 2.2 at AA level, and request the most recent conformance report. Check whether text can be enlarged, whether screen readers work with core functions, and whether colour contrast is adequate. It is also fair to ask whether a non-digital alternative exists for residents who cannot or will not use a smartphone. An app that is the only route to essential services should meet a higher accessibility threshold than one that merely supplements a staffed reception.
Fees, tiers and the risk of revision
The commercial model behind a resident app may be invisible at the point of sale. Some apps are included within the service charge; others involve a subscription, a premium tier or a fee for additional users. Ask how the service is funded, whether the current arrangement is fixed for a defined period, and what happens when the contract is renewed.
Service-charge transparency matters here. If app costs are recovered through the service charge, residents should be able to see them as a identifiable line item rather than an unexplained management overhead. If a separate subscription is proposed, check whether it is optional in practice. A 'free' app that becomes chargeable after the first year is a different proposition from one that is genuinely included.
Exit arrangements and continuity
Perhaps the most neglected question is what happens when the app provider changes, fails or is replaced. Residents may have stored documents, booking histories and community messages in the platform. The building may rely on the app for access control integration. The lease or tenancy should not leave residents stranded if the supplier exits the market.
Ask for the contract term, termination rights, data export arrangements and the process for migrating to a new provider. Check whether the managing agent holds a backup of essential building information outside the app. For renters, confirm what happens to app access at the end of the tenancy and whether any personal data is retained after the keys are returned. These are not hypothetical concerns in a market where proptech providers consolidate and business models evolve.
A practical audit trail
Before committing, assemble a short evidence pack: the app terms of use, privacy notice, accessibility statement, fee schedule, fallback arrangements and exit plan. Ask the developer or managing agent to confirm in writing which functions are essential and which are optional. If possible, speak to existing residents about reliability, support response times and whether the app has changed since first occupation.
The resident app can be a genuine improvement in how a connected building is run. But it should be audited as an operating system for the scheme, not accepted as a brochure flourish. In 2026, the prudent question is not whether a building has an app. It is whether the building, and its residents, can function fairly and transparently without it.