Budget vs estimate: what is the difference?

These two words get used as if they mean the same thing. In TimeTracker they are different objects, on different things, with different jobs.

​

The one-line version

An estimate is a guess about effort. A budget is a limit on spend.

You can have one without the other. Many projects run with budgets and no estimates. Some internal projects have estimates and no budget.

​

Side by side

​

An example with both

Northwind agrees a website redesign with Bluebird Coffee for $40,000. That $40,000 is the budget. It sits on the project. Priya then breaks the work into tasks and estimates each one: Those are estimates. At an average $100/hour, 264 hours is about$26,400 of billable value – comfortably inside the $40,000 budget, with room for revisions. Now the work happens. Sarah, Jonas and Ana record time against those tasks. Two things are tracked in parallel:

• Estimate vs actual, per task. Homepage wireframes was estimated at 8 hours and took 11. That is useful for quoting the next job.
• Budget burn, for the project. $18,400 of the$40,000 is used. That is useful for knowing whether you are still making money now.

They answer different questions, which is exactly why both exist.

​

How they interact

They are independent, with two connections:

1. Estimates roll up. The sum of task estimates gives you a bottom-up forecast you can compare against the budget before work starts. If your estimates already exceed the budget, you priced the job wrong – and you know on day one, not in month three.
2. Task caps. A task can carry its own cap that counts toward the project budget, for cases where one piece of work must not run away. See task-level caps.

Otherwise, changing an estimate never changes a budget, and changing a budget never changes an estimate.

​

When to use each

Use estimates when:

• You want to know if a task is running long
• You are quoting future work and need past accuracy to learn from
• You are balancing workload across a team
• You want to spot the task that always takes twice as long

Use budgets when:

• A client agreed a fixed fee
• You sold a block of hours
• You run a monthly retainer
• You need an alert before a project stops being profitable

Use both when you want the full picture: budgets tell you if the project is healthy, estimates tell you which task made it unhealthy.

​

A third thing people confuse: the quote

A quote is what you told the client. A budget is what you enforce internally. They are usually the same number, but they do not have to be. Northwind quotes Bluebird $40,000 and sets an internal budget of$36,000, keeping $4,000 of headroom for revisions. The client sees the quote. The team works to the budget, and the alert fires early enough to do something about it. See quote to invoice.

​

Which one is telling me I have a problem?

​

Permissions

Note that task.reviseEstimate is separate from task.edit. Someone can edit a task’s title and assignee without being able to move the number the plan depends on.

​

Common questions

​

Related guides