Stop chasing your team: the system that replaces checking up by phone

You know the typical day. A message to find out whether the cleaning is done. A call to check the contractor actually came. A spreadsheet nobody fills in. By evening you roughly know what has been done, and the next day you start again. This is not a management problem. It is a system problem.

The real cost of chasing

Chasing people costs you three times. First, the owner's time: a few minutes per follow-up, several dozen follow-ups a day. Second, attention: every follow-up breaks what you were doing, and getting back into it takes longer than the follow-up itself. The third is the most expensive and nobody counts it: the relationship. A team that is chased all the time ends up concluding that it is not trusted, even when that is not the message.

The usual reflex is to add a tool. A dedicated group chat, a shared spreadsheet, a task app. Three weeks later the tool is dead and the chasing is back, with a layer of guilt on top.

Why tracking spreadsheets die

Because they ask for extra work from people who get nothing out of it. A cleaner who finishes a property at 2 pm has already finished their job. Asking them to open an app and tick a box adds an unpaid task whose only beneficiary is you.

They will do it for three days, then every other day, then not at all. That is neither bad will nor a training problem. It is the rational behaviour of someone given extra work with nothing in return.

The conclusion is simple, and it changes everything: tracking must not be a task, it must be a by-product of doing the work.

Define “done” before measuring anything

Before any tool, you have to settle a question most businesses have never settled: what is a finished task?

In our own cleaning operation, the answer took a while to settle. Is it done when the person leaves the property? When the dirty linen has gone? When the supplies are restocked? When the photos are taken? As long as everyone had their own definition, no measurement meant anything, and two people could say “it's done” while talking about two different realities.

Write the definition in one sentence, test it on ten real cases, fix it, freeze it. That sentence is worth more than any software. Without it, you will be measuring noise.

Let the work produce the proof

Once “done” is defined, the question becomes: what trace does the work naturally leave?

Often the trace already exists somewhere and nobody collects it. A guest departure is in the schedule. An access code was used. A message was sent. A photo was taken because it is already needed for something else. The system work is to connect those signals so the information comes up without anyone having to type it in.

In practice it looks like this: the job appears automatically in the morning on the phone of the person concerned, with the address, the time and the checkpoints. They confirm it in one gesture at a moment when the phone is already in their hand, for example to send the photo they are asked for anyway. That confirmation time-stamps the job, updates the schedule and makes the information visible to everyone at once.

Nobody filled in a report. Nobody chased anyone. The information exists because the work happened.

Make visible rather than monitor

There is a difference in kind between a system that monitors and a system that makes things visible, and teams feel it immediately.

Monitoring measures people: who was slow, who missed what. Making visible measures the state of the work: what is done, what is not, what is late. The first creates fear and false data, because people end up reporting what you want to hear. The second creates autonomy, because everyone sees their place in the whole and no longer needs to ask.

A sign that never lies: when the system is well built, the team is the first to ask for it back when it breaks down. They do not want to be controlled, they want to stop wasting time coordinating.

The only metric that matters at first

It is tempting to set up a dashboard with fifteen indicators. Do not do it yet. At the start, a single number tells the truth: how many times a day do you have to ask where something stands?

Count it for a week, before changing anything. Count again a month later. If the number has not dropped, the system is not working, however many screens you have installed. This number has another merit: it cannot be gamed.

The mistakes we see most often

1. Installing the tool before writing the process. A tool speeds up what exists. If the process does not exist, the tool only speeds up the mess.
2. Asking for double entry. If the information has to go into the app and into the group chat, the app will die. One piece of information, one place.
3. Confusing tracking with reporting. Tracking serves the team during the work. Reporting serves the owner afterwards. If your tracking tool is really a reporting tool, the team has no reason to use it.
4. Trying to cover everything from day one. Start with a single type of job, the one that comes up most often. Run it for a month. Then extend.

Where to start this week

Take the job you chase most often. Write in one sentence what “done” means for it. Look for the trace that job already leaves somewhere. Connect that trace to a single place that both you and the team look at. Then count how often you chase.

Within two weeks you will know whether the subject deserves a real investment, and you will know it from a number rather than a feeling.

Frequently asked questions

How do you stop chasing your team for updates?

By making tracking a by-product of the work rather than an extra task: define what “done” means, find the trace the work already leaves, and bring it into one place that both you and the team look at.

Why do team tracking spreadsheets get abandoned?

Because they ask for extra work from people who get nothing out of it. After a few days the boxes stop being ticked. It is rational behaviour, not bad will or a lack of training.

What is the difference between monitoring and making work visible?

Monitoring measures people, who was slow and who missed what, and tends to produce fear and false data. Making work visible measures the state of the work, what is done, not done or late, and gives the team autonomy.

Which metric shows that a tracking system works?

The number of times a day you have to ask where something stands. Count it for a week before any change and again a month later: if it has not dropped, the system is not working.