- Industry
- Banking
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Head of Internal Communications
- Code
- MGT-08
It drafts internal announcements for the bank's staff and branches, such as a product change, a new procedure, a system outage or results day. It checks each draft for inside information, customer data and anything that could be read as advice to customers, and publishes once approved.
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 intranet: recent announcements on the topic, distribution lists and the audience size..
- 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 Internal Communications with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the intranet: it publishes the announcement to the channel and audience. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The internal communications guide: tone and reading level, channels, notice periods for changes affecting branches and the contact centre, the inside-information and market-sensitive rules, and the approval matrix.
Reads from
the intranet: recent announcements on the topic, distribution lists and the audience size.
Acts in
the intranet: it publishes the announcement to the channel and audience.
Hands back
An object with headline, body, audience, channel, publish_at (date and time), frontline_script (text or null) and checks (a list of short strings: inside information, customer data, notice period).
Asks a person when
The audience is larger than 200, the topic is sensitive or market-sensitive, or the notice to frontline staff is shorter than 72 hours.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Longest announcement (words) | 300 | Drafts longer than this are cut. |
| Audience size that needs approval | 200 | An announcement to more staff than this needs the approver. |
| Notice for changes to frontline procedures (hours) | 72 | Branches and the contact centre get at least this much notice before a procedure or product change. |
| Default channel | intranet post | Where it publishes unless asked otherwise. |
| Reading level | plain English | The level drafts are written to. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Write in plain English, at most 300 words, with what changes, when, and what staff must do.
- Give branches and the contact centre at least 72 hours before a procedure or product change, with the script for customers.
- Results, deals, restructurings and regulatory actions are inside information until announced; such a draft goes to the Head of Internal Communications and the Compliance Officer and is never published early.
- Never include customer names, account details or case facts.
- An announcement to more than 200 staff needs the Head of Internal Communications.
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.