Reminders and tasks: nothing gets forgotten

When a count is finished, a list of differences appears and the real work begins there: someone has to go back to every row and find the cause. In practice this often shrinks to one remark made in an aisle: "Take another look at the tile adhesive in zone B". The worker says "sure", but the next day two other jobs turn up. A spoken instruction gets lost in two places: in the head of the person who received it and in the memory of the person who gave it. Below is a way to turn rechecking into a system of tasks that you can follow. No special software is required; routine matters more.

Where a spoken instruction breaks

In a Telegram group a message sinks under thirty others, and a paper slip vanishes from a desk. Three things then happen: two people recount the same place, nobody goes near another, and by evening it is unclear who did what. When the manager asks "is everything done?", the answer is usually a guess.

What a good task consists of

A task is a single record of the work, the person doing it, the deadline and the expected result. With five elements it is hard to misunderstand:

• place: zone, row, bin or rack, as precise as possible;
• item: full name and code;
• assignee: one specific person, not "the team";
• deadline: an hour or a day;
• result: what has to be written down and returned.

Compare the two. A poor task: "Something is off with the tile adhesive, take a look." A good task: "Zone B-3, second row, tile adhesive 25 kg, code 2041. Recount without looking at the booked balance. Today by 14:00. Write the result and the cause (a carton in the wrong bin, an opened sack and so on) in the comment."

On a recount task, do not show the assignee the booked balance. Once they see the figure, they may bend their own number towards it.

Statuses and deadlines

Four statuses are enough: new, in progress, done, could not be done. The fourth is the one most often forgotten, yet it is the most useful: "could not find it" is also an answer, it does not stall the process, and it signals the manager to make a decision.

Set deadlines by value. Say 23 differences appeared after the count and there are four people. The eight most expensive positions go on the list in the morning and are recounted by 12:00, the other fifteen by the end of the day. Finding the cause gets a separate deadline, for example two working days. One person can hold eight to ten open tasks at once; with more, the important ones sink.

A completed task does not mean the work is over. The manager reviews the result and takes one of three paths. If the recount matches the books, the difference is closed as "an error in the first count". If the recount confirms the first result, the difference moves on to the adjustment approval stage. If both results turn out different, the task goes for a third count to another experienced worker. Each path leaves a short note in the comment, and later the answer to "which cause repeats most often?" comes from there.

Reminders: when and to whom

A reminder is a signal, not a phone call, and two are enough. The first goes to the assignee an hour before the deadline; the second, if the deadline has passed, goes to the zone lead. A reminder repeated every day soon stops being noticed. Tasks older than two days land on the manager's separate list, and the manager decides what to do with them.

If there is no special software, Excel will do. Columns: position, place, assignee, deadline, status, result, comment. Set the status column to a drop-down list and filter by assignee. If you work through Telegram, open a separate group for tasks only: one message, one task, with the result written as a reply to that message.

Common mistakes

• Ten positions are lumped into one task; the assignee does half and the rest is lost.
• A task is closed with the word "done" but the result figure is not recorded.
• Every task is marked "urgent", so none of them is.
• The manager never reviews completed tasks, and the assignee stops writing results down.

Conclusion

The strength of a task system lies not in technology but in precision: who, what, where, by when and with what result. If you cannot run the rechecking yourself, the StockCheck team recounts the positions and hands over the causes of the differences as a list.