Portfolio Reporting for Property Development: KPIs and Pack

Your board does not care that Estate B poured slabs on time if the whole business runs out of cash in March. Once a South African developer runs three or four schemes at once, the monthly report changes role. It stops being a project update. It becomes the main tool for deciding where money, people and attention go next. Most portfolio reports fail at that job. They arrive late, and every scheme looks green until it suddenly turns red.

This guide explains how to build portfolio reporting for property development that a board, an equity partner and a senior lender can use. It covers the KPIs to track across estates, the structure of a monthly pack and RAG rules (red, amber, green status). It also covers cash flow and drawdown consolidation, sales against construction, and the usual traps when adding schemes together.

Who reads a portfolio report and what they need from it

A portfolio report has three or four readers, and each one asks a different question. One pack written for everyone ends up as 40 pages that nobody reads past page three.

Start by naming the readers and the decision each one has to make:

Reader	The question they ask	What they need to see	Cadence
Managing Director / Owner	Which scheme needs me this month?	Ranked problems, cash headroom, decisions pending	Monthly, plus a weekly flash
Board / investment committee	Is the business on track, and is the next land deal safe?	Portfolio margin, peak funding, risk register	Monthly or quarterly
Senior lender and the bank’s QS	Is the loan secure, and is each drawdown justified?	Certified progress, cost to complete, covenant headroom, pre-sales	Monthly, per facility
Equity or mezzanine partner	When do I get my money back, and at what return?	Forecast profit, timing of transfers, distributions	Quarterly

Some terms in that table. A drawdown is a payment released from the development loan (the facility). The bank’s QS (quantity surveyor) checks site progress before each one. Covenants are loan conditions, such as minimum pre-sales, and headroom is your margin before you break one. Peak funding is the month the business needs the most cash. A mezzanine partner lends behind the bank, at a higher return.

Two rules follow. First, the lender pack is per facility and the board pack is per portfolio, so keep them separate. Second, the board pack is for decisions. Each page ends with “no action needed” or with a decision, an owner and a date.

The core KPIs to track across every estate

Pick a small set of KPIs, define them once, and calculate them the same way on every scheme. Comparing estates is the whole point of portfolio reporting. That only works if “percentage complete” means the same thing in Midrand as it does in Ballito.

Most residential developers end up with KPIs like these after a few reporting cycles. The RAG thresholds are examples only. Set your own with your board and your lenders.

KPI	How to define it	Example RAG rule
Progress vs plan	Weighted milestone % complete per unit, rolled up per estate, against the baseline programme	Red if more than 5 percentage points behind
Build duration per unit	Days from setting out to practical completion	Red if 15% over target
Cost to complete	Committed cost not yet paid, plus a forecast for work not yet ordered	Red if forecast final cost is above budget plus contingency
Forecast margin	Profit on cost per estate, against the feasibility study (lenders often look for 15% to 20%)	Red below the floor agreed with the board or lender
Drawdowns certified vs forecast	Value certified by the bank’s QS this month, against the cash flow forecast	Red if under 85% of forecast
Sales funnel	Units reserved, sold, bond granted, transferred	Red if pre-sales fall below the lender’s condition
Days to transfer	From bond granted to registration at the Deeds Office	Red above 90 days
Approvals outstanding	Rezoning and township approvals, building plans, NHBRC enrolment, occupation certificates	Red if it blocks a phase
Cash headroom	Undrawn facility plus cash, minus the next 3 months’ outflow	Red below one month of outflow

A note on weighted milestones. Most developers turn unit progress into a percentage by giving each stage a weight: foundations, slab, wall plate, roof, finishes. The exact weights matter less than using the same list on every estate. If one site counts roof trusses as 10% and another as 6%, the total means nothing.

Test your KPI set: if you cannot calculate a KPI the same way for every scheme from records that already exist on site, drop it. A KPI that needs a special spreadsheet every month will be wrong by the third month.

How to structure a monthly portfolio pack

A good portfolio pack reads from the top down: one page to decide, then detail only for the schemes that need it. Board members should be able to stop after page two and still know what to do.

This structure works for three to ten schemes:

