One late notice, and £173,000 of a £184,000 roof stops being recoverable.
Section 20 caps what you can recover at £250 a flat if the consultation is not run properly. Forty-four flats at £250 is £11,000 against £184,000 spent, leaving £173,000 the client company has to find from somewhere else. This consultation was correct at every stage but one — the Statement of Estimates went out six days late. Block management is a business where the software either holds the statutory clock, or the firm absorbs the difference.
We built the screens that make it stop — every one of them live and clickable below. Then we build the same for your agency, with no commitment: the screens your team would use, in your language and your brand, linked up so you can walk your own process through them. Open it, show your team — if it's a fit, we'll make a detailed, priced proposal.
Marlbourne Property Management does not exist. We cannot show live client systems, so this study is built around a fictional managing agent — invented firm, invented buildings, invented people, invented figures. What is not invented is the work: the statutory processes, the sequence of notices, the obligations, the data structures and the failure modes are all real, and the screens are genuine working pages rather than pictures of pages. Every mockup on this page opens and responds to clicks.
What this is not: a service charge accounting package. It does not hold the client account, raise the demands or produce the year-end statements, and it is not something an agency would swap its accounting system for. Displacing one of those is a far larger undertaking than this. Your accounting, your banking and your auditor all stay exactly where they are.
What it is: the layer none of them owns — the Section 20 notice that went out too late to recover the money, the certificate that expired between visits, the works order nobody closed, and the compliance calendar that currently lives in somebody's diary. Where a tool already does its job, we integrate with it rather than replace it.
On scope: the law referred to throughout is that of England and Wales — principally the Landlord and Tenant Act 1985 and the Building Safety Act 2022. Scotland and Northern Ireland have materially different regimes, and a system built for either would need a different statutory core.
A managing agent that has outgrown its spreadsheets
Marlbourne manages residential blocks across the Thames Valley and the South East. It is a good firm with a serious problem: the business has roughly doubled in five years and the systems have not moved. The accounts package handles the money. Everything that decides whether the money is recoverable lives in Word documents, Outlook and a shared drive.
- Blocks under management
- 184
- Units
- 6,412
- Staff
- 22
- Property managers
- 8
- Local authorities covered
- 11
- Higher-risk buildings
- 9
- Service charge demanded, year
- £9.74m
- Client companies (RMC / RTM)
- 131
- Certificates to keep in date
- 1,842
- Current systems
- 4 + shared drive
Seven failures, and what each one actually costs
None of these is a technology problem in the abstract. Each one is a specific way a managing agent loses money, loses time, or acquires a liability it cannot see.
One record per building, and a clock on everything the law dates
The system is built around two ideas. First, the building is the record — every certificate, lease term, works order, document and consultation hangs off it, so nothing has to be assembled later. Second, anything with a statutory or contractual date drives a task before it becomes a problem, and keeps the evidence of what was served, to whom, and when.
Seven screens follow. Each one opens as a real page — click through them.
Seven screens. Every one of them real.
No screenshots, no slideware — each screen below is a working page, rendered live in its frame. Click a frame or its link to open the full screen in a new tab and use it.
Portfolio overview
The morning view for a director or an operations manager. Not a wall of vanity metrics — a ranked list of what carries consequence this week, with the statutory items above the financial ones and the reason each item is on the list.
Section 20 consultation clock
The screen this whole study is built around. Five stages, each with its statutory date, its service evidence, and its observation log. The estimates sit against the stage that requires them, the leaseholder's nominated contractor is tracked separately because it must be included regardless of price, and no stage can close without recording who authorised it.
It watches both triggers, not just the famous one: qualifying works above £250 a leaseholder, and qualifying long-term agreements above £100 a leaseholder a year. The system applies the right test to the right agreement rather than relying on somebody remembering there are two.
Building record
Everything about one block in one place: units and apportionments read from the lease, key dates, the reserve fund against the ten-year plan, the building safety information as structured data rather than a folder of scans, and documents filed against the obligation they evidence.
Compliance & building safety register
One register across all 184 blocks, sorted by consequence rather than by date entered. A certificate uploaded against an obligation sets its own next due date from the interval in the regulation. Higher-risk buildings carry their safety case readiness, their open gaps, and who is accountable.
Service charges, budgets & recovery
The budget builder pulls prior-year actuals and live contract uplifts, then shows the per-unit consequence of every line before the demand goes out. Demand runs refuse to issue without the prescribed information. Credit control is a defined ladder where nothing escalates past final notice without a person deciding and the system recording who.
Works orders & contractor compliance
Committed cost hits the budget the day the order is raised, not the day the invoice arrives. An order that would take a budget head past its limit cannot be approved by a property manager and routes to the client directors with the variance already worked out. A contractor whose cover has lapsed is blocked the same day, and the exposure it creates is shown in full.
Leaseholder & director portal
A second audience, so a second interface — no staff navigation, no jargon, and the same statutory clock rewritten in plain English so a leaseholder can see exactly where a consultation has got to and how long they have to comment. Documents appear the moment they are filed. Issues go straight to the named property manager with a reference and a date.
Statutory notices can be served through it, but only where that leaseholder has agreed in writing to electronic service. The system holds the consent per unit, records when it was given, and falls back to post for anyone who has not given it — because a notice served by a route the leaseholder never accepted is a notice that was not validly served.
Statutory core first, because that is where the money is
Four phases of two weeks each — eight weeks end to end. The order matters as much as the speed: the statutory core goes live first, so the firm stops losing recoverability in week four rather than week fourteen. Each phase ends with something the team actually uses, not a demo.
Discovery & data
Weeks 1–2.
- Lease abstraction rules — apportionment, charge dates, reserve permissions
- Migrate blocks, units, leaseholders
- Map the obligation set and intervals
- Agree approval limits and escalation
Statutory core
Weeks 3–4.
- Section 20 consultation engine and evidence trail
- Compliance register with automatic next-due dates
- Building safety record and gap tracking
- Building record and document filing
Finance & works
Weeks 5–6.
- Budget builder with per-unit impact
- Demand runs and prescribed information checks
- Credit control ladder
- Works orders, committed cost, contractor compliance
Portal & rollout
Weeks 7–8.
- Leaseholder and director portal
- Parallel run on a pilot group of blocks
- Training by role, not by feature
- Switch-off plan for the spreadsheets
Eight weeks is possible because most of it already exists. The engine underneath — the client and property records, document handling, approval limits, escalation rules, the portal — is running in production across six sectors already. What actually gets built for a managing agent is the statutory core: the consultation stages, the obligation intervals, the apportionment rules read from the lease. That is the part this study is about, and it is the part we would spend the eight weeks getting right.
What is real here, and what is not
Real
- The statutory processes, the notice sequence, and the consequences of getting them wrong
- The obligations, intervals and data structures behind every screen
- The failure modes — all seven are drawn from how managing agents actually work
- The screens themselves: working HTML, not images, built the way we build the real thing
- Our track record. Sentient has built systems of this shape for medical tourism, student management, retrofit and remediation, financial brokerage, property management and lead response — six live platforms across six sectors
Not real
- Marlbourne Property Management. It is invented, along with its buildings, staff, contractors and leaseholders
- Every figure on every screen. The numbers are constructed to be plausible, not measured
- Any claimed outcome. We have deliberately not put a saving or a return on this page, because we would be making it up
- Any resemblance to a client. We do not show live client systems, which is precisely why this study exists
The engine underneath is already in production
The difficult parts of this system exist and run today — they are just doing it for other sectors. Live platforms, with the same client and case records, document handling, approval limits, escalation rules and portal at the centre of each:
- Medical tourism
- Student management
- Retrofit & remediation
- Financial brokerage
- Property management
That is why the working mockup is a realistic offer: we are not sketching a new product to sell you, we are showing you what the existing one would look like with your stages, your language and your brand on it — before any build begins.
We would rather show you your own screens
This took a fictional agency and made its process visible. The same exercise works better with a real one — your buildings, your language, your brand — and it costs you nothing to find out whether it is worth building.
A conversation about your buildings, your managers and where the money stops being recoverable.
A working mockup of your own process — clickable, in your language and your brand.
Click through it with your team. If it's a fit, we'll come back with a detailed, priced proposal. If not, we part on good terms.
Ready to see your own screens running like this?
Tell us how your agency actually runs — your buildings, your consultations, your compliance calendar, where the money leaks — and we'll show you how we'd build it. If it's a fit, we build your screens. No commitment — and a detailed, priced proposal only if you ask for one.
What happens next
- We reply within one working day — a person who has read your note, not a bot.
- If it's a fit, we build your mockup — the screens above, re-skinned to your process and your brand.
- You click through it before anyone commits — if it earns the build, we talk about that.
Every enquiry is confidential — we never share your details, and we never put client work on a website.
Thank You!
Your message is on its way. We'll be in touch with you directly — usually within one working day.