Translation assurance
questions, answered.

Horyzun is a multilingual publish assurance company. Translation tools and translators create localized content. Horyzun reviews that content before publication and reports whether the meaning, terminology, claims, and conditions still match the approved source. You receive the findings, the reasoning behind them, and an approval record. This independent assurance layer sits between translation and publication.

No. Horyzun does not produce translations. Your agency, internal team, freelancer, or machine translation workflow continues to produce the content. We review it. The review is separate from translation production. Your release owner retains final approval.

No. Keep the translation management system, CAT tool, or machine translation engine you already use. Horyzun is complementary. The practical pattern is: translate in your existing workflow, then send the finished content to Horyzun for independent review before you publish it.

Translation quality assurance can include automated checks, linguistic review, and approval workflows. Horyzun focuses on independent pre-publication multilingual review against an agreed source and review brief. A human reviewer assesses material differences. The findings and their resolution support a documented release decision. If your current process already provides this evidence and independence, an additional review may not be necessary.

A translation can read naturally and still change what the content commits you to. An obligation becomes an option ("must" becomes "may"). A qualified claim becomes a promise ("designed to reduce" becomes "guaranteed to reduce"). A condition disappears ("within 30 days" becomes "at any time"). We call this semantic drift. It is difficult to catch by reading the translation on its own, because nothing in the sentence looks wrong.

Meaning against the approved source: claims and their limits, obligations and their force, conditions and eligibility, defined terms and approved terminology, consent and permission scope, numbers, dates, and units. We review meaning preservation under the constraints you agree in advance. Style, creative adaptation, and brand voice are outside the scope unless a specific wording is named as a constraint.

The review brief records what must remain true for one asset: the source intent, the terminology that is fixed, the claims that must not get stronger or weaker, the conditions that must survive, and the versions and languages in scope. We agree it with your team before the review starts. In our documentation, items that cannot change are called locked invariants. Our guides explain how to scope one.

An approval records a decision against the agreed review brief and the exact versions examined, together with the reasoning for each resolved finding. It is a scoped statement: the content passed the review it was given. It is not a guarantee that no error exists and not a legal or regulatory certification. Your designated release owner retains final publishing authority.

The review scope and constraints, the source and target versions examined, each material finding with the passage that raised it, the resolution and who made it, any questions left open, and the named release owner. A later reader should be able to follow what was checked, what changed, and why the content was approved.

Automated checks compare the source and the translation and surface differences. A human reviewer then judges which differences matter in context, explains the finding, and records the reasoning. A difference is not automatically a defect, and that judgment is not something we automate away.

Content where a change in meaning creates a real consequence: policies and terms, privacy and consent notices, refund and eligibility rules, safety and product instructions, regulated product information, pricing and offer terms, and public claims. Low-consequence content rarely justifies the step. We would rather scope a narrow review of what matters than a broad review of everything.

Yes. A vendor can take part in the review workflow and resolve findings. The record shows the independent findings and the release owner's decision separately, so the accountability stays visible on both sides. A provider can include the review record with its deliverables once the agreed review is complete.

No. Horyzun governs the approval, not the project. Assignments, deadlines, and vendor management stay in the tools you use today. During a pilot we agree a practical way to exchange content and findings alongside them.

We can scope reviews for consequential and regulated content, and we agree the reviewer qualifications, evidence requirements, and approval responsibilities in advance. Be clear about the limit: a Horyzun review supports your compliance process by documenting what was checked and decided. It does not by itself establish regulatory compliance or replace your legal review.

We scope languages per engagement, based on the reviewers we can assign to your content and subject matter. Tell us the language pairs in your next release and we will confirm what we can review and what we cannot.

It depends on the volume, the number of languages, and how much of the content carries claims or conditions. We agree the turnaround with you when we agree the scope, before the review starts. If a deadline does not allow a useful review, we will say so.

We agree confidentiality and content handling before you share an asset. Our confidentiality policy is linked in the footer, and you can raise specific handling requirements in the first conversation.