One-page summary. Portfolio margin, cash headroom, peak funding month, the three biggest risks and the decisions you need. Write it in sentences, not only charts.
RAG grid. One row per estate and one column per KPI from the table above. This is the page people remember.
Consolidated cash flow and drawdowns. A 12-month forward view across all schemes, with each facility shown against its limit.
Sales against construction. Units built, sold and transferred per estate, with the gaps highlighted.
Cost and margin. Budget, committed, actual and cost to complete per estate, with the change since last month.
Approvals and compliance. Outstanding municipal approvals, NHBRC enrolments and occupation certificates, with expected dates and the cost of delay.
Exceptions only. One page for each red scheme. Green schemes get no page.
Risk register and decisions log. What you decided last month, whether it happened, and what is new.

Keep the same shape every month so readers know where to look. Our guide to residential property development management software for multi-project portfolios compares single-project and portfolio needs.

Setting RAG rules that mean something

RAG status only works if you write the rules down before the numbers come in. Otherwise every project manager reports amber, ambers turn red overnight, and the board stops trusting the colours.

Three habits make RAG useful:

Write a threshold for each KPI. “Red if forecast margin drops below 15%” is a rule. “Red if we are worried” is a mood.
Show the trend next to the colour. An amber that was green last month is more urgent than one that has been stable for six months. Add an arrow.
Separate the status from the cause. A red programme because the municipality or Eskom has not connected bulk electricity is a different problem from a slow contractor. The board should see which one it is.

Watch for “watermelon” reporting: green outside, red inside. The usual sign is a scheme that stays green on cost while its contingency drains. Report contingency used as its own line, and you will see the drain early. Our guide to construction cost overruns in South Africa covers the usual causes.

Still building the board pack from WhatsApp updates and site visits? Wakha brings every estate into one software, with Gantt progress, budget vs actual in ZAR, a cash flow command centre and multi-project portfolio analytics: see a product demo.

Consolidating cash flow and drawdowns across schemes

Each scheme has its own facility, but the business has one bank balance, so report cash at both levels. The real risk in a portfolio is rarely one scheme running short. It is two or three schemes needing equity in the same month.

Build the consolidated view in this order:

Forecast monthly cash in and out for each scheme: land, contractor payments, fees, municipal contributions, interest, drawdowns, transfer proceeds and retention releases.
Link each scheme to its facility. Show the drawn balance against the limit.
Add the schemes together to get the portfolio’s net cash position for each month.
Mark the peak funding month and the equity the business must put in before then.

This three-estate example (figures for illustration only) shows why it matters:

Month	Estate A	Estate B	Estate C	Portfolio net
November	+R1,800,000	-R2,400,000	-R600,000	-R1,200,000
December	+R900,000	-R3,100,000	-R1,900,000	-R4,100,000
January	-R300,000	-R1,200,000	-R2,600,000	-R4,100,000
February	+R4,200,000	+R600,000	-R1,100,000	+R3,700,000

Each estate on its own looks manageable. Together, the portfolio is cash-negative three months in a row: R1,200,000 in November, then R4,100,000 in December and again in January. The business needs R9,400,000 of cover in total before February’s transfer income arrives. Most of that gap falls over the builders’ holiday, when transfers slow down. A report per project hides it.

Report drawdowns at the certified value, because the bank pays on its QS’s number. Show retention as money you still owe, with a release date. Retention is the share of each contractor payment you hold back until the work is complete. It is usually released in stages after practical completion, so on a large contract it can move millions of rand between quarters. Our guide to property development cash flow software covers forecasting for a single scheme. The funding behind each facility is covered in residential development finance in South Africa.

Reporting sales against construction

A developer gets paid at transfer, so the gap between units built and units transferred is where profit hides. If sales and construction sit in separate reports, nobody sees that gap.

Put both on one page per estate and track four numbers:

Sold but not started. Buyers are waiting for a build. Risk: bond approvals expire and buyers walk away.
Built but not sold. Finished units with no buyer. Risk: holding costs and interest, with no income in sight.
Built and sold but not transferred. The most expensive group. The sale is made on paper but stuck with conveyancers, banks or a missing occupation certificate.
Transferred. Money in the bank.

