Answer the question without rebuilding the spreadsheet
Twenty-two reports, built on demand from the records the team already created — what is pending, in progress, overdue or finished, who is carrying how much, what the forms said — narrowed to the dates, department or person you need, and exported 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.
- 22 built-in reports in five groups: tasks, people, handovers and collaboration, recurring schedules, and forms and checklists.
- Filter by a From and To date, department, person, status and priority — and by branch in a workspace that runs branches. Apply them together; Reset clears them.
- Each report states which date its range filters on — created, completed, due, blocked, handed over — and lists the filters it applied above the table.
- Export to CSV, Excel or PDF with the same filters: the file holds the rows the table showed, and Excel and PDF print the filters in their header.
- Access is gated by the report permission, and exporting by its own — reporting is not implicitly available to everyone with a login.
What you get
Overdue is a report, not a discovery
Pending, in-progress, overdue and blocked tasks are each a query rather than a memory. Overdue Tasks counts the days late, and Blocked Tasks shows the reason the assignee gave.
Workload you can defend
The Workload report shows what each person is actually holding — and, on rows of their own, the tasks still sitting in a department queue that nobody has picked up.
The period you are asking about
Choose the dates and every report narrows to them: completions on the completed date, overdue work on the due date, handovers on the day they happened. Dates are India time and include both days.
Audits read item by item
Form & Checklist Answers lists every answer given on a task form, and every checklist item ticked or not, with who ticked it, when, and the notes left on it. Pick one form to read a single audit.
How it works
In the order a person using it meets them.
- 1
Choose the report
Twenty-two reports, listed down the side of the screen in five groups. Each one is a defined query against live records rather than a blank report builder.
- 2
Set the filters
From and To dates, department, person, status and priority, then Apply. A filter a report does not use is greyed out, and the line above the table says exactly what was applied.
- 3
Check the chart and the insights
Beside the table sits a visualisation — a status donut where the rows carry a status, a ranked bar where they carry a count — and a short list of insights computed from the same rows. A report that is a list, such as Handover History, says so instead of drawing a misleading chart.
- 4
Export if it has to travel
CSV, Excel or PDF from the same screen, with the same filters. The file name says which dates it covers, and 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, with the days late, so the week starts by rescuing rather than planning.
- 2
Workload second
Who is carrying what, and what is still sitting unclaimed in a department queue. Two overloaded queues explain most of the first list.
- 3
Department Performance third
Total, completed, overdue and completion rate per department — narrowed to last week’s dates, it shows which team the first two lists are actually concentrated in.
- 4
Productivity last
What each person completed over the period. Read it against the workload rather than instead of it.
The result
The meeting is about decisions rather than about collecting the information the meeting was going to be about.
Tasks
Lists of tasks carrying the code, title, status, priority, assignee, department, due date, created date, who created the task and who last assigned it.
- Task Summary — every task in the workspace
- Pending Tasks — raised or assigned, but not yet in progress
- Tasks in Progress — in progress, in review or reopened
- Completed Tasks — everything that reached Completed, with the date it did
- Overdue Tasks — past the due date and still open, with the days late
- Blocked, Cancelled and Rejected Tasks — stuck or dropped; Blocked shows the reason
People
Where the work sits and how it is distributed. Employee and Department Performance follow the Performance Analytics settings, so they agree with the dashboards.
- Employee Performance — open, completed and overdue per person, with their base role
- Department Performance — total, completed, overdue and completion rate per department
- Productivity — tasks each person completed; the last 30 days unless you choose dates
- Workload — open tasks per person, plus the open tasks nobody has picked up
Handovers, collaboration and recurring schedules
The history that used to be readable only task by task, now across the workspace.
- Handover History — who passed which task to whom, with what was done and what was left
- Tasks by Collaborator and Collaboration Statistics — who joined collaborative work and how far it got
- Task Timings — how long each task took to be accepted, first answered and completed
- Recurring Schedules — active schedules, upcoming occurrences, success rate, failed runs and how often each ran, in India time
Forms and checklists
Form & Checklist Answers gives every answer on a task form its own row — choices by their label, people and departments by name — and every checklist item its own row, ticked or not, with who ticked it, when, and any notes. A Master Data answer is named for people who can read Master Data.
What these reports are not
Worth knowing before a trial rather than during one. There is no custom report builder: reports are a defined set, and bespoke analysis happens in a spreadsheet against an exported file. The longest lists stop at a stated limit — 1,000 handovers, timings or failed runs, and the answers from the 2,000 most recent tasks — and say so on the report; a narrower date range brings in the rest.
Frequently asked questions
Not as a custom query builder. Reports are a defined set of 22, each filterable and exportable to CSV, so bespoke analysis happens in a spreadsheet against exported rows rather than inside TaskIt.
Yes. Every report can be narrowed by a From and To date, a department, a person, a status and a priority — whichever of those the report uses — and by branch in a workspace that runs branches. Each report says which date the range applies to, such as the completed date or the due date. The filters you apply carry through to the CSV, Excel and PDF exports.
Anyone whose role holds the report permission, which by default is Admins and Managers; exporting is a separate permission. Both are stored on the role, not granted by a job title, so they 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 tables of what exists — tasks, people, handovers, schedules, answers — narrowed to the period and people you choose. Performance analytics is the timing analysis: average time to 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 for those two weeks and compare them with your spreadsheet.