Skip to the page

DocsPlanning

DocsPlanning

Reports

Outcomes shipped, tasks closed, on-time delivery, AI share, utilisation and dependency health over the last 7, 30 or 90 days, with a CSV export.

Reports looks back over a period and compares it with the one before: what shipped, how much was closed and by whom, how much of people’s working time was booked, and where work is stuck right now.

Open Reports in the sidebar’s second Workspace section, beside Integrations and Settings. Every member of the workspace can open it.

Choose the period and the projects#

  • 7 days, 30 days and 90 days set the period. Reports opens on 30 days.
  • Projects beside them opens a checklist. Tick as many projects as you like, or All projects for everything. Archived projects are in the list, marked “(archived)”, because reports are history: work done in a project still counts after it’s archived.
  • Team narrows every figure to the work of one or more teams, and Utilisation by person to their members. If you’re in a team, Reports opens on My teams; Show everyone in the line under the filters widens it.

The period is the last 7, 30 or 90 days up to and including today. The line under the title gives its dates. Each headline figure is compared with the same number of days immediately before.

The period and the project are part of the page’s address, so you can bookmark a report or send someone a link to it.

The four headline figures#

FigureHow it’s worked out
Outcomes shippedOutcomes finished in the period.
Tasks closedTasks moved to Done in the period.
Closed on timeOf the closed tasks that had a due date, the percentage finished by the end of that day. The note underneath says how many tasks that’s out of. Tasks with no due date aren’t counted.
AI share of throughputThe percentage of closed tasks that were assigned to an AI worker.

Under each figure is the same measure for the period before, such as “vs 12 prior 30d”. For AI share the change is given in percentage points (“pp”).

A task or outcome counts on the day it was finished, not the day it was due.

Tasks closed per week#

A bar for each week in the period, split between People and AI workers by who the task was assigned to.

  • Weeks start on Monday. The first and last weeks may be partial, because the period rarely starts on a Monday.
  • A closed task that had no assignee isn’t in the bars, though it’s still counted in Tasks closed. A note under the chart says how many there were.
  • Hover over a bar for the week’s numbers, or open Show as table.

Throughput by project#

Tasks closed in the period for each project, most first. Projects that closed nothing aren’t listed. Click a project’s name to open it.

By team#

Owners and admins see By team once the workspace has teams. Each team has a bar for the tasks closed in the period among its work, followed by three numbers: closed, open now and blocked now. Click a team’s name to see the whole report for that team.

This section compares teams with each other, so the Team filter doesn’t narrow it. The Projects filter does.

Utilisation by person#

Each active member’s booked time as a share of their working hours across the period. People come first, highest first, then AI workers.

  • People are measured in calendar time: the hours they were booked for.
  • AI workers are measured in machine time: the time the worker was busy.
  • ▲ and a red bar mark a person booked for more than their working hours over the whole period.
  • A dash means the person had no working hours in the period.

Hover over a bar for the hours behind it and how many days the person was over. These are the same rules as the Capacity screen, applied to a longer stretch.

With a project chosen, only bookings in that project are counted, against the person’s full working hours. Utilisation then shows how much of their time that project took, not how busy they were overall.

Dependency health#

This panel isn’t about the period. It shows where work is stuck right now.

For each outcome that isn’t done, it counts the open tasks that are:

  • Blocked: the task’s status is Blocked.
  • Waiting on a dependency: the task depends on a task or an outcome that isn’t done yet.

The bar is the share of the outcome’s open tasks that are stuck, and the figure beside it is stuck tasks out of open tasks. Outcomes with nothing stuck aren’t listed, and the most stuck come first. Click an outcome to open it.

With a project chosen, a task waiting on work in another project still counts as waiting.

Export#

Export CSV at the top of the page downloads everything on screen as one spreadsheet file, for the period and project you’ve chosen. It holds, in order:

  • the period’s dates;
  • the four headline figures, each with the previous period’s value;
  • tasks closed per week by people, by AI workers and unassigned;
  • tasks closed per project;
  • for each person, hours booked, working hours and utilisation;
  • for each outcome with stuck work, the tasks blocked and waiting.

What isn’t here#

  • Support desk figures. Service levels have their own report. See SLAs.
  • Estimate against actual time. Projik records booked time, not time actually spent, so there’s no report comparing the two.

    Type to search every page. ↑ ↓ to move, Enter to open.