FINANCE

Flag Burn Variance vs Forecast and Page on Overrun

Compares actual monthly burn against the forecasted budget per category, and when overspend exceeds tolerance it logs the variance to Coda and pages finance via PagerDuty.

CategoryFinance
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMonthly schedule after actuals finalized
  • ActionQuery Snowflake actual spend by category vs forecastSnowflakeSnowflake
  • LogicCompute per-category and total variance vs tolerance
  • ActionWrite variance report to CodaCodaCoda
  • OutputPage finance via PagerDuty on overrunPagerDutyPagerDuty

What it does

Catches budget overruns that quietly erode runway. Each close it lines up actual spend against the forecast for every expense category, computes the variance, and escalates when a category or the total blows past the allowed tolerance.

When to use it

Use this when your runway model assumes a forecast that departments routinely overspend. It surfaces the specific category driving the overrun so the fix is targeted, not a blanket freeze.

How it works

  1. 1A monthly schedule runs after actuals are finalized.
  2. 2Query Snowflake for actual spend by category and join it to the forecast.
  3. 3A branch computes per-category and total variance against the tolerance band.
  4. 4If any overrun exceeds tolerance, write a variance report row to Coda.
  5. 5Trigger a PagerDuty incident tagged with the worst-offending category and the runway impact.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect PagerDutyIncidents, on-call, escalations.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.