Intelligence Reports

A Report Card is one chart, table or panel drawn from your organization's time, tasks, budgets and billing over a date range. Each has a code, AT-001 upward, that does not change, and you can ask for a card by its name or its code. This page lists all 45, grouped the way the builder under Custom groups them.

An intelligence report is the page that holds them: a masthead naming the range, the projects and the people, then one Report Card after another in the order they were asked for. It opens from a link with a six-character code, and anyone with the link and its code can read it. Above each card are its name, its code and a one-line description, and the info fold beneath it explains how the card's numbers are worked out.

Getting an intelligence report

There are two ways. Ask your agent for the cards you want, by name or code, for a range and, if you like, for certain projects or people; Intelligence Reports with Your Agent walks through it. If you name no card, you get every card except the origin cards, At a glance first. Or open Custom under Reports, pick the cards in the builder, save the report and share it; Custom Reports describes the builder.

Owners, admins and managers can get an intelligence report. Owners and admins see every active project, money included. A manager sees the projects they are a member of and no money: the Money cards are left off, and so is the money on the other cards.

At a glance and Project card

These two cards belong to no group. The builder shows them first, above the groups.

AT-001 At a glance — Four tiles for the range: hours logged with the effort beneath it, the billable share and its value, overhead (split with backlog hours when there are any), and return on effort, each with a daily trend line. The quickest read of how much work went in and how much of it was billable or finished.
AT-002 Project card — One panel per project in scope, even a project with no hours in the range: its hours, effort, overhead and backlog hours with its recent daily pace, its tasks against their estimates, and its billable hours by invoice state.

Effort

Where the range's hours went: by day, project, person, client and kind of work.

AT-101 Hours per day by entry state — A column for each day, split into hours that are new, approved or invoiced on the day the report was made, so you can see how much logged time is still waiting for approval or invoicing.
AT-102 Hours by project — A bar for every project in scope with the share of its hours that is billable, showing where the team's time went and how much of it you can bill.
AT-103 Hours by person — A bar per person with the share of their hours spent on no task, showing who carried the hours and whose time is going to overhead.
AT-104 Hours by kind of work — A bar per category holding every hour logged under it, with a category used on several projects counted once, showing what kinds of work took the team's time.
AT-105 Hours and value by client — A bar per client split into billable and not billable, with the value of the billable hours, showing which clients the time went to and what it is worth.
AT-106 Hours by person, by project — A bar per person split by project, showing who is spread across several projects and who works on one.
AT-107 Kind of work within each project — A bar per project split by category, showing the mix of work inside each project; projects with no hours in the range are named in a note.
AT-108 Who does what kind of work — A bar per person split by category, showing who sticks to one kind of work and who covers many.
AT-109 Effort by capacity type — One bar divided by capacity type, showing how effort on tasks shared out across your capacity types; overhead, backlog hours and categories with no capacity type are left out.
AT-110 Activity — A lane for each person who logged hours, with a bar for each day, their total and their number of days with hours, plus a count of active members who logged nothing, showing who is logging and how steadily. Only the 20 people with the most hours get a lane.

Delivery

What the range finished, and how the hours on it compare with the estimates. The four estimate-against-actual cards leave finished tasks with no estimate off the chart and count them in a footnote.

AT-201 Return on effort — Three tiles: return on effort, the closed hours behind it, and all hours logged, each with its daily trend, showing how much of the range's time went into work the range also finished.
AT-202 Finished work by kind: estimate against actual — For tasks finished in the range, a row per category setting the estimate beside the hours logged over each task's life, with the accuracy, so you can see which kinds of work run over or under estimate.
AT-203 Finished work by capacity type: estimate against actual — The same comparison by capacity type, showing which kinds of capacity estimate well.
AT-204 Finished work by person: estimate against actual — The same comparison by assignee, showing whose assigned work lands on estimate; the hours are everyone's on those tasks, not only the assignee's.
AT-205 Finished work by project: estimate against actual — The same comparison by project, showing which projects estimate well.
AT-206 Tasks finished in the range — A table of every task finished in the range with the day it finished, its estimate, its hours over its life, its accuracy and its billable value, with totals: the list behind the delivery numbers.

