Skip to main content

Overview

The Ollang Project Management Dashboard supports three different mechanisms to improve localization quality and consistency:
  • Memories
  • Global Custom Instructions
  • Folder-Level and Project-Level Guidelines
These systems work together to help organizations:
  • preserve terminology consistency,
  • maintain brand voice,
  • improve translation quality,
  • standardize localization behavior,
  • and operationalize multilingual content at scale.
Each mechanism serves a different purpose.

Understanding the Difference

Memory

Stores historical translations, approved terminology, and multilingual reference content.

Custom Instructions

Global account-level guidance applied when no folder or project guidelines exist.

Guidelines

Folder-level or Project-level instructions controlling localization behavior for specific workflows.

Memories

Overview

Memories help organizations preserve:
  • approved terminology,
  • historical translations,
  • brand language,
  • multilingual consistency,
  • and localization context.
Instead of translating every Order from scratch: Ollang can reference previously approved linguistic material to improve translation consistency. This is especially important for:
  • enterprise localization,
  • recurring content,
  • regulated industries,
  • product localization,
  • media localization,
  • and brand-sensitive workflows.

How Memories Work

Memories act as:
  • multilingual contextual references.
Organizations can upload previously approved translation material which can then help guide future localization workflows. Example:
Future Orders involving similar content may reference this approved terminology.

Creating a Memory

Project Management Users can create Memories directly from:
  • the Memories section inside:
  • the Ollang Project Management Dashboard.
Memories can also be managed programmatically through the public API: create, rename, and delete memories, and import translation units into them. See List Memories, Create Memory, and Import Memory Items. Workflow:
Example:

Multiple Memories

Organizations are not limited to:
  • a single Memory.
Users may create:
  • multiple Memories,
  • multiple terminology repositories,
  • and specialized localization references.
Example:
This enables:
  • department-specific localization,
  • content-type specialization,
  • and multilingual operational consistency.

Supported Memory Formats

The platform currently supports:

TMX

Translation Memory Exchange format commonly used in enterprise localization.

CSV

Spreadsheet-based terminology and translation reference format.

XLSX

Structured terminology and multilingual reference files.

JSON

Structured localization and multilingual data workflows.

Memory Matching Behavior

Memories function as:
  • contextual linguistic guidance.
When matching content:
This helps preserve:
  • consistency,
  • terminology quality,
  • and multilingual continuity.
For the exact definitions of a full (exact) match, a fuzzy match, and how they feed the translation readiness score, see Translation Readiness, Matching, and Context Assets.

Where Memory Matches Are Shown

Memory match visibility depends on context management being enabled for your workspace. Contact your Ollang account manager if you do not see the cards described below.
With context management enabled, Project Management users can see:
  • before the Order — TM exact and TM fuzzy coverage on the Translation readiness card of the New Order form,
  • after the Order — which Memory (name and version) was used, how many segments it grounded, and the per-segment match evidence on the Assets utilized card of the Order details page.

Global Custom Instructions

Overview

Global Custom Instructions represent:
  • organization-wide localization guidance.
These instructions are automatically applied when:
  • no Folder-level guideline exists,
  • and no Project-level guideline exists.
Global Custom Instructions act as:
  • fallback localization behavior.

Typical Use Cases

Global Custom Instructions are commonly used for:
  • brand tone,
  • writing style,
  • terminology preferences,
  • localization behavior,
  • and organization-wide standards.
Example:

Important Behavior

Global Custom Instructions only apply when no Folder-level or Project-level Guidelines are configured.
Hierarchy:

Folder-Level Guidelines

Overview

Folder-Level Guidelines represent:
  • instructions uploaded to a specific Folder.
These guidelines automatically apply to:
  • all Projects,
  • and all Orders inside that Folder.
They keep applying when a Project also has its own Project-level Guidelines; the two are used together. A Folder guideline stops applying to a single Project only when it is removed from that Project.

Example Use Case

Example:
All Projects inside the Folder inherit:
  • the same localization behavior.

Folder-Level Workflow


Managing Folder Guidelines Through the API

Folder-level documents can also be managed programmatically, without the dashboard: The three folder-level document types are guideline, guideline_glossary, and character_list. Documents attached through the API behave exactly as those uploaded in the dashboard: they apply to every project already in the folder and to projects created in it afterwards, including projects created through Direct File Upload. Removing a document detaches it from those projects as well.

Project-Level Guidelines

Overview

Project-Level Guidelines represent:
  • highly specific instructions uploaded to a particular Project.
These Guidelines are used together with:
  • the Folder-Level Guidelines of the Project’s Folder.
They add to the Folder’s guidance rather than replacing it. Project-level guidance is used when:
  • one Project requires unique localization behavior.

Example Use Case

Example:
Result:
while:
If one of the Folder’s guidelines should not apply to Episode 5 at all, remove it from the Episode 5 Project. The other Episodes keep it.

Override Hierarchy

Project-Level and Folder-Level Guidelines are combined, not ranked. When a Project has guidelines of its own and its Folder has guidelines too, all of them are used for the Project’s orders, with the Project-Level documents first. Adding a Project guideline does not switch off the Folder’s guidelines.
Meaning:

If a Project has its own Guidelines:

  • they are used together with the Folder’s Guidelines.

To keep a Folder Guideline away from one Project:

  • remove it from that Project, in the dashboard or with Remove Project Document. The Folder keeps it, and its other Projects keep using it.

If neither a Project nor a Folder Guideline exists:

  • Global Custom Instructions are used.

Managing Project Guidelines Through the API

Project-level documents can also be managed programmatically, one project at a time: The document types are the same as for folders: guideline, guideline_glossary, and character_list. The list also returns the folder documents that apply to the project, with their current content and folderId set. Removing one of those stops that folder document applying to this project only; the folder and its other projects keep it. Changing project guidelines needs the same write access as folder guidelines.

Supported Guideline Formats

Guidelines may be uploaded in formats such as:

PDF

Commonly used for localization instructions and style guides.

DOCX

Commonly used for structured guideline documentation.

TXT

Lightweight instruction format for localization guidance.

XLSX

Structured terminology or instruction reference sheets.

Example Enterprise Localization Setup

Result:

Memory vs Guidelines

Memory

Helps preserve historical translations, terminology consistency, and multilingual reference material.

Guidelines

Controls how localization should behave for a specific workflow or Project.

Best Practices

Organizations typically achieve best results by combining:
Example:
This helps improve:
  • consistency,
  • translation quality,
  • brand alignment,
  • and multilingual scalability.

Important Operational Notes

Yes. Organizations can create multiple Memories for different content types, departments, or terminology domains.
Memories are global and available organization-wide.
No. Project-Level Guidelines are used together with the Folder-Level Guidelines. To stop a Folder guideline applying to one Project, remove it from that Project; the Folder and its other Projects keep it.
Yes. A Project’s own guidelines and its Folder’s guidelines are all used for the Project’s orders, with the Project-Level guidelines first.
Not currently. Visibility into Memory source attribution is part of the future roadmap.
The platform automatically applies active Global Custom Instructions.