A budget lets you cap the effort or cost on a project and watch how close you are getting. You set budgets on a project's Edit page, in the Budget panel. Budgets are configured by managers, admins, and owners; what a member can see depends on a setting described below.
The main budget is an hours cap. Enter a number of Total project hours and Time Trakkr tracks logged hours against it. Leave it blank for no hours cap.
Underneath are two options that shape how the hours budget behaves:
By default every hour logged on a project counts against its budget. If your budgets are for billable work only, change Project budget counting to Count billable hours only under Settings → Preferences. It applies to the whole workspace, and only an administrator can change it.
Everything that reports budget use follows the setting: the project page and
its alert band, the Projects list, a person's budget on a project, the
Budget vs actual report, the /reports/project_budget API, the alert email,
the weekly project rollup, and the assistant, which also says which hours it
counted. A task's budget always counts every hour on that task.
A budget that resets every month is measured against one month at a time. The project page opens on the current month, and Previous month / Next month step through the project's history; Return to this month brings you back. You cannot step into the future.
So "Budget remaining" on a 20 hour retainer means remaining this month, not remaining for the life of the project. Stepping back to a month that ran over shows that month over, without affecting the one you are in.
On the Projects list, Spent is every hour the project has ever had, while Remaining for a monthly budget is this month's allowance less this month's hours. The This month column shows those hours, so the two add up: a 20 hour retainer with 5 hours logged this month reads 5 under This month and 15 under Remaining, however large Spent has grown. Projects on a fixed budget leave This month empty, because for them Spent is already what the budget is measured against.
Projects on a fixed budget have no month controls: their budget is one running total, and defaulting them to a single month would hide most of their history.
The hours chart draws a dashed line at a monthly budget and colors any month over it, so a run of overspends is visible at a glance.
The Budget vs actual table under Reports compares a budget to whatever date range you are looking at. For a monthly budget the Budget column shows the allowance for that whole range: the monthly figure times the calendar months the range touches. A 20 hour retainer over a quarter shows 60 against the 60 hours logged — a project exactly on plan — and the row says budget is per month: 20:00 × 3 so you can see where the figure came from. A month counts once the range touches it, so January 31 to February 1 allows two months.
The /reports/project_budget API keeps budget as one month's allowance, as
integrations already read it, and adds months_in_range, budget_for_range
and budget_remaining_for_range beside it. Compare spend with
budget_for_range. budget_by names the budget a row is listed for:
project_hours, project_fees, person_hours, internal_cost or none. Only
with project_hours is budget the project's hours budget; otherwise it is
null. The assistant does the same: ask it about a quarter and it
measures against three months' allowance.
Each row shows the project's client, so two clients' projects called "Support" are not confused.
A project is listed when it has an hours or cost budget, or when anyone on it has a per-person budget — a project budgeted only per person is listed too, marked budgeted per person, with no project figure.
On a project that uses per-person budgets, Budget by person lists everyone who logged time in the range, not only the people with a budget. Someone assigned without a budget, or who logged time without being assigned at all, shows No budget, with their hours. Those are often the hours that explain why the project total ran over. Projects without per-person budgets do not list everyone. Per-person budgets are visible to managers, admins and owners only.
Alongside hours, you can set a Cost budget in dollars to cap what the project costs to deliver. Because cost figures are money, only managers, admins, and owners ever see this.
Directly below it is Include expenses in cost budget. Tick it to count billable and reimbursable expenses toward the cost budget as well as labour, so the budget reflects the true cost of the work. This checkbox only becomes available once you have entered a cost budget amount.
A Fee budget caps what the work is worth: an amount of money that the project's billable hours, priced at their hourly rates, are measured against. It is Harvest's "total project fees" budget, and a Harvest import brings it across.
It is money, so only managers, admins and owners ever see it — on the project page, in the Budget vs actual report (where a monthly fee budget is scaled to the range like hours), in the API and through the assistant. Show budget progress to everyone does not reveal it to members.
Beyond the project total, you can allocate hours more finely on the same Edit page:
These are hour allocations that sit under the project total; they help you plan and spot when one task or one person is running long.
The alert percentage now does two jobs. It still sends the email, and it also marks the project where you are already working:
Nothing appears when nothing is wrong. There is no permanent "0 projects over budget" line, because a message that is always there is one people stop reading.
Over budget shows even with email alerts switched off. Turning the alerts off means you do not want to be emailed; it does not mean the project should stop telling you it is over. With alerts off there is no early Near budget warning, because the warning line and the over-budget line become the same number.
You can also ask the assistant "which projects are near their budget?" without naming one.
By default, budget progress is visible only to the people who manage the project and to administrators. To open it up, tick Show budget progress to everyone on this project.
The same rule decides the marks described above: a member sees a project's Near budget or Over budget state only where that project has this ticked, and the assistant applies the same rule rather than working around it.
When that is on, members assigned to the project see a budget panel too — but an hours-only one. It shows the budget hours, the hours spent, the percentage used, and whether the budget resets each month. It never shows any money: cost budgets, fee budgets, rates, and dollar figures are still withheld from members, matching the money rules in roles and permissions. This lets you keep your team aware of how much time is left without exposing what the work is worth.
A typical setup is a Total project hours cap with Send email alerts turned on at 80%, and Show budget progress to everyone enabled so the team can pace themselves. For retainers, add Budget resets every month. For cost-sensitive work, add a Cost budget and, if expenses matter, Include expenses in cost budget. To cap what the work is worth to the client, add a Fee budget. Budgets sit on top of the project's billing type, so you can combine, say, person rates with a monthly hours cap.
Everything above can also be set without opening the project:
PATCH /v1/projects/{id} takes budget (hours), budget_is_monthly, over_budget_notification_percentage, show_budget_to_all, cost_budget and cost_budget_include_expenses, the same names Harvest's API uses, and fee_budget, fee_budget_is_monthly and fee_budget_notification_percentage for the fee budget. A person's budget on a project is budget on their user assignment, and a task's budget is budget on the task. Send only what you want to change. See the REST API.Settings such as the alert percentage or Budget resets every month belong to a budget, so they are refused when there is no hours or cost budget for them (for the fee budget's own settings, no fee budget) — including in the same request that removes the project's budgets, which is told exactly that. A project with no budget has no alert percentage: the API and the assistant report it as empty rather than as 80%. A budget with email alerts switched off reports it as empty too, and changing the budget's other settings leaves the alerts off.
The same people can do it as on the Edit page: managers, admins and owners. A person has to be assigned to a project before they can have a budget on it; the assistant will not assign them for you. An MCP connection made with an organization API key can read budgets but not change them, because those keys are read-only. To change budgets from Claude, connect by signing in, or use a personal access token.
To see the budgets of several projects together — every phase of a piece of work, or a client's support contract across years — group them into an engagement. The Time report then shows a Budget by engagement rollup.
Updated 2026-11-08. Still stuck? Contact support or return to the Help Center.