Knowing if a retail storetask is done is like finding a needle in a haystack.

Chasing completion is a full-time job. Nobody in your business has that job.

A Monday morning at a fashion retailer with about 60 stores. The VM lead opens the group chat to check the weekend flip went in.

She counts thumbs up. Nineteen, out of sixty.

So the spreadsheet comes out, and the rest of the morning goes on working out which forty-one stores are silent, which of those actually did the work and forgot to say so, and which need a phone call. Her description of this:

"It's almost a whole role sometimes."

And then, in the same conversation, how the business closes the gap:

"We get the naughty list out and we've got a weekly newsletter and we name and shame where required. It is constant, the follow-up."

Two sentences, and you have the operating model of a large number of retail businesses.

Somebody already has this job. It just isn't in their position description.

At a second retailer, in a different part of the fashion market, chasing task completion is close to a full-time job for the VM team. Not a task within a job. A meaningful share of what the function does all week.

Two independent businesses, and in one the load sits on operations while in the other it sits on visual merchandising. Which tells you the work is structural rather than a quirk of how one team is organised.

So do the arithmetic on your own business. Whose calendar does the chasing sit on? What did you hire that person to do? What are they not doing this week because forty-one stores didn't reply?

Nobody put this role in a budget. It is being staffed anyway, out of the time of people you hired for something else.

The naughty list is the enforcement mechanism a lot of retailers actually run on

It is easy to read "name and shame" as a bit of retail folklore. It isn't. For the operator quoted above, it is the genuine control mechanism. There is no other lever.

A visual merchandising lead at a liquor retailer has it worse. Around 30% of her stores did not complete a network survey. She had to work out which ones, by hand, and then chase them, except that she is not permitted to contact stores directly. Task requests in her business route through a central comms portal, on a schedule. So the follow-up for a survey nobody filled in has to be queued behind everything else the support office wants to send.

Public shaming is what a business reaches for when it has no record. It is a symptom rather than a strategy, and it is expensive in a way that never shows up anywhere. It spends your relationship with the stores you most need to move.

A thumbs up is not evidence, and everyone involved knows it

An owner-operator running a womenswear network described the version of this that most people will recognise:

"If I asked everyone in my chat group have you all signed off every store for VM… everyone had to give me a thumbs up. And at any point in time if we went and did store visits and something wasn't done, I would go back and I would say, but you gave me a thumbs up for that."

Asking for photos instead sounds like the obvious upgrade. Sometimes it is. But an operator at a hardware retailer told us what happened when they mandated photo evidence without governing it. One store manager worked out nobody was checking, photographed his carpet, and submitted it for every task.

His conclusion is the one worth keeping:

"Don't ask for it if you're not going to govern it and check it. It loses credibility really quick."

We have written about the difference between reported, verified and proved work [in more detail elsewhere]. The short version for this post: asking for evidence you never look at is worse than not asking, because the stores learn what the ask is worth and apply that lesson to the next one.

Chasing scales with store count. Nothing else in the process does.

Here is why this feels worse every year even though nothing about it got harder.

From an apparel group with more than 500 stores:

"Sometimes there might be a task where you just have to respond to an email and say yep this is done… when you apply that by 500 plus stores, that's a lot of wasted time."

And from a retailer at 60 locations, already at the limit:

"As we get bigger too, with 60 locations, we haven't got time to read through every single end of week report."

The chasing load rises roughly in line with store count. The team doing the chasing is fixed. Open twenty stores and you have added twenty stores' worth of follow-up to the same person's Monday, and nobody proposed a headcount for it because nobody has ever named the work.

That 60-store retailer and the 500-store one are describing the same wall at different distances from it.

You are chasing because the original message never confirmed itself

Chasing is not a discipline problem. It is a downstream cost of sending instructions through a channel that carries no confirmation.

An operations manager at an apparel group traced it directly:

"A lot of our comms and directions are all going through email and emails get overlooked, they get missed. So then things don't get done and it's just this constant trying to find out who's done what, and follow up."

Another described the split of her team's week: "we spend quite a lot of time sending out coms to stores and obviously quite a lot of time following up to make sure that the execution has actually taken place."

Sending and chasing as two halves of the same job. The second half exists because the first half produced no record.

Measure the gap, not the people

If you want to replace the naughty list with something, replace it with three numbers.

Time to live. How long from deploying a change until every store is actually doing it. This is the number that tells you whether your process works, and it is far more useful than a completion percentage.

Verified completion rate. What proportion of completions came with evidence attached rather than a tick.

Rework rate. How often work had to be done again because it wasn't right the first time. This one is uncomfortable and it is the most diagnostic of the three.

A note on naming, which matters more than it should. Call it "time to live" rather than anything that sounds like a score being kept on stores. One customer asked us to soften the tone of an automated summary because the output read, in his words,

"a bit like you're annoyed. Do something about it, I guess."

Any completion metric you publish inherits that risk the moment a store manager reads it.

And be honest about what changes. Follow-up doesn't disappear. It moves from chasing every store to chasing the exceptions, which in most weeks is a much shorter list.

The short version

Chasing completion is a real job. It is unfunded, it is unnamed, and it is sitting on your VM lead or your ops coordinator on top of what you actually hired them for.

It scales with every store you open. Thumbs up and photographs of carpets are what you get when you ask for evidence without a system to hold it.

Replace the chase with a record, and the naughty list stops being necessary. Not because stores got better, but because you stopped needing to find out.

Frequently asked questions

Who is responsible for chasing task completion in a multi-store retailer? In practice, usually nobody formally. It falls to whoever owns the directive, which tends to be the national VM manager, the store comms lead or a retail ops coordinator, on top of their actual job.

How do retailers currently confirm a campaign went live in every store? Group chat sign-offs, emailed photos, spreadsheets, and a store visit some weeks later. All of those are self-reported, and none produces a record you can run a report against.

Does asking for photos fix it? Only if you check them. One store manager submitted a photo of his own carpet for every task once he worked out nobody was looking. Asking for evidence you never review costs you credibility faster than not asking at all.

What should you measure instead of completion? How long it takes from deploying a change until every store is actually doing it, what proportion of completions were verified rather than ticked, and how often the work had to be redone.

Every quote in this piece comes from a recorded conversation with a retail operator. Names, brands and identifying details have been removed.