Feature

Store checklists

The checklist decides the quality of everything that follows. If the questions are vague, no analysis can rescue them.

What a visit checklist is

A visit checklist is the set of questions the team answers at every point of sale, defined in advance and identical for everyone. It serves two purposes at once: making sure nobody forgets to check something important, and producing answers in a comparable format, so hundreds of visits can be added up rather than read.

Where most checklists fail

They fail by being too long and by using open questions where closed answers belong. A 40-question checklist gets rushed; a free-text field produces 30 different ways of saying the same thing. Either way the data exists but decides nothing.

How to design one that works

  1. Start from the decision, not the question

    For every question, know which decision it supports. If there is no decision attached, the question goes. That single criterion cuts half of most checklists.

  2. Prefer closed answers

    Yes/No, a fixed scale or a list of options. Free text only for what cannot be anticipated, and always as a complement.

  3. Keep it short

    Between 8 and 15 questions per brand is the range where completion quality stays high. Above 20 it starts to drop.

  4. Require photos where evidence matters

    Make the shelf and promotional material photos mandatory. That is what turns an answer into proof.

  5. Test in the field before launching

    Run three real visits with the checklist before handing it to the team. There are almost always two ambiguous questions that only surface in store.

  6. Review with data

    After a quarter, look at which questions always get the same answer. If 98% answer "yes", the question stopped informing and can go.

Who defines and who answers

Trade marketing

Defines what gets checked and against what criteria, aligned with what was negotiated with the retailer.

Supervision

Adjusts the checklist when a question turns out ambiguous or something recurring is not covered.

Field team

Answers in store. They are the ones who know which questions make no practical sense, and worth listening to.

Analysis

Uses the answers to compare. Entirely dependent on questions being closed and stable over time.

Use cases

1

Per-brand checklist in a multi-brand visit

A merchandiser represents four brands in the same store. Instead of four visits or one giant checklist, they answer one checklist per brand inside a single visit. The data comes out separated by brand, which later allows analysing each one on its own and seeing which others it co-occurs with.

2

Seasonal campaign checklist

For six weeks a block of three questions about the Christmas campaign is added. When the campaign ends the block is removed, but the answers stay in the history and can be compared against next year.

3

Regulated compliance audit

In categories with display rules, the checklist includes the legal criteria and requires a photo. The record then doubles as proof of compliance, with date and location.

What changes

Badly designed checklistWell designed checklist
Open questions, free-text answersClosed answers, addable and filterable
40 questions rushed through10 to 15 questions answered with attention
Changes every quarterStable, therefore comparable over time
Photos optional and rarely presentMandatory where evidence matters
Nobody knows what decision it supportsEvery question has a decision attached

Specifications

Checklists per workspaceNo limit
Question typesYes/No, multiple choice, scale, numeric, text and photo
ScopePer brand, per category or per location type
Mandatory fieldsConfigurable per question
Health score weightConfigurable, so critical criteria weigh more
ChangesOld answers keep the checklist version they were given under
AnalysisFilterable in the Analysis Centre by question, answer and period

Frequently asked questions

How many questions should a checklist have?

Between 8 and 15 per brand is the range where completion quality stays high. Above 20 answer quality drops visibly, because people start answering out of habit.

Can I have different checklists per store type?

Yes. A hypermarket and a convenience store do not share criteria, and forcing the same checklist produces "not applicable" answers that pollute the data.

What happens to the history if I change the checklist?

Old answers stay tied to the version they were given under, so they are neither lost nor remapped to the wrong question. Frequent changes hurt comparability, so it is worth batching them quarterly.

Should I use free-text questions?

Sparingly, and always as a complement to a closed answer. A notes field at the end is useful; replacing objective criteria with free text makes analysis impossible.

How does the checklist feed the health score?

Each question can carry a weight. Negative answers on high-weight criteria pull the store indicator down further, which makes the health score reflect what actually matters instead of treating everything equally.

Can the team suggest changes?

They should. The people in store are the first to notice an ambiguous question. It is worth reviewing the checklist with the team once a quarter.

Related

Want help designing the first checklist?

In the setup session we build the checklist with you, starting from what you already check in stores today.