Budget review process in practice

Johorix - Budget Review

Budgets don't
fail at year-end.
They fail in March.

A site built around the part of financial planning most guides skip entirely.

Written from inside the process - not from a textbook or a pitch deck.

Specific enough to be useful. Honest enough to be trusted.

Working through a budget review cycle

Where this started

The gap
no one writes about

Johorix started because of a specific frustration: most writing about budgeting covers either the setup phase or the annual summary. The mid-cycle review - the moment when you actually catch problems before they compound - was almost invisible in practical guides.

That gap came from years of sitting in review meetings where the numbers were technically correct but the conversation was going nowhere. The data existed. The framework for reading it didn't.

This site exists to fill that specific gap. Not budgeting in general - the review process in particular.

Hands-on budget analysis session

Lived experience

The subject isn't studied here - it's worked through

The content on this site comes from direct involvement in budget review cycles across different organisation sizes and structures. That includes quarterly variance analysis, mid-year reforecasting, and the kind of line-by-line interrogation that happens when a department is significantly off-track.

That background shapes what gets written - and what gets left out. There's no interest in covering ground that's already well-documented elsewhere. The focus stays on the parts of the process that are genuinely underexplained.

How
content connects

Each piece on this site is written with a specific position in the review cycle in mind. Reading them in sequence builds a working understanding of the full process - not just isolated techniques.

Foundations first

Pieces on core review mechanics - variance categories, timing, approval chains - are written to stand alone before anything else.

Layered depth

More specific topics - scenario modelling, stakeholder communication, reforecast triggers - reference earlier pieces rather than re-explaining basics.

Explicit links

Related pieces are linked within the text where the connection is meaningful - not as a navigation pattern, but because the ideas genuinely depend on each other.

Cumulative reading

Someone who reads across the full site ends up with a coherent mental model of the review process - not a collection of unrelated tips.

Honest
about the fit

This site is not for everyone - and that's intentional. The content assumes you're already inside some kind of financial planning process, even a basic one.

Good fit

Finance professionals, team leads and operations managers who participate in budget reviews and want to understand the process more deeply. Also useful for anyone who has to present budget data to stakeholders and wants clearer frameworks for doing that.

Less useful

If you're looking for personal budgeting advice, investment strategies, or an introduction to accounting basics - this isn't the right place. The focus is narrow by design: the organisational budget review cycle specifically.

Finance professional reviewing budget documents

Where
to start

01

Read the About page

It explains the specific lens this site uses - which saves time if you're trying to decide whether the content is relevant to your situation.

02

Go to the Blog

Start with whichever topic matches the stage of the review cycle you're currently in - the pieces are written to be useful immediately, not just as background reading.

03

Get in touch if something's missing

If a specific part of the review process isn't covered and you'd find it useful, reach out. The content roadmap is shaped partly by what readers actually need.

Budget review meeting in progress
Analysing budget variance data

Read more,
ask more

The blog is where the detailed work lives. Each piece is written to be read in full - not skimmed for bullet points. If you want to follow along as new content is published, the contact page is the best way to stay connected.

Questions are welcome. If something in a piece is unclear, or if you disagree with a framing, write in. That kind of feedback genuinely improves what gets written next.

Go to the blog