Estimates and budget alerts
Updated
Allotted time is the estimate on a task. It is what turns logged hours into variance figures, a forecast and overrun alerts.
Set allotted time on a task
Set it from the task's detail slideout, from a project's Time tab, or on the task row in a project's table. It takes the same duration formats as a time entry, up to 999 hours, and you can clear it again.
A task with no estimate is not treated as zero. It is counted separately and left out of variance figures.
Super Admins, Creators, Collaborators and Integrators can set allotted time. The field is unavailable once a task is complete or archived, or once its project is archived.
Set allotted time on a playbook
Put estimates on the tasks inside a playbook or module template, and every project created from it starts with those estimates in place. This is where estimates pay off, and it is what the Playbook variance report compares against.
Estimates on a template follow the same permissions as editing the template.
Where estimates show up
Task rows and the task slideout β worked against allotted, with overrun shown in colour.
A project's Time tab β worked against allotted per task and per module, plus the project's weekly pace.
Allotted vs worked in Insights β which projects and tasks are running hot.
Playbook variance in Insights β whether your estimates hold up across projects.
Forward capacity in Insights β built from open assigned tasks that have an estimate and a due date.
Budget alerts
Turn on Alert project owners in Settings and pick a threshold. When hours logged against a project's estimated tasks cross that share of the allotted total, the project owner gets an email.
One email per project per threshold.
Raising the threshold arms it again, so a project already past the new figure alerts once more.
Only the project owner is emailed. The project needs an active owner.
Thresholds above 100% are allowed, for teams that only want to hear about clear overruns.
Improve your estimates
Playbook variance averages worked against allotted across the completed projects run from the same playbook. Projects still running, and archived projects that never finished, are left out. A module's variance counts only the runs that logged time and had an estimate for that module.
When a module runs more than 25% over its allotted hours, an Aero suggestion offers a new estimate: the average hours logged on the module's tasks that have an estimate. It suggests one module at a time. When several modules run over, it picks the one with the most average worked hours. Modules that run under their estimate get no suggestion. Select Apply to playbook to accept it, or Dismiss to hide it.
Apply to playbook updates the current published version of the playbook. It scales the module's tasks that already have estimates, in proportion, and tasks with no estimate stay as they are. It fails if the playbook has an open draft or someone else is editing it. Projects already running are not changed β the next project created from the playbook starts with the new figures.
To apply a suggestion, you need an access role that lets you edit the playbook, such as Playbook Editor. The report shows a warning when fewer than five completed projects make up the averages, so you know when a figure is based on very little. When no project from the playbook has finished yet, it says there's nothing to average yet.