Low-consequence content moves
Internal bulletins and support articles run automated, with no human in the path.
OneStandard · For regulated and high-consequence content
Prove which language version shipped, and how it was made.
OneStandard is TextUnited’s language risk module. It grades content by what an error would cost, routes each grade to the process it requires, and produces a record an auditor can check. Wording without the required evidence does not get released.
0
For the people who answer when an authority asks
Quality managementRegulatory affairsTechnical documentationProduct complianceLegalRisk
Classification · Where the whole thing starts
Being wrong costs a different amount in each of these.
An Austrian company builds packaging machines and sells them into Germany, France and Poland. Four documents leave the building in the same week. Nobody in the company reads Polish.
| Safety instruction — An operator does what it says | A wrong verb in a maintenance step injures somebody. The inspector treats the translated version as the instruction, not as a translation of one. |
| Warranty clause — It obliges the company differently in French | The wording signed in the customer’s language is the version a court reads. |
| Product datasheet — A customer orders from it | A wrong specification produces an order the factory cannot fill. It costs money and a relationship. |
| Internal service bulletin — A colleague reads it and moves on | Machine output is enough. Spending a reviewer here takes them from work where they are needed. |
Classification is the input to everything that follows, so OneStandard records it. Content class, market, regulatory scope and product link are stored as data, so an auditor can ask how a document was classified and get an answer.
Your policy turns those four classes into four different requirements.
Policy · Written by your compliance officer, not by us
Your rules decide what each class requires.
A policy rule is a condition over classification dimensions plus a floor: the minimum a document of that kind must reach. Rules are stored as data rather than code, so your compliance officer can read, review and cite them in an audit.
Every rule that matches is collected, and the strictest floor wins. Adding a regulation can only tighten a requirement.
Each resolution is recorded with the rules that fired and the policy version in force, so the record says what was required, why, and under which revision of your policy.
Polish operating manual · packaging machine · in scope of MR 2023/1230 | Policy evaluation |
R-01 · content class: safety instruction | Floor: AL3 |
R-05 · market: PL, published externally | Floor: AL3 |
R-06 · regulatory scope: MR 2023/1230 | Floor: AL4 — required |
Policy version 2026.3 · resolved 12 Nov 2026 | 3 rules matched |
Once the requirement is set, the content goes where the requirement sends it.
Routing · The pipeline follows the policy
Each document takes the route its class requires.
The mechanics are the same automations any team builds. What differs is who chose the route: the policy already resolved it.
High-consequence content collects signatures
Safety and regulatory content collects the review steps its floor demands, in order, from qualified roles.
Evidence is written during, not after
Every step records what it did while it did it.
Your existing pipeline keeps running
OneStandard listens to the work rather than replacing it. Translation, review and terminology stay where they are.
The gate · The part auditors care about
Wording without its evidence does not get released.
OneStandard computes what a document version achieved from the record of what happened to it. Nobody types that number in. If the record supports a lower level, release stops.
A document carries the level of its weakest section. One unreviewed safety warning caps the whole manual: no averaging, and no percentage of the document reviewed.
Editing after approval cancels the approval for what changed. Every entry is bound to a hash of the text at that moment.
You can still publish. It costs a named authority, a coded reason and a documented exception that appears on the record.
Document | Quick-start guide, crane v4.2 · PL |
Required by policy | AL3 |
Computed from the record | AL2 |
Reason | 4 segments edited after review |
Certificate | Not available |
What comes out the other side is the thing you hand over.
The record · What an auditor receives
One record per document version answers six questions.
Not a dashboard, and not a report assembled the week before an audit. A file a quality manager hands to a notified body or market-surveillance authority.
Which text. Identified by a hash of the content, binding the record to the wording that shipped.
Which level, under which policy. The requirement, rules and policy version in force.
Which steps ran. In order, each one attributed to a qualified role.
Which checks passed. Quality estimation, terminology, revision sign-off and QA gates.
When. A qualified timestamp puts the record before any dispute.
Whether anyone changed it since. A hash chain and qualified electronic seal make edits visible.
An auditor will ask how long you can produce it for.
What the record does not contain: no source text, target text or personal names. Roles and pseudonymous references only, so you can hand it to a third party without a confidentiality discussion.
Ten years · And after us
The record outlives the contract.
The Machinery Regulation requires digital instructions to stay available for at least ten years after the machine goes on the market. Evidence about those instructions has to last at least as long.
Verification does not depend on TextUnited. An auditor can take the certificate, recompute the hashes with an offline verifier and confirm integrity without logging in.
The verifier is open source. Anyone can read what it checks, which is the point of asking somebody to trust a record.
All of this is being built now, with the first companies that have a date in the calendar.
Questions
What compliance teams ask first
Is OneStandard a compliance certification?
No. A notified body certifies products. OneStandard produces evidence about translated content for auditors, notified bodies or courts.
Who decides how important a document is?
Your policy does, and your compliance officer writes the policy. Every classification is recorded as an input to that decision.
What happens if somebody edits a document after approval?
The approval stops counting for the text that changed. The document drops to the level supported by surviving evidence.
Can we publish when evidence falls short?
Yes, with a documented exception: a named authority, a coded reason and a visible record entry.
Does the record contain our content or people’s names?
Neither. It holds hashes, roles, timestamps and policy references, not source text, target text or personal names.
What happens if we stop using TextUnited?
The record remains verifiable with an offline verifier, so integrity does not depend on logging into TextUnited.
Do we need OneLanguage as well?
OneStandard governs the process and evidence. OneLanguage is where translation, review and terminology work can happen.
How do we start?
Bring one product family and the markets it ships to. We map classes, write the first policy and run one document version end to end.
Building this with the first companies
The Machinery Regulation applies from 20 January 2027.
OneStandard is being built now with manufacturers that have that date in the calendar and content that has to survive an inspection. Your content classes and policy shape the product.
Bring one product family and the markets it ships to. We will map the content classes with you and run one document version through to a record you could hand over.