Five things that go wrong in multilingual social work, rehearsed before they happen

Multilingual social marketing risk scenarios are rehearsal prompts, not predictions. Do not assign an invented likelihood or universal severity. The five scenarios below are the structure of this article.

Worked example: a 'carbon neutral' claim, translated from English into Welsh for an Instagram post. If the source owner withdraws the claim, the rehearsal asks who freezes the source version and stops the Welsh scheduled post.

What to take away

Before you act

The approved claim changes after translation starts

Trigger: the source owner withdraws or amends a claim while target versions are in review or live.

Owner: source-claim owner, with the publishing controller able to pause every affected asset.

Containment: freeze the source version, stop scheduled posts and identify all target files, landing pages and creator briefs derived from it. Do not ask reviewers to patch wording without a new approved source.

Evidence and recovery: reconcile the dependency register, obtain subject approval, commission professional language work, complete native-level and accessible final-render checks, then verify withdrawal of superseded versions. Restart only when the source owner and each specialist signs the same version. CAP's misleading-advertising rules provide the UK substantiation boundary, not approval of the corrected claim.

An AI or supplier update changes output

Trigger: a model, policy, prompt route, subprocessor, data location or output format changes, or the acceptance set produces a new material error.

Owner: AI service owner and security lead.

Containment: disable the assisted step, preserve logs and return to the last approved manual route. Block unreviewed output from publication.

Evidence and recovery: recheck provenance, privacy terms, access and version; rerun the fixed language, subject, bias, accessibility and security tests. The NCSC's secure AI system guidance treats change and operation as lifecycle concerns. It does not guarantee recovery. Restart requires recorded acceptance from each relevant reviewer.

Personal or confidential material enters the wrong service

Trigger: monitoring, a reviewer or a supplier alert identifies unauthorised input, disclosure or retention.

Owner: incident lead, with the privacy officer and data controller deciding the statutory route.

Containment: revoke access, stop further transfer, preserve appropriate evidence and follow the approved incident plan. Do not copy exposed data into informal investigation channels.

Evidence and recovery: establish affected records, systems, recipients and deletion status; test credentials and approved routes; record rights handling and any required notifications. The ICO's AI risk toolkit is under DUAA review, so qualified advice must use current material. Check the date shown on the ICO page before you rely on it. Restart only after the controller accepts the residual risk and the secure path passes testing.

A target format creates an access barrier

Trigger: assistive-technology testing, user feedback or live-render inspection finds missing information, unusable controls or an inaccessible alternative.

Owner: accessibility lead and publishing controller.

Containment: pause the affected target asset and provide the approved accessible route if one exists. Preserve the report and exact rendering.

Evidence and recovery: correct the target version, repeat professional language and subject review where meaning changed, test the final route again and confirm linked landing content. GOV.UK's inclusive communication guidance is a useful public-sector reference, not a private campaign pass. Restart needs a documented final-render result.

The social account or agency relationship fails

Trigger: unauthorised access, platform suspension, lost administrator access, supplier insolvency signal or termination notice.

Owner: account owner, security lead and contract owner.

Containment: invoke the access register, revoke supplier credentials, preserve logs, stop spending authority and activate the approved communication route.

Evidence and recovery: restore buyer-controlled administration, reconcile scheduled assets, verify billing, export records, confirm deletion duties and test a clean publication with non-production content. The NCSC's supply-chain security guidance supports supplier-risk planning but does not set a recovery time.

Review these exercises when the language, claim, platform, supplier, law or data flow changes. Retire a scenario only when its trigger can no longer occur in the documented system. The cluster remains on publication hold until named specialists approve the controls.

Common questions

What should happen when the source owner withdraws a claim during translation?

See "The approved claim changes after translation starts" above.

How should a team respond to an AI or supplier update that changes output?

See "An AI or supplier update changes output" above.

What steps are needed when personal or confidential material enters the wrong service?

See "Personal or confidential material enters the wrong service" above.