NEW

Time estimation in actiTIME: set the next estimate from the hours your team actually logged

What's eating up your time? Find out
November 2026
Time estimation in actiTIME: set the next estimate from the hours your team actually logged

A team lead quotes a repeat project the way it was quoted last time. The estimate lives in a spreadsheet or in the proposal, the hours land in the timesheet, and nobody puts the two side by side task by task. So the design work that ran 30% over on the last three projects runs 30% over again, and on a fixed fee every one of those hours is unbilled.

Software teams have measured how often this happens. In a review of software effort estimation surveys published in 2003, Kjetil Moløkken and Magne Jørgensen of Simula Research Laboratory (Norway) found that 60% to 80% of projects overran their effort or schedule, and that most surveys put the average overrun at 30% to 40%. A new estimation technique helps less than you would expect. What helps is putting the estimate and the actual hours on the same task, so the next estimate starts from what the work really took.

Short answer:
In actiTIME, you set an estimate on each task, your team logs hours against those tasks, and the Estimated vs. Actual Time Report shows the variance by customer, project, task or type of work. A notification fires when a task reaches a set share of its estimate. Next time, you copy the tasks and replace old estimates with real averages.

Why estimates repeat the same miss

Most teams do compare estimates with actuals, but only at the level of the whole project and only after it closes. By then the comparison says “we went over” without saying where. Three things keep the same miss coming back:

  • The estimate and the hours sit in different places, so the comparison takes manual work and gets skipped.
  • Work nobody estimated, such as client calls, reviews and rework, is tracked against general tasks or not at all, so it never shows up as part of the overrun.
  • The next estimate is written from memory, and people remember past projects as shorter than they were.

What breaks the pattern is a simple loop. You estimate each task, track time against that task, read the variance while the project is still running, and reuse the actuals when you set up the next one. Here is how each part works in actiTIME.

How do you estimate project time in actiTIME?

Time estimation in actiTIME takes eight steps. You turn on Task Estimates, put an estimate on every task, show estimates in the timesheet, set a notification for worked out estimates, and run the Estimated vs. Actual Time Report during and after the project. Each step below names the setting or report and what it gives you. Settings come from the actiTIME user guide on configuration and work management.

  1. Turn on Task Estimates.

    Go to Settings → Turn Features On / Off and switch on Task Estimates. This adds the estimate field to tasks, the Estimated vs. Actual Time Report to the Reports Dashboard and the estimate notification to Settings → Notifications. Task Estimates is part of the paid version and included in the 30 day trial.

  2. Build the project from a past one.

    In the Tasks interface, click + Add New and create the project. You can copy tasks with their descriptions, estimates and types of work from any active or archived project, so a repeat project starts with last time’s task list instead of a blank page. For long task lists, use Import Tasks from CSV.

  3. Enter an estimate on every task.

    Managers with the “Manage Scope of Work” permission set estimates for tasks in their scope. Edit the estimate directly in the tasks list, in the task’s settings panel, or for many tasks at once with Edit Properties → Estimate on the bulk actions panel. Give every task a number, including client meetings and reviews, because a task without an estimate drops out of the variance by default.

  4. Show estimates where people track time.

    In the Timesheet View, each user can open the settings icon and add Estimate and Variance to the task details. The Calendar View can show the estimate and the estimate vs. progress variance in hours or percent on each time card. People then see how much of a task’s estimate is left before they log the next hour.

  5. Set a notification for worked out estimates.

    In Settings → Notifications, create a rule for the notification of worked out task estimate. It alerts recipients when the time reported for a task reaches the percentage of the estimate you choose. More on thresholds and recipients below.

  6. Add a time budget for the whole project if you need a ceiling.

    Task estimates add up, but a client or sponsor usually agrees to a total. A time budget on the project or customer tracks hours invested against hours allocated, and its progress bar turns red once the budget is exceeded. Setting time budgets also needs the “Manage Scope of Work” permission.

  7. Run the Estimated vs. Actual Time Report.

    Open it from the Reports Dashboard while the project runs and again when it closes. The next section explains which settings answer which question.

  8. Feed the actuals into the next estimate.

    When the next similar project starts, run the report grouped by task names across past projects, then use the averages to replace the copied estimates. The worked example shows the arithmetic.

How do you read the Estimated vs. Actual Time Report?

The report compares each task’s estimate with the time spent on it up to a date you choose and shows the variance. According to the reporting section of the actiTIME user guide, variance is calculated as time estimate minus spent time. A positive variance is the estimate still left; a negative variance is time spent beyond the estimate.

The report supports up to three levels of grouping plus a detail level, with these options: customers, projects, projects having the same names, tasks, tasks having the same names, and types of work. At the lowest level it shows either per user or per task data, or you can hide that and keep only the summary rows. It exports to HTML, CSV and PDF, so the same view works for internal project time reporting and for a client update.

Question Report settings What you get
Which open tasks are already over? Open tasks only, grouped by project, then task; date set to today Tasks with a negative variance, while there is still time to act
How much of the whole project is still uncommitted? All tasks, with “Include estimates of not started tasks” selected The full estimate, including tasks nobody has started
How much work never had an estimate? All tasks, with “Include time spent on the tasks without estimates” selected All hours spent on the project, so meetings and rework show up in the total
What does a task usually take across projects? Completed tasks only, grouped by tasks having the same names Estimated and spent hours per recurring task, summed over every project that has it
Which kind of work runs over most? Grouped by types of work, then project Variance by design, development, testing or any other type of work you use
Is a miss about the estimate or about one person? Grouped by task, with per user data shown at the lowest level Spent hours per person on each task

Data in the report follows permissions and assigned scope. Managers run it for their team or for all users, depending on their permissions, while regular users see a personal Estimated vs. Actual Time Report with their own hours.

We can generate any report we need

One of the greatest features actiTIME offers is the customizable reporting. We can generate virtually any report we need, grouped in different ways and only for the people assigned to each project. And if the report is not there, well, it’s really easy to create a new one and save it for future use. Go for actiTIME! It’s simple, but also very powerful! You won’t regret the decision. The software + support combination makes actiTIME the best tracking solution in the market.

Worked example: a repeat project re-estimated from actuals

A small web agency runs the same “website refresh” project for different clients. It has finished three of them in actiTIME, each with five estimated tasks, and it quotes a fixed fee based on a blended billing rate of $100 per hour. All figures here are illustrative.

What the report shows. Run with completed tasks only and grouped by tasks having the same names, the Estimated vs. Actual Time Report adds up each task across the three projects:

Task (3 projects) Estimated vs. spent Variance and new estimate
Discovery workshop 36 h estimated, 33 h spent +3 h; new estimate 11 h per project
Design mockups 120 h estimated, 159 h spent −39 h; new estimate 53 h
Content migration 72 h estimated, 117 h spent −45 h; new estimate 39 h
Development 240 h estimated, 246 h spent −6 h; new estimate 82 h
QA and fixes 48 h estimated, 75 h spent −27 h; new estimate 25 h
Client meetings (no estimate) Visible only with “Include time spent on the tasks without estimates”: 42 h spent Add as an estimated task: 14 h

Development, the biggest task, was estimated almost exactly. The overrun came from content migration, design and QA, and from meetings that were never estimated at all. A project level comparison would only have said “about 22% over” and would have hidden all of that.

Old estimate per project: 12 + 40 + 24 + 80 + 16 = 172 h
Estimated tasks only, 3 projects: 630 h spent ÷ 516 h estimated = 1.22
With unestimated meetings: (630 + 42) h ÷ 516 h = 1.30
New estimate per project: 11 + 53 + 39 + 82 + 25 + 14 = 224 h
Fixed fee at the old estimate: 172 h × $100 = $17,200
What that fee really earned per hour: $17,200 ÷ 224 h = $76.79
Fee at the new estimate: 224 h × $100 = $22,400

The agency was charging for 172 hours and delivering 224. Quoting from the task level actuals adds 52 hours and $5,200 to each project, and more than a quarter of that (14 hours) is work that only became visible once the report included tasks without estimates.

Sensitivity. Content migration scales with the number of pages. If the next client’s site has 50% more pages than the average past project, migration rises from 39 to 58.5 hours and the project from 224 to 243.5 hours, or $24,350. Leaving out the meetings task understates every project by 14 hours, which is $1,400 of work quoted at zero.

Three projects make a thin history, so treat the averages as a first correction. If a task’s spent hours swing widely between projects, ask why before you reuse the number: a different client, a different scope or time logged to the wrong task. Our guide to project estimation techniques shows how to turn the same data into a correction factor for projects that are similar but not identical.

How do you get warned before a task runs over?

Set a notification of worked out task estimate in Settings → Notifications. It emails recipients when the time reported for a task reaches the percentage of its estimate you specify, so you hear about an overrun while there is still time to talk to the client or move work around.

Setting up notifications takes the “Manage Account & Permissions” and “Manage System Settings” permissions. Each rule names its recipients: particular users, departments or time zone groups, or everyone with the “Manage Scope of Work” permission. Users without an email address or without the needed permissions get nothing, even if you select them. Rules run daily or on selected weekdays, at the time set in General Settings, and arrive in each recipient’s local time zone. You can also create more than one rule of the same type, for example one at 80% as an early warning and another at 100%.

In the worked example, an 80% rule on the 53 hour design task fires at 42.4 hours. That still leaves more than 10 hours of estimate to agree on scope with the client instead of explaining an overrun afterward.

For money rather than hours, the notification of overrun project budget tells managers when project cost, based on users’ pay rates, exceeds the budget. The red progress bar on a time budget covers the hours side at project or customer level.

Where should the first estimate come from?

actiTIME records estimates and actuals; it does not produce the first number for you. For a brand new kind of project, build project estimates bottom up from the task list with the people who will do the work, then let tracked hours correct it from the second project on. Software teams face the widest swings, which is why software project time estimation benefits most from task level history.

The general method lives in our other guides, so it is not repeated here:

What actiTIME does not do here

actiTIME covers estimates, tracked hours, alerts and variance reporting. A few things it leaves to you, with the workaround for each:

  • No suggested estimates. The report gives you the history, but actiTIME does not calculate or fill in the next estimate. Read the averages and enter them, in bulk with Edit Properties if needed.
  • One number per task, no ranges. There is no built in optimistic and pessimistic pair or three point field, and no story points. If you want to record a worst case, a numeric custom field for tasks can hold it, but the report calculates variance against the estimate field only.
  • Estimates live on tasks. Project and customer totals come from report subtotals. For a ceiling on the whole project, add a time budget.
  • No scheduling. Tasks carry deadlines, statuses and priorities, but actiTIME does not spread estimated hours over a calendar or a Gantt chart.
  • Changing an estimate moves the baseline. A task holds one estimate, so raising it mid project changes what the variance is measured against. Decide upfront whether you keep the original estimate and track the overrun, or update it when the scope changes and note why in the task comments.
  • Not in the free version. Task Estimates and Budgets are not part of the free version for up to 3 users. They work in the 30 day trial and in the paid versions.

Where the estimate loop breaks

The report can only show what people logged. These habits spoil the data without anyone noticing:

  • Estimates used as targets for individuals. When going over is punished, people log time to whatever task still has estimate left, or stop logging at the estimate. The variance then looks perfect and teaches you nothing. Use the per user view to find where a process needs help, not to rank people.
  • General tasks that absorb everything. A task called “General” or “Admin” on every project soaks up real work and hides which task ran over. Create named tasks for meetings, reviews and rework, and estimate them.
  • Blank estimates. Tasks without estimates drop out of the default report. Run it once with “Include time spent on the tasks without estimates” to see how much you are missing.
  • Time entered days later. Hours reconstructed at the end of the week drift toward the estimate. Time-Track Approval and a weekly reminder help keep entries current.
  • Reviewing only at the end. A post mortem helps the next project but not this one. Run the open tasks view weekly while the work can still change.

Set estimates on tasks, track hours against them and see exactly where each estimate missed with actiTIME

Try Free

Time estimates

FAQ

Are task estimates available in the free version of actiTIME?

No. The free version for up to 3 users does not include Task Estimates or Budgets. Both are part of the 30 day trial, which has every feature, and of the paid versions, which start from $5 per user per month. See actiTIME pricing for details.

Can team members see their estimates while they track time?

Yes. Regular users can see task estimates in the task properties and run a personal Estimated vs. Actual Time Report. In the Timesheet View they can add Estimate and Variance to the task details, and the Calendar View can show the estimate vs. progress variance on each time card.

What timesheet and project features does actiTIME offer small teams?

Beyond estimates, actiTIME has a weekly Timesheet View, a Calendar View with start and stop times, iOS and Android apps, and the Time Management Assistant extension for Chrome. On the project side there are deadlines, priorities, workflow statuses, a Kanban board and time, cost and billing budgets. Reports cover hours, overtime, leave, cost of work and billing, with PDF invoices from tracked time. The full list is on the actiTIME features page.

Start the next estimate from real hours

Estimates improve when someone checks them against the hours the work took, task by task, and then uses the result. actiTIME keeps both on the same task and shows the gap in the Estimated vs. Actual Time Report, with task estimates, alerts and budgets around it.

Start a free trial of actiTIME with full features for 30 days. After the trial, teams of up to 3 users can keep using it for free.

Are you ready to drive your business growth with actiTIME?

Start Using actiTIME