Request a pilot and tell us about one asset you are preparing to publish. We will discuss the languages, the risks, the timing, and the review path, then agree a focused pilot if there is a fit.

Consider Horyzun when a multilingual release contains safety instructions, material claims, or conditions that must retain their meaning, and your release owner needs an independent basis for approval. Start with one asset whose review causes uncertainty or repeated escalation. Agree the scope, reviewer qualifications, and evidence before a pilot begins.

A changed instruction found after publication can require corrections across languages and another approval cycle. Horyzun aims to surface material differences before release and keep findings, resolutions, and version references in one review record. A pilot should measure review time, repeated escalations, and correction effort against your current process. Cost savings and reduced liability are not established outcomes; an approval record documents a decision and does not transfer responsibility.

Horyzun is designed to operate within existing quality, compliance, localization, security, and regulatory workflows.

The standards and regulations relevant to a PublishSafe engagement depend on the customer's industry, jurisdiction, content, intended use, internal quality system, and supplier requirements.

Examples of standards and regulatory frameworks that may be relevant include:

Translation and localization

• ISO 17100 — Translation services: requirements covering professional translation processes, translator and reviser competence, resources, and quality-controlled translation delivery.
• ISO 18587 — Post-editing of machine translation output: requirements for full human post-editing of machine-translated content and post-editor competence.
• ISO 5060 — Evaluation of translation output: guidance for systematically evaluating human translation, post-edited machine translation, and machine-translation output.
• ISO 11669 — Translation projects: guidance for specifying and managing translation projects and their requirements.

These standards can inform how translators, reviewers, evaluators, specifications, and verification processes are incorporated into a PublishSafe workflow.

Quality and compliance management

• ISO 9001 — Quality management systems: a general framework for establishing controlled, repeatable, and continually improving quality processes.
• ISO 37301 — Compliance management systems: requirements and guidance for organizational compliance-management systems.

PublishSafe can support these environments through defined review procedures, traceability, controlled records, documented findings, issue resolution, and approval evidence.

Medical devices and life sciences

• ISO 13485 — Medical-device quality management systems: requirements for quality-management systems used within the medical-device industry.
• ISO 14971 — Medical-device risk management: a framework for identifying, evaluating, controlling, and monitoring risks associated with medical devices.
• FDA Quality Management System Regulation (QMSR / 21 CFR Part 820): the United States medical-device quality-system regulation, which incorporates ISO 13485:2016 by reference.
• 21 CFR Part 11: requirements that can apply when regulated records or signatures required by FDA regulations are maintained electronically.
• EU Medical Device Regulation (EU MDR 2017/745): European requirements governing medical devices, including information provided with devices such as labeling, warnings, and instructions for use.
• EU In Vitro Diagnostic Regulation (EU IVDR 2017/746): European regulatory requirements applicable to in vitro diagnostic medical devices.

Horyzun does not replace the manufacturer's quality management system, regulatory affairs function, risk-management process, or final release authority. PublishSafe can instead operate as a controlled supplier or verification process within those systems.

Information security and privacy

• ISO/IEC 27001 — Information security management systems: requirements for managing information-security risks and protecting confidentiality, integrity, and availability.
• ISO/IEC 27701 — Privacy information management systems: requirements and guidance for managing personally identifiable information and privacy controls.

These standards can become relevant when customers provide confidential, proprietary, personal, legal, financial, clinical, or other sensitive content for multilingual processing.

Artificial intelligence governance

• ISO/IEC 42001 — Artificial intelligence management systems: requirements for governing the responsible development and use of AI systems, including areas such as accountability, transparency, risk management, and oversight.

Where AI-assisted systems are used within PublishSafe, Horyzun's model is to use automation as part of a controlled assurance process rather than treating AI output as final professional, legal, regulatory, or release approval.

No. The standards listed above should not be interpreted as certifications held by Horyzun.

