Make budget alert notifications context-aware by evaluating spend against the position within the budget period, so users are only alerted when the spending pace represents a real risk of overrun.

Problem

CCM Perspectives budgets currently support six threshold alerts (Actual 50/80/100% and Forecast 50/80/100%). Alerts fire purely on the percentage threshold, with no awareness of where we are in the budget period.

Example: a "Forecast 50%" alert triggers the same way on day 5 of the month as on day 25 — even though these have very different financial meanings. This produces noise on normal spend patterns and dilutes the signal when a real risk exists.

Requested behavior

Introduce dynamic, time-aware budget notifications that evaluate both:

Budget consumption percentage

Progress through the budget period

The platform should decide whether the current spending velocity indicates an elevated probability of exceeding the budget, and alert accordingly.

Example (monthly budget, Forecast 50%)

Day 8 → Notify. Velocity suggests likely overrun before month-end.

Day 15 → Optional notification, depending on configurable tolerance.

Day 25 → Do not notify. Normal spending behavior; no user attention needed.

Suggested configurability

Toggle between "Static thresholds" (today's behavior) and "Dynamic / time-aware" mode per budget.

Configurable tolerance band for the "warning" zone.

Applies to both Actual and Forecast alerts, across monthly / quarterly / yearly budget periods.

Benefit

Reduces alert fatigue, surfaces only financially meaningful risks, and improves budget governance across Perspectives.