- Industry
- Procure AI
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Client Engagement Lead
- Code
- MGT-09
It turns the transcript or notes of a client steering group, category strategy review or supplier negotiation debrief into a record of the decisions taken, the actions with one owner and a date each, and the open questions. It files the record against the engagement and creates the actions in the project management tool, keeping negotiation positions and supplier pricing out of anything shared with suppliers.
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 project management tool: the engagement's meetings, attendees and existing open actions..
- 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 Client Engagement Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it files the record against the engagement and creates the actions as tasks. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The meeting record standard, the confidentiality rules for negotiation positions, bid data and client strategy, and the distribution lists for each client steering group.
Reads from
the project management tool: the engagement's meetings, attendees and existing open actions.
Acts in
the project management tool: it files the record against the engagement and creates the actions as tasks.
Hands back
An object with meeting, date, client, restricted (true or false), decisions (a list with decision and agreed_by), actions (a list with action, owner, due_date) and open_questions (a list).
Asks a person when
The record is restricted, an action is assigned to a client or supplier person, or the record would go beyond the attendees.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Due date when none is given (days) | 7 | Actions without a date are due this many days after the meeting. |
| Flag actions without an owner | On | When on, an action with no clear owner is flagged rather than guessed. |
| Create actions as tasks | On | When on, actions are created in the project management tool. |
| Restricted topics | negotiation positions, bid prices, should-cost, client budgets | A meeting that covers these is marked restricted. |
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, with who agreed it; discussed but not agreed is an open question.
- Every action has one owner and a due date; with no date use 7 days, and when on is true flag an action with no clear owner.
- A meeting covering negotiation positions, bid prices, should-cost, client budgets is marked restricted and goes only to our attendees and the client's.
- Nothing from a negotiation debrief or bid discussion goes to a supplier.
- Create actions as tasks only when on is true.
See the 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.