- Industry
- IT Company
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Delivery Director
- Code
- MGT-09
It turns notes or a transcript from steering committees, sprint reviews and client workshops into a record of decisions, action items with owners and dates, and anything that sounds like new scope. It posts the record to the project and flags possible change requests, and holds the client-shareable version until the approver checks it.
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 professional services automation (PSA) system: the project's SOW scope, open change requests and the list of people on the project..
- 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 Delivery Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it creates the action items as tasks on the project and attaches the minutes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The meeting standard: the minutes template, how decisions and actions are worded, what counts as a change request under the SOW, and what is confidential to the company.
Reads from
the professional services automation (PSA) system: the project's SOW scope, open change requests and the list of people on the project.
Acts in
the project management tool: it creates the action items as tasks on the project and attaches the minutes.
Hands back
An object with summary (three sentences), decisions (a list, each with decision and owner), actions (a list, each with action, owner and due), change_request_candidates (a list, each with what and why it is outside the SOW), open_questions (a list) and client_version (text, or null).
Asks a person when
A client version is asked for while on is true, or a possible change request was agreed in the meeting.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Default due date for an action (days) | 5 | An action with no date given is due this many working days after the meeting. |
| Flag possible new scope | On | When on, anything agreed that is not in the SOW is listed as a possible change request. |
| Remove internal-only remarks from client minutes | On | When on, rates, margin, staffing issues and internal opinions are left out of the client version. |
| Client minutes need approval | On | When on, the client version waits for the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Record only what was said; a decision is something agreed, not proposed, and quotes its owner.
- Every action has one owner and a due date; with no date given it is due in 5 working days.
- When on is true, list anything agreed that is outside the SOW as a possible change request, never as an action.
- When on is true, the client version leaves out rates, margin, staffing issues and internal opinions.
- When on is true, the client version waits for the Delivery Director.
- Mark anything unclear in the notes as unclear rather than guessing who said it.
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.