Answer the question without rebuilding the spreadsheet
Reports are built on demand from the records the team already created — pending work, overdue work, workload, handover history, collaboration and recurring execution — and export to CSV, Excel or PDF.
Reporting is included on every plan term.
The problem
The monthly report is usually somebody’s Sunday
When the record of the work is a chat thread and a spreadsheet, reporting means reading both and retyping the result — which is slow, error-prone and, by the time it is finished, describing last week.
- Numbers are assembled by hand, so two people produce two different answers to the same question.
- The report describes the period it took to write, not the period it is about.
- Nobody can drill from a total to the tasks behind it, because the total was typed.
- Overdue work is discovered when a customer asks, not when the date passes.
- Workload is estimated from impressions, which is how one person ends up with three times the queue of another.
How TaskIt handles it
Reports computed from the same rows the team is working in
Every report is a query over live records — no import, no export-then-clean, no separate reporting database that is a day behind.
- Five report groups covering tasks, people, workflow, collaboration and recurring schedules.
- Built on demand, so a report run at 10:00 describes the workspace at 10:00.
- Export any of them to CSV for further analysis, Excel for a colleague, or PDF for a meeting.
- Access is gated by the report permission, which also governs the performance figures — reporting is not implicitly available to everyone with a login.
- Company-scoped by the signed-in user’s workspace, so a report can only ever contain your own data.
What you get
Overdue is a report, not a discovery
Pending and overdue tasks are a query rather than a memory. The list is the same one the task table shows, so acting on it is one click away from reading it.
Workload you can defend
The Workload report shows what each person is actually holding. Rebalancing a queue stops being a negotiation about whose impression is right.
The recurring routines are measurable
Execution success rate, failed executions and most-frequently-recurring tasks turn a checklist into something with evidence behind it.
Exports go where the meeting is
CSV when someone wants to pivot it, Excel when they want to read it, PDF when it has to be attached to minutes.
How it works
In the order a person using it meets them.
- 1
Choose the report
Reports are grouped by what they answer: tasks, people, workflow, collaboration and recurring. Each is a defined query, not a blank report builder.
- 2
Set the scope
Narrow to a department, a person or a date range where the report supports it, and run it against live records.
- 3
Read it on screen
The result is a table you can scan, so a quick question does not require an export at all.
- 4
Export if it has to travel
CSV, Excel or PDF from the same screen. The exported file contains what the table showed — there is no second, differently-calculated version.
A Monday morning review in ten minutes
Four reports, in the order that makes each one useful.
- 1
Overdue Tasks first
Anything already past its date, so the week starts by rescuing rather than planning.
- 2
Workload second
Who is carrying what. Two overloaded queues explain most of the first list.
- 3
Failed Recurring Executions third
A routine that silently stopped is the failure nobody reports, because there is no requester waiting for it.
- 4
Handover History last
Work that has changed hands three times usually points at an unclear owner or a step that belongs to a different department.
The result
The meeting is about decisions rather than about collecting the information the meeting was going to be about.
Tasks
The operational four: what exists, what is outstanding, what is finished and what has slipped.
- Task Summary
- Pending Tasks
- Completed Tasks
- Overdue Tasks
People
Where the work sits and how it is distributed. Productivity is a rolling 30-day view; workload is what each person is holding right now.
- Employee Performance
- Department Performance
- Productivity (30 days)
- Workload
Workflow and collaboration
The reports that only exist because handovers and department work are recorded as events rather than as field edits.
- Handover History — every transfer, in order, across the workspace
- Acceptance & Completion Times — acceptance time, first response time, completion time
- Tasks by Collaborator — who contributed to shared work
- Collaboration Statistics — how shared work is actually being shared
Recurring
Whether the scheduled routines are running, and whether the tasks they create are being done.
- Active Recurring Schedules
- Upcoming Recurring Tasks
- Recurring Execution Success Rate
- Failed Recurring Executions
- Most Frequently Recurring Tasks
Frequently asked questions
Not as a custom query builder. Reports are a defined set — eighteen definitions across five groups — and each exports to CSV, so bespoke analysis happens in a spreadsheet against exported rows rather than inside TaskIt.
Anyone whose role holds the report permission, which by default is Admins and Managers. It is a stored permission on the role, not something granted by a job title, so it can be given to one person without giving them anything else.
Yes. Reports are built on demand from current records rather than from a nightly snapshot, so a report describes the workspace at the moment it was run.
Reports are point-in-time tables — what exists right now. Performance analytics is the timing analysis: average time to accept, start, complete and turn around, computed from stored timestamps, with time windows and rankings.
Where to go next
The capabilities either side of this one, and the problems it is bought to solve.
Run the report you currently build by hand
Put a fortnight of work through a workspace, then run Workload and Overdue Tasks and compare them with your spreadsheet.