top of page
Search

How to Run a CUI Translation Workflow for a US Contractor Handling Federal Documents with AI

23 hours ago
7 min read

Translator reviewing a controlled federal document workflow



Table of Contents

 

 

Direct answer

 

A CUI translation workflow treats the translated file as CUI whenever the source is CUI. The contractor confirms the designation in the contract, restricts access to named and trained people, keeps files in systems approved for CUI, and keeps CUI out of any internet-enabled or unaccredited AI system. Each stage has an owner, a control and a record. Disposal follows the contract and records schedules.

 

Definition and scope

 

What counts as CUI in a translation project

 

The National Archives defines Controlled Unclassified Information (CUI) as information the Government creates or possesses, or that an entity holds for or on behalf of the Government, which a law, regulation or Government-wide policy requires or permits an agency to protect with safeguarding or dissemination controls. Classified information is excluded. So is information a non-executive entity keeps in its own systems that never came from an executive branch agency.

 

A university compliance office states that project material is CUI when the US government or its agent provides it or it arises under sponsored work, and the agreement says so. The sponsor’s award documents carry the duty to identify CUI and the security requirements.

 

Derived documents

 

The regulation at 32 CFR Part 2002 states that information not listed in the CUI Registry, such as vendor proprietary information, does not qualify as CUI. It also states that a document derived from a CUI document is itself CUI if it contains controlled information. A translation, a glossary extract and a translation memory segment all fall under this rule when they carry the controlled content.

 

Scope of this reference

 

This text covers US contractors and their language vendors handling federal material such as technical manuals, regulatory submissions, contracts and clinical or financial records. It does not cover classified information. It does not replace the contract, the agency’s CUI policy or counsel.

 

Steps, owners and controls

 

1. Intake and designation

 

Owner: contracts or compliance lead.

 

Control: written confirmation of CUI status. The federal sponsor determines whether an award involves CUI. ISOO Notice 2026-07 requires contracts that need CUI access to give the prime contractor guidance on identifying government-furnished and contractor-developed CUI, challenge processes, access, marking, safeguarding, decontrol and disposition, reporting, self-inspection, misuse and penalties. Record the CUI category and any dissemination control before a file reaches a translator.

 

2. Authorization of people and vendors

 

Owner: security officer and localization manager.

 

Control: access control list and training record. The same notice requires agencies to track training for personnel who handle CUI. A contractor should hold equal records for each linguist, reviewer and project manager. Flow-down clauses must reach every subcontracted vendor. Strong authentication for staff access is a related control, covered in guidance on secure employee access beyond VPN.

 

3. Preparation and system check

 

Owner: CISO and localization operations.

 

Control: system approval. 32 CFR Part 2002 requires authorized holders to keep CUI in controlled environments, under direct control or behind at least one physical barrier, and to prevent unauthorized people from accessing, observing or overhearing it. On federal systems, protection follows FIPS 199, FIPS 200 and NIST SP 800-53. For nonfederal systems, the contract usually points to NIST SP 800-171.

 

The translation management system, the file transfer path and any translation memory or term base are components that store or transmit CUI. Each needs to be inside the assessed boundary.

 

4. Translation

 

Owner: language vendor project manager.

 

Control: approved tooling only. ISOO Notice 2026-01, dated March 30, 2026, prohibits agency personnel from inputting CUI into AI systems that are internet-enabled, connected to infrastructure outside the agency’s control, or not accredited for CUI protection. Contractors should read that as the standard the sponsor will apply and confirm the contract terms. Public chatbots and public cloud translation tools fail this test.



5. Review and quality assurance

 

Owner: subject-matter reviewer and QA lead.

 

Control: documented QA with terminology checks against an approved term base. The FBI’s National Virtual Translation Center describes a quality assurance program, linguists tested for professional-level proficiency, post-editing of machine output and real-time project visibility. These are useful reference points for a contractor’s own program.

 

6. Marking

 

Owner: document control.

 

Control: marking check before release. HUD’s CUI marking policy requires portion marking with the acronym CUI plus category, limited dissemination markings where required, and a decontrolling date or event where feasible. Under 32 CFR 117.14, contractors use 32 CFR 2002.20 and the CUI Marking Handbook. That section also requires translations of classified information into another language to carry US markings and the foreign-language equivalent. Markings must survive layout and desktop publishing.

 

7. Delivery

 

Owner: project manager and security officer.

 

Control: encrypted transfer to named recipients, logged. Protection at rest and in transit is a stated requirement in ISOO Notice 2026-07. Email attachments to unmanaged accounts are not a compliant path.

 

8. Decontrol and disposal

 

Owner: compliance lead.

 

Control: disposition record. HUD’s CUI policy says authorized holders must clearly indicate when information is no longer controlled when they restate, paraphrase or re-use it, and that unauthorized disclosure is not decontrol. A translation is a restatement, so it follows this rule. The NVTC example describes no storage of translations or source documents past 90 days after project completion. The contract sets the actual retention period.

 

Decision criteria

 

Use these criteria to choose a translation route for CUI.

 

Criterion

Question

Evidence to request

Data location

Where is processing hosted?

Architecture description, hosting contract

AI boundary

Is any model internet-enabled or shared?

System diagram, accreditation status

Personnel

Who can open files?

