When does a body corporate legally come into existence?

Under s.35(3) of the Unit Titles Act, registration of a body corporate is automatically triggered when a property reaches five or more unit owners. Properties with fewer than five owners operate on a different track (s.35(4)) — registered by-laws apply, but a formal body corporate is not required. The handover obligations intensify once the five-owner threshold is crossed.

What is the difference between a building with fewer than five owners and one with five or more?

Below five owners: by-laws govern, but no registered body corporate, no formal committee structure under ss.35–63. At five or more: body corporate must register, hold AGMs, maintain an ownership register (s.51), collect service charges (ss.57–61), and comply with the full governance framework. Many new developments cross this threshold within the first sales cycle — handover planning should assume five owners, not three.

What documents must a developer provide at handover under Section 37?

Section 37 requires the developer to hand over critical documents including as-built architectural and engineering plans, warranties and service logs for major plant (lifts, generators, pumps), insurance policies, the ownership register foundation, registered by-laws, and financial records showing opening admin and sinking fund balances. The handover must enable the new committee to operate without relying on the developer's informal records.

When must the first AGM be held after committee election?

Section 48(2) requires the first AGM within three months of the committee's election. Subsequent AGMs must be held at least annually, within 15 months of the previous one (s.48(3)). The first AGM approves the budget (s.58(5)), elects or confirms committee members, and establishes the governance rhythm for the building's operational life.

Can owners refuse handover if documents are incomplete?

Owners should not accept operational control — or sign acceptance minutes — until the Section 37 document pack is complete and verified. Incomplete handover is the leading cause of warranty loss, missing as-builts, and developer fee collection continuing indefinitely. Document gaps at handover become special levies within 18–24 months when equipment fails and nobody knows who serviced it last.

Developer handover checklist: taking control of your new body corporate in Tanzania

The key ceremony is perfect. Ribbons, speeches, photos for the developer’s website. Unit owners receive their title deeds and walk through apartments that still smell of fresh paint. Three months later, the lift grinds. The interim chairman asks the developer for the service log. The developer’s site office has closed. The warranty folder — if it ever existed — is in a project manager’s personal email account. The “management fee” the developer collected for twelve months never sat in a body corporate bank account. Nobody can find the as-built drawings for the pump room.

The keys were handed over. Control was not.

The transition from developer-led management to owner-governed body corporate is the highest-risk moment in a building’s life. Get it wrong, and you spend the next decade paying for it in special levies, lost warranties, and committee burnout.

The legal baseline — before the checklist

Four sections define the handover landscape:

Section	Requirement
s.35(3)	Five or more owners → body corporate must register
s.35(4)	Fewer than five owners → by-laws track, no formal body corporate
s.37	Developer must hand over documents, records, and operational assets
s.48(2)	First AGM within three months of committee election
s.51	Ownership register — every title, every owner, every fractional share

The myth to dispel: The developer does not manage your building forever. Their role is construction, sales support, and statutory handover — then exit. Buildings that never complete handover remain dependent on a entity with no legal obligation to stay, collecting fees into accounts owners cannot audit.

For the full statutory picture, see the Unit Titles Act explainer.

The five-owner rule — plan for it on day one

Many developments sell unit one through four under interim arrangements. The moment the fifth title transfers, s.35(3) triggers. The body corporate must exist. AGMs must happen. Service charges must flow through governed accounts.

Committee mistake: Waiting until “we have enough owners to bother” before setting up registers, bank accounts, and by-laws. By unit five, you are already non-compliant — and the developer may have left.

Owners	Governance status
1–4	By-laws apply; interim management typical
5+	Body corporate registration mandatory; full ss.35–63 framework

Interim committees in new developments should operate as if the five-owner threshold is imminent — because in active sales, it usually is.

The ultimate handover checklist

Use this checklist before signing any handover acceptance. Do not mark handover complete until every item is verified — not promised.

Legal and registration

Body corporate registration certificate (once five owners reached)
Registered by-laws filed with Land Registry (s.50)
Master deed with fractional share schedule — every unit mapped
Unit title numbers cross-checked against physical units on site
List of any pending title transfers or developer-retained units
Developer management agreement — termination date and final accounting

Technical and facilities

