Skip to main content
A budget turns tracked work into three numbers: utilisation (how much you have used), forecast (what the job will cost by the end) and health (a green, amber or red judgement). None of them are typed in. All three are derived from time entries, rates and estimates.

What counts toward a budget

This is the single most important rule, and it differs by budget kind.

A money budget counts approved cost

Utilisation on a money budget is:
Approved cost is the sum of cost rate × hours for every entry a reviewer has approved, plus any adjustments. Time that is tracked but not yet approved does not count. It sits in a separate figure, shown under the budget bar as “3.5h awaiting approval”. A tooltip explains it: submitted time is excluded from spent and margin until a manager approves it.
This is why a busy project can show 0% utilisation. Everyone has tracked, nobody has approved. Approve the timesheets and the bar moves.

An hours budget counts everything logged

Utilisation on an hours budget is:
Every logged millisecond counts, whatever its approval state. That is deliberate. An hours budget is about capacity, and capacity is consumed the moment someone works, not the moment a manager signs off.

What does not count

The forecast

Utilisation tells you where you are. The forecast tells you where you are heading.
Remaining hours floor at zero. If you have already tracked more than the estimate, there is nothing left to project, so the forecast equals the actuals. A project with no estimates has no remaining hours, so its forecast equals what has happened so far. Estimates are what make a forecast forward-looking.

Completion percentage

With no estimate, completion is unknown rather than zero. The app leaves it out rather than showing a misleading 0%.

Effective hourly rate

This is the real rate the project is earning, blended across everyone who worked on it. With zero tracked hours it is shown as a dash with the tooltip “No tracked hours yet”.

Health

Health is a colour derived from the numbers. It is never a field you set.
Any one of these turns a project red:
  • the forecast cost exceeds the budget
  • utilisation is 100% or more – the budget is consumed
  • utilisation leads completion by 25 percentage points or more – you are spending far ahead of progress
Red beats amber. Amber beats green.

Why the 25-point rule matters

A project at 60% utilisation sounds fine. A project at 60% utilisation and 30% completion is not – it is burning budget at twice the rate it is delivering work. On current trend it needs 120% of the budget to finish. The 25-point rule catches that while there is still time to act, rather than waiting for utilisation to cross 100%.

When the numbers update

The figures update as facts move, not on a schedule. The Overview reads a precomputed figure, so it stays fast on a project with a hundred thousand time entries.

Example

Bluebird Coffee – Website Redesign, a $40,000 money budget with a 400-hour total estimate. Work done so far What the panel shows Health check
  • Forecast cost 19,250vsbudget19,250 vs budget 40,000 – not over.
  • Utilisation 31.25% – under 75%.
  • Utilisation minus completion = 31.25 − 62.5 = −31.25 – far from the +25 threshold. The project is delivering faster than it is spending.
  • Forecast 19,250vs9019,250 vs 90% of budget (36,000) – not approaching.
Result: On track, assuming no overdue tasks and fewer than five entries pending approval. The bar reads 31% spent · 63% complete, with the completion tick sitting well ahead of the fill.

The Financials panel

On a project’s Overview: With no budget and no approved time, the panel shows No budget set and a Set budget button instead.
The cost tiles are omitted, not blanked, for someone without time.viewCost or rate.viewCost. The grid reflows. There is no greyed-out placeholder hinting at a number you are not allowed to see.

Permissions

Common questions

You have a money budget, and none of that time is approved yet. A money budget counts approved cost only. Look for the “awaiting approval” caption under the bar.
Because an hours budget measures capacity, and capacity is used up the moment someone works. Approval status is irrelevant to it.
It is not wrong, it is just not forward-looking. With no estimate there are no remaining hours to project, so the forecast equals the actuals. Add task estimates to get a real forecast.
No. Health is derived, never hand-set. Change the underlying facts – raise the budget, reduce the remaining estimate, clear the overdue tasks, or approve the pending time.
Check the other amber triggers: one overdue task, or five or more entries pending approval, will do it on their own.
They are different measures on the same axis. The fill is utilisation (spend). The tick is completion (progress). Seeing the fill run ahead of the tick is the warning sign.

Troubleshooting

Set a project budget

Every field on the Budget form.

Hours vs money budgets

Which unit measures what.

Budget alerts

What fires at 50, 75, 90 and 100 percent.

Profitability and margin

Revenue minus cost.

Task estimates

The input the forecast depends on.

Budget vs estimate

Two numbers that are straightforward to mix up.