Review Financial Performance

Turn current financial results into a clear view of what changed, what evidence supports the likely drivers, and what deserves attention.

Keep calculated variance separate from business explanation. A numerical movement does not prove its cause.

1. Define the comparison

Establish:

• company or entity;
• reporting period;
• currency;
• intended audience;
• decision being supported;
• comparison baseline;
• accepted actuals;
• materiality;
• sign conventions;
• relevant definitions.

The baseline may be:

• budget;
• forecast;
• prior month;
• prior quarter;
• prior year;
• another accepted view.

Use the user's accepted definitions and materiality rules rather than imposing generic thresholds.

If actual or baseline versions conflict, resolve the controlling version or expose the conflict before calculating conclusions.

2. Build a comparable evidence set

Use approved sources such as:

• financial statements;
• spreadsheets;
• planning models;
• dashboards;
• billing records;
• payment records;
• operating data;
• relevant business context.

For consequential figures, preserve:

• source;
• version;
• filters;
• as-of date;
• definition.

Normalize before comparing:

• periods;
• currencies;
• units;
• dimensions;
• signs;
• accounting treatment where relevant.

Recalculate:

• totals;
• material variances;
• percentages;
• relevant derived metrics.

Keep accounting measures and management metrics separate when definitions differ.

Do not force unlike measures into a single comparison.

3. Identify decision-relevant movements

Prioritize movements that could affect a decision.

Do not overwhelm the review with every small variance.

Where evidence permits, decompose material movements into drivers such as:

• price;
• volume;
• mix;
• timing;
• headcount;
• compensation rate;
• vendor rate;
• currency;
• one-time items;
• collections;
• usage.

Use operating evidence to test explanations, such as:

• contracts;
• headcount plans;
• sales records;
• usage data;
• operational records;
• relevant meetings.

A plausible explanation is not automatically a verified cause.

Label unverified explanations as hypotheses and state what evidence would confirm them.

Show meaningful offsets and unexplained residuals instead of hiding them inside a generic "other" category.

4. Evaluate cash, runway, margin, and forward implications

When relevant, explain how current performance affects:

• cash;
• runway;
• gross margin;
• operating margin;
• hiring capacity;
• spending;
• forecast assumptions;
• decision thresholds.

Do not update the forecast automatically.

When accepted findings should change the forward financial view, route to the financial-forecast workflow.

5. Stress-test explanations

For important conclusions, ask:

• Does the source support the movement?
• Does the evidence support the proposed cause?
• Are periods and definitions comparable?
• Is timing responsible for part of the variance?
• Is there counterevidence?
• Is a one-time item distorting the trend?
• Is the movement driven by a denominator effect?
• Is a source incomplete or stale?

Distinguish:

• calculated facts;
• verified business drivers;
• hypotheses;
• unknown residuals.

6. Deliver the smallest useful review

Provide only the level of detail needed for the decision.

A useful review may contain:

• scope;
• baseline;
• materiality;
• coverage limitations;
• compact scorecard or comparison table;
• material favorable drivers;
• material unfavorable drivers;
• source links or references;
• cash implications;
• runway implications;
• margin implications;
• forecast implications;
• decisions;
• follow-up questions;
• source-quality problems;
• unresolved conflicts.

Lead with what changed and why it matters.

When the accepted analysis should become a broader founder, leadership, or team update, route it through the appropriate status-update workflow.

7. Preserve the accepted review method

After confirmation, preserve:

• definitions;
• source mappings;
• materiality;
• dimensions;
• sign conventions;
• comparison logic;
• review structure.

A recurring review may prepare a draft from named sources.

It should stop when:

• source version is unclear;
• definition changes;
• entity changes;
• period is ambiguous;
• materiality changes;
• source coverage becomes incomplete;
• comparison logic no longer applies.

8. Keep the analysis read-only

This workflow analyzes financial information.

Do not automatically:

• change a budget;
• change a forecast;
• modify a ledger;
• edit a source report;
• write to external financial records;
• publish results;
• share sensitive analysis beyond the accepted audience.

Those are separate actions requiring appropriate authority.