Access list, training log

Flow-down

Do subcontractors accept CUI clauses?

Signed clauses

Audit trail

Are access and edits logged?

Sample log

QA

Is review by qualified linguists documented?

QA procedure, certificates

Marking

Do markings survive formatting?

Marking check step

Disposal

Are files and memories purged on schedule?

Disposition record

Certifications support the answer but do not replace the contract. ISO 27001 covers information security management. ISO 17100 covers translation services. ISO 18587 covers post-editing of machine translation output. None of them equals authorization to hold CUI.

 

Examples

 

Medical device manual under a federal contract

 

A device maker supplies a manual under a defense health contract. The contract marks design details as CUI. The manual is translated into Spanish and Korean. The translation inherits the CUI marking and category. Linguists work in an approved environment. The term base is treated as CUI if it holds controlled terms.

 

Contract amendment for a financial institution

 

A bank supports a federal agency and receives a CUI-designated contract amendment. Legal translation goes to a vendor named in the flow-down. The reviewer is a lawyer on the access list. Delivery is logged.

 

Decontrolled document

 

An agency decontrols a technical bulletin on a set date. The contractor translates it afterward. Per the HUD policy, the translation indicates the content is no longer controlled, and CUI markings are removed from the newly created document.

 

Failure modes and mitigations

 

Failure

Cause

Mitigation

CUI pasted into a public AI tool

Staff outside the localization team use AI freely

Written ban, approved tool list, technical blocking

Unmarked translation

Marking lost in layout

Marking check before release

Translation memory leaks controlled terms

Memory treated as non-CUI

Classify memory and term base with the project

Unauthorized linguist access

Freelancer added without review

Access control list tied to training records

Flow-down gap

Subcontractor not bound

Contract clause review at onboarding

Late disposal

No retention owner

Disposition record with date

Old guidance used

Rescinded notices followed

Review the ISOO notices list at each contract renewal

Current rules to track

 

The ISOO notices page lists Notice 2026-01 on AI, and Notice 2026-07 and Notice 2026-08 of September 2, 2026. Notice 2026-07 rescinds CUI Notices 2022-01 and 2020-01. NIST finalized SP 800-171 Rev. 3 on May 14, 2024. According to a professional legal analysis, DoD kept Rev. 2 as the DFARS 252.204-7012 standard until it announces otherwise. Confirm the version your contract cites. Assessments under SP 800-171A Rev. 3 may be independent third-party or government-sponsored.

 

Documenting and improving the workflow

 

ISOO Notice 2026-07 requires agencies to document and disseminate CUI procedures, track training, run annual self-inspections and put self-inspection and misuse-reporting requirements in contracts. A contractor should mirror this: a written procedure, a training log, an annual review of the vendor chain and an incident path. Changes to tools or vendors go through the same system approval as step 3. Teams that use AI in marketing and content should also set written rules on where AI output is allowed, as in this guide on AI text instructions, so that general-purpose tools never touch controlled files.

 

Where AD VERBUM fits

 

AD VERBUM provides AI+HUMAN hybrid translation on a proprietary LangOps System hosted on EU servers, with subject-matter expert review and a network of 3,500+ linguists. It holds ISO 27001, ISO 42001, ISO 17100, ISO 18587 and ISO 13485 certifications, audited independently by Bureau Veritas, and aligns to GDPR and HIPAA. Services are listed on the AD VERBUM services page. Contract authorization for CUI is confirmed per project.


AD VERBUM

Our view is that a CUI workflow succeeds when the vendor accepts the same controls as the contractor: named access, a closed AI environment, documented QA and a disposal record. Machine output alone does not meet that standard, and we do not treat MT or NMT as AI translation. Our AI+HUMAN hybrid model keeps subject-matter experts in the loop on every file, and our LangOps System runs on private infrastructure rather than outsourced public cloud tooling for core processing. We read our own analysis of machine translation risks as a security question first and a speed question second.   Eric Brown

 

Key points

 

  • A translation of CUI is CUI when it contains controlled information.

  • The sponsor and the contract decide CUI status.

  • CUI must stay out of internet-enabled or unaccredited AI systems, per ISOO Notice 2026-01.

  • Every linguist and reviewer needs authorization and a training record.

  • Markings must survive formatting and appear on the translated file.

  • Decontrol must be indicated when content is restated.

  • Disposal follows the contract and records schedules.

  • Check the ISOO notices list for changes.

 

FAQ

 

Does translating a CUI document create new CUI?

 

Yes, when the translation contains the controlled information. 32 CFR Part 2002 states that a derived document is CUI if it holds controlled content. The translation, translation memory segments and glossaries built from it need the same marking and handling.

 

Can a contractor use machine translation or an AI tool on CUI?

 

Only in a system accredited for CUI and under the agency’s control. ISOO Notice 2026-01 bars CUI from internet-enabled or unaccredited AI systems for agency personnel. Confirm the contract terms before any tool is used.

 

Who decides whether a translation project involves CUI?

 

The federal sponsor determines it, and the contract or award documents should identify it. Ask the contracting officer when documents are silent.

 

What should a language vendor provide before receiving CUI?

 

A system description, an access control list, training records, QA procedure, flow-down acceptance and a disposal plan.

 

Sources

 

 
 
bottom of page