They represent standards, regulations, and quality frameworks that may govern a customer's operations or may be relevant to how a multilingual workflow is designed.

Some standards apply to manufacturers, some to translation-service providers, some to organizational management systems, some to particular processes, and some only under specific circumstances.

Horyzun's role is to make it possible to configure the multilingual review process around the requirements that apply to the customer's particular environment.

For example, a medical-device manufacturer operating under ISO 13485 and FDA QMSR may require qualified translators, controlled terminology, defined reviewer responsibilities, version traceability, discrepancy resolution, and documented approval before translated labeling is released.

A financial institution may instead require specialized financial reviewers, strict confidentiality controls, preservation of disclosures and contractual conditions, internal compliance approval, and auditable records.

The applicable workflow is therefore determined by the customer's regulatory and quality requirements rather than by applying the same certification model to every industry.

No.

Where a workflow requires particular qualifications or professional judgment, PublishSafe can incorporate the appropriate personnel, including:

• certified or qualified translators
• independent linguistic reviewers
• medical or scientific specialists
• regulatory affairs professionals
• lawyers and legal translators
• financial or compliance specialists
• quality-assurance personnel
• privacy and security personnel
• authorized customer approvers

Horyzun provides the verification, workflow, evidence, and governance layer around those participants.

It does not convert automated analysis into professional authority that the underlying regulation or customer quality system requires a qualified person to exercise.

Yes.

PublishSafe is intended to integrate with existing quality and localization processes rather than force organizations to replace them.

Customers can define requirements such as:

• approved translators and reviewers
• required professional qualifications
• approved terminology
• protected claims, warnings, and instructions
• prohibited terminology
• required review stages
• segregation between translator and reviewer
• escalation procedures
• risk classifications
• approval authorities
• version-control requirements
• record-retention requirements
• electronic approval requirements
• confidentiality and data-handling requirements

PublishSafe can then preserve the resulting translation, verification findings, reviewer decisions, revisions, approvals, and release evidence as part of a controlled multilingual workflow.

No.

Translation quality standards and regulatory compliance address different questions.

A translation may have been produced according to a professional translation process while still being subject to additional requirements imposed by the customer's industry, jurisdiction, quality system, labeling requirements, legal obligations, or internal approval procedures.

Likewise, using qualified translators alone does not automatically establish regulatory compliance.

For high-consequence content, organizations may need to demonstrate not only who performed the translation, but also what requirements governed it, what was reviewed, which risks were identified, how issues were resolved, who approved the final content, and which version was ultimately released.

PublishSafe is designed to make that process explicit and traceable.

No.

Horyzun does not issue ISO certification, FDA approval, CE marking, notified-body certification, regulatory authorization, or legal opinions.

A PublishSafe Approval Record is evidence of a defined multilingual review and release process. It documents what was reviewed, which findings were identified and resolved, who participated in the approval process, and what content was ultimately approved.

It should not be interpreted as a regulatory conformity certificate.

Horyzun can support multilingual review and release workflows where errors in meaning can create financial, regulatory, legal, operational, safety, or reputational consequences.

Examples include:

• medical-device labeling, instructions for use, safety information, and software interfaces
• pharmaceutical and life-sciences content
• financial-services and fintech disclosures, product terms, customer communications, and platform interfaces
• insurance policies, notices, and customer-facing documents
• legal and contractual content
• privacy policies, consent language, and regulatory notices
• cybersecurity and enterprise software documentation
• product claims, warranties, refund terms, and conditions
• compliance-sensitive marketing and public communications
• other multilingual content where preserving the exact meaning of the source matters

Horyzun can operate alongside an organization's existing translators, language-service providers, subject-matter experts, legal teams, regulatory teams, and internal reviewers.

No.

Horyzun does not issue regulatory approvals, legal opinions, government certifications, notified-body certifications, or other statutory approvals.

PublishSafe provides structured multilingual verification, risk findings, human review, decision records, and approval evidence that organizations can incorporate into their existing quality, compliance, legal, or release processes.

