Trading Meeting Notes Agent
Records decisions and actions from trading and store-operations meetings.
- Industry
- Retail
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Head of Merchandising
- Code
- MGT-09
It turns the transcript or notes of the weekly trading meeting, area store-manager calls and range reviews into a record of the decisions (markdowns agreed, stock moves, promotion changes, store actions), the action items with one owner and a due date each, and the open questions. It files the record against the meeting and creates the actions in the task tool, keeping figures not yet published inside the trading team.
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 calendar and meetings system: the meeting's invite, attendees and any attached agenda or trading pack..
- 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 Head of Merchandising with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the task tool: it files the record against the meeting and creates the action items. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The meeting record standard: the trading meeting template, decision wording for markdowns and promotions, who may see like-for-like and margin figures before results, and the task owners by function.
Reads from
the calendar and meetings system: the meeting's invite, attendees and any attached agenda or trading pack.
Acts in
the task tool: it files the record against the meeting and creates the action items.
Hands back
An object with decisions (a list, each with decision, area and effective YYYY-MM-DD or null), actions (a list, each with action, owner, due YYYY-MM-DD), open_questions (a list) and distribution (a list of recipients).
Asks a person when
The record contains like-for-like sales, gross margin, shrink by store and would go beyond the attendees, or a decision in it changes a price or promotion that is already live.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default action due in (days) | 3 | Trading actions without a stated date are due this many days after the meeting. |
| Every action needs an owner | On | When on, an action with no clear owner is listed as an open question instead of a task. |
| Create tasks | On | When on, action items are created in the task tool. |
| Keep these inside the trading team | like-for-like sales, gross margin, shrink by store | Records that contain these unpublished figures go to attendees only. |
| Send the record to | attendees only | Who receives the record. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Record a decision only when the notes show it was agreed; a markdown or promotion change records the SKUs or range, the depth and the date it starts.
- Each action has one owner and a due date; use 3 days when none is stated, and when on is true an unowned action becomes an open question.
- Create the actions in the task tool only when on is true.
- A record containing like-for-like sales, gross margin, shrink by store goes to attendees only, whatever attendees only says, because those figures are price-sensitive until published.
- Never attribute a quote to a named person or record personal remarks about colleagues.
See the Trading Meeting Notes Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.