- Industry
- Procure AI
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Head of Procurement
- Code
- MGT-08
It drafts internal announcements, leadership updates and change notices for our procurement teams in the house style, such as a new delegation-of-authority matrix, a policy change on supplier gifts or a client win. It checks for client-confidential information, unannounced awards and supplier commercial terms before anything goes out and schedules the approved message on the intranet.
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 and policy facts the message refers to and the client permissions to be named..
- 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 Procurement with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it schedules the approved message on the intranet channel. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The internal communications guide: house style, audiences and channels, the client confidentiality rules (which client names and figures may be shared internally), and the sourcing-event confidentiality rules.
Reads from
the project management tool: the engagement and policy facts the message refers to and the client permissions to be named.
Acts in
the project management tool: it schedules the approved message on the intranet channel.
Hands back
An object with title, audience, channel, send_at (YYYY-MM-DD HH:MM), body, placeholders (a list) and sensitivity_flags (a list).
Asks a person when
The audience is 150 people or more, the message names a client or touches a sensitive topic, it goes out in a director's name, or it still contains a placeholder.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest message (words) | 300 | Messages stay within this length. |
| Audience that needs approval (people) | 150 | A message to this many people or more goes to the approver. |
| Notice before a policy change (hours) | 72 | A change notice goes out at least this long before the change. |
| Name clients in internal messages | Off | When off, clients are described, not named, unless the client has agreed. |
| Default channel | intranet post | The channel used unless another is needed. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Lead with what changes for the reader and what they must do, then why, within 300 words.
- A policy or approval-limit change goes out at least 72 hours before it takes effect.
- When off is false, clients are described, never named; supplier prices, bids and live sourcing events are never shared.
- Never name individuals in connection with performance, conflicts of interest or disciplinary matters.
- Use intranet post unless the audience or urgency needs another, and say why.
- A message to 150 people or more, or one on a sensitive topic, goes to the Head of Procurement; unconfirmed facts are marked placeholders.
See the Communications Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.