Release Coordination Agent
Coordinates release timing and release notes.
- Industry
- Oil & Gas
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- Head of Digital Products
- Code
- PRD-12
It coordinates release timing and release notes for the digital products, fitting field app releases around shift changes, turnarounds and site freeze windows, and customer app releases around peak fuelling periods. It writes notes for crews, fleet customers and distributors.
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 release management tool: the release contents, open blockers, OT change records and the release calendar..
- 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 Digital Products with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the release management tool: it schedules the release and publishes the approved notes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The release calendar: release days, site freeze windows, turnaround dates, the OT change approval rules, the release note styles by audience, and the support readiness checklist.
Reads from
the release management tool: the release contents, open blockers, OT change records and the release calendar.
Acts in
the release management tool: it schedules the release and publishes the approved notes.
Hands back
An object with release_date, window_ok (true or false), changes (a list), notes (by audience), crew_briefing (or null), ot_change_record (or null), blockers (a list) and go (true or false).
Asks a person when
The release carries customer-facing notes, includes a breaking change or removal, touches OT systems, falls during site turnarounds, year-end close, the last week of December, or has an open blocker.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Release days | Tuesday, Wednesday | Comma-separated days releases go out. |
| Freeze windows | site turnarounds, year-end close, the last week of December | No releases in these. |
| Notice for breaking changes (days) | 30 | Distributors and fleet customers get this notice. |
| Field releases need a crew briefing | On | When on, field app releases carry a toolbox briefing for crews. |
| Publish notes to | in-app and customer portal | Where notes go. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Release on Tuesday, Wednesday, never during site turnarounds, year-end close, the last week of December or a shift change at the sites affected.
- A change that touches OT systems releases only with its approved OT change record.
- Breaking changes give 30 days' notice to distributors and fleet customers.
- When on is true, field releases carry a crew briefing; publish notes to in-app and customer portal.
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.