Skip to content
Task tracking

See what is open, what is late and who has it

Tracking work should not mean chasing people. Every task in TaskIt has an owner, a status, a due date and a timeline, so the current state of the whole workload is something you read rather than something you assemble.

Free for 30 days. No card required.

Sound familiar?

The problems this page is about

If none of these describe your week, a different page on this site probably does.

How it goes today

  • You find out something slipped when a customer tells you

    Overdue work has no way to announce itself when the record of it is a message. By the time it surfaces, the apology is already the first move.

  • Every status update costs somebody twenty minutes

    A stand-up or a round of "where are we on this?" is the manual replacement for a status field. It scales with headcount and stops the work it is asking about.

  • Stuck and slow look identical

    A task that has been blocked for four days and a task that is progressing normally are both simply open. Nobody knows which one needs help.

  • Nobody agrees on what is actually assigned

    "Can someone look at this" was assigned to everyone and therefore to no one — so it is either done twice or not at all.

With TaskIt

  • One owner, visible at all times

    A task always has exactly one current assignee. Ownership is a field with a name in it rather than a shared assumption, and it stays correct through every handover.

  • A status that means something

    Twelve lifecycle statuses distinguish not started, in progress, handed over, blocked, awaiting review and approved. Blocked in particular is a deliberate statement with a recorded reason, not an absence of movement.

  • Dates that surface themselves

    Every create form carries a due-date picker with a past-date guard. Overdue work appears in the Overdue Tasks report and on the dashboard rather than waiting to be noticed.

  • Three views over the same records

    A board when you want to see where work is stacking up, a table when you want to filter and act in bulk, a grid when you want to scan. Each person keeps their own preference.

  • A timeline behind every task

    Accepts, progress updates, comments, attachments, handovers, reviews, joins and leaves are all recorded with timestamps, so "what happened here?" is answered by reading rather than by asking.

Worked example

Tracking a week of work at a 20-person business

What replaces the Monday meeting and the Thursday chase.

  1. 1

    Monday morning

    Open Overdue Tasks. Four items, three of them with the same department — which is the real finding, not the four items.

  2. 2

    Monday, five minutes later

    Open Workload. One person is holding eleven tasks and two are holding three. The overdue list stops being a mystery.

  3. 3

    Wednesday

    Two tasks show as Blocked with recorded reasons. Both are waiting on the same supplier, which is one phone call rather than two.

  4. 4

    Friday

    Completed Tasks for the week, exported to PDF, is the weekly report — assembled by a query rather than by a person.

The result

Nobody was asked for a status update all week, and the two things that actually needed a manager got one on the day they became visible.

What you end up with

The result

No percentages, because nothing here has measured yours — these are the changes the mechanism produces.

Late work is caught while it can still be fixed

The gap between a task slipping and someone noticing shrinks from "when it is escalated" to "when the date passes".

The status meeting loses its purpose

When the information is already on screen, the meeting becomes about decisions — or stops happening, which is usually the better outcome.

Workload becomes a fact, not an argument

Rebalancing a queue is a conversation about a report rather than about whose impression of "busy" is more accurate.

History survives the people

Because the task ID never changes, the trail stays readable long after the person who did the work has moved on.

FAQ

Frequently asked questions

A to-do list records what should happen. Task tracking here records what did happen: who accepted the work and when, what progress was logged, whether it was handed over, whether it was blocked and why, and who approved it. That history is what makes the current status trustworthy.

Very little. Accepting a task moves it to In progress and stamps the start time in one action, a handover records the transfer as part of doing it, and submitting for review is the same click as finishing. Progress figures are the only regularly typed value.

It depends on the permissions stored on your role. Company-wide visibility is a permission a role either has or does not — it is not implied by being an administrator. Employees see their own work plus their department’s unclaimed queue.

The assignee marks it Unable to Complete with a reason, which moves it to Blocked and puts it in front of a manager, rather than leaving it to sit quietly until the due date passes.

Keep reading

Where to go next

The capabilities behind this page, and the neighbouring situations they also cover.

Track one week and compare

Run your real workload through a workspace for a week, then look at Overdue Tasks and Workload against what you thought was true.