Guide · 19 August 2026

How to track assignments in a work chat

Most assignments that disappear in a chat were handed out without a named owner or a deadline, and nobody was asked to report back. Careless people are rarely the cause. Here is what breaks, and seven rules that fix follow-through without rolling out a heavyweight system.

Written for a work group in Telegram: a department, a branch office, contractors, a project team.

Why assignments get lost in a chat

There are four reasons, and each comes from how the request was worded. The people who received it are rarely the problem.

Ownership is diffused

“Folks, we need that report” is addressed to everyone and therefore to no one. When several people could take it on, each of them assumes someone else will. Psychologists call it the bystander effect, and the more people see a request, the less likely any one of them is to act on it.

The deadline has no date

“By the end of the week”, “when you get a chance”, “ASAP” are not deadlines. There is no moment at which such a request becomes overdue, so there is no moment at which a reminder is due either.

Nobody owes you a report

No one is obliged to say “done”. The work counts as finished when the person who asked happens to find out, or never finds out and discovers the gap in a meeting.

The feed eats the context

Forty messages later the request has scrolled away. Nobody will go looking for it: it is easier to hand the same job to whoever is online right now. Sometimes two people end up doing it, and sometimes nobody does.

Seven rules that fix it

Each rule changes how a request is written, and you can start with your next message instead of waiting for people to change their habits.

Every piece of work has one owner, named

“Could someone handle this” is the most common shape of an assignment that never happens. Name the person. If the work is shared, split it. Instead of “put the deck together”, write “Marat: the sales slides; Dilnoza: the financials”. Then each part has a single person responsible for it and a status of its own.

Joint work without a split is fine too, but then every participant reports individually rather than the senior one reporting for all.

A deadline is a date and a time

“By the end of the week” reads differently to everyone: Friday 6 p.m. to one person, Sunday night to another. Write “by 22 Aug, 18:00”. With an exact time everyone reads the deadline the same way. The task also gets a moment when it becomes overdue, and a reminder can go out ahead of that moment.

If the assignee sets the date rather than you (“when can you do it?”), still insist on an actual date and record it exactly like an assigned one.

The person who did the work reports it

When one person answers for five, you are monitoring their memory rather than everyone else’s work. Whoever did the work marks it done, and the assignment closes only once everyone has, not when the first person reports.

There is a side effect that often matters more than the tracking. Once the group sees progress name by name, anyone falling behind can see it for themselves, and the manager does not have to point it out in front of everyone.

Reminders arrive before the deadline, and privately

Once the deadline has passed, a reminder can only help you work out what went wrong. A useful one arrives a day, three hours and an hour before, and it goes privately to whoever has not finished. A public “reminder for everyone” punishes the people who already delivered and stops working by the third time.

The group should hear about an overdue task exactly once. If the group chat gets “still not done” every morning, people stop reading it within a few days.

Results get signed off

When the assignee marks the work done, that is their claim about it. Until the person who asked accepts the work, the assignment is not closed. Sign-off takes seconds and removes the most common argument: “but I did it” versus “that is not what I asked for”.

Work sent back for rework should stay on the same assignment, with its history and the same person. If it becomes a new task, the earlier discussion is lost and the statistics no longer match what happened.

Recurring duties are not created by hand

A weekly report or a monthly reconciliation runs on a schedule, and so does opening the shift every morning. Whoever creates these by hand will miss one sooner or later, usually in a week that is already overloaded. A recurring assignment should appear on its own, and its absence should be noticeable.

Status lives in one place

If you have to scroll back through the conversation to work out where things stand, that is detective work. An assignment needs one card that updates instead of ten messages about it. Open the card and it tells you what has to be done, by whom and by when, and who has already reported.

How to phrase an assignment: what → who → when

Every assignment has to answer these three questions. When one answer is missing, the message is closer to a wish, and nobody can be held to it.

This is how it gets lost
  • “Folks, we should update the price list”
  • “Get it done by the end of the week”
  • “Let me know when it’s ready”
This is how it can be tracked
  • “Update the September price list in the shared folder”
  • “Marat: the equipment section; Dilnoza: the services section”
  • “Due: 22 Aug, 18:00”
  • “Mark it done on the assignment card and attach the file there”

A practical test: reread the message as if you were not the author. If it is unclear who exactly has to do something and at what point it counts as done, rewrite it before sending.

Which of these rules DeloPulse enforces

You can follow the rules above by hand. The bot is for the busy weeks, when nobody has time to check each message against them.

A named owner
An assignment goes to several people at once, and each of them gets their own status instead of one shared status.
A real deadline
In the Mini App form the due date is a mandatory step: a date, a deadline the assignee names when the bot asks, or an explicit “no deadline”.
A report from everyone
Every assignee has their own “Done” button. The assignment closes once all of them have used it.
Reminders before the deadline
For a deadline with a time, 24 hours, 3 hours and 1 hour ahead; for a date-only deadline, on the morning of the previous working day and on the morning of the due day. As direct messages, and only to those who have not reported yet.
Sign-off
When review is on, the person who asked accepts the work or sends it back for rework on the same card, without a new task.
Recurring duties
Repeating assignments are created on schedule automatically and reach assignees like any other.
One visible status
One card in the chat that is edited on every change, instead of a stream of new messages.

The mechanics are covered on the home page; how this differs from other Telegram task bots and trackers is broken down in the comparison with alternatives.

Frequently asked questions

Where do I start if there are dozens of assignments already buried in the chat?

Do not migrate the old ones. Start with the next assignment: name the person, set a real due date and agree that marking it done is mandatory. Within a week you will see which assignments used to simply vanish.

Do we need a task tracker if the team is small?

For a small team a full tracker is usually overkill: it gets set up, the work still happens in the chat, and the system drifts away from reality. It is more practical to leave the work where it already happens and add tracking on top of the conversation.

How do I keep track without becoming a micromanager?

Tracking annoys people when it is manual and public: “any update?” in the group chat. A private reminder before the deadline and a status everyone can see remove the need to ask at all.

What if the assignee just goes quiet?

Silence is already a signal once an assignment has a deadline and a mandatory report. First a private reminder before the deadline, then a single public notice that it is overdue. Daily nagging in the group chat does not work, because people stop seeing it.

Should I treat an assignment as done just because the assignee says so?

No. The assignee’s mark is a claim; what closes the assignment is your sign-off. Checking takes seconds and costs far less than discovering the wrong result a week later.

Easier to try than to read about

Hand out your next assignment by these rules

Add DeloPulse to a work group and assign a task to two colleagues with a deadline. You will see the difference on the first card. It costs nothing and needs no sign-up.

Add the bot to a group