Sectional Title Development Software (SA): Plans, Register & Transfers

Sectional title is the backbone of South African apartment blocks, townhouse complexes and most multi-unit residential schemes. It is also where generic project management tools quietly fall apart. A freehold house has one erf, one owner and one transfer. A sectional title development has a sectional plan, a body corporate to establish, a register of units and exclusive-use areas, and a staged sequence of transfers as buyers take occupation. Software built for a single house simply does not have the concepts to hold any of that.

This guide explains what software should manage across a sectional title development in South Africa, where standard PM tools fall short, and how to keep the build, the sales and the registration sequence aligned instead of drifting apart across spreadsheets.

Why sectional title breaks generic tools

The trouble starts with the data model. A generic project tool thinks in tasks and a single budget. A sectional title scheme thinks in units — each with a participation quota, a section number, possibly an exclusive-use area, its own sale, its own snag list and its own transfer date — all rolling up to a scheme-level programme, budget and body corporate.

When your tool has no concept of a unit register, you end up maintaining it in a spreadsheet on the side. The spreadsheet then has to be reconciled by hand against the build programme, the sales status and the conveyancer’s transfer schedule. Every one of those reconciliations is a chance for the truth to diverge, and on a sectional title scheme the truth diverging means a buyer’s transfer is delayed or a body corporate hands over with missing documents.

What sectional title development software should manage

A platform fit for a South African sectional title development needs to carry the scheme at two levels at once: the whole scheme, and each individual unit. The capabilities below are what separate real sectional title support from a project tool with a unit list bolted on.

The unit register

Every unit, its section number, participation quota, exclusive-use areas, sale status and transfer status, in one place that the build programme and the sales pipeline both read from. This is the spine of a sectional title scheme, and it should not live in a separate spreadsheet.

Body corporate set-up

A sectional title scheme ends with a body corporate that has to be handed a functioning entity: rules, an opening budget, a maintenance plan and a complete document set. Software should help assemble that handover pack as the scheme runs, not leave it to be reconstructed from email at the end.

Staged transfers

Units transfer over time as buyers take occupation, and each transfer depends on the register being opened, the unit being complete and compliant, and the conveyancing being in order. Tracking transfer readiness per unit — build complete, snags closed, compliance documents filed — keeps the conveyancer moving instead of waiting.

Shared-cost allocation

Common property — roads, services, landscaping, the clubhouse — is a real cost that has to be carried by the scheme and, ultimately, apportioned. Allocating shared costs across units on a defined basis is something generic budgets cannot do, and it is exactly the kind of multi-unit logic a sectional title scheme needs.

Keeping build, sales and registration aligned

The hardest part of a sectional title development is not any one of build, sales or registration. It is keeping all three in step. A unit that is sold but not built cannot transfer. A unit that is built but has open snags should not transfer. A scheme whose register is not yet opened cannot transfer anything.

Purpose-built software keeps these aligned by making them read from the same record. Wakha’s Gantt scheduling holds the build programme with milestones and dependencies, so a slip on a block shows up against the units in it. Its budget management and cash flow command center track cost and drawdowns in ZAR across the scheme. Its mobile site diary captures progress, snags and inspections per unit from the field. And its buyer portal gives each purchaser a progress view, which matters enormously on a sectional title scheme where buyers commit early and wait through a long build.

Sectional title need	Generic project tool	Purpose-built SA software
Unit register	Spreadsheet on the side	Built in, scheme-wide
Shared-cost allocation	Manual apportionment	Allocated across units
Per-unit transfer readiness	Untracked	Tracked with compliance
NHBRC enrolment per unit	Separate	In the compliance tracker
Body corporate handover pack	Reconstructed at the end	Assembled as you go

The sectional title sequence, in brief

To see why software has to think in units, it helps to recall how a sectional title scheme actually comes together. A land surveyor draws the sectional plan, dividing the building into sections and common property and assigning each section a participation quota. The plan is approved and the sectional title register is opened at the Deeds Office, at which point the units legally exist and can be transferred. The body corporate comes into being automatically once the first unit transfers to a buyer other than the developer, and from that moment there is a real entity with rules, a budget and a maintenance obligation.

