Field tasks: seeing that work sent from head office actually happened

In chain businesses work flows constantly from head office to the field: a planogram change, putting up campaign material, updating price labels, a safety check. Sending that work is easy; seeing that it was done is hard.

The classic solution is email and the phone: the regional manager calls, asks, takes notes. That is manageable across twenty stores; across two hundred it isn't.

A task is not an announcement

This distinction is the module's reason to exist. An announcement informs; a task expects a result. It is enough for an announcement to have been read; a task has to have been done.

That's why a task has three extra fields: a deadline, an owner and evidence of completion. Companies that try to squeeze tasks into their announcement system break the function of both.

Photo evidence

In field work a completion tick alone means little — the box can be checked and the work not done. An optional photo request closes that gap: the new shelf layout, the poster that went up, the area that was cleaned.

Getting the dose right matters. Requiring a photo for every task means the field team spends its day photographing, and it creates resistance to the system. Photos should be requested only for work with a visual outcome.

Task templates

Most work sent to the field repeats: the weekly cleanliness check, the monthly stock count, campaign start and end. Defining these as templates that can be assigned on a recurring basis markedly reduces the load on the head-office team.

As important as a template's content is who it goes to: all stores, a specific region, a specific format (high street, shopping centre). A wrongly targeted task is the fastest way to lose trust in the field.

Store health scores

When you need to look at the whole rather than individual tasks, a score combining a few indicators helps: task completion rate, number of overdue items, audit results, staff turnover.

The value of a score lies less in ranking than in showing anomalies. A store that has been fine for months dropping in score is a reason to visit. Turning the score into a performance penalty breaks the system: stores start improving the score rather than the work.

It has to be two-way

The most common design mistake is building the system one-way: head office sends, the field executes. But the field has things to say — missing materials, an instruction that can't be applied, customer feedback.

Being able to add a note to a task and having a "couldn't complete, because…" option builds that loop. The reasons behind incomplete tasks are the most valuable data head office has: if the same reason comes from thirty stores, the problem isn't in the field but in the instruction.

Mobile and poor connectivity

The user may be inside a stockroom, in a back office or on the road. It isn't enough for the app to work on a phone; its behaviour on a weak connection has to be predictable too. A connection dropping mid-upload must not lose the task.

Most of these teams have no corporate email account, so the sign-in path has to account for that — we cover that access problem in our engagement article.

Notification balance

Field teams can't check their phones through the day. Instead of an instant notification for every task, collecting the day's task list into a single notification at shift start works far better. Urgent tasks should stay in a separate tier and be used sparingly.

Audits and self-assessment

The close relative of field tasks is the store audit. The difference: a task makes work happen, an audit measures a state. Keeping both on the same infrastructure is practical because both use checklists and photo evidence.

One combination that works well: tracking the gap between the store's own self-assessment and the regional manager's audit. A systematic gap between the two scores shows that the store has misunderstood the standard — and that calls for training, not a penalty.

Measurement

• On-time completion rate — broken down by store and region.
• Average completion time — from assignment to finish.
• Reasoned non-completion — which task types consistently can't be done?

The third is the most instructive. A task type that consistently fails doesn't show incompetence in the field; it shows head office wrote an unrealistic instruction.

We cover shifts and handovers in a separate article and shared-area screens in our digital signage article.