On plot-and-plan schemes, also track the bank valuer’s stage inspections. Each stage the valuer signs off releases a progress payment from the buyer’s building loan. On turnkey schemes, the full price is paid at transfer, so “built but not transferred” is the KPI to watch.

If built-but-not-transferred grows for two months in a row, the cause is usually paperwork: a late occupation certificate, a missing NHBRC document or a conveyancer backlog. Under the Housing Consumers Protection Measures Act, a bank may not lend on a new home that is not enrolled with the NHBRC. So a missing enrolment stops the buyer’s bond, and the transfer with it. These problems are cheap to fix and expensive to ignore. The NHBRC enrolment process explains the documents that most often hold transfers up.

Reporting cadence: who updates what, and when

A monthly pack is only as good as the weekly and daily data behind it. If the team records site progress once a month from memory, the pack reports what people hope happened.

This cadence works for most mid-size developers:

Frequency	Activity	Owner
Daily	Unit milestones and site diary entries	Site manager / foreman
Weekly	Transfer status with conveyancers, programme flash to the MD	Transaction manager, construction director
Monthly (day 1 to 5)	QS valuation, certified drawdown, cost to complete	QS, finance
Monthly (day 6 to 8)	Portfolio pack issued	Finance or project office
Monthly (day 10)	Board or executive committee review	MD
Quarterly	Deep dive per estate, feasibility update	Board

Most developers skip the daily step, yet it makes everything else accurate. When the site team updates each unit’s tasks and site diary on the day, the monthly percentage complete rests on current data. Software with multi-project portfolio analytics, such as Wakha, then rolls every estate up into one view. You define the KPI weights once, and the pack starts from live data.

Consolidation traps to avoid

Most portfolio numbers go wrong when you add the schemes together. These traps come up again and again.

Different cost codes per scheme. If Estate A books bulk services under “civils” and Estate B under “infrastructure”, the portfolio cost line is meaningless. Use one list of cost codes for every scheme.
Mixing committed, invoiced and paid. Pick one basis per column and label it. Build cost to complete on committed cost. Otherwise orders you have already placed drop out of the forecast.
Different cut-off dates. One QS values on the 25th, another on the last day of the month. Align the cut-offs, or the portfolio adds two different months together.
VAT treatment. Report every figure either including or excluding VAT. Do it the same way throughout, and say which on every page.
Loans between group companies. Many developers hold each estate in its own company (a special purpose vehicle, or SPV). Remove loans between those companies from the consolidated cash view, or you count the same money twice.
Old feasibility baselines. Margin “against feasibility” means little if the feasibility is three years old. Update it formally, record the date, and keep the original for comparison.

The bottom line

Good portfolio reporting for property development uses a small set of clear KPIs, calculated the same way on every scheme. Feed them with site data captured as the work happens, and present them in a pack that leads to decisions. Start with two pages: the consolidated cash flow and sales against construction. Together they show most of the problems that hurt South African developers.

FAQ

What is portfolio reporting in property development?

Portfolio reporting in property development is a regular report that brings every live scheme into one view. It covers progress, cost to complete, margin, cash flow, drawdowns and sales, measured the same way on each estate. It helps the owner, board and funders decide where money and attention go next.

What should a monthly property development portfolio report include?

A one-page summary with decisions, a RAG grid by estate, a 12-month consolidated cash flow, and sales against construction. Then cost and margin, approvals and a risk register. Add exception pages only for red schemes.

How many KPIs should a developer track across a portfolio?

Eight to twelve is usually enough. Each one must be calculated the same way on every scheme, from records that already exist.

How is a lender report different from a board report?

A lender report covers one facility. It shows certified progress, cost to complete, pre-sales and covenant headroom for that scheme. A board report covers the whole portfolio: total margin, peak funding, risks and decisions. Build both from the same data.

How do you calculate percentage complete across several estates?

Use a weighted milestone list for each unit type, with the same weights on every estate. Roll unit percentages up to the estate, then to the portfolio, weighted by budget value. Report the result against the baseline programme, so the board sees slippage as well as progress.

Related articles: