Glossary
The words we use, defined once, in plain English.
Terms
- Content operation
- The whole running function that keeps an organisation’s content going out: strategy, people, approvals, the engine that does the work, publishing and measurement.
- Content engine
- The system inside a content operation that does the repeatable work: research, drafting, formatting, scheduling, publishing and measuring. A good one runs on accounts you own, is tested like software, and never publishes without human approval.
- Approver
- A named person on the client’s side who can release an item for publishing. Nothing is published until an approver says yes.
- Editor
- The named person on the client’s side who is responsible for what is published. Often also an approver.
- Register
- One list of every item in the operation, with its ID, date, pillar, platforms, languages, status and who can release it.
- Content pillar
- One of a small number of themes the content plan is built around, such as field operations or safety.
- Calendar rules
- The rules the engine follows when scheduling: days off, holidays, the maximum number of posts a day, and how pillars are mixed.
- Publishing switch
- A single control with three settings — off, test and on — that decides whether the engine publishes, publishes to a test channel, or publishes for real.
- Watchdog
- An independent check that runs outside the system it watches, every day, and raises an alert if something has stopped.
- On-time rate
- Items published within 15 minutes of their scheduled time, divided by items scheduled.
- Incident
- Any stop or failed publish. We log every incident on our status page.
- Automated test
- A check written in code that runs before changes go live and fails if the engine would behave wrongly. We add one for every fault we find.
- Diagnostic
- Beeyawn’s paid first step: we map your content, data and approvals, design the engine and confirm a go-live date. The fee is credited to the build.
- Build
- The one-off work to set up and test the engine on your accounts, usually 6–10 weeks after the Diagnostic.
- Run
- The monthly service: producing, approving, publishing and measuring content, and improving the engine.
- Interview-to-Video
- An add-on that turns one recorded conversation into an article, social posts and short edited clips.
- Paired posts
- Language versions of the same post, approved together and published together.
- Workflow
- A sequence of automated steps, such as “draft, send for approval, schedule, publish, log”. Our engines use n8n workflows on the client’s server.
- AEO (answer engine optimisation)
- Writing and structuring pages so that AI assistants and search features can quote them accurately: answer first, one idea per section, sources and dates stated.
- GEO (generative engine optimisation)
- Another name for making content findable and citable by generative AI tools such as chat assistants.
Tell us what you publish today. We’ll tell you, in 20 minutes, whether an engine would help.
Book an intro call