Foreign Language Translation Workflow for Intel

Principal workflows

• Take in requests: Requests are entered by staff or sent by your intake system through the Work API, and each must be confirmed unclassified. The due date is set from the priority's target, and the original due date is kept whenever it changes.
• Assign the right linguist: The queue lists open requests by priority and due date and suggests a linguist for each: Active, available, at the minimum proficiency level in the language and under capacity, with dialect and subject matches first and then the lightest workload. Coordinators assign one request at a time or all of them by workload.
• Translate, check and certify: Your linguists translate outside the app and track their work in My work, where the approved glossary terms for each language pair are listed. When a translation is ready, a second linguist reviews it and records the QA result and findings by category, and a certifying linguist other than the translator certifies it where the request needs it.
• Deliver and report: A request can be delivered only with a passing QA result and any required certification. Once delivered it is locked, a printable cover sheet records who translated, checked and certified it, and turnaround, backlog, throughput and quality reports show how the office is doing.

Who uses it

• Linguists and translators who translate, gist and check documents
• Requesting offices that follow their requests and receive the translations
• Mission managers who set request priorities and due dates
• Intelligence oversight officers responsible for handling rules
• Translation office managers who set targets, levels and capacity

Reporting

• Backlog by language, priority and age
• Requests delivered and words translated per linguist and language
• Turnaround against the agreed and the original due date
• QA findings by category, linguist and language
• Requester feedback on delivered translations
• Linguist coverage per language and proficiency retests due

Features

• Translation queue: Open requests by priority and due date, with filters for past due, at risk and on hold, each request's age and review status, and the suggested linguist.
• Linguist suggestions: Eligible linguists listed for each request, dialect and subject matches first and then the lightest workload, with Assign or Assign all by workload.
• Proficiency checks: With the check on, only Active, available linguists at your minimum level in the language can be given a request, and only qualified second linguists can review it.
• Linguist roster: Linguists by language and proficiency level, coverage per language against open requests, open workload and proficiency retests coming due.
• My work: Each linguist's own list of requests to translate, to review in QA and to certify, and glossary terms waiting for their approval.
• Certification: Where a request needs it, a certifying linguist other than the translator certifies it after a passing QA result and before delivery.
• Due dates and holds: Due dates set from your priority targets, holds while the requester answers a question, and every due-date change kept with its reason and the original date.
• Second-linguist QA review: A QA reviewer other than the translator records the result, finding counts by category and notes, and every rework round is counted.
• Review status on every request: Each request shows where it stands, from waiting for a linguist to QA reviewed, certified or gist delivered, on its page, in the queue, on the cover sheet and in the turnaround export.
• Glossaries and terminology: Approved translations of recurring terms for each language pair, listed on every matching request, proposed by linguists and approved by a certifying linguist or a product administrator other than the person who proposed them.
• Quality: QA findings by category, linguist and language and requester feedback, next to turnaround, on-time delivery, backlog by age and throughput by linguist, with CSV exports.
• Handling rules and audit trail: Every request must be confirmed unclassified, delivered requests are locked, and every change, assignment and export is recorded with the person and time.

Integrations

• Request intake systems: Translation requests sent by your intake system's team through the Work API, each confirmed unclassified and checked by the same rules as requests entered by staff.
• Analytic and reporting tools: Turnaround, backlog, throughput and quality exported as CSV, or requests read through the Work API, for the reporting tools your office already uses.
• Personnel data and proficiency testing: Linguists and their recorded proficiency levels loaded by CSV import or sent through the Work API from your personnel or language testing records.
• Webhooks: Event notices, without field values, sent to your own systems when a request is created, assigned, moved or changed, so they can read it through the Work API.
• Sign-in: Users sign in with their Moraph account, using email and password and, optionally, two-step verification. Sign-in through your own identity provider (SAML or OpenID Connect) is not offered.
• Security information and event management: Product administrators export the activity log as CSV for your SIEM and auditing systems; each export is itself recorded.
• Work API: Requests, linguists and glossary terms available to your own reporting tools through the Moraph Work API with a read-only key.

Deployment

• Unclassified records only: For unclassified administrative records only: requests must be confirmed unclassified, and no classified material belongs in records, comments or files.
• Connected use only: The app runs in Moraph Apps with a network connection; there is no disconnected or offline configuration, and linguists translate outside the app.
• Moraph cloud: Hosted on Cloudflare's network for unclassified administrative records.
• With a managed service: Optionally supported by a Moraph managed service for day-to-day administration.

Security and privacy

• Nothing sent to outside services: The app sends nothing to translation services or other outside systems: it holds the workflow record, and your linguists translate outside it.
• Access by product role: Viewers read, users enter and work requests, and product administrators change settings and export; a linguist can't change their own levels or record QA on their own translation.
• A second linguist checks, people decide: Only the QA reviewer's own account or a product administrator can record a QA result, never the translator, and only a certifying linguist other than the translator can certify.
• Encryption and keys: Material is encrypted at rest and in transit.
• Complete audit trail: Every change, assignment, QA result, certification and export is recorded with the person and time, and the history can't be edited.
• Unclassified only: Each request must be confirmed unclassified before it is saved, and classified material must never be entered, attached or pasted into comments.

Limitations

• It doesn't translate, transcribe or identify languages. Your linguists translate outside the app; it tracks the request, the people, the checks and the delivery.
• It doesn't test or certify proficiency. Levels are as recorded from your language program, and retest reminders depend on the test dates entered.
• It doesn't check translation quality itself. QA results and finding counts are what your reviewer records; the app enforces who may record them.
• It doesn't decide who translates. Suggestions follow your recorded levels, availability and workload, and a coordinator assigns.
• Effort estimates and at-risk flags come only from the word counts entered and the daily word rate your office sets; they are estimates, not a schedule.
• It doesn't receive material on its own. Requests come from staff or from your intake system through the Work API.
• It is not for classified material. Each request must be confirmed unclassified, and classified material must never be entered, attached or pasted into comments.
• Compliance with handling rules, including rules for information about US persons, remains your organization's responsibility. The app enforces the unclassified confirmation and its workflow rules, and records what happens.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/foreign-language-translation-workflow-for-intel. Purchasing routes and company information: www.moraph.com/how-to-buy.