Tell the right language owner when source content changes.
When a service changes in one language, other versions need assessment. ImbaHub can implement change tracking that connects identified source edits to the right language records and review tasks. Automation signals a need; it does not establish translation quality or publish changes without an expressly agreed workflow.
- Source
An identified record and watched version change.
- Change queue
Affected languages receive a traceable review need.
- Decision
An owner assesses content against the right version.
A delivered change signal is not an approved translation.
The source changes again while translation is underway. Is an old completion click enough?
Not if it refers only to the earlier source. Compare versions at completion and preserve the new review need.
Define relationships and change direction
Choose a source for each content group and identify language records that are genuine equivalents. Not every local page must follow the same original. Local market information must not be overwritten merely because a source page changes.
Fictional example: a company changes from installation to advisory services. Its Swedish source, Norwegian offer and English explanation need review, while a separate local service has another scope. Connect approved content IDs rather than similar page headings.
Choose changes that should create a task
Scope watched fields, relationships and events. A publication flag and a new delivery condition need not create the same task. Define whether drafts, published evidence or both are monitored and how the recipient recognises the difference.
Event support and delivery behaviour vary between systems. Review the actual connection and exercise repeated or failed signals. Technical receipt does not establish that a language owner read the message or completed the change.
| Element | Decision to establish | Check |
|---|---|---|
| Relationship | Which records are equivalents? | The right language records need review |
| Fields | What can change local meaning? | Important edits detected; irrelevant noise limited |
| Version | Which source did review assess? | Decision can be compared with a new source |
| Owner | Who receives and owns the task? | Queue is visible and actionable |
| Completion | When may a language be called current? | Assessment matches the right source version |
Preserve review needs when the source changes again
If a translator works against an older source when another edit arrives, the queue must retain that new need. A later completion click must not silently acknowledge something the reviewer never assessed.
Scope a version comparison at completion and a procedure for unknown source evidence. Duplicate events should not create conflicting tasks. Missing signals need an agreed comparison or follow-up rather than an assumption that notifications always arrive.
Hand over a traceable flow for one content type
An initial delivery can cover one content type, one source, selected languages, a review queue and version-bound completion. Localisation, machine translation, publication and external project tools need separate scope. Ready-made Imba CMS integrations are not assumed.
Handover identifies relationships, triggering changes, failure handling and retest ownership. We propose scope and price after review. Show a source change and the language versions it should affect without sharing private customer data.
Sources and further reading
Questions, answered
Does creating a task make the translation correct?
No. It identifies a review need. A responsible person must assess language and facts.
Should all local text be overwritten from one source?
No. Model genuine relationships and preserve local fields and offers under agreed ownership.