Visit Scenario
A visit scenario is the situation an observer is briefed to create during a visit, so that behaviour under a specific condition can be observed rather than inferred. Requesting an item that is out of stock, attempting a return, or asking a question that requires product knowledge are all scenarios. Without one, an observer records only whatever happened to occur.
What Is a Visit Scenario?
Some behaviour only appears under specific conditions, and waiting for those conditions to arise naturally makes a programme unaffordable. The scenario manufactures them. Requesting something the shelf does not hold, attempting a return, querying a price, or requesting something requiring product knowledge each build a defined situation where the reaction is witnessed directly instead of being guessed at from an ordinary transaction.
The design has to survive contact with a real outlet. A reason for being there that no genuine customer would have marks the visitor out immediately, so the scenario is ordinary enough to be unremarkable while still producing the interaction the scorecard needs. Timing is part of it rather than logistics, since an outlet on a quiet Tuesday morning and the same outlet on a Saturday afternoon are different operations. What the visitor may and may not do is settled in writing beforehand, because whether they may make a purchase, press a refusal, ask for a manager or record anything carries practical and occasionally legal consequences.
How Visit Scenario Is Scored on a Visit
The situation itself carries no marks. What is scored is how the outlet responded to it.
- The visitor first records whether the situation was successfully created at all, since a scenario that could not be run produces no valid observation.
- Where it was, the responses are scored against the instrument in the ordinary way, with the situation providing the condition rather than the measure.
- Where it was not, whether the doors were shut, the product was absent or the exchange never came about, the visit is flagged as invalid and rerun rather than marked on whatever else occurred.
- Deviations by the visitor are recorded explicitly, because a situation executed differently from the brief has measured something other than what was designed.
- Across a cycle, results are read only against visits where the same situation was actually created, since anything else compares different measurements.
How Visit Scenario Works in Practice
- The behaviour to be observed is named first: how a refusal is handled, whether product knowledge exists, how a return is processed, or what happens when an item is unavailable.
- A situation is designed that produces it, plausible enough that a genuine customer might create it and specific enough to force the interaction.
- Timing is fixed as part of the design. Day of week, hour and trading conditions are varied across the programme, because a cycle run at one time of day measures that time of day.
- Boundaries are written down before anybody travels: whether a purchase is required, whether a refund may be attempted, whether a manager may be asked for, and what may be recorded.
- The visitor executes it and records what happened against the instrument. Where the situation could not be created, because the outlet was closed or the circumstances did not arise, the visit is marked compromised and repeated rather than scored.
Visit Scenario: A Worked Example
| Scenario | Outlets | What it tests |
|---|---|---|
| Straightforward purchase enquiry | 18 | Baseline service |
| Request for an out-of-stock item | 18 | Whether alternatives are offered |
| Return without a receipt | 12 | Policy consistency |
| Complaint about a previous purchase | 12 | Escalation handling |
| Price query against a competitor | 18 | Discounting discipline |
The same fortnight's programme, viewed by scenario rather than by outlet.
Each scenario is scripted to the point where the shopper's own judgement is removed, because the purpose is to compare branches rather than to describe one visit well. The out-of-stock and no-receipt scenarios are the informative ones: they place staff in a situation the policy covers but the training may not, and that is where practice diverges most between outlets. Scenarios are rotated between rounds so that staff cannot learn the test. Running every scenario at every outlet would be cleaner statistically and is usually too expensive, so the two lighter scenarios are sampled.
Common Mistakes With Visit Scenario
A poorly designed situation produces observations nobody can use.
- Giving the visitor a pretext no ordinary customer would have, which is noticed immediately and changes everything that follows.
- Running every visit at the same time of day, so the programme measures one trading condition and reports it as the outlet.
- Leaving it to the visitor to decide whether to buy, press a refusal or ask for a manager, which produces inconsistent visits and occasionally worse.
- Designing a situation the outlet cannot actually encounter, so staff respond to something artificial and the score reflects the design.
- Omitting what the visitor may record, which is a legal question as much as a practical one and should never be settled in the aisle.
Need Help With Visit Scenario?
A definition describes; it does not verify. Once behaviour under a specific condition has to be observed, somebody has to attend, count and reconcile, which is the work behind how a mystery audit works. The starting point is a list of locations and the records as they currently stand.