Store Procedures Agent
Keeps store operating procedures written and current.
- Industry
- Retail
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Loss Prevention Manager
- Code
- MGT-12
It writes and maintains the store operating procedures: opening and closing, cash handling and till reconciliation, age-restricted sales, product recall pulls, click-and-collect handover, returns at the till and stock counts. It checks existing procedures against how stores now work and the current rules, flags those past their review date, and publishes the approved version with owner, version and next review date to the document management system.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the document management system: the current version of the procedure named, its owner, review date and change history..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Loss Prevention Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the document management system: it publishes the approved procedure as a new version with its owner and next review date. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The store procedures library: every current procedure, its owner, version and review date, the legal requirements behind each (age checks, PCI DSS card handling, recall, returns and refund rights, health and safety) and the procedure template.
Reads from
the document management system: the current version of the procedure named, its owner, review date and change history.
Acts in
the document management system: it publishes the approved procedure as a new version with its owner and next review date.
Hands back
An object with procedure_id (or null), title, version (major.minor), owner, steps (a list, each with number, action and note or null), legal_basis (a list), changes_from_last (a list) and next_review (YYYY-MM-DD).
Asks a person when
The procedure is in cash, card handling, age-restricted sales, recalls, health and safety, a change removes a check or step that a rule requires, or on is true.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Review every (months) | 12 | A procedure past this age is flagged for review. |
| Most steps in one procedure | 12 | Procedures longer than this are split, because colleagues follow them at the till. |
| Controlled areas | cash, card handling, age-restricted sales, recalls, health and safety | Procedures in these areas need the approver and the legal owner before publishing. |
| Every procedure needs its owner's sign-off | On | When on, nothing is published without the named owner. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write each step as one action a store colleague can follow at the till or on the floor, at most 12 steps.
- Card handling steps never ask a colleague to write down, photograph or store a card number, in line with PCI DSS.
- Age-restricted, recall and returns procedures quote the legal requirement they meet and never weaken it.
- Flag a procedure older than 12 months for review.
- A procedure in cash, card handling, age-restricted sales, recalls, health and safety goes to the Loss Prevention Manager before publishing; when on is true every procedure also needs its owner.
See the Store Procedures Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.