Variance Explainer · AI agent | Built AI

It explains the variance continuously, not at quarter-end

The work of a variance pack is mostly reconstruction: tying actuals to plan, isolating what moved, and writing it up. The Variance Explainer does that reconstruction as actuals arrive, so the asset manager spends the time on the decision the variance implies, not on assembling it.

It watches

New actuals are posted

A GL refresh or a new month of actuals is the trigger to rebuild the bridge.

It does the work

Bridges, isolates, drafts

It builds the NOI bridge against plan, isolates the line-level drivers, and drafts the variance narrative traced to the GL.

Then it stops

The AM approves the narrative

The narrative is a draft until an asset manager reviews and approves it. The judgment about what it means stays with a person.

The pipeline

New actuals in, a written variance narrative out

  1. New actuals
    A GL refresh or new month of actuals triggers the bridge.

    →

  2. Build NOI bridge
    Actuals tied to plan and prior, computed on the deterministic engine.

    →

  3. Isolate drivers
    Line-level drivers ranked by contribution, each traced to the GL line.

    →

  4. Draft narrative
    A plain-English variance narrative assembled, then held for AM approval.

    Variance written the day actuals land means the problem it points to is days old, not a quarter old.

See it work

One run, every figure cited

Ask the Variance Explainer what moved. It returns the NOI bridge, the ranked drivers, and a drafted narrative, with every number traceable to the GL line behind it.

Variance Explainer · AI agent

Tenant: Asset Management

Explain the Q2 NOI variance for Block 37.

Variance Explainer

NOI +$184k vs plan ( +3.1%). Bridge built against plan and prior year.

Top driver: recoveries +$121k, from the Northwind expansion commencing early.

Offset: repairs +$54k over plan, a one-time roof remediation.

Draft narrative assembled, line by line, each figure linked to the GL.

Approve narrative

The boundary

It drafts and computes, then it waits

It can write the variance. It cannot decide what to do about it.

The Variance Explainer assembles the bridge and the narrative, but the call, re-forecast, escalate, leave it, belongs to the asset manager. The draft is fully traced so that approval is a review, not a rebuild.

The boundary, in one line

Trigger: new actuals are posted.
Human approval: an asset manager approves the narrative.
What it cannot do: re-forecast or publish the pack without approval. The full architecture, controls and audit trail live on the security & governance page.

See the platform on your own portfolio.

Bring a live deal, a fund or a stack of documents and watch the graph light up across your own systems, extract, simulate and author, with every number traceable to source. No migration, nothing leaves your tenant, and nothing acts without your sign-off.