A tracker is only as true as the last time somebody updated it, and in most teams that was last week. In Task Bundals nobody moves a card by hand. A piece of work changes state when the person sends proof and when a manager approves it, so the screen you look at is what really happened.
The owner opens one screen and reads three counts. Each count opens the work behind it. The same counts, kept over weeks, become a report by branch and by person.
The tracker’s first screen. Done, running late, stuck and open problems, with the person behind each one.
The same counts over a week or a month, by branch and by person. A report opens on screen, exports as a CSV file and prints.
Nobody picks a status from a menu. Each state is the result of something that happened.
The owner sees every branch. A manager sees the people and the work of their own branch. A staff member has no account: their link opens the one piece of work it was made for. There are no timers, no screen recording and no tracking in the background.
A count tells you something is late. These two screens tell you which piece of work it is and what is in its way.
Every piece of work with its person, its due time and where it stands. See it as a list, a board or a calendar.
What is blocking the work, raised by a manager or by staff from their own link. Each problem has a person and a fix-by time.
No setup fee. No charge per branch.