Make an annual mortgage check-in useful before the client asks

A practical workflow for mortgage brokers

An annual mortgage check-in can easily become a generic rate email: the same message, sent to every client, with no clear reason to respond. The broker still has to find the latest documents, establish what has changed and work out which questions are worth asking.

A better starting point is a prepared review queue. Each due file can carry a dated RBA cash-rate timeline, a small suburb briefing and a document checklist. The context helps the broker prepare the conversation; the customer’s current loan details and goals still come from the customer and their documents.

Prepare the review before opening the conversation

Start with the servicing date already stored in the broker’s system. For a mock review item linked to Richmond VIC 3121, resolve the recorded locality to HtAG locality ID VIC2167. Then retrieve one Richmond house-market summary, its historical annualised growth fields, the latest official cash-rate target and a continuous monthly cash-rate series.

The interface can turn that evidence into three compact areas:

• Review context: the annual review due date and a clearly labelled mock record identifier.
• Documents to check: the latest loan statement, the customer’s current interest rate and repayment details, and any updated income, expense or goal information the broker normally verifies.
• Dated evidence: the official cash-rate timeline and Richmond house-market observations, with their scope and source period visible.

The broker can use the prepared item to decide which documents are out of date and which questions need an answer. The screen should not calculate a new repayment, rank products or produce a recommendation. Any customer figure should remain separate from the macro and suburb data.

Keep observation, interpretation and action separate

Observation: across the continuous monthly series from 30 September 2025 to 31 August 2026, the official cash-rate target increased from 3.60% to 4.35%. The change was 0.75 percentage points, or 75 basis points, made up of three 25-basis-point increases in February, March and May 2026.

The Richmond house-market snapshot for 31 August 2026 reported a Typical Price of $1,666,826 with High confidence. The annualised-growth endpoint reported a 2.31% one-year historical price change and a 4.24% one-year historical rent change. For a one-year period, these annualised fields equal the matching cumulative changes.

Interpretation: the rate environment changed during the review window, while the selected Richmond house cohort recorded different historical rates of change for price and rent. That is enough to make a dated, document-led conversation more relevant than a generic email. It does not show what happened to an individual customer’s mortgage rate, repayments, property value or household position.

Suggested action: place the mock file in a human-reviewed queue with a prompt to verify the latest customer documents and ask what has changed since the previous review. Record the customer’s current rate, balance, repayments and goals only from the appropriate customer or lender evidence. Decide any next step through the broker’s normal fact-find, compliance and product-review process.

Use market context without turning it into lending advice

The RBA cash rate is the official cash-rate target. It is not the customer’s mortgage rate, and the 75-basis-point movement must not be copied into a customer field or presented as the change in their repayments. Lender pricing and individual loan settings can differ.

The Richmond figures describe houses across the suburb, with all bedroom counts included. Typical Price is an area-level adjusted price measure, not a valuation of the customer’s property. The growth figures are historical annualised changes. They are not forecast Capital Growth, a Growth Rate Cycle measure or an RCS score.

This workflow therefore makes no borrowing-capacity, serviceability, eligibility, pricing or refinance recommendation. Its job is narrower: give the broker current, dated context and a cleaner checklist before speaking with the client.

Reuse the evidence across the review book

The production capture used five distinct operations across five requests and returned 16 rows: one locality, one market summary, one growth record, one current cash-rate record and 12 monthly cash-rate observations. Request count, returned rows and production cost are separate measures.

Fetch the macro timeline once, then reuse it across due reviews. Cache each accepted suburb and property-type snapshot for the relevant source period, so every Richmond house review does not repeat the same market calls. Refresh according to the application’s data policy when a new source period is available. The public visual uses fixed captured data, so inspecting it creates no reader-time HtAG requests.

Implementation appendix

The HtAG API documentation covers the five approved operations:

1. GET /reference/locality — resolve Richmond, VIC 3121 and retain locality ID VIC2167.
2. GET /markets/summary — retrieve the 31 August 2026 Richmond house summary for all bedrooms.
3. GET /markets/growth/annualised — retrieve historical annualised price and rent changes for the same suburb, property type and period.
4. GET /economics/cash-rate — retrieve the latest RBA official cash-rate target.
5. GET /economics/cash-rate/series — retrieve the full monthly series with changes_only=false.