Every one of those steps is unit-aware. The participation quota set on the plan drives levies and shared-cost shares later. The opening of the register gates every transfer. The first transfer creates the body corporate. A tool that cannot hold a unit register cannot track any of this; it can only track tasks, which is why developers end up running the real sectional title logic in a spreadsheet alongside the software they paid for.

Common sectional title mistakes software prevents

A handful of mistakes recur on sectional title developments, and most are coordination failures that a single source of truth removes.

Transferring before a unit is genuinely ready is the costliest — a transfer pushed through with open snags or a missing compliance document creates a dispute with a buyer who now owns the problem. Per-unit transfer-readiness tracking, tied to snags and compliance, prevents this. Losing track of which units are sold, reserved or available is another, and it leads to double-sales or stalled marketing; a live unit register fixes it. And handing a body corporate an incomplete document set at the end — no proper as-builts, no warranty records, no maintenance plan — sours the relationship from day one and is avoided by assembling the handover pack as the scheme runs rather than scrambling for it afterwards.

Levies, exclusive-use and the body corporate budget

A sectional title scheme does not end at practical completion; it hands over a living entity. The body corporate that comes into being needs an opening budget, a maintenance plan and a clear record of how the scheme is structured — and much of that is set during development, not after it.

Participation quotas, fixed on the sectional plan, drive each owner’s levy share and their share of common-property costs. Exclusive-use areas — a parking bay, a garden, a storeroom assigned to a particular unit — have to be recorded accurately, because they affect both what an owner controls and what they contribute. If these details are scattered across a sales spreadsheet, the conveyancer’s file and the developer’s memory, the body corporate inherits confusion on day one.

Software that holds the unit register properly carries this information through the development and into the handover pack. The opening levy budget can be built from the same cost data the developer already tracks, rather than estimated from scratch. The maintenance plan can draw on the as-built record and warranty information captured during the build. The result is a body corporate that starts with a clean, consistent picture of the scheme — which is the difference between a smooth handover and a first year of disputes.

This is the kind of detail single-project tools simply have nowhere to store, and it is why developers running sectional title schemes on generic software end up rebuilding the body corporate picture by hand at exactly the moment they are trying to exit the scheme.

Where Wakha fits

Wakha is a South African construction and property development software.. Its NHBRC and autocompliance tracker keeps enrolments and inspections in order across units; its B-BBEE procurement tracker handles spend-by-BEE-level on the build; its progress payments speak JBCC, NEC and GCC; and its financials run in ZAR with VAT.

The multi-unit, shared-cost thinking that a sectional title scheme demands is also where Wakha differentiates from tools built around single projects: costs that belong to the whole scheme can be carried and apportioned, rather than forced into a single line that hides the real per-unit picture.

If you are developing a sectional title scheme and running the unit register in a spreadsheet, see how Wakha keeps the build, the sales and the registration in step: explore Wakha.

Frequently Asked Questions

What is sectional title development software?

It is software that manages a sectional title scheme across its whole lifecycle, holding both the scheme and each individual unit — the unit register, participation quotas, build progress, sales status and transfer readiness — in one source of truth. Unlike a generic project tool, it understands that a scheme is dozens of units rolling up to a body corporate, not a single job.

Why can’t I just use a normal project management tool?

A normal project tool has no concept of a unit register, exclusive-use areas, staged transfers or shared-cost allocation. You end up maintaining those in spreadsheets and reconciling them by hand against the build and sales, which is where delays and missing documents creep in on sectional title schemes.

Can it handle staged transfers and the body corporate?

Purpose-built software tracks transfer readiness per unit — build complete, snags closed, compliance filed — so transfers move as units finish rather than all at once. It should also help assemble the body corporate handover pack as the scheme runs, instead of reconstructing it from email at the end.

Does it track NHBRC enrolment for each unit?

It should. Each residential unit needs to be enrolled with the NHBRC, and managing this across a whole scheme is far easier inside a compliance tracker than in a spreadsheet. Wakha’s NHBRC and autocompliance tracker keeps enrolments and inspections in order across the units in a scheme.

Related Articles: