What Does a UK Block Management Company Actually Do?

Block management is the professional running of a residential block of flats on behalf of whoever owns the freehold. It covers the money and the mortar: collecting the service charge, insuring the building, keeping it compliant, planning maintenance of the communal areas, and dispatching engineers when the lift or the boiler fails. A block management company, usually acting through a named managing agent, is the firm leaseholders deal with for every repair, budget, and Section 20 notice. The real job, though, is coordination: one agent between leaseholders, a freeholder, and a roster of contractors, keeping dozens of buildings moving at once.

Picture a Tuesday morning. Two leaseholders in different blocks report the same failing communal boiler within the hour. The agent logged it yesterday, has already chased the heating contractor twice, and the only record of any of it lives in an email thread nobody outside it can see.

What does a block management company actually do?

Ask a block management company what it does and you'll get a service list: service charge budgets and year-end accounts, buildings insurance, health and safety and fire compliance, planned maintenance of the communal parts, reactive repairs, and the appointment of contractors to carry all of it out. That list is accurate. It's also the brochure, not the day.

Underneath it sits a standard the industry holds itself to. The RICS Service Charge Residential Management Code, in force since 2016, sets out how a managing agent should handle other people's money: service charge funds held in trust, budgets and accounts issued clearly and on time, and demonstrable value for money on everything leaseholders are charged for. Following the Code isn't legally mandatory, but an agent departing from it has to justify why, which is why most reputable firms treat it as the floor rather than the ceiling.

The reason the service list undersells the job is that none of those duties happen in isolation. A single communal boiler repair isn't one task; it's an intake call, a triage decision about urgency, a contractor with the right cover and certification, an access arrangement with residents, a report afterwards, and an invoice that has to match what was actually done. This is what the trade means by property managing agents coordinating maintenance across landlords, tenants, and contractors, and it's why the role is less about buildings than about keeping a dozen conversations moving without dropping one.

The residential texture shows up in the small stuff. A lot of what arrives as an emergency is really an in-flat appliance the leaseholder could sort without a call-out, so a good agent deflects what isn't communal before it becomes a job. Access is its own puzzle: concierge and keyholder arrangements, tenants who work days, contractors who only have mornings free. None of it is hard on its own. All of it, multiplied across forty buildings, is the job.

Block management company vs managing agent vs freeholder: who does what

These three terms get used interchangeably, and the blur causes real confusion the moment something goes wrong. The freeholder, or a leaseholder-owned company that controls the building, owns the legal responsibility. The block management company is the firm they appoint to run it. The managing agent is your named point of contact inside that firm. Often one firm covers all the operational roles, but the responsibilities behind them don't collapse into one.

Who appoints whom depends on the building's structure. On many blocks the freeholder appoints the agent directly. Where leaseholders have formed a Residents' Management Company (RMC) or exercised their Right to Manage (RTM), that leaseholder-controlled company becomes the client and appoints the agent itself. Either way, one rule holds: statutory duties can't be delegated away. Under the Building Safety Act 2022, a managing agent can carry out building-safety work on behalf of the accountable person, but the legal duty, and the liability if it's breached, stays with the freeholder or the company that holds the building.

Here's who carries what.

The practical upshot for a leaseholder is simple. Day to day, you deal with the managing agent. But if the service is failing, the lever you actually hold points at whoever appointed them, because that's the party with the power to replace them.

The money side: service charges and Section 20

The service charge is the engine of block management, and it's also where scrutiny is fiercest. Leaseholders fund it, so leaseholders want it justified line by line. The agent sets an annual budget, collects contributions, holds them in trust, pays suppliers, and reconciles the lot at year end. Most routine spend runs through without ceremony.

Major works are the exception, and this is where the law gets specific. Under Section 20 of the Landlord and Tenant Act 1985, if a single leaseholder's share of a qualifying works bill would exceed £250, the agent has to run a formal consultation before the money is committed. Skip it and the amount recoverable from each leaseholder is capped at £250, whatever the work actually cost. For a roof or a lift replacement across a block, the gap between spent and recoverable is enough to sink a managing agent's year.

The consultation itself runs in stages with statutory notice periods, typically a 30-day window for leaseholders to respond at each stage, and it's exactly the kind of work that eats an agent's week: notices served, leaseholder observations gathered and answered, estimates obtained and circulated, all of it documented in case anyone challenges the charge at a tribunal later. It's the money and the paperwork in one job, and it lives or dies on the trail. A consultation you ran but can't evidence is, for practical purposes, a consultation you didn't run, because the recovery cap bites the moment you can't prove the process.

The part the brochure skips: one agent, several contractors, dozens of buildings

Here's what no block management company puts on its website, and what the leasehold-advice sites never quite name either: the daily bottleneck isn't the repair. It's the chase. A routine fault, one leaseholder reporting a broken door entry, is genuinely simple. The agent logs it, sends a contractor, done. The job only turns hard when it multiplies.

Run it at portfolio scale. The same failing boiler throws off five reports from five leaseholders across two blocks, each expecting a personal reply. A contracted engineer can't refuse the job, but as any managing agent will tell you, the question was never whether they'd accept it. It's whether they'd acknowledge in time. So the agent's real day isn't fixing things. It's chasing acknowledgments, chasing named engineers, chasing the RAMS, chasing the report that proves the work happened, and fielding the same "any update?" from a dozen leaseholders while they do it.

Price that out and the scale gets uncomfortable. A managing agent looking after forty blocks can be carrying a couple of hundred open repairs across them at any one time. At even ten minutes of chasing each, the acknowledgment, the named engineer, the report afterwards, that's close to a full working week every week swallowed by follow-up, before anyone judges whether the work was any good. It isn't the buildings that fail to scale. It's the chasing.

And here's the part that keeps it invisible: none of that chasing lives in a system. SLA tracking is retrospective, so a missed response is discovered after it happens rather than forecast before it. The record of who promised what, and when, sits in an email thread the leaseholder is cc'd on. When that leaseholder asks why the boiler still isn't fixed, the honest answer isn't in any dashboard. It's reconstructed from memory and a scroll back through the inbox. That is the real state of block management on most portfolios, and it's the thing the category never names.

Keeping leaseholders updated across multiple buildings

This is the question that quietly decides whether a block management company is any good. Not can it fix a boiler, but can it tell forty buildings' worth of leaseholders where their repair stands, at the same time, without a person manually typing every update. Communication in most blocks is one-way: leaseholders report, then wait, then chase, and the agent absorbs the chasing as unpaid overhead.

The reason updates lag is structural. A job's status lives in three places at once: the contractor's word, the agent's memory, and whatever the last email said. To answer "where's my repair," someone has to reconcile those three on the spot. Do that across dozens of buildings and the update itself becomes a job, which is why it usually doesn't happen until the leaseholder chases again. The building's paper trail claims one thing; what actually happened lives somewhere the leaseholder can't see. Multiply one silent repair by a portfolio and you get the pattern every managing agent knows: the same fault reported three, four, five times, because nobody could confirm it was already in hand.

This is the gap channel-first coordination is built to close. Instead of a portal nobody logs into, updates go out on the channels leaseholders already use, and the record updates as the work moves rather than after someone finds time to type it. It's the same argument behind why channel-first beats a tenant portal and the broader case for AI in property maintenance, and it's why more agents now route repairs through an AI helpdesk built for multi-building coordination rather than hire another coordinator.

What block management looks like when the chase runs itself

Everything above holds whether or not you ever change how you work. But it points somewhere. At Heyfixit we put AI agents on the coordination layer between a repair being reported and a repair being closed, across every building an agent manages at once. The agents answer the intake, triage urgency, dispatch and chase the contractor, keep each leaseholder updated on their own channel, verify the work was actually done, and match the invoice, writing every step to the record as it happens. Your existing systems stay the record. What changes is who does the chasing between the statuses.

The value lands exactly where the manual middle used to sit. Coordination labour comes off the agent's desk, leaseholders get answers without chasing, and the record is audit-ready because it was captured as the work happened, not reconstructed for a Section 20 challenge months later. Across live deployments in the UK and UAE, this has driven a 50–60% reduction in helpdesk labour costs.

The honest boundary: we don't make the judgment calls. The agents assemble, chase, verify, and recommend; a person still approves the spend, signs off major works, and owns every safety decision. Judgment stays human, always. We're a coordination layer on top of the tools you already run, not a replacement for your managing agent or your systems. If the chase across your buildings is where the week actually disappears, that's the part we take off your desk. See how the coordination layer works.

Cover image by Egor Myznik on Unsplash.

Vishak C Prakash

Co-Founder & CEO

Vishak spent six years as a digital transformation consultant to facilities management and real estate operators across the UK, Middle East, Canada, and Australia — working with teams at CBRE, Siemens UK, British Land, and Brookfield. He now runs Heyfixit, building AI agents for facilities management.

LinkedIn