You won the block, now the hard part
The directors have chosen you, the notice has been served, and the handover date is set. What arrives from the outgoing agent is a zip file: a spreadsheet of leaseholders with half the email addresses missing, PDF ledger statements, a list of contractors, some scanned leases, last year's accounts and a note saying the rest will follow.
Someone on your team now spends days typing leaseholder details and opening balances into your block management system, while also trying to work out which contracts are live, which checks are due and what is outstanding with the insurers.
Why every takeover starts from scratch
Handover information comes in whatever shape the outgoing agent or developer keeps it. There is no common format, and the outgoing agent has little reason to make it tidy. The data also contains errors: old owners, wrong addresses, balances that do not agree with the ledger.
Your team handles each takeover as a one-off, so the knowledge of what to ask for and what usually goes wrong lives with whoever did the last one.
What a messy takeover costs you
The first months of a new instruction are when directors judge you. If demands go to the wrong addresses, opening balances are wrong or a contractor is not paid because nobody knew about the contract, that first impression is hard to undo.
There is also the staff cost of re-keying everything, and the risk of missing something important, such as an ongoing consultation or an open claim, that was buried in the handover files.
Our takeover process
We build a repeatable takeover toolkit that turns whatever arrives into clean, checked data, with a clear list of what is still missing.
- Handover checklist: a request list for the outgoing agent covering leaseholders, balances, funds, contracts, insurance, checks, open works, claims, consultations and documents, tracked item by item.
- Extraction: spreadsheets and PDFs, including scanned ones, are read by document models and turned into structured records: leaseholders, units, balances, contracts and dates.
- Cross-checks: leaseholder names are compared against the Land Registry information you hold, balances are checked against the ledger totals, and duplicates or gaps are flagged.
- Missing list: anything absent or inconsistent is listed for your team to request from the outgoing agent, with the evidence attached.
- Loading: once approved, clean data is imported into your block management system through its import tools or API.
- Opening file: open works, claims, consultations and upcoming checks are loaded into your trackers so the property manager starts with a full picture.
| Handover item | Usually arrives as | What we do with it |
|---|---|---|
| Leaseholder list | Spreadsheet with gaps | Cleaned, deduplicated, cross-checked |
| Balances and funds | PDF statements | Extracted and reconciled to totals |
| Contracts | List or folder of PDFs | Dates, values and renewal terms extracted |
| Building checks | Certificates in a folder | Dates read and loaded into the checks calendar |
| Open issues | Emails and notes | Summarised into a starting task list |
Your first months with the new block
Demands go to the right people, balances match, contractors are known and paid, and the property manager starts with a clear list of what is open. The missing information list gives you a documented trail of what was requested from the outgoing agent and when.
Because the process is repeatable, the next takeover is easier than the last, and your team does not rely on one person's memory of how it went.
Is your takeover process like this?
- Handover data is re-keyed into your system by hand.
- Opening balances have been wrong on new instructions.
- Contracts or checks were discovered months after taking a block on.
- Each takeover depends on one experienced person.
- There is no standard list of what you ask the outgoing agent for.