Reports

One screen across every active project. How many tasks are done, how many hours have gone in, and how close each budget is to the line.

A project page tells you about one project. Reports tells you about all of them at once, which is where an overrun shows up while there is still time to do something about it.

Go to Work then Reports. Only active projects appear here, so completed and archived work does not crowd out the jobs actually running.

Task progress by project

The first table is a straight count, one row per project:

Project name
Tasks, the total on the project
Done, how many of them are finished
Members, how many people are on it

It is a quick answer to "which of these has barely started" and "which one has three people on it that could be on something else".

Hours and budget burn

The second card takes each active project in turn and shows how much of its budget is gone.

Every row names the project and how many hours have been logged against it. Underneath, a bar and a figure show the burn:

On a project budgeted by hours, you see hours logged against hours budgeted.
On a project budgeted by amount, you see billable value against the budgeted amount, in the project's own currency.
A project with no budget set says so and shows no bar. Hours logged are still counted.

The over-budget flag

If a project has a Budget alert at % set under Settings then Billing and budget, and the burn has reached it, the row gets a red badge saying so.

That threshold is per project and worth setting deliberately. Eighty percent on a two-week job is a shrug. Eighty percent on a six-month one is a conversation with the client.

Nothing here is set up separately

Reports is built entirely from the projects, budgets and time entries you already have. There is nothing to configure. If a project is missing a bar, it has no budget; if a project is missing entirely, it is not active.

Where the numbers come from

Tasks and Done come from the tasks on each project, counted in whatever column you have marked as the finished one. See projects and tasks.
Hours come from time entries, whether they were captured with the timer or logged by hand. See time tracking.
Billable value is billable hours priced at whichever rate applied: task, member or project default.

For money that has actually been invoiced or received rather than value tracked, go to Finance.

Reading it

The two cards answer different questions, and they are most useful side by side.

Lots of tasks, few done, few hours logged. The project has been planned and not started. Either it is genuinely waiting on something, or it has quietly slipped down everyone's list.

Few tasks left, budget nearly gone. The dangerous one. The work looks nearly finished, so nobody is worried, and the remaining ten percent is going to be unpaid. This is the moment to raise it, not the week you invoice.

Hours logged, no budget bar. The project has no budget set. That is a perfectly reasonable choice on retained or open-ended work, but if it was an oversight, set one under the project's Settings then Billing and budget and the row starts telling you something.

When a project is running hot

Nothing here changes anything on its own. Reports is a read-only view, so acting on what it tells you means going to the project:

Open the project and check the Money tab, which breaks the same figure into tracked, billable and unbilled hours.
Look at Time to see which days and which people the hours went to.
Either raise a new invoice for the unbilled part, or agree a revised budget with the client and update it under Settings.

Who can see this page

Reports needs the same access as projects. A team member who cannot open Projects will not see Reports either, and will be told as much rather than shown an empty screen. Access is handed out under Team.