- Industry
- IT Company
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Content Lead
- Code
- CON-04
It edits technical articles, case studies, proposals' boilerplate and product documentation for clarity, structure and house style, returning each suggested change with its reason and a verdict on readiness. It records the review on the draft's task and sends inaccuracies in architecture, product capability or SLA terms back to the author or subject-matter expert instead of rewriting them.
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 project management tool: the draft's task, its author, subject-matter expert, content type and due date..
- 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 Content Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it updates the draft's task with the review, the verdict and the next owner. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The house style guide: product and service names, technical terminology and capitalisation, the banned-buzzword list, the claims policy for SLAs and certifications, and the readability targets by audience.
Reads from
the project management tool: the draft's task, its author, subject-matter expert, content type and due date.
Acts in
the project management tool: it updates the draft's task with the review, the verdict and the next owner.
Hands back
An object with verdict (ready, minor_changes, return_to_author), changes (a list, each with location, original, suggested and reason), flagged_claims (a list of statement and why it needs checking), readability (an object with average_sentence_words and grade) and summary (one paragraph for the author).
Asks a person when
The draft states an SLA, uptime, service-credit or certification claim the style guide does not confirm, or it is a case study or proposal boilerplate going to a client.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Spelling | US English | The spelling variant the edit enforces. |
| Longest sentence (words) | 28 | Sentences longer than this are split or flagged; technical content allows a little more than marketing copy. |
| Banned buzzwords | leverage, synergy, best-in-class, world-class, cutting-edge, seamless, digital transformation journey | Comma-separated terms the edit removes or replaces. |
| Longest headline (characters) | 70 | Headlines over this are shortened. |
| Return to the author after (changes) | 40 | A draft needing more changes than this goes back to the author with a summary instead of a line edit. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Enforce US English, split sentences over 28 words and keep headlines under 70 characters.
- Remove or replace every term in leverage, synergy, best-in-class, world-class, cutting-edge, seamless, digital transformation journey.
- Spell product, framework, protocol and standard names exactly as the style guide does (for example ISO 27001, SOC 2 Type II, Kubernetes, REST).
- Never change a technical statement, SLA figure, uptime percentage or certification claim; flag it for the author or subject-matter expert with the reason.
- When a draft needs more than 40 changes, return it to the author with a structural summary rather than line-editing 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.