Final responsibility for regulatory compliance and publication remains with the organization responsible for the content.

Yes.

Horyzun is designed to support organizations where multilingual content passes through controlled review and approval processes.

Depending on the industry, this may include medical devices, pharmaceuticals, financial services, fintech, insurance, legal services, enterprise software, cybersecurity, and other regulated or high-consequence environments.

The exact workflow depends on the organization's applicable regulations, internal policies, quality systems, content type, risk profile, and release requirements.

Horyzun supports these processes; it does not replace them.

Not necessarily.

In many regulated environments, organizations are responsible for qualifying and controlling the suppliers, software, and external services used within their own quality or compliance systems.

Requirements vary significantly by jurisdiction, industry, intended use, and the role a supplier performs.

Horyzun is designed to support this supplier-controlled model through defined workflows, traceability, human review, version history, documented findings, and approval records.

Where a customer has specific supplier qualification or validation requirements, these can be addressed as part of the engagement.

No.

Horyzun can work with qualified professional translators, certified translators, subject-matter specialists, internal localization teams, or an organization's existing language-service provider.

For specialized content, customers may require reviewers with domain-specific qualifications or experience in areas such as medicine, pharmaceuticals, finance, law, engineering, or regulatory affairs.

PublishSafe adds a structured verification and governance layer around those people and workflows rather than replacing their expertise.

Approval responsibilities depend on the customer's workflow and the risk associated with the content.

A PublishSafe workflow can include:

• professional translators
• independent linguistic reviewers
• subject-matter experts
• legal or compliance personnel
• regulatory affairs teams
• quality assurance teams
• product owners
• authorized customer approvers

Horyzun records the review process and provides evidence supporting the release decision.

Final authority remains with the organization and the personnel it designates.

Horyzun may use automated and AI-assisted systems to analyze multilingual content, compare source and target meaning, identify inconsistencies, enforce terminology, and surface potential risks.

AI output is not treated as final regulatory, legal, or professional approval.

For workflows requiring human review, identified findings are evaluated and resolved by appropriately qualified personnel before final approval.

Automation is used to strengthen the review process and make potential meaning failures easier to identify, not to remove human accountability.

Yes.

Horyzun does not require organizations to replace their current translation provider.

PublishSafe can review translations produced by:

• internal localization teams
• professional translators
• language-service providers
• specialized industry translation vendors
• machine-translation systems
• AI translation systems
• previously published or legacy translations

This allows Horyzun to operate as an independent assurance layer between translation and publication.

Yes.

Horyzun is designed to complement existing localization infrastructure rather than replace it.

An organization can continue using its preferred translators or language-service providers while using PublishSafe for additional semantic verification, risk analysis, review governance, and approval evidence before release.

PublishSafe focuses on whether important meaning has changed between the approved source and the proposed translation.

Depending on the content and engagement, verification can include:

• missing or added information
• obligation changes such as "must," "should," or "may"
• warnings and prohibitions
• terminology consistency
• numerical values, units, dates, and quantities
• claims and disclaimers
• eligibility conditions
• refund and cancellation conditions
• privacy and consent language
• permissions and restrictions
• functional instructions
• ambiguous wording
• tone and authority
• inconsistencies across related content

A translation can be grammatically fluent while still changing one of these elements. PublishSafe is designed to surface those differences before publication.

Depending on the engagement, PublishSafe can preserve evidence such as:

• approved source content
• reviewed target content
• language and locale
• content scope
• source and target versions
• approved terminology
• protected or locked requirements
• identified semantic discrepancies
• severity or risk classifications
• reviewer findings
• reviewer dispositions
• revisions made to resolve findings
• reviewer and approver identities
• timestamps
• version history
• approval status
• review scope and limitations

The resulting record provides a traceable explanation of how a multilingual release decision was reached.

No.

A PublishSafe Approval Record documents the scope, review process, findings, resolutions, and approval decision associated with a multilingual release.

