Before signing a block management software agreement, RMC and RTM boards should interrogate data architecture, statutory compliance features, access controls, and data ownership—not just surface-level dashboards. A well-designed platform must streamline statutory reporting under leasehold law, support Building Safety Act obligations where applicable, and maintain complete audit trails without compromising data privacy or creating operational friction.
Key takeaways
- Purpose-built block management software must support open-book accounting while strictly enforcing role-based permissions to comply with UK GDPR and protect privileged board communications.
- Procedural compliance modules should track statutory Section 20 consultation stages under the Landlord and Tenant Act 1985 to prevent major works cost-capping disputes.
- For Higher-Risk Buildings (18m+ or 7+ storeys), software should support the digital Golden Thread by maintaining immutable audit logs for statutory safety certifications.
- Platforms must provide transparent contractor tendering and direct invoice linking to ensure all service charge expenditure is auditable against Section 21 year-end accounts.
- Boards should insist on full data portability, ensuring that historical accounts, maintenance logs, and compliance records can be extracted cleanly if managing agents or software vendors change.
1. Financial Transparency: Is the Platform Built for Open-Book Auditing?
Traditional block management tools often operate as closed ledgers, presenting leaseholders with static year-end summaries that obscure individual contractor costs and tendering history. Under the Leasehold and Freehold Reform Act 2024 and Sections 21–22 of the Landlord and Tenant Act 1985, leaseholders hold clear rights to transparent, standardized financial reporting.
Key question to ask:
Does the platform support itemized, transaction-level ledgers where every expense is linked directly to its underlying supplier invoice, work order, and proof of completion?
A compliant platform should allow directors and auditors to review financial records in real time and generate statutory summaries without requiring weeks of manual data compilation prior to an AGM.
2. Data Governance & GDPR: How Are Permissions and Privacy Handled?
While transparency is essential, raw director dashboards contain sensitive information that cannot legally be shared with all residents. Individual service charge arrears, dispute records, solicitor correspondence covered by Legal Professional Privilege (LPP), and staff payroll details must remain strictly confidential under the Data Protection Act 2018 and UK GDPR.
Key question to ask:
Does the system feature granular, role-based access control (RBAC)?
The platform must provide a clear separation between:
- Director views: Comprehensive oversight of financial balances, legal correspondence, and arrears management.
- Resident views: Individual account balances, payment history, building announcements, maintenance ticket statuses, and general communal accounts.
3. Statutory Compliance: Does the Software Support Section 20 and Safety Duties?
Managing major works and safety compliance requires adherence to strict statutory timelines:
- Section 20 Consultations: Under the Landlord and Tenant Act 1985, qualifying works exceeding £250 per unit require formal Notice of Intention, tendering, and Notice of Estimates stages. Software should track statutory observation periods (30-day windows) to avoid procedural errors that cap cost recovery.
- Building Safety Records: For Higher-Risk Buildings (18m+ or 7+ storeys), the software should facilitate the "Golden Thread" mandated by the Building Safety Act 2022, storing structural plans, Fire Risk Assessments (FRAs), lift maintenance certificates, and safety case documentation.
Key question to ask:
Does the system automate statutory notice workflows, record resident observations, and maintain an immutable compliance log for building safety audits?
4. Contractor Procurement: Does the System Eliminate Hidden Markups?
Opaque contractor procurement remains a primary driver of service charge inflation. When managing agents route maintenance through closed supplier networks without transparent tendering, leaseholders often face administration markups and uncompetitive pricing.
Key question to ask:
Does the software enable open, competitive tendering and direct contractor invoicing without proprietary platform markups?
The system should allow boards to benchmark quotes, verify contractor accreditations (e.g., Gas Safe, NICEIC), track work orders from dispatch to sign-off, and review unredacted supplier invoices.
5. Data Ownership: Who Controls the Building's Historical Records?
A major vulnerability for RMC and RTM companies is vendor lock-in. When a building changes managing agents or software providers, historical maintenance records, warranties, and financial ledgers are frequently lost or trapped in proprietary file formats.
Key question to ask:
Who owns the building’s data, and what is the export protocol if the contract ends?
Ensure the contract explicitly states that all financial data, maintenance logs, and compliance records remain the property of the RMC/RTM company, exportable in standard, open formats (such as CSV and structured PDF) with zero exit penalties.