Budget alerts
Open Projects → Budget Alerts in Thermal →
What it's for
Budget alerts shows which projects have spent their budget or are forecast to exceed it. Figures are computed when you open the page, using phase budgets, incurred costs and the remaining-cost estimates on the project record.
The route is /projects/budget-alerts.
Tabs
There are no tabs.
Panels and controls
One searchable table shows each project's alert, reason, budget, cost to date, budget used, forecast final cost, forecast position and watch threshold. Select a project name to open its record.
On first load, projects appear in this order:
- Over: incurred cost has reached or exceeded 100% of budget.
- Watch: budget used has reached the project's watch threshold, or forecast final cost is above budget.
- OK: incurred cost is below the watch threshold and no known forecast overrun is present.
- Unknown: a complete positive budget or usable cost figures are missing. This is not a confirmation that the project is within budget.
Projects with higher budget use appear first within each alert state. Canceled and deleted projects are excluded.
Budget used is cost to date divided by budget. It is a spending percentage, not a daily rate or historical trend. Forecast position compares forecast final cost with budget. A known forecast cannot be lower than cost already incurred. An unavailable forecast appears as No estimate.
Costs use the received-cost basis of the WIP schedule. Ordered materials that have not been received do not count as incurred purchase-order cost. Commission is excluded.
What it accepts
This is a read-only list. A project needs budgets on every live phase for its budget to be complete. Set phase budgets and remaining-cost estimates on the project record.
How to configure it
The default watch threshold is 80%. A configured project override takes precedence over the company threshold. The Over boundary stays at 100%. This page has no threshold editor.
Who can see it
You need access to Projects and permission to view costs. The server checks both requirements for direct links too.
A branch-restricted user sees only projects pinned to a live site in that branch. Projects without a site appear only for users with access across branches. Another company's projects are excluded.
See Roles & permissions for access settings.