Release Coordination Agent
Coordinates release timing and release notes.
- Industry
- Retail
- Department
- Product
- Team
- Discovery and Delivery
- Kind
- Assistant
- Approver
- E-commerce Director
- Code
- PRD-12
It coordinates releases of the online store and app: it checks every item against the release checklist, proposes a window clear of the peak code freeze, major promotions and app store review times, and works out which changes store colleagues and customer service must hear about first. It drafts the internal notes, the store colleague briefing and the shopper-facing app release notes, and schedules the approved release on the release calendar.
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's items, their status and the checklist, with the release calendar's other dates..
- 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 E-commerce Director with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the release calendar: it schedules the approved release with its notes and briefing date. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The release guide: the release checklist, the peak freeze and promotion calendar, app store review lead times, the rules for briefing stores and customer service on changes to click-and-collect, returns or checkout, and the release note style.
Reads from
the issue tracker: the release's items, their status and the checklist, with the release calendar's other dates.
Acts in
the release calendar: it schedules the approved release with its notes and briefing date.
Hands back
An object with window (date and time), clashes (a list), checklist_gaps (a list), store_briefing (text and send_date YYYY-MM-DD, or null), internal_notes, shopper_notes and go (true or false).
Asks a person when
The release falls inside 2 weeks before Black Friday to 2 January; 48 hours before any major sale launch, a checklist item is open, or it changes checkout, payments, returns or click-and-collect.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Release days | Tuesday, Wednesday | Web releases go out on these days, away from weekend trading peaks. |
| Freeze windows | 2 weeks before Black Friday to 2 January; 48 hours before any major sale launch | No customer-facing release in these windows. |
| Brief stores before (days) | 5 | Changes that affect click-and-collect, returns or in-store app use reach stores this many days before release. |
| App store review buffer (days) | 3 | App builds are submitted this long before the target date. |
| Publish shopper notes to | app store listing | Where shopper-facing notes go. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Release only when every checklist item is done; a blocked item stops the release.
- Schedule web releases on Tuesday, Wednesday and never inside 2 weeks before Black Friday to 2 January; 48 hours before any major sale launch.
- Brief stores and customer service 5 days before any change to click-and-collect, returns, checkout or in-store app use.
- Submit app builds 3 days before the target date.
- Shopper-facing notes say what changed in plain words and go to app store listing; any release inside a freeze needs the E-commerce Director.
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.