Back to Journal
Feasibility governance: versioning and the RBA calendarPhoto: SiteLogic editorial image

Feasibility

Feasibility governance: versioning and the RBA calendar

A development feasibility is a living document, not a one-off spreadsheet. Tying version control to the Reserve Bank's scheduled rate decisions gives a disciplined, defensible reason to revisit assumptions.

·Written and fact-checked . Published .·6 min read

Most feasibilities are built once, presented once, and then quietly ignored until something goes wrong. The spreadsheet gets built at acquisition, sits in a folder through the permit process, and only gets reopened when a bank wants an updated number or a builder's quote comes in over budget. By then the assumptions baked into the original model are often a year or more stale, and nobody can say exactly when they stopped being reliable.

Lachlan Voss discusses this discipline at length in his book, The Victorian Property Developer, but the practical fix is simpler than the book's full theory: treat the feasibility as a versioned document, and tie each new version to a scheduled, external event rather than to an ad hoc "something feels off" trigger. The Reserve Bank's monetary policy calendar is the cleanest anchor available, because it is public, fixed well in advance, and directly upstream of the two inputs that move a feasibility more than any other: the cost of debt and the market's appetite to pay for the finished product.

What applies

The Reserve Bank of Australia's Monetary Policy Board meets on a published schedule, available on the RBA Monetary Policy Board schedule, with each meeting followed by a decision on the cash rate target and an accompanying statement. The current RBA cash rate target is published on the same site and updated the moment a decision is announced.

This is not a Victorian planning instrument, and it does not sit inside the ordinary run of clause analysis this masthead usually covers. But no VPP clause or state tax touches a feasibility as directly as the cash rate does, because it flows straight into your debt facility's interest cost, and it shapes the borrowing capacity and risk appetite of whoever eventually buys or leases the finished product. A feasibility that ignores the calendar this decision sits on is treating a known, scheduled risk as an unknown one.

How to model it as a governance discipline

The practical version of this discipline has three parts.

First, version every feasibility file. Not "final", "final_v2", "final_v2_ACTUAL": a disciplined numbering scheme (v1.0, v1.1, v2.0) with a change log tab that records what changed, why, and against which inputs. This sounds pedantic until the day a financier asks why your projected margin moved between two board papers and you cannot reconstruct the answer.

Second, set your review cadence against the RBA schedule rather than an arbitrary calendar interval. The board meets on a fixed published rhythm through the year. A feasibility held for six months during design and permit stages will span several of these meetings. Rather than waiting for a rate movement to force a reopening of the model, build the habit of checking the current cash rate target and the tone of the accompanying statement after every scheduled decision, and log a note in the version history even when the answer is "no change required". A null result recorded on schedule is still governance. An unrecorded assumption is a liability.

Third, separate the two channels the cash rate affects, because they move on different timeframes and do not always move together. The direct channel is your own debt cost: a construction facility or land loan priced off a benchmark rate that tracks the cash rate with a lag measured in weeks. The indirect channel is buyer and tenant capacity: mortgage serviceability for your eventual purchasers, which responds to the same decisions but filters through bank lending standards and household budgets over a longer horizon. A rate hold can leave your own debt cost stable while buyer sentiment continues to soften on the back of an earlier move working through the system. Model both channels as separate line items with separate review triggers, not as a single "interest rate" assumption.

What to check before exchange

Before you commit to a site, check the date of the next two scheduled Reserve Bank meetings against your projected settlement and construction timeline. If a meeting falls between exchange and settlement, or between settlement and finance drawdown, build a contingency band into your interest cost assumption rather than locking a single point estimate. The current cash rate target, and the RBA's own published commentary on the balance of risks, are available directly from the source rather than through second-hand market commentary, and they should be the figure you cite in your model, dated to the day you checked it.

Check your own facility's margin over the relevant benchmark with your financier, because the cash rate itself is not what you pay; it is the base your bank's own facility rate is set against, and that spread is negotiated separately and can move independently of the Board's decisions.

Confirm with your broker or bank contact how quickly your specific facility re-prices following an RBA decision. Some facilities reprice within days, others carry a fixed term before adjustment. That lag determines how much runway you have between a decision and its effect on your actual cash flow.

Practical steps for a governance file

Keep a single running document, separate from the numbers workbook, that logs: the version number, the date, the trigger for the review (scheduled RBA meeting, quote received, permit condition issued, design change), and a one-line summary of what moved and by how much in relative terms. This is the document you hand to a financier, a joint venture partner, or, eventually, your own future self trying to remember why an assumption changed eighteen months ago.

Attach the source you checked to each entry rather than a remembered figure. A note that says "confirmed against the RBA cash rate page, no change since last review" is defensible in a way that "rates seem stable" is not.

Record keeping and review

The discipline pays off most clearly at the point of sale or refinance, when a valuer, financier or purchaser's due diligence team asks why the feasibility says what it says. A versioned file with dated, source-linked entries answers that question in minutes. An undated spreadsheet with a single "assumptions" tab invites exactly the kind of scrutiny that slows a settlement down.

None of this replaces professional financial advice on your specific facility or hedging position. It is a record-keeping habit, not a substitute for a broker's or an accountant's judgement on what to do about a rate movement once you have noticed one. What it buys you is certainty about when you last looked, and against what.


Published by the SiteLogic Editorial desk. Every fact traces to a primary source. See our standards and corrections register.

Fact-checked: 19 July 2026 · Review by: 19 July 2027

Sources: rba.gov.au · rba.gov.au

Our standards·

Share this article

Get new articles by email

Weekly digest of new articles. No spam. Unsubscribe any time.

Was this useful? Try the tool this post is based on:

Pro on SiteLogic. Logi: up to 60 messages a day. Logi also stops at US$15 of model cost in a Melbourne calendar month. The Developer Comms Kit and unlimited saved projects. The Strategy Lab simulator runs without Pro. Saving a scenario needs a signed-in account. $60/month or $600/year, ex GST. First 3 months are $30/month, ex GST, on monthly Pro.

See Pro pricingFree tier stays free.