Time tracking in ClickUp: how it works and which plans include it
ClickUp is one of the few task tools that ships a timer rather than leaving it to an integration. That sounds like the whole problem solved, and for a team of two or three it often is. The trouble usually starts later, when someone has to turn a month of recorded entries into something an accountant or a client will accept, and discovers that the recording half and the reporting half are priced separately.
This article covers what ClickUp's native time tracking actually does, which plan each piece sits on, the places teams reliably get stuck, and how to tell whether the answer is a plan change or a different tool.
What native time tracking means here
ClickUp's timer lives on the task. Start it, work, stop it, and the entry attaches to that task with the person who recorded it. Entries can also be added after the fact by typing a duration or a range, which matters more than the timer itself, because most hours in most teams are entered from memory rather than captured live.
Around that core, ClickUp layers several distinct things that are easy to conflate:
- Time tracking. The timer and manual entries on a task.
- Time estimates. A planned duration set on the task, separate from what was recorded.
- Timesheets. A per person view of entries across a date range.
- Timesheet approvals. A step where a submitted week is reviewed and signed off.
- Billable time, notes, and labels. Metadata on each entry that turns hours into money.
These are listed as separate rows on ClickUp's pricing page, and they do not all arrive at the same tier. That separation is the single most useful thing to understand before choosing a plan, because a team that only checks whether "time tracking" is included will get a surprise at the reporting stage.
Which plan includes what
According to ClickUp's pricing page as of September 2026, the plans and prices look like this.
| Plan | Price | Notable usage limits |
|---|---|---|
| Free Forever | $0 | 60MB storage, unlimited tasks, unlimited members, 5 Spaces, 2 Teams |
| Unlimited | $7 per user per month billed yearly, $10 billed monthly | Unlimited storage, unlimited Spaces, Folders, and Forms |
| Business | $12 per user per month billed yearly, $19 billed monthly | Adds the reporting and permission layer above Unlimited |
| Enterprise | Contact sales | Adds organisation wide administration and compliance |
The time related rows in the same comparison table sit like this.
| Capability | Free Forever | Unlimited | Business | Enterprise |
|---|---|---|---|---|
| Time Tracking | Trial | Included | Included | Included |
| Timesheets | Trial | Trial | Included | Included |
| Timesheet Approvals | Not listed | Not listed | Not listed | Included |
| Notes, labels, and billable time | Basic | Basic | Included | Included |
Two lines deserve attention. Native Time Tracking is named explicitly among the things the Unlimited plan adds to Free Forever, and the Free column for that row is marked as a trial rather than a permanent inclusion. And timesheet approvals appear only against Enterprise, which is a meaningful jump for a small team that simply wants someone to sign off a week before it goes on an invoice.
Prices and feature placement change. Read the pricing page on the day the decision is made rather than trusting a table anyone wrote earlier, including this one.
Where teams get stuck
The plan table explains some frustration but not all of it. Three patterns show up repeatedly regardless of tier.
The hierarchy makes reports ambiguous
ClickUp organises work as Spaces, Folders, Lists, tasks, and subtasks. Time can be recorded on a task or on a subtask, and whether a parent task's report includes its subtasks' hours depends on how the view is configured. On a small board nobody notices. On a client project with three levels of nesting, two people produce two different totals for the same month and neither is obviously wrong.
The fix is a convention rather than a setting: decide that hours are recorded at exactly one level, write it down, and enforce it when reviewing. Teams that skip this step spend the reconciliation time every month instead of once.
Estimates and actuals drift apart quietly
A time estimate is a plan. A tracked entry is a record. Both live on the task and both are displayed as durations, which invites people to read one as the other. A task showing eight hours may mean eight hours were planned, eight were recorded, or both by coincidence. Reports that mix the two produce numbers that look precise and are not.
A related trap is that an estimate entered early is rarely revised. The scope changes, the task grows, and the eight hour estimate stays where it was because nothing forces anyone to update it. Comparing recorded hours against a stale estimate then produces a variance report that says more about how old the estimate is than about how the work went.
The timer is only as good as the habit
This is not specific to ClickUp, but the presence of a native timer makes it easier to assume the problem is solved. It is not. Someone will forget to start it, someone will leave it running overnight, and someone will record nothing for a week and fill it in on the last day of the month from calendar entries. Accurate hours come from a fixed weekly moment when everyone reconciles, plus one person whose job it is to notice empty weeks. The software stores what that habit produces.
Setting it up so the numbers survive a month
Most of the accuracy problem is decided in the first week of setup, not in the reporting view. Four decisions do the heavy lifting.
Decide the level, once
Pick whether hours go on tasks or on subtasks and apply it everywhere. Mixed levels are the most common cause of two people producing two different totals, and the mixture is invisible until someone runs a report. Writing the rule into the space description costs nothing and saves the argument later.
Make billable an explicit choice
If any hours are billable, mark every entry one way or the other rather than leaving the flag at its default. An unmarked entry is not a neutral entry. It is an entry that will be read as whichever option the report author assumed, and it will be read differently next month.
Name projects the way the invoice names them
Time reports become invoice lines. When the list name and the invoice line differ, someone translates between them every cycle, by hand, from memory. Naming them identically from the start removes a recurring task that nobody ever thinks to measure.
Fix the weekly moment before the month end
A short weekly reconciliation is cheaper than a long monthly one, because people can still remember last Tuesday and cannot remember three weeks ago. Put it on the calendar, give one person the job of noticing empty weeks, and treat a missing week as a thing to chase rather than a thing to estimate. This one habit separates teams whose hours match reality from teams whose hours are a reconstruction.
Comparing the cost honestly
For a five person team, the arithmetic at September 2026 prices is straightforward.
Unlimited at $7 per user per month billed yearly is $35 a month, and gives the team the timer with notes, labels, and billable time in basic form. Business at $12 per user per month billed yearly is $60 a month, and adds timesheets as a full feature rather than a trial. Approvals mean a conversation with sales.
Whether that is expensive depends entirely on the alternative. Running a separate time product alongside a free task tool usually costs the same or more once the reporting tier is included, and adds a second member list to maintain. Running everything in one place and paying for the tier that includes timesheets is often the cheaper honest answer, which is a point in favour of staying rather than moving.
The case for looking elsewhere is different and more specific. It is not price. It is that the reporting features a small team needs sit two tiers up, next to features that same team will never touch. Paying Business prices for organisation wide permissions in order to get a weekly timesheet is a poor trade for five people. A comparison of how different tools package this is the fastest way to see whether the packaging, rather than the product, is the problem.
What a timesheet has to do to be useful
If the decision is between plans or between tools, it helps to know what the finished thing must produce. A timesheet that only stores durations is not finished.
It has to cover a week, per person, in one view. Days across, projects down, totals in both directions. Anything that requires exporting and pivoting in a spreadsheet has moved the work rather than removed it.
It has to have a submitted state. A week that is filled and a week that is agreed are different things. Without that state change, nobody can tell whose week is missing, and the month end scramble is guaranteed.
It has to understand more than hourly. Hourly, per project, and fixed monthly are three different payment shapes. A system that models only hours forces the other two into manual adjustment every cycle, which is exactly the work the tool was bought to remove. Tools that carry all three through to the report are the ones where the export goes straight to invoicing. This is worth checking against the feature list of any candidate before a trial, because it is not something a demo will surface.
It has to share one member list with the tasks. When hours and tasks reference the same person record, adding and removing people happens once. When they do not, the two lists drift and hours go missing.
Deciding what to do next
Three situations, three different answers.
If the team is on Free Forever and tracking is mostly for self awareness, stay there and check the trial status on the time tracking row before building anything on it. The habit matters more than the tier.
If hours already feed invoices, the choice is between Unlimited plus manual reporting and Business with timesheets included. Work out the monthly difference for the actual head count and weigh it against the hours currently spent assembling the report by hand. For most teams under ten people, the manual assembly loses.
If the only reason to be on a higher tier is the timesheet, that is the case worth examining. Look at what else comes in that tier and ask whether any of it will be used. If the answer is no, the packaging is wrong for the team, and a tool where timesheets are an add on rather than a tier can cost materially less. Pinateca prices timesheets that way, which makes the comparison easy to run on real head count.
Q1. Is ClickUp time tracking available on the free plan?
ClickUp's pricing comparison table marks Time Tracking as a trial on Free Forever, and lists Native Time Tracking among the features the Unlimited plan adds. Treat the free tier as a way to evaluate tracking rather than a permanent home for it, and check the current pricing page before planning around it.
Q2. What is the difference between time tracking and timesheets in ClickUp?
Time tracking is the recording of entries against tasks. Timesheets are the per person view of those entries across a date range. They are separate rows on the pricing page, and timesheets are listed as a trial on Free Forever and Unlimited, and included on Business and Enterprise.
Q3. Which plan is needed for timesheet approvals?
The comparison table lists Timesheet Approvals against Enterprise only. Teams that need a review and sign off step before hours go on an invoice should confirm this with ClickUp directly, since it is a large jump for a small team.
Q4. Why do two people get different totals for the same project?
Usually because hours are being recorded at different levels of the hierarchy, some on parent tasks and some on subtasks, and the two reports roll them up differently. Pick one level, write the rule down, and check it during the weekly review.
Q5. Is it cheaper to use a separate time tracking tool alongside a free task tool?
Rarely, once the reporting tier of the separate tool is included and the cost of maintaining two member lists is counted. The stronger argument for moving is not price but packaging, specifically when the timesheet a small team needs sits in a tier full of features that team will never use.
