Skip to main content

​
Overview

Workflows inside the Ollang Project Management Dashboard determine:
  • how Orders are processed,
  • which providers are used,
  • which AI models are selected,
  • how language pairs are configured,
  • and how localization pipelines operate.
A Workflow is a reusable operational configuration that defines how localization should happen for a specific language pair. Example:
This allows organizations to:
  • standardize localization workflows,
  • benchmark provider quality,
  • optimize costs,
  • and maintain consistency across multilingual operations.

​
What is a Workflow?

A Workflow is a reusable configuration that determines:
  • which providers are used,
  • which language pair is localized,
  • how localization is processed,
  • and how Orders are operationalized.
Instead of manually selecting providers every time, organizations can:
  • preconfigure workflows,
  • reuse them across Orders,
  • and standardize operational quality.
B1
B2

​
Workflow Scope

Workflows can currently be configured at:

Global Workflow

Default workflow configuration applied across the organization.

Folder-Level Workflow

Folder-specific workflow configuration overriding global settings.
Project-level workflows are not currently supported. Workflows can be configured globally or at the Folder level.

​
Global Workflows

​
Overview

Global workflows act as:
  • organization-wide default workflows.
These workflows automatically apply when:
  • no Folder-level workflow exists.
Example:
This becomes:
  • the operational default for all applicable Orders.

​
Folder-Level Workflows

​
Overview

Folder-level workflows allow teams to configure localization differently for specific operational use cases. This is useful when:
  • different teams require different providers,
  • different content types require different quality standards,
  • or experimentation is needed.
Example:
Even though:
  • the language pair is identical,
the workflow may differ depending on:
  • operational requirements,
  • content type,
  • and quality expectations.
B3
B4

​
Workflow Override Logic

Folder-level workflows always override:
  • Global workflows.
Hierarchy:
Example:
Result:

​
Workflow Architecture by Order Type

Different workflows can be configured independently for different localization stages. Supported workflow categories include:

Video Captioning (CC)

Speech-to-text and caption generation workflow.

Subtitle Translation

Translation workflow for multilingual subtitle localization.

AI Dubbing

Voice synthesis workflow including Lip Sync and Audio Description.

Document Translation

Localization workflow for structured and document-based content.

Studio Dubbing

Workflow coordination for studio-managed dubbing operations.

​
Multiple Workflows for the Same Language Pair

Organizations may configure multiple workflows for the same language pair across different Folders. Example:
This enables:
  • benchmarking,
  • experimentation,
  • quality optimization,
  • and use-case-specific localization.

​
Provider Architecture

​
Overview

Ollang acts as an orchestration layer. Rather than forcing a single provider, the platform enables organizations to:
  • choose providers,
  • benchmark providers,
  • compare results,
  • and optimize workflows.
This creates operational flexibility because:
Organizations can continuously optimize workflows based on:
  • quality,
  • cost,
  • speed,
  • and content type.

​
Speech-to-Text (STT) Providers

Speech-to-text providers are commonly used for:
  • Video Captioning,
  • transcription,
  • subtitle generation,
  • and speaker diarization.
Supported examples include:

Ollang Agentic

Recommended orchestration-first workflow optimized for flexibility.

Speechmatics

Commonly used for multilingual speech recognition.

AssemblyAI

Speech-to-text provider for transcription workflows.

AWS

Enterprise-oriented transcription workflow option.

​
Translation Providers

Translation providers are used for:
  • subtitle translation,
  • document translation,
  • multilingual localization,
  • and AI-assisted language generation.
Examples include:

Ollang Agentic

Recommended orchestration workflow for multilingual localization.

OpenAI

LLM-based multilingual translation workflows.

Claude

Translation workflow for reasoning-intensive localization tasks.

Gemini

Multilingual translation and contextual language generation.

​
Text-to-Speech (TTS) Providers

TTS providers are used for:
  • AI Dubbing,
  • Audio Description,
  • voice synthesis,
  • and multilingual speech generation.
Supported examples include:

ElevenLabs

Commonly used for multilingual voice generation and dubbing workflows.

Gemini TTS

Used for controllable voice prompting and expressive delivery.

Azure TTS

Enterprise voice synthesis option.

​
Workflow Lifecycle

​
Important Operational Rule

Workflow updates only affect future Orders.
Already-created Orders:
  • remain unchanged,
  • preserve their operational workflow,
  • and continue using the workflow selected at Order creation.

​
AI Quality Benchmarking

Organizations commonly benchmark providers using:
  • AI QC Evaluation,
  • Human QC Annotation,
  • analytics,
  • and localization performance tracking.
This helps teams understand:
Because the AI ecosystem evolves rapidly:
The platform is intentionally designed for:
  • experimentation,
  • optimization,
  • and provider flexibility.

​
Example Enterprise Workflow

​
Example Multi-Folder Benchmarking

Teams can later compare:
  • localization quality,
  • human edit percentage,
  • QC outcomes,
  • and operational performance.

​
Important Operational Notes

No. Workflows can currently be configured at Global level and Folder level only.
Yes. Folder-level workflows always take precedence.
Yes. Different Folders may use different workflows for the same language pair.
No. Workflow updates only affect future Orders.
Yes. Different workflow stages can use different providers.
No. Ollang acts as an orchestration layer and allows organizations to choose providers based on operational goals.