This is the standing file for your mystery-shopping programme — one copy that your account team and ours both keep current. It is not tied to any single visit or reporting period. Everything a coordinator needs to dispatch work correctly lives here, so update it the moment a location, cadence or cap changes.
Key contacts on both sides — name, role, email and what they decide:
One row per location. Cadence is how often that location is visited — coordinators dispatch straight from this list.
Locations added, closed or paused since the last review:
Approved Scenario Library
Only ticked scenarios may be briefed. Anything else needs written approval from the account contact first.
Scenario notes — scripts, products to ask for, phrasing to avoid:
How much each scored area contributes to the overall visit score. Weightings should total 100%.
| | |
|---|
| | |
Product knowledge and advice | | |
Store condition and presentation | | |
Speed of service and queueing | | |
| | |
Brand standards and compliance | | |
Purchase & Reimbursement Caps
Standard purchase cap per visit:
Raised cap, and the scenarios it applies to:
Travel or parking allowance, if any:
What gets raised immediately rather than waiting for the next report — and to whom, by which channel, within what window.
Periods when no visits are dispatched — refits, peak trading, stocktakes, holidays. Include the locations affected.
Dated entries as the programme evolves — cadence changed, scenario added, cap raised, score trend up or down, action agreed at a review. Newest at the top.
Supporting material — store lists, brand standards, scenario scripts:
Keep this file current — every assignment we dispatch is built from what is written here.