It is not an FDA approval, CE certification, legal opinion, notified-body certificate, government authorization, or other regulatory conformity certificate.

Its purpose is to provide organizations with structured and auditable evidence of their multilingual review process.

Yes.

Horyzun can support multilingual workflows involving medical-device labeling, instructions for use, user interfaces, safety information, product documentation, and related content.

PublishSafe can incorporate qualified medical translators, independent reviewers, terminology controls, semantic verification, discrepancy resolution, and documented approval.

The medical-device manufacturer remains responsible for its quality system, regulatory obligations, supplier controls, and final release decision.

Yes.

Horyzun can support high-consequence pharmaceutical and life-sciences content where changes in terminology, instructions, warnings, claims, quantities, or other meaning may create material risk.

Relevant domain experts and qualified reviewers can be incorporated into the workflow according to the customer's requirements.

Horyzun does not replace regulatory, medical, scientific, or legal review required by the organization.

Yes.

Horyzun can be used to verify multilingual financial and fintech content such as disclosures, product terms, customer notices, eligibility conditions, fees, promotional claims, platform interfaces, and other customer-facing communications.

PublishSafe can help identify changes involving numbers, conditions, obligations, permissions, exclusions, claims, and other meaning that may materially affect how a financial product or service is represented.

Yes.

Horyzun can provide an additional verification and review layer for multilingual contracts, policies, terms, notices, and other legal or compliance-sensitive content.

Qualified legal translators, lawyers, or other authorized specialists can remain responsible for legal interpretation and final approval where required.

Horyzun does not provide legal advice or replace legal counsel.

Traditional translation review often focuses heavily on linguistic quality: grammar, fluency, style, terminology, and readability.

Those qualities matter, but a translation can read perfectly while still changing the underlying meaning.

For high-consequence content, a subtle change can affect:

• what a customer is promised
• what a user is required to do
• who is eligible
• when a refund applies
• how a warning is interpreted
• what a product is claimed to do
• how personal information may be used
• what rights or restrictions apply

PublishSafe focuses specifically on identifying, documenting, resolving, and approving these meaning-level differences before content is released.

Horyzun sits between translation and publication.

A typical workflow may look like:

Approved source → Translation → PublishSafe verification → Qualified review → Issue resolution → Authorized approval → Publication

Horyzun can therefore work with existing translation-management systems, localization teams, agencies, translators, reviewers, and internal approval processes.

Its role is to provide an independent assurance and governance layer before multilingual content is released.

Localize manages localization for websites and applications and offers a Translation QA workflow for review before publication. Consider Horyzun when your release owner also needs a review separate from translation production, with findings tied to source and target versions. Keep Localize for localization and agree the content handoff during a Horyzun pilot. This does not imply a native integration.

Localize Translation QA documentation ↗

Phrase offers localization tools and quality evaluation, including automated checks and configurable AI checks. Horyzun's proposed role is a separate review of publication readiness: agree what must remain true, assess material differences with human judgment, and document their resolution. Consider a pilot if your existing Phrase workflow leaves a gap in independent review or approval evidence. Confirm the handoff and scope before sharing content.

Phrase Quality Evaluator documentation ↗

No. RWS provides translation, localization, and linguistic quality assurance services. Horyzun's focus is independent translation assurance after content has been translated. First assess the review and evidence included in your existing RWS engagement. Consider Horyzun where your release owner needs an additional independent assessment against a defined brief. The value depends on the gap in your current process.

RWS localization and quality assurance services ↗

Trados supports translation work and quality review. Its Smart Review feature provides AI assessment and feedback on translation quality. Horyzun focuses on a scoped review before publication, with human judgment and evidence for the release owner's decision. Continue using Trados for translation. Evaluate Horyzun if your process needs independent review beyond the checks and approvals you already perform. Content exchange is agreed per pilot; a native connector is not assumed.

Trados Smart Review ↗