As-built architectural drawings (all floors, common areas, roof)
As-built engineering drawings (structural, MEP, pump room, lift shaft)
Elevator installation certificate, warranty, and service contract
Generator warranty, commissioning report, and fuel supplier contract
Water pump and tank specifications with service history
Defects liability period documentation — start date, end date, scope
Security system, CCTV, and access control handover with admin credentials
Fire safety equipment register and last inspection certificate
Waste management and fumigation contracts

Financial

Separate body corporate bank account — not developer’s account
Opening admin fund balance documented with bank statement
Opening sinking fund balance documented — verify 5% allocation plan
Service charge schedule and first-year budget draft for AGM approval
List of owner arrears, developer subsidies, or unsettled accounts
All supplier contracts with payment terms and notice periods
Insurance policies (s.54) — building, public liability, committee indemnity

Governance

Draft ownership register per s.51 — title number, owner, fractional share, occupier
Tenant notification log (s.31 — seven-day reporting requirement)
First AGM notice template with quorum calculation worked out
Committee election records and filing plan (s.47 — 15 days to Land Registry)
Minute book or digital minute system — inaugural meeting recorded
Clearance certificate process documented for future unit sales (s.30)

Failure modes — what happens when handover is botched

Developer stays as “manager” indefinitely. Fees continue to a developer account. Owners have no AGM-approved budget, no elected committee on record, and no legal standing to challenge expenditures. This can persist for years.

Warranties vanish. The lift fails in month fourteen. The warranty required service every six months. Nobody has the service log. The manufacturer declines coverage. Owners pay full replacement cost — a special levy that proper handover would have prevented.

Register never established. Unit six sells before unit three’s ownership change is recorded. The new owner at unit six does not receive AGM notice. A budget passes without their vote. They challenge the service charge increase. The entire AGM is contestable.

Financial co-mingling discovered at first audit. The developer collected “service charges” that included a markup for “management.” No sinking fund was ever funded. When RERA or an external auditor asks for separated accounts, there is nothing to show.

For what auditors expect once handover is complete, see what audit-ready records look like.

The first 90 days after handover

Period	Priority
Days 1–14	Verify bank account, confirm register, inventory all warranties
Days 15–30	Elect interim committee if not done; schedule first AGM
Days 31–60	Issue first AGM notice with budget papers and sinking fund statement
Days 61–90	Hold first AGM; file committee changes within 15 days (s.47)

The first AGM is not a formality. It is the meeting that legally authorises service charge collection (s.58(5)), approves the admin and sinking fund budgets, and elects the committee that will govern for the next year. For the full workflow, see how to run a clean AGM.

Swahili agenda anchor for owners:

Mkutano wa mwaka wa kwanza wa mwaka — uidhinishaji wa bajeti na uchaguzi wa kamati.

Born-digital vs blank spreadsheet

The worst handover gift a developer can give is an empty Excel file and a WhatsApp group. The best is a pre-configured operating system:

Ownership register populated from title plan — every unit, every fractional share calculated.
Admin and sinking fund accounts separated from day one.
First AGM pack generated from live data — not assembled from scattered PDFs.
Clearance certificate workflow ready for the first resale.

Developers who deploy Kasri before key handover give the inaugural chairman a login, not a homework assignment. Owners who inherit a blank spreadsheet spend their first year reconstructing what the developer already knew — and lose warranties and trust in the process.

Handover and the clearance certificate chain

Every unit sold after handover requires a clearance certificate at transfer. Buildings that establish clearance workflow at handover — live ledger, logged PDFs, dated issuance — protect buyers from day one. Buildings that defer it discover inherited arrears at the first resale, often from the developer’s own unsettled accounts.

RERA-readiness starts at handover

The RERA-readiness checklist assumes twelve operational items exist: digital ownership register, tenant register, separated funds, AGM minutes, clearance certificate log, and more. Every item is easier to establish at handover than to reconstruct three years later from a developer’s abandoned site office.

Handover is not the end of the developer’s responsibility. It is the beginning of the body corporate’s compliance life.

This week’s action

If you are a unit owner in a new development: Share this checklist with your interim committee. Do not accept handover until Section 37 documents are verified in hand — not emailed “soon.”

If you are on an interim committee: Schedule a handover audit meeting with the developer. Walk the checklist line by line. Record what is missing in meeting minutes.

If you are a developer: Complete handover before site office closure. Pre-configure governance systems while you still have project staff who know where the pump room is.

Book a Kasri demo for developer handover deployments — pre-configured registers, fractional shares, and first AGM packs before keys are cut.

Updated July 2026 for RERA draft status.