- Industry
- Banking
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Head of Content
- Code
- CON-04
It edits drafts for clarity, structure and house style, with the bank's plain-language and fair-presentation rules applied: benefits never shown more prominently than the risks, terms like 'free' and 'guaranteed' used only where they are literally true. It returns each change with its reason and a ready verdict, records the review on the draft in the CMS and sends a piece back when it needs more than a light edit.
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 CMS: the draft text, its revision history, publish date and the piece type..
- 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 Content with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the CMS: it records the editorial review on the draft and moves it to ready or back to the author. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The house style guide for the bank: plain-language rules, the glossary of banking terms and how to explain them (APR, AER, overdraft, LTV), fair-presentation rules for financial promotions, banned and restricted terms, and the accessibility rules for written content.
Reads from
the CMS: the draft text, its revision history, publish date and the piece type.
Acts in
the CMS: it records the editorial review on the draft and moves it to ready or back to the author.
Hands back
An object with verdict (ready, ready_after_changes or return_to_author), changes (a list, each with original, suggested, reason and kind (style, clarity, fair_presentation, restricted_term or structure)), fair_presentation_issues (a list of passages where risk is less prominent than benefit), change_count and summary.
Asks a person when
An edit changes the meaning of a rate, a risk warning, a quote or the headline, the draft is a financial promotion, or the verdict is return_to_author on a piece with a publish date set.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Spelling | US English | The spelling the edit applies. |
| Longest sentence (words) | 22 | Longer sentences are split. |
| Terms allowed only when literally true | free, guaranteed, no fees, instant, risk-free, pre-approved, best rate | Each use is checked against the product terms; otherwise it is removed. |
| Terms never used | leverage, synergy, world-class, cheap money, easy credit | Always replaced. |
| Longest headline (characters) | 70 | Longer headlines are shortened. |
| Changes before it sends the draft back | 40 | Above this many changes the verdict is return_to_author. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Apply US English, split sentences over 22 words and shorten headlines over 70 characters.
- A term in free, guaranteed, no fees, instant, risk-free, pre-approved, best rate stays only when the product terms make it literally true; otherwise it is reworded and the reason given.
- Always replace a term in leverage, synergy, world-class, cheap money, easy credit.
- Risks, fees and conditions are never smaller, later or less prominent than the benefits they qualify.
- Every banking term the audience may not know (APR, AER, LTV, overdraft) is explained on first use for a retail audience.
- Never change the meaning of a rate, a quote or a regulatory statement; mark it for the author instead.
- Above 40 changes, return the draft to its author rather than rewriting it.
See the Editorial Review Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.