Flow

How work moved through the range: task counts, scope against effort, the burn-up, daily pace and throughput.

AT-301 Task flow by project — A bar per project counting the tasks that touched the range: finished in the range, finished at another time, and those in doing, todo or backlog on the day the report was made, with the average lead time; shows whether each project is closing work or piling it up.
AT-302 Scope, hours and overhead by capacity type — For each capacity type, the estimated hours of the tasks in play beside the effort logged on them in the range, with the accuracy and the overhead logged under that type's categories.
AT-303 Burn up: hours — Running totals through the range of hours on tasks, backlog hours and overhead, against a line for the estimated hours of the scheduled tasks and a line for the effort logged on the ones that finished in the range; shows whether finished work keeps pace with the hours going in.
AT-304 Pace — Daily lines for velocity, momentum, overhead and any backlog hours, over columns of planned load; shows whether the team's daily rhythm matches the work the schedule puts on each day.
AT-305 Throughput — A column for each day that finished tasks, with the number finished and the hours they took over their life, and a line for their estimates; a column above the line means that day's tasks ran over.

Planning

Projects, epics and cycles measured against their estimates and budgets.

AT-401 Hours against estimate by project — A meter per project filling with the effort logged in the range on its tasks against their estimates, with the average task accuracy and how many tasks carry no estimate.
AT-402 Epics: scope against hours — A row per epic active in the range setting its estimated hours, backlog tasks included, beside the effort ever logged on its tasks, with the accuracy, the hours in the range and its daily pace; shows which epics are outgrowing their estimate.
AT-403 Cycles — A row per cycle touching the range: how many of its tasks finished inside it, the effort against its scope with the accuracy, the overhead in the same days, and the project's cost by the cycle's end against the budget in force; shows whether each cycle delivered and stayed within budget.

Load

Scheduled and logged hours against each person's capacity.

AT-501 Scheduled load by person — From the day the report was made, each person's scheduled hours on each working day against their daily capacity, up to 15 working days, with a badge for work already past its end date; shows who is overbooked. It appears only when the report was made during the range.
AT-502 Capacity consumed by overhead — For each person with a capacity set, their capacity over the range beside their hours on tasks and on overhead, and the share of that capacity the overhead used up.

Attention

What is late, what the range touched, and who has days with nothing logged.

AT-601 Tasks needing attention — Open tasks past their end date, ranked by working days late, with the project, assignee and state of each. It appears only when the report was made during the range.
AT-602 Tasks touching the range — A table per project of every task scheduled or worked in the range, with its state, assignee, dates, estimate, and effort before and during the range: the task list behind the other cards.
AT-603 Hours logged — A lane per active member marking each working day so far with and without hours on the report's projects, with their total for the range; shows who has gaps in their logged time.

Money

Billable value by invoice state, and budgets against what has been spent.

AT-701 Where the money sits — For each project, all the billable value ever logged, whatever the range, split into unbilled, invoiced but unpaid, paid and written off on the day the report was made; shows how much is still waiting to be billed or collected.
AT-702 Value by invoice state — The same split for the billable value of the hours logged in the range, as of the day the report was made.
AT-703 Budget remaining through the range — A line through the range of the money left in the projects' budgets, falling as cost is logged and stepping up on the day each milestone or epic budget comes into force; shows how fast the budget is going and whether it has run out.
AT-704 Billable value by project — A bar per project of the billable value of the hours logged in the range, showing which projects earned the most.
AT-705 Budget spent by project — A meter per project of everything spent on it to date against the budget in force, marked when the project is over budget.
AT-706 Epics: budget spent — A meter per epic active in the range of the cost on its tasks against the epic's own budget, split into what was spent before the range and what the range added.

Origin

