The weekly review should identify the decision behind each variance

Every difference gets explained and nothing changes

Imagine the weekly financial meeting spends half an hour describing why receipts and costs differed from the forecast. The explanations are plausible, but nobody records a decision or checks what happened afterwards.

A variance review should support action where action is needed. Distinguish information worth noting from a difference that changes a payment, collection or operating decision.

Choose the material differences

Focus on movements significant enough to affect the business's current decisions. Explain how the team identifies them and allow unusual small items to be raised where they indicate a wider problem.

Avoid treating a single percentage threshold as suitable for every line. A small unexpected payment can matter when cash is tight, while a larger timing movement may already have a clear explanation.

Establish the cause before the response

Check whether the difference reflects timing, volume, price, an incorrect assumption or a reporting error. Do not assign an operational remedy to a bookkeeping mistake or call a missed receipt a permanent loss without evidence.

business.gov.au's cash-flow guidance recommends monitoring expected and actual cash movements. Use the comparison to identify the question requiring attention rather than simply producing a longer commentary column.

Source: business.gov.au: Guide to managing cash flow

Write the decision in one sentence

For each actionable issue, record what will be done, who owns it and when the result will be reviewed. Identify any information needed before the decision can be finalised.

For example, a receipt shortfall may require the account owner to confirm which invoices the customer has approved before management revises the outgoing-payment plan. The action should address the actual uncertainty.

Check whether the action worked

At the next meeting, review the result against the recorded decision. If the action did not resolve the issue, explain what changed and whether a different response or advice is required.

Do not close an item merely because an email was sent. Completion should relate to the outcome the meeting needed, such as a confirmed allocation or a corrected forecast assumption.

Use a short decision log next week

Add a small action section to the next financial review. Carry unresolved decisions forward with their current status and remove closed items only after the result is recorded.

The aim is a shorter path from information to a useful response. A clear decision log helps the business learn whether its weekly review is changing what people do, not just how much they know.