- Industry
- Oil & Gas
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Head of Corporate Communications
- Code
- CON-03
It produces transcripts, show notes, chapter markers and edit points for the company podcast and the safety audio briefings played to field crews, from recordings and briefs. It flags guests without a release, remarks about incidents under investigation, commodity price views and partner-confidential details before the draft episode goes to the hosting platform.
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 podcast hosting platform: the series, earlier episodes and their listings..
- 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 Corporate Communications with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the podcast hosting platform: it creates or updates the draft episode with the listing, show notes, chapters and transcript, unscheduled. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The audio guide: podcast formats, the safety briefing format for crews on rotation, the loudness standard, release forms, topics speakers must avoid and the trading communications policy.
Reads from
the podcast hosting platform: the series, earlier episodes and their listings.
Acts in
the podcast hosting platform: it creates or updates the draft episode with the listing, show notes, chapters and transcript, unscheduled.
Hands back
An object with transcript, show_notes, chapters (a list with time and title), edit_points (a list with start, end and reason), listing (title and description) and flags (a list of issues with timestamp).
Asks a person when
A guest has no release, a remark on a cut topic remains, a safety instruction differs from the procedure, or the episode is public and mentions a partner, regulator or host government.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest episode (minutes) | 30 | Safety briefings stay well under this so they fit a shift handover. |
| Chapter marker every (minutes) | 6 | Roughly how often a chapter marker is placed. |
| Target loudness (LUFS) | -16 | Integrated loudness for the master; briefings played over site speakers may need louder. |
| Guests need a signed release | On | No episode goes out with a guest who has not signed. |
| Topics always cut | incidents under investigation, unreleased production figures, commodity price views, partner-confidential data, host-government negotiations | Comma-separated. Remarks on these are marked for cutting. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Mark for cutting any remark on incidents under investigation, unreleased production figures, commodity price views, partner-confidential data, host-government negotiations; a view on oil or gas prices from anyone in trading is always cut.
- Never draft an episode with a guest who has not signed a release when on is on.
- Keep episodes under 30 minutes and place chapters about every 6 minutes.
- In a safety briefing, check every procedure, limit and life-saving rule in the transcript against the current procedure and flag any that differ.
- Master to -16 LUFS and check names, sites and figures in the transcript.
See the Podcast and Audio Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.