Home
What needs your attention, and where to go next.
Dashboard
Budget vs actuals per month
Breakdown
Overrun & underspend hotspots
Year on year
Budget lines
Every planned IT cost for the year.
Register
Budget versionsA version is a frozen photograph of the budget figures. Actuals are never versioned. Save an Approved version when the budget is signed off (it becomes the year's baseline); save Latest estimate versions during the year. Viewing a version is read-only; restoring is an explicit, guarded rollback.
Baseline vs current estimate vs actuals
Compare any two versions
Copy budget to next yearInstantiate the next fiscal year: non-contract lines are copied (amounts verbatim, New flips to Existing), contract-linked lines are regenerated from each contract's phasing for the target year, and existing target-year lines are merged, never duplicated and never deleted. Contracts ending before the target year are flagged, not carried. The copy changes the working budget only. Save an Approved version afterwards to set the new year's baseline.
Actuals
What has really been spent, per line.
Lines
Monthly actualsKeyboard
↑↓←→ move · Enter save + down · Esc revert · Ctrl/⌘ V paste a row of 12 from Excel
Cell shading
saving
save failed → retry
locked period · click the lock in a month header to toggle
Postings
2postings behind the cell · click to drill down · click the line name to edit its postings
Contracts
Every agreement behind your spend and when you can act on it.
RegisterA contract is a header plus items. Totals derive bottom-up and are never stored. Click a row to see its line items; the pencil () button on the row opens the full editor. Sorting is view-only: S.contracts is never reordered.
Portfolio
Spend grouped by initiative.
Projects
People
The establishment: budgeted positions and what each one costs this year. A position's FY cost is entered, not derived: you type the fully-loaded figure Finance already carries.The months are spread across the period the position is staffed. Positions roll into a budget line the same two ways a contract does: project into landing, or apply into the plan with per-position attribution.
Positions
Org chart
Teams
Persistent product teams and what each may spend.
Teams
Allocation keys
A key is a named rule for splitting shared spend across teams.Point a budget line or contract at a key instead of a single team, and its money is divided per month by the rule. It is never stored divided. Revisions are effective-dated: change a key from July and July onward changes, while closed months stay exactly as reported.
Keys
Vendors
The parties behind your spend.