A financial model review workflow that leaves evidence

For: Analyst or finance manager reviewing a model they did not build

A financial model review workflow moves from a formula check to a version comparison and ends with a written list of findings. Each finding names the cell, the problem and the fix. The point is evidence: a reviewer who says row 27 was overwritten has to show it.

The situation

Someone else built the model, the deadline is close, and the question is not whether it is elegant but whether it is wrong. The reviewer needs to find the faults that change a number, fast, and be able to show where each one is.

What the work looks like today

Most reviews start with Go To Special, choosing Constants to surface typed numbers (Microsoft Support). Then the totals get traced with Trace Precedents, and if the workbook has changed since the last version, Spreadsheet Compare shows what moved between the two files.

Each of those is a separate operation with its own output. Nothing joins them into a list that can be sent to the model owner.

Where CalcoraSuite fits (planned)

The intended shape is one pass that produces a findings list: broken formulas, hardcoded inputs inside calculation blocks, ranges that stop short, and calculations nothing reads. Each finding carries its cell reference, so a note can quote it and a re-run can show it gone.

That is a plan, not a shipped feature. The model audit page states the current status, and the features page lists all six together.

Get early access

Test each add-in on a real model before it is released.