Every time entry records how it was written: in the app, through the API, or as a draft accepted by an agent. A draft your agent wrote that you accept yourself in the app counts as written in the app. The origin cards split the work by these three, and AT-808 counts tasks by how they were opened.

The origin cards come only when you ask for them. Name any of them to your agent, or add one to a Custom report, and the card splits all the hours across the three origins, dropping none. You can also ask your agent for hours written one way only, such as only what agents wrote. The masthead then shows an Origins row, and most cards count only those entries. Hours counted task by task, such as on the estimate cards and the task tables, still include every entry, and the budget cards are not drawn.

AT-801 Work by agents — Three tiles: the share of the range's hours that came in as drafts accepted by an agent, with its daily trend; how many of the tasks with hours in the range carry agent hours; and how many of the tasks scheduled, worked or finished in the range an agent opened.
AT-802 Hours per day by origin — A column for each day split by how the hours were written, showing how much of each day came through the app, the API or an agent.
AT-803 Hours by project, by origin — A bar per project split the same way, showing where agent and API hours land.
AT-804 Hours by person, by origin — A bar per person split the same way, showing whose hours come in through agents or the API.
AT-805 Hours by kind of work, by origin — A bar per category split the same way, showing which kinds of work agents are logging.
AT-806 Hours by byline — A bar per tool named as the writer of the draft an entry was accepted from, split the same way; hours typed in the app or written through the API sit under No byline.
AT-807 Hours by task, by origin — A bar for every task with hours in the range, split the same way, so you can see which tasks agents worked on.
AT-808 Finished tasks by how they were opened — A bar per project counting the tasks it finished in the range by how each was opened: on the board, by a user from the time entry form, through the API, or by an agent.

Reading the cards

Hours logged is every hour on a time entry dated in the range, whether the entry is new, approved or invoiced. The cards divide it three ways. Effort is hours on a task that was not in backlog when the time was logged. Backlog hours are hours on a task while it sat in backlog; they count in hours logged but never as effort or against an estimate. Overhead is hours on no task.

A task finished in the range when its finish day falls inside it: the end date of a task marked done, or, for an archived task that carried work, the last day work was logged on it. Return on effort is the effort logged in the range on tasks that finished in the range, as a share of all hours logged. Work in the range on a task that finishes later does not count, so a longer range can show a higher return. Lead time is the working days from a task's start date through its finish day.

Trend lines skip quiet days. On each day the card looks at the seven days ending on it, fewer at the start of the range, and a day among them counts when its hours reach at least a tenth of those seven days' hours; a day that does not count among its own seven shows as a short dash on the baseline. Velocity is the hours logged on the counted days divided by how many there are, and momentum is the same average for effort alone.

Scope is the estimated hours of a set of tasks, and accuracy is the effort on those tasks as a percent of their scope, so anything over 100% ran over its estimate. Some cards count the hours inside the range and some a task's whole life, and the card says which. Planned load spreads each scheduled task's estimate evenly over the working days of its schedule. Working days are weekdays when your organization leaves weekends out, and every day otherwise.

Value is billable hours at the rate recorded on each entry; when your organization does not bill backlog, hours on backlog tasks are not billable. Cost is every hour, billable or not, at the cost recorded on its entry, and the budget cards measure cost. A project's budget in force on a day is its own budget, plus each milestone budget from its Milestone Date, plus each epic budget from the earliest start date among the epic's tasks.

Cards that show a current state, such as open tasks or invoice state, read it on the day the report was made. When you ask your agent for certain people only, the hours narrow to theirs, but estimates and budgets belong to whole tasks and projects, so accuracy, estimate lines and budgets are not drawn.

Warnings about missing setup

When a card on the page depends on something your organization has not set up, a Warning box above the first card says so, once for the whole page. It can carry three notes. A billable category with no rate: its hours count as billable but add no value, and the note names the categories and the hours left unpriced. Tasks with hours but no estimate: that work has no estimate to be measured against, so scope reads low and accuracy can read high, and the note counts the tasks and their hours. A project with no budget in force by the end of the range: the Budget spent by project card has nothing to measure its spend against.