A budget alert told you a project had crossed its budget and left you to work out the rest. Two things were missing, and together they could lead you to a confident wrong conclusion.
It did not name the client. Plenty of projects are called "Monthly Retainer", so the email identified the work only if you happened to have one of them. It now shows the client alongside the project.
It did not say what the hours covered, and for a budget that resets each month it counted every hour ever logged against a single month's quota. A 20-hour monthly retainer with a year of history behind it looked hundreds of hours over and read as permanently blown, which is not something the number can be trusted through. A recurring budget is now measured over the current month, the same figure the project page has always shown, and the email names the period it is reporting — "Logged (September 2026)", or "Logged (all time)" for a budget that does not reset.
A note about hours possibly belonging to the previous cycle has gone with it. It existed to hedge a figure that was not period-scoped; now that it is, the caveat would be wrong.
Two smaller corrections came with this:
- A recurring budget now alerts once per period rather than once ever. If you crossed a monthly budget in one month and heard nothing in the months after, that is why.
- If your organization counts only billable hours toward budgets, the alert now respects that. It previously counted everything, so the email and the project page could disagree.