Use case · tracking work

Track employee tasks without a spreadsheet nobody updates

Every tracking method breaks in the same place: somebody has to type the current state into it. You can rely on a status when the assignee sets it themselves as they finish, in the app they already have open. Any other status shows things as they were when someone last got round to updating it.

Try it in your group

Free, no sign-up. Statuses, deadlines and history live on the task card.

Four ways teams track work, and where each one breaks

In each case someone has to keep the status current by hand, and after a few busy weeks nobody does.

A shared spreadsheet

Accurate on the day it was filled in, and drifting every day after. The person who maintains the sheet is rarely the person doing the work, so the sheet and the real state of the work drift apart, and nobody notices until someone makes a decision based on the sheet.

The chat itself

Everything is in there, technically. Reconstructing who promised what takes twenty minutes of scrolling, so nobody does it and “where are we” gets answered from memory.

A tracker in another tab

Boards and issue trackers work, and they live outside the conversation. The team keeps discussing work in the messenger, the board is updated by one conscientious person, and by week three it describes a project that no longer exists.

Asking at the standup

A verbal round of updates costs the whole team’s morning and rewards whoever presents best. It also arrives once a day, which is too late for a deadline at 18:00.

What gets recorded without anyone maintaining it

The status changes when the assignee taps “My part is ready”, from the group, from a direct message or from the Mini App. Nobody has to write anything down afterwards, because that tap updates the record.

Who is on the task and since when: Every assignee is a separate line with their own state: accepted, in progress, done, or sent back for rework. The card shows 1 / 3 rather than a single status that hides two people.
Lateness is calculated, not declared: Overdue is not a status somebody remembers to set. It follows from the deadline that applies to that person, which means it cannot be forgotten, and it clears itself when the work lands.
Deadline changes with their reason: When an assignee asks for more time, the request, your answer and the new date stay on the card. A month later, when someone asks why it slipped, you open the card instead of trying to remember.
Review, kept separate from completion: When review is on, marking work done and having it accepted are separate states on the card, so you can see which finished tasks nobody has checked yet.
Statistics per period: In the Mini App: the group’s tasks with filters, a deadline calendar, history, and a discipline rating showing who delivers on time and who is chronically late.
Your own summary across groups: One person can be in several work groups. The Mini App gives them a single list of what they owe, so tracking does not mean checking five chats.

Add the bot to a group

The record starts with the first task that has a deadline. The only setup is the group’s language and time zone.

Tracking tasks is not monitoring people

Managers often ask where that line is, so here is what the bot records and what it does not collect.

It records task events, not employees

Assignments, reports, deadline changes and comments on tasks. It takes no screenshots, logs no keystrokes and tracks neither location nor activity time. The bot works through the official Bot API and doesn't parse or store the conversation around the tasks.

The rating only counts what the assignee controls

If you sat on a result for a week before accepting it, that week is not charged to the person who did the work. Lateness is measured against their own deadline, not against a shared one that never applied to them.

The group hears about a miss once

When a deadline passes, one message names who did not make it, and it is removed when the task closes. When the chat keeps a running count of who is behind, people start hiding problems instead of raising them.

Each group sees only its own work

Tasks are isolated by chat, and every action is authorized on the server rather than by whichever button the interface happened to show. A member of one group cannot read another group’s tasks.

Frequently asked questions

Where do I see everything at once?

In the Mini App inside Telegram: the group’s tasks with filters, a calendar of deadlines, the history of changes and statistics for the period. For a quick check the card in the chat is enough, and for the wider picture you open the Mini App.

Does the bot read what we write in the chat?

No. It doesn’t parse or store ordinary messages: from the group it only notes who wrote, so it knows the members, and tasks are created with /task or in the Mini App. It works through the official Bot API with no userbot account, cannot retrieve the group’s history, and each group’s data is isolated from the others.

How does the bot decide that a task is overdue?

It compares the current time with the deadline that applies to that assignee, personal one included. Overdue is a computed property rather than a status anyone sets, so it cannot be left switched on after the work arrives.

What happens with tasks that have no deadline?

They get no automatic reminders, because there is no moment to count from, but the author can add a manual one. When the date should come from the assignee, switch the task to ask them for one: the bot requests a deadline, they name it, and reminders start from there.

Can I see who is systematically late?

Yes, in the per-period rating. It is built from personal deadlines and excludes delays caused by a review that was waiting on you, so the number reflects what the assignee controlled.

One group, one week

Let the tracking happen while people work

Add DeloPulse to a work group, assign the tasks you would have written into a spreadsheet, and compare the two on Friday.

Add the bot to a group