Knowledge Base

Answers to the questions we hear most often about reporting in Teamwork.com — covering Custom Reports, the Time Report, Profitability Report, Utilisation Report, Budget Reporting, Dashboards, Formula Fields, Scheduled Reports, Exports, and Advanced Reporting.

In this article

Not yet — Invoiced Time is currently only available on the Time Report. Adding invoiced amount, billed time, and billed expenses to Custom Reports is one of our most requested features and is something we're actively working toward. The main challenge is handling multiple currencies safely when showing invoice dollar amounts.

This is almost always caused by overlapping or duplicate budgets on the project. Forecasted cost is calculated per budget, so if two budgets cover the same period, the estimated time and cost get counted twice. Check the project's budget settings for any overlapping date ranges.

Task Custom Reports only include time on tasks that are due within your selected date range, while the Time Report shows all time logged within that range regardless of a task's due date. If a task has no due date, or a due date outside the range, its logged time won't show up on the Custom Report. Comparing row counts between the two reports is a good way to confirm this is what's happening.

Yes — we're working on this. Once available, it will let you forecast based on resource allocations (soft bookings) alongside tasks that already have estimated time (hard bookings).

Currently, user Custom Reports only support filtering by project tags — not task tags or task/project custom fields. This is a known limitation. Advanced Filters may support this in the future, though there's no confirmed timeline yet.

Task Custom Reports only include tasks with a due date inside the report's date range. Tasks with no date are left out, because without a date to anchor them, they'd otherwise show up on every report regardless of the period you're looking at. We've considered adding a toggle to include them, but that risks surfacing old completed tasks unexpectedly, so for now the Everything > Tasks page is the best place to see undated tasks.

Not yet — Custom Reports currently aggregate time per task, project, or user rather than showing individual time logs. The closest option today is the All Time page, which lists individual time logs with grouping options. A time-log-based report type is something we'd like to add in the future.

Not directly — rates can change partway through a report period, which would make a single rate figure potentially misleading. As a workaround, add a formula field that divides your billable total by billable time to get an effective average rate. Use "Billable Total (time based)" rather than the standard billable total so expenses don't inflate the result.

Only if they also have the "Can create Custom Reports" site permission, which effectively grants edit access to any report they can see. Without that permission, the date range, filters, and column picker are hidden, and the report stays view-only.

By default, project Custom Reports show projects based on their start and end dates. Turning on "Activity in Range" instead shows only projects with activity inside your selected date range. Activity here means project edits and activity log events — logging time or completing tasks doesn't count.

On fixed fee and retainer budgets, revenue comes from the budget fee itself rather than from individual logged hours, so billable time on these projects will show $0 revenue at the user level — the project generates the revenue, not the person. On time & materials (T&M) projects, billable totals should reflect actual rate × hours; if you're not seeing that, get in touch with support so we can take a look.

This column currently totals the estimated time across every task in the project, regardless of the report's date range. We know this can be confusing, and we're considering adding a version of this column that respects your selected date range.

Because a formula can return almost anything — an ID, a percentage, currency, or plain text — the system doesn't automatically know whether to sum it, average it, or leave it alone. We're working on giving numeric and currency formula columns sum and average options in the summary row.

Yes — on scheduled Custom Reports, the "With data from" option offers relative ranges like this week, last week, previous month, and this quarter. The report recalculates the actual dates each time it runs. We're also working on bringing these same relative options to the date picker on report pages themselves.

This is in progress — we're actively building support for allocated time and allocated time percentage as columns on project Custom Reports.

Not yet, though it's a small addition we're considering. The main open question is what to display when a project has more than one budget type — for example, showing the most recent one or labeling it as "Mixed."

Not currently — Custom Reports show total time per task based on the report's overall filters, without a way to add a column scoped to just one tag. A future time-log-based report type would make this possible. In the meantime, a workaround is to run a task report filtered by that tag and group it by user.

Not yet — the interface currently supports two levels of grouping. Adding a third is possible for on-screen viewing, but doing it well for exports takes more work, so it remains on our list for a future update.

Yes, Custom Reports are limited to a 2-year span between the start and end dates, to keep performance solid. If you need to look further back, you can build separate reports for different 2-year windows (for example, one for 2020–2021 and another for 2022–2023). For larger-scale reporting needs, Teamwork Connect offers direct database access.

Custom Reports respect each user's permissions — a site admin sees all the data, while a standard user only sees data from the projects they have access to. If you need everyone to see the same view, have an admin create and share the report; shared reports use the creator's access level for every viewer.

Recurring tasks aren't fully supported yet when a report looks into future dates for estimated time. We're continuing to improve how recurring tasks show up in reporting.

Not natively — Custom Reports don't currently support parent/child task grouping. As a workaround, try Advanced Reporting with the appropriate grouping applied, or export to Excel and nest the data manually.

Right now, % completed is calculated as tasks completed divided by total tasks — it doesn't factor in the progress percentage set on individual tasks. Adding a column that takes task-level progress into account is something we're considering.

Reports with more than 10 enabled columns can't be sent as a PDF — reduce the number of columns, or export as CSV or Excel instead. We're also planning to let you choose columns and filters directly from the scheduling dialog in an upcoming update.

Turn on the summary row, which offers sum and average options for standard columns. For custom field columns specifically, you may need to apply a grouping first — grouping by any column activates the total row for every numeric column, custom fields included.

Forecasted cost and revenue are calculated from a task's estimated time multiplied by the assignee's cost or billable rate. Since unassigned tasks have no assignee, there's no rate to apply, so they show $0 for both figures.

A task counts as "assigned" if it was created before the report's end date, and it's either still open (status "new" or "reopened") or was completed after the report's end date. In short, it captures tasks that were active, or only recently finished, during the reporting period.