Tenant, multi-site
Demand lands, we check the cap, you see whether to query. The query letter is a one-liner: 'cap Y3, demand exceeds by X%'.
1-line
query letter
Service charge
Caps, Schedules, Reconciliations: Done.
We pull the cap, the basis and the applicable years, then watch every demand against them.
Cap, basis, years.
Brentmoor's £13,356 cap, basis and years stated.
Demands and reconciliations on the same clock.
Service-charge demands have a contractual reconciliation window. Late reconciliation is a tenant lever; we surface the deadline before the landlord misses it.
- Service-charge year-endYear closes
Actuals frozen. Landlord has the contractual reconciliation window from this date.
- + 60 daysReconciliation drafted
Itemised lines uploaded against the cap. Drift vs prior year computed.
- + 180 daysDemand reconciled
Reconciled demand sent. Tenant team sees the cap check the same day the demand lands.
- Reconciliation lateTenant lever
Missed window flags on the dashboard. The tenant team now has a contractual point to query.
Every demand, every reconciliation, written atomically.
Demand uploaded, cap checked, variance recorded, dispute (if any) attached. The full thread sits in the audit log; the next reconciliation starts with the baseline.
The cap, the basis, and the years it applies.
A cap with no indexation is rare; a cap with no applicable-years schedule is rarer. We capture all three so the demand can be checked against the clause.
Cap value & basis
Numeric cap pulled from the clause, with the indexation basis (CPI, RPI, fixed %) tagged for portfolio analytics.
Applicable-years schedule
Caps often apply only to specific years (Y1-3, then open). The applicable-years window extracted so the cap isn't applied where it doesn't.
Reconciliation alerts
Compare actual demand vs cap. Within 5% of cap: flag. Over cap: red. Tenant team sees the breach before they have to argue it.
Demand vs schedule
The annual reconciliation should fall in a specific window. Late reconciliation is a tenant lever; we flag the missed window.
Itemised demand storage
Upload the demand; itemised lines stored against the cap. Future demands have a baseline for variance analysis.
Tenant + landlord views
Tenant: 'is this fair?'. Landlord: 'am I within the cap?'. Same data, two dashboards.
Anyone with a service-charge dispute waiting to happen.
Service-charge disputes are the most common landlord/tenant friction. The cap clause is the most-cited evidence. Have it ready.
Landlord, managing agent
Reconciliation dates per lease are different. Our pipeline view scheduled the reconciliation work so demands go out compliantly.
Per-lease
reconciliation pipeline
MAT estates team
Academies often have low caps with strict indexation. Variance alerts go to the trust's finance director, not just estates.
Finance-routed
variance alerts
Hotel Group
Shopping-centre service charges with large caps. Itemised line-level storage surfaces the categories driving year-on-year drift.
Line-level
drift analysis
Related
Other Lease Topics.
The rest of what we pull out of a lease, each tied back to the source page.
The Cap Exists. Make Sure It's Enforced.
14-day Pro trial. No card. Lease parsing on every paid tier.