Skip to main content
TimeTracker warns you as a project consumes its budget. Alerts fire at 50%, 75%, 90% and 100% of the budget, plus two extra warnings – one when the forecast breaks the budget, and one when the margin falls below your floor. Each alert fires once. It will not nag you every time someone logs an hour.

The four kinds of alert

The first two are the ladder. The last two are breaches – they have no percentage, they are true or false.

The ladder

The four rungs are fixed at 50, 75, 90 and 100 percent. A rung fires only on the crossing – the moment usage moves from below it to at or above it. Re-evaluating the same position fires nothing, and usage dropping back down crosses nothing.

Money budget – $40,000

Hours budget – 600 hours

The two ladders are separate

A money budget and an hours budget use different counters and different alert copy.

Fires once – and what that really means

Each rung fires once per project, per pool. A monthly budget re-arms the whole 50/75/90/100 sequence at the start of each month, read in your workspace timezone. See recurring retainers.
Raising the budget does not re-arm an already-fired rung on a one-time budget. If a project crossed 90% of a 10,000budgetandyouraiseitto10,000 budget and you raise it to 20,000, the 90% alert has already fired. You will not get a second one when it crosses $18,000.

Crossing several rungs at once

Sometimes a single time entry crosses more than one rung. Logging 10 hours against a 1-hour budget crosses all four at once. The alert copy handles that honestly. Instead of saying “reached 50%” while the project sits at 1000%, the message leads with the real figures – how much has been used and what the budget was.

The two breach alerts

Forecast over budget

Fires when the projected cost to complete exceeds the budget – even though the project has not spent it yet. This is the early-warning alert. A project at 40% utilisation with a large remaining estimate is heading over long before it gets there. Headline: Forecast exceeds project budget.

Margin below floor

Fires when the projected profit margin drops under the Alert if margin falls below percentage on the project’s Budget card. If that field is blank, this alert can never fire on the project. Headline: Forecast margin below threshold. See set a project budget for where the floor is entered.

Who gets told

Recipients are the project managers plus workspace Owners and Admins.
  • Delivered in-app and by email by default.
  • The person whose action triggered the alert is excluded – you are never emailed about your own click.
  • Each person can tune their own notification preferences.

What an over-budget email says

An over-budget message states where the project actually stands, then asks for a decision:
Please review the project and decide whether to:
  • Increase the budget
  • Approve the overage
  • Pause further work on the project
An hours-budget message also names the entry that tipped it over and who logged it, because that is the reader’s first question.

Example

Harbor Logistics – Mobile App. 600 hours, one-time. Check the maths: 302 ÷ 600 = 50.33%; 454 ÷ 600 = 75.67%; 543 ÷ 600 = 90.5%; 604 ÷ 600 = 100.67%. At each rung, Priya Raman and Northwind’s owners and admins get an in-app notification and an email. On 2 July the email says the total logged time has reached 604 hours, which exceeds the allocated budget of 600 hours, and offers the three decisions. The project’s health chip is now Over budget.

The in-app Alerts list

Every project’s Overview has an Alerts panel listing fired, non-dismissed alerts.

What Dismiss does and does not do

Dismiss removes the row from the in-app list. That is all. Dismissing is housekeeping. It can never accidentally cause a duplicate alert later.

Health and alerts are different things

They are related but not the same. A project can be red without any un-dismissed alert, if someone dismissed them all. And a project can have an old 50% alert on screen while it is perfectly healthy today. Read health for the current position; read alerts for what happened. See how budgets work for the health rules.

Permissions

Common questions

You should have received the 50%, 75% and 90% rungs. Each crossing is detected on the move, so a single large entry can fire several. Check your notification preferences if some are missing.
On a one-time budget each rung fires once, ever. Raising the ceiling does not un-fire a rung that has already gone.
No. The four rungs are fixed.
Not per project. Each person tunes their own delivery in their notification settings. Leaving the Alert if margin falls below field blank does switch off the margin alert for that project.
You are excluded as the actor from an event you triggered. Your project’s other managers were notified.
No. Caps are informational and never alert. See task-level caps.
Because the hours ladder counts every logged hour and the money ladder counts only approved cost. The hours ladder always runs ahead.

Troubleshooting

How budgets work

Utilisation, forecast and the health rules.

Set a project budget

Setting the amount and the margin floor.

Recurring retainers

Why the ladder re-arms monthly.

Hours vs money budgets

Why the two ladders move at different speeds.

Profitability and margin

The margin the floor alert watches.

Budget permissions

Who can arm and change an alert.