How to Manage Block Management with CRM Software

Block management — managing communal areas, shared services, and collective obligations in multi-unit buildings — is operationally different from residential lettings. It involves multiple leaseholders, a freeholder or management company, shared service charges, communal maintenance, insurance, and a regulatory framework that demands precision. If you're an estate agent adding block management to your lettings business, a CRM adapted for block management isn't optional. It's the difference between running a profitable service line and drowning in spreadsheets and compliance deadlines.

What makes block management different from lettings

In a standard residential letting, the structure is straightforward: one landlord, one property, one or more tenants. You collect rent, manage the property, deduct your fees, and keep tabs on one relationship triangle.

Block management flips this. A single building might have 20, 50, or 100 units, each owned by a different leaseholder. Rights and obligations are governed by legislation like the Landlord and Tenant Act 1985 and professional standards from bodies including RICS. You're managing the building as a whole, not individual units. That means you interface with leaseholders, the freeholder, contractors, insurers, and — sometimes — the tenants living in units owned by absent leaseholders.

The financial model is also upside-down compared to lettings. Instead of collecting rent and taking a percentage, you collect service charges from each leaseholder, manage a shared budget, and account for every penny spent on communal areas and services. Transparency isn't a nice-to-have. It's a legal requirement (and a critical trust-builder with people who've just paid £20,000 for their share of a new roof).

Why your standard lettings CRM won't cut it

Most CRMs are built around the unit. Xero's estate-agent package, Zoopla's tools, even some property-specific CRM platforms — they're optimised for "one property, one landlord, straightforward accounting." They work fine for lettings.

For block management, they're like trying to fit a three-tier cake into a two-tier box. You'll force it, something breaks, and you spend half your time working around the tool instead of using it.

The core issue: a lettings CRM doesn't treat the building as a distinct operational entity. It doesn't know how to track service charges separately from rent, handle multiple leaseholders against a single property, or manage the Section 20 consultation process (which has its own legal timelines and documentation requirements). Trying to adapt a lettings CRM to block management is possible, but it's a workaround, not a workflow.

Building your block management infrastructure in CRM

If you want block management to work alongside lettings in a single CRM, you need to configure the data structure correctly from the start.

Building records as the root entity. Your primary record is the building, not the unit. Each managed building needs its own record capturing: building name and address, number of units, freeholder or management company details, the insurance policy reference, communal areas and shared facilities. Units are then linked to the building, each with its own leaseholder contact, lease terms, and service charge obligations.

This sounds simple. It's not, because most CRMs default to a property-as-root structure. You'll need to either choose a CRM that supports building-level records natively (like Relentify's CRM), or accept that you're building a semi-manual hierarchy using custom fields and linked records.

Leaseholder contacts and their scenarios. Each leaseholder is a contact record. That record should include contact details, their unit number, lease start and end dates, monthly service charge amount, ground rent, and full payment history. But here's the complication: some leaseholders live in their unit. Others have let it to tenants. Your CRM needs to handle both, linking the tenant record to the unit and the unit to the building. If you can't do that cleanly, you'll end up with duplicate contacts or missing context when a tenant asks about repairs.

Service charge tracking and accounts. Service charges are the beating heart of block management. Each leaseholder pays a share of building running costs — maintenance, insurance, cleaning, utilities, management fees. You collect these charges, manage the budget, and produce annual accounts showing leaseholders exactly where their money went.

Your CRM (or integrated accounting system) needs to track service charge demands, payments, arrears, budget allocations, and anticipated costs. It should also support production of formal annual service charge accounts. This isn't a nice report. It's a legal document. Leaseholders will scrutinise it. Getting the numbers right and the narrative clear is worth whatever integration effort you need.

Communal maintenance as distinct from unit maintenance. Maintenance requests fall into two categories. Unit maintenance is the leaseholder's responsibility (their boiler, their window). Communal maintenance is the management company's responsibility (the building's roof, the shared entrance, the lifts). Your CRM should distinguish these clearly and track communal work against the building record, not the individual unit.

Major works — roof replacement, external redecoration, lift replacement — are a third category entirely. They require consultation with leaseholders, multiple quotes, formal decisions, and a defined process. Your CRM should track the consultation timeline, store quotes and decisions, and record which leaseholders approved the work and when.

Managing landlord relationships is complex even in lettings, and block management adds another layer: you're managing the relationship between the building as a legal entity and dozens of individual leaseholders who may not know each other. A CRM that supports building-level records makes this manageable.

Compliance: the non-negotiable bits

Block management carries compliance obligations that go beyond lettings, and they're enforced. Miss one, and you're facing fines, legal action, or loss of business.

Fire safety. Multi-unit buildings have specific fire safety requirements under the Fire Safety Order 2005. You need fire risk assessments, fire-rated doors, emergency lighting, alarm systems, evacuation plans. Track all of these in your CRM: assessment dates, remedial actions, inspection records, contractor certificates. This is audit-trail stuff. If something goes wrong, the first question is "where's your evidence that you knew about it and acted?"

Building insurance. The insurance policy must be current at all times. Leaseholders have the right to request sight of the policy. Your CRM should store the certificate, track the renewal date, flag renewals before they lapse, and record any claims. This is a field where a simple calendar reminder in a CRM is far better than an email in someone's inbox that gets buried.

Health and safety in communal areas. Risk assessments for shared spaces — car parks, gardens, corridors, lifts, stairwells — should be recorded and monitored. Document what you've assessed, what risks you've identified, and what actions you've taken. Store this in your CRM linked to the building record.

Section 20 consultation. For major works above a certain cost threshold, leaseholders must be formally consulted. The law specifies exact timelines (notice periods, response times) and documentation requirements (the consultation notice must include prescribed information). Your CRM should track every stage, store all correspondence, record responses, and generate audit reports. Mess this up, and the work can be challenged in court. CRM software that supports property compliance across multiple properties is not a luxury here — it's the only way to keep track reliably.

Keeping everyone informed

Block management is high-communication work. Building-wide notices, service charge reminders, AGM invitations, consultation letters, emergency alerts — they all need to reach leaseholders efficiently. And you need to maintain individual communication histories.

Your CRM should support bulk communication (send an email to all 47 leaseholders in Building A in one action) while also maintaining individual correspondence records. When a leaseholder emails you about their lease or a repair, you should see both their personal history with you and the building-wide communications they've received. This matters for context: if a leaseholder is upset about a service charge increase, they might be less upset if the CRM reminds you that you sent them a detailed notice three weeks prior explaining the increase.

Two-way communication is also critical. Leaseholders will contact you with queries, concerns, and complaints. Your CRM should log these, categorise them, and track resolution. This protects you (you have a record of all communication) and improves service (you know what issues recur and can address them systematically).

The block management opportunity

For lettings agencies, block management is a revenue lever. Blocks generate recurring fee income, often with long-term management contracts that provide stability. A 50-unit block on a 2% management fee is £500–£1,000 in monthly recurring revenue per building. Many blocks are managed by the same agency for years. The business is less volatile than lettings (where tenancy turnovers create gaps) and more profitable (service charges are higher-value transactions than individual rents).

But the operational complexity means you need systems that match the task. The compliance requirements are strict. The financial accounting is detailed. The stakeholder management is demanding. The communication cadence is relentless. Attempting block management without appropriate CRM infrastructure is risky.

A CRM that handles both residential lettings and block management — with building-level records, service charge tracking, compliance audit trails, and bulk communication — lets you expand your services without duplicating your technology stack. You stay in one system for all property management operations, relationships, and finances.

Frequently Asked Questions

Can I use a lettings-specific CRM for block management? Technically yes, but it's not ideal. Most lettings CRMs are optimised for unit-level records and straightforward rent collection. You'll need to work around the system's assumptions about your data structure, and you'll likely end up with a hybrid approach (some data in the CRM, some in spreadsheets, some in external accounting software). It works, but it's slow and error-prone. A CRM built to support building-level records from the start saves time and reduces compliance risk.

What's the most difficult part of implementing a CRM for block management? Data migration and the initial configuration. You likely have historical records of buildings, leaseholders, service charges, and major works scattered across spreadsheets, PDFs, and old systems. Pulling all that into a structured CRM format takes work. Once it's done, the day-to-day is much simpler — but the initial setup is the bottleneck. Budget 2–4 weeks for a medium-sized portfolio (10–20 buildings).

How do I track Section 20 consultations in a CRM? Create a workflow record linked to the building. Include the notice issue date, response deadline, list of leaseholders consulted, responses received, and final decision. Store all associated documents (the notice, quotes, leaseholder responses, approval records). When the consultation period ends, the CRM should flag the deadline so you know when to move to the next stage. For major works involving multiple buildings, use a template that you can replicate for each building.

Do I need separate accounting software, or can the CRM handle service charge accounts? Most CRMs don't produce formal service charge accounts natively. They can track income and expenses, but generating a compliant service charge account (with the required format, leaseholder apportionments, and narrative) usually requires integration with accounting software like Xero or QuickBooks, or a specialist block management accountant. Choose a CRM that integrates cleanly with your accounting system so data flows between them without manual re-entry.

What happens if a leaseholder lets their unit to a tenant? How do I track that? Create a unit record linking the leaseholder to the property. Then create a tenant record linked to the unit. The CRM should show: Leaseholder A owns Unit 5, Tenant B lives in Unit 5. All service charge invoices go to Leaseholder A (they're responsible for payment). Maintenance requests from Tenant B should be logged against Unit 5 and flagged to Leaseholder A. This requires a CRM that supports linked records and hierarchical structures — not all do.

How often should I update leaseholder records? At minimum, annually (lease renewal, service charge review, insurance renewal). More frequently if there are changes: new leaseholders, lease assignments, contact details, payment method changes. Some leaseholders are inactive (they've sold the lease or inherited it). Keep those records but flag them as inactive so you don't accidentally send invoices to the wrong address. Regular audits (quarterly or semi-annually) catch address changes and contact updates that leaseholders don't proactively report.

Should block management and lettings be in the same CRM, or separate systems? Same system. You'll have properties that are partly lettings and partly managed blocks. You'll have buildings with units that are leased out. Keeping everything in one CRM with clear record types (building vs. individual property, leaseholder vs. landlord vs. tenant) is cleaner than juggling two systems. The admin burden of switching between platforms and manually syncing data defeats the purpose.

How much of block management can be automated in a CRM? Reminders (renewal dates, compliance deadlines), bulk communication (send invoices to all leaseholders in a building), reporting (service charge statements), and audit trails can all be automated. What can't be automated: the judgment calls (approving major works costs, handling disputes, interpreting lease terms). A good CRM removes the administrative grind and keeps you focused on the decisions only you can make.