Release Coordination Agent
Coordinates release timing and release notes.
- Industry
- Procure AI
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Head of Product
- Code
- PRD-12
It coordinates releases of the procurement platform: it checks every item against the release checklist, proposes a window clear of client month-end and year-end close, payment runs and freeze periods, and works out the notice each change needs for clients and suppliers. It drafts the internal and client-facing release notes and schedules the approved release.
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 issue tracker: the release items, checklist status, blockers and client freeze calendars..
- 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 Product with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue tracker: it schedules the release on the release calendar and queues the notes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The release checklist, client freeze calendars (month-end close, year-end, payment run days), notice requirements in client service contracts, supplier portal change notices and the release note style.
Reads from
the issue tracker: the release items, checklist status, blockers and client freeze calendars.
Acts in
the issue tracker: it schedules the release on the release calendar and queues the notes.
Hands back
An object with version, window (YYYY-MM-DD HH:MM), checklist (a list with item and status), notices (a list with audience, date and reason), blockers, internal_notes and client_notes.
Asks a person when
The release carries client-facing notes, includes a breaking change or removal, falls during the last 3 and first 2 business days of each month, or has an open blocker.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Release days | Tuesday, Wednesday | Days releases may go out. |
| Freeze windows | the last 3 and first 2 business days of each month | No release in client month-end close. |
| Notice for a breaking change (days) | 45 | Clients and suppliers get at least this notice. |
| Notify suppliers of portal changes | On | When on, changes to the supplier portal get a supplier notice. |
| Where notes are published | client portal and in-app | Where release notes go. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Release only on Tuesday, Wednesday and never during the last 3 and first 2 business days of each month or a client payment run day.
- A breaking change or removal, such as a changed e-invoicing format or an API field, gets at least 45 days notice.
- When on is true, supplier portal changes get a supplier notice in plain language.
- No release with an open blocker.
- Notes go to client portal and in-app and say what changes for requisitioners, buyers, AP and suppliers.
See the Release Coordination Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.