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. The only status worth trusting is the one the assignee sets themselves, at the moment they finish, in the app they already have open. Everything else is a report about last Tuesday.

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

Four ways teams track work, and where each one breaks

Not one of them is stupid. They fail for the same reason: somebody has to keep typing the current state into them.

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 two versions of reality separate quietly and meet at the worst moment.

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 Done, from the group, from a direct message or from the Mini App. That tap is 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 the question “why did this slip” has an answer that is not a memory.
Review, kept separate from completion: Marking work done and having it accepted are two states. The card keeps them apart, so “finished” does not quietly mean “nobody looked at it”.
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.

Tracking tasks is not monitoring people

The line matters, and it is worth stating what the bot does not collect.

It records task events, not employees

Assignments, reports, deadline changes and comments on tasks. No screenshots, no keystrokes, no location, no activity timers. The bot works through the official Bot API and processes what is addressed to it, not the conversation around it.

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. A running public commentary on who is behind teaches people to hide 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.

Questions people actually ask

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. The chat card answers the quick question, the Mini App answers the wide one.

Does the bot read what we write in the chat?

No. It processes commands and messages addressed to it, through the official Bot API, with no userbot account involved. It cannot retrieve the group’s conversation, 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 are tracked but not reminded about, because there is no moment to remind against. 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, which is what keeps the number arguable in the right direction.

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