Skip to content
EITHRA
ENRU
Request a pilot

Governed communications

Trusted information in. Approved communications out.

EITHRA turns trusted company knowledge into evidence-backed communications, routes exact versions for human review, and keeps a durable record of what was approved, changed and exported.

One record for sources, evidence, versions and decisions.

Request a pilotExplore the platform
01Trusted Source02Evidence & Version03Human Review04Exact Approval05Manual Export

EITHRA / Review
Exact version. Human decision.

DECISION APPLIES TOLinkedIn announcement · v5
v5
Evidence
7/8 source-backed1 evidence issue
Approver
Sarah LeeSample reviewer
Review state
In review
Decision on v5
Approval required
Approve v5Request changes
Product example · Sample dataExplore the decision →

Exact sources. Exact versions. Human decisions.

01 / HOW IT WORKS

From trusted information to an approved version.

Connect the source, evidence and exact wording. Keep review, approval and manual export in one traceable record.

Illustrated workflow01 / 07
Trusted company informationProgramme briefingEITHRA
01Claim / Evidence
02Exact version
03Human decision
04Decision record

Start with a report, policy, research, briefing or statement your organisation trusts.

02 / WHY EITHRA

AI helps create the draft.EITHRA governs what happens next.

When a communication matters, the draft is only the beginning. Your team needs to know what supported it, which version was reviewed, who decided and what left the organisation.

  1. 01

    Source-linked evidence

    Keep important claims connected to the material that supports them.

  2. 02

    Exact versions

    Changes create a new version. Approval never carries over automatically.

  3. 03

    Human decisions

    Review, approval and manual export stay with your team — with a record of each step.

  4. 04

    Durable decision record

    Keep what was supported, changed, approved and exported understandable after the work is done.

03 / INSIDE EITHRA

The communication. The evidence. The version.

Follow one communication from its source through evidence, exact versions and human decisions. See what changed and what was exported.

Interactive product demoSample content · Northbridge Forum

EITHRA

Start with what you know.

A source version and brand context are linked to one communication.

Bound versionSource linked
Source
Northbridge Community Forum — programme briefing · v3
Brand context
Northbridge Professional Community · v1
Configured channels
LinkedIn post
Language
English
Target date
18 Nov 2026
Brand timezone
Europe/London
Read sample source

Northbridge Community Forum brings members together on 18 November 2026. The programme includes a community briefing and a discussion of the next programme. Prepare a LinkedIn announcement for members.

View brand context

Calm, factual and welcoming. Use the programme as the source. Do not add unsupported claims or promises.

A linked source is a starting point. It does not verify every claim or approve a material.

Start with what you know.

A website-only example. No live generation, product changes or publishing.

View real product captures
Real product · Sample content
Northbridge ForumEvidence, versions and export controls stay beside each material.
02 / 03
Email v3, Website v1 and LinkedIn v4 — each approved independently.
Email v3, Website v1 and LinkedIn v4 — each approved independently.Open full capture

Email shown first. Scroll to Website and LinkedIn.

04 / ASK EITHRA

Ask about the work. Keep the record.

Ask EITHRA works in the context of your sources, communications and versions. The conversation helps you navigate the work; evidence and human decisions stay with the version.

Ask EITHRA.Review the version.
Ask EITHRAContextual AI interface inside EITHRA

Scope: Northbridge / LinkedIn announcement · v5

“What still blocks approval of LinkedIn announcement v5?”
Answer
One evidence issue remains. v5 needs its own human decision.
Evidence
“Help shape what’s next” has no support in programme briefing v3.
Programme briefing

Illustrated answer scoped to the Northbridge v5 example. No live AI response. Decisions belong to the version, not the conversation.

05 / HUMAN CONTROL

Approval belongs to exact words.

A meaningful edit creates a new version that needs its own decision. The previous approval remains in history; it never approves the latest draft.

Continue the same exampleInteractive product demo · Sample content

Northbridge Forum / LinkedIn post

Member communication

Prepared in EITHRA
Current version · v5In review

Northbridge Forum

Be part of the conversation at Northbridge Forum and help shape what’s next.

7/8 source-backed1 evidence issue

Illustrative evidence count. Source-backed does not mean guaranteed accuracy. A person reviews meaning and citations.

“The programme includes a community briefing and a discussion of the next programme.”

“Help shape what’s next” has no matching source evidence in this example. A person must review it.

1 evidence issue

“Help shape what’s next” has no matching source evidence in this example. A person must review it.

Manual Export

Available only after you approve the current version. Downloads sample text; nothing is published.

A website-only example. No live generation, product changes or publishing.

View real approval captures

Recorded example: Annual Programme. Separate from the Northbridge demo.

One asset’s version history · Annual ProgrammeReal product · Sample content

Approval requiredv3 has no approval. It must be sent for review.

Approval required
Approval requiredOpen full capture
4 / 7

Recorded product states · Annual Programme example. Browsing these captures does not approve or export anything.

EITHRA supports source-grounded communications with human review and version-specific approval. Source support does not guarantee truth; your team decides what is ready to use.

06 / DECISION HISTORY

A decision record people can actually understand.

See which source was used, what changed, who decided and which version left the organisation.

  1. 01Source v3 added
  2. 02v4 created
  3. 03Evidence reviewed
  4. 04Changes requested
  5. 05v5 created
  6. 06v5 approved
  7. 07v5 exported

Illustrative sequence. Decisions and export in the interactive demo above are recorded only after your actions.

07 / PRODUCT DIRECTION · IN DEVELOPMENT

Designed for what happens after the source changes.

The direction is to make it clear which claims and communications a new source version affects, and what needs another review.

Source versionAffected claimAffected communicationRe-review

Keep your existing systems. Govern what moves between them.

EITHRA complements the organisation’s working environment. Source access and delivery paths are scoped in the pilot. This is a product direction, not a catalogue of shipped integrations.

Existing knowledgeEITHRADownstream destinations

08 / WHO IT IS FOR

Built for teams that cannot afford a wrong external statement.

  • Corporate Communications
  • Executive Communications
  • Public Affairs
  • Institutional Communications
  • Events & Programmes

09 / START SMALL

Start with one consequential communications workflow.

Bring one real process: the trusted sources, the people who review it and the communications that need to leave the organisation.

We’ll make the evidence, versions and decision path explicit. Pilot scope is agreed around your real workflow.

Request a pilot

Tell us where the work starts.

Your request will be sent to EITHRA. Confirmation appears after your request is saved.

Communication channels *

Choose two or three. These describe your workflow, not connected integrations.

Please do not include source files, personal information about others, passwords or access details.

Privacy

No public signup. Your request is confirmed only after it is saved.