Scottish public sector AI content operations and Gaelic language duties

On Content AI Lab, we cover AI-assisted content operations for UK teams. Scottish public sector AI projects show how Gaelic language duties, procurement rules and UK GDPR shape the content workflow.

This article looks at those duties through a content operations lens: drafting, translation, review, records and governance. Read it if you manage public-facing AI content in England, Scotland, Wales or Northern Ireland.

What to take away

How this fits AI-assisted content operations

This site covers AI-assisted content operations. This article treats Scottish procurement, Gaelic language duties and UK GDPR as operating constraints on the AI content workflow, not as a separate public sector topic.

Use it to set named reviewers, glossary control, accessibility checks and audit logs before a tool goes live. Those steps decide whether an AI content tool survives audit and public scrutiny.

The same operating model works for any AI content team. Name the task, assign reviewers, control the glossary, check data and accessibility, and log decisions before launch.

For readers outside Scotland, treat these rules as a stress test. They show which controls make an AI content workflow defensible when language duties, data law and procurement oversight meet. That is the core of AI-assisted content operations.

How Scottish public bodies buy AI content tools under procurement rules

Scottish public bodies buy AI content tools through regulated procurement. The rules come from the Procurement Reform (Scotland) Act 2014 and the Public Contracts (Scotland) Regulations 2015, alongside the Scottish Government's procurement policy.

A council, health board or government agency cannot simply subscribe to a tool on a card. It must define the requirement, test the market and record the award.

Start with the business case. What content task will the tool do? Drafting, translating, summarising, tagging or checking accessibility? Each answer changes the route. A tool that only helps staff write internal notes is lower risk than one that publishes public-facing bilingual content.

Then choose the route. Low-value purchases may sit under a framework or a quick quote. Higher-value contracts need an open or restricted procedure. The current thresholds, published by the Scottish Government, are £139,000 for central government goods and services, £214,000 for sub-central bodies, and £5,372,000 for works.

Contracts of £50,000 or more for goods and services are regulated under the Procurement Reform (Scotland) Act 2014. Scottish buyers often use Public Contracts Scotland to advertise, and the Scottish Government's procurement plan to schedule the work. The route must match the estimated contract value, including VAT and any extension period.

Write the specification around outcomes, not product names. Say what the tool must do for Gaelic, for accessibility and for records. Ask for evidence of data protection compliance, not just a privacy policy link. This is where many AI content tools fail at tender stage.

Before you map data protection duties, decide who owns the content. If the tool trains on your drafts, you have a data question. If it stores your drafts outside the UK, you have a transfer question.

If it produces Gaelic that no human checks, you have a language duty question. These are procurement questions because they belong in the contract.

Steps for a compliant Scottish purchase

A worked example helps. NHS Highland's Gaelic Language Plan commits to bilingual public communications for health services. In a procurement for AI content tools to support that plan, the health board estimates the contract at £80,000 for goods and services. That is below the £214,000 sub-central threshold and above the £50,000 regulated procurement threshold.

It uses Public Contracts Scotland to seek quotes. The specification asks for UK data hosting, a Gaelic review workflow and an audit log.

Two suppliers bid. One cannot show where its training data comes from. NHS Highland awards to the other and records the reason.

Gaelic language duties and bilingual content production

The Gaelic Language (Scotland) Act 2005 gives Gaelic official status in Scotland. It established Bòrd na Gàidhlig and requires public bodies to produce Gaelic language plans. Those plans set out how the body will use Gaelic in its work, including public communications. For many Scottish public bodies, bilingual content is not optional.

A rushed translation of a statutory notice is not the same as a Gaelic version prepared with language expertise. The duty is about status, not just text volume.

There is a practical shortage of Gaelic reviewers. That makes workflow design important. Use AI content tools for first drafts, terminology checks and formatting, then route the text to a qualified Gaelic speaker. Tools such as Phrase, Smartling and LanguageWire can handle drafts and terminology. Build the review step into the content operations process, with named roles and sign-off.

Terminology matters. Gaelic has regional and institutional variation. A health board and a council may use different terms for the same service. Keep a shared glossary and update it. AI content tools can apply a glossary, but someone must own it.

Bilingual content also means layout. Gaelic and English have different word counts and sentence shapes. A design that fits English may overflow in Gaelic. Test templates with both languages before launch. This is a content operations task, not a translation afterthought.

Example: a Gaelic language plan in practice

The Scottish Government's Gaelic Language Plan 2022 to 2027 sets out commitments for bilingual publications and digital services. In one workflow, staff use AI content tools to draft English, then a Gaelic translator adapts the text. The translator flags two terms for the glossary. The body publishes both versions on the same day and logs the review.

That is a repeatable bilingual content process.

UK GDPR obligations for public sector AI content operations

UK GDPR and the Data Protection Act 2018 govern how Scottish public bodies handle personal data. AI content tools often process personal data, even when staff do not intend it. A draft case study may contain a real name. A prompt may include an email. A transcript may include a service user's details.

Public bodies need a lawful basis for that processing. Consent is rarely the right basis for routine public communications. Public task or legal obligation usually fits better. Record the basis before the tool goes live, not after a complaint.

The ICO publishes UK GDPR guidance and resources for organisations, including public bodies. Use it to check your lawful basis, your retention rules and your approach to automated decision-making.

If an AI content tool makes decisions about individuals, such as ranking complaints, the rules are stricter. The same applies where one system sits inside several UK regulations at once.

Data protection impact assessments matter. A DPIA is required for high-risk processing. AI content tools that analyse personal data, monitor staff or profile service users can cross that line. For example, a tool that records and analyses staff drafts to improve its model is a DPIA trigger.

The contract should state: "The supplier shall host all personal data in the UK and shall not transfer it outside the UK without the authority's prior written consent. " Complete the DPIA before procurement closes, so the contract can carry the right clauses. uk.

International transfers need attention. Many AI content tools process data outside the UK. Check the transfer mechanism and the safeguards. If the supplier cannot meet UK standards, the tool is not suitable for public sector work.

Staff training is part of compliance. People paste more than they should. Set clear rules on what may and may not go into an AI content tool. Keep a record of training and review it.

G-Cloud and framework routes for Scottish buyers

G-Cloud is a UK-wide framework for cloud services, run through the Crown Commercial Service. Scottish public bodies can use it, and many do. The G-Cloud buyers' guide explains how to search the Digital Marketplace, compare services and call off without a full tender.

The framework suits commodity cloud services, including some AI content tools. It saves time and gives standard terms. But it does not remove the need for due diligence. You still check data location, security, accessibility and Gaelic support.

Scottish buyers also use Scottish Government frameworks and local arrangements. The choice depends on value, urgency and fit. A framework call-off can be fast, but it limits negotiation. An open procedure takes longer but lets you shape the contract.

Check the framework's scope. On G-Cloud 14, Lot 2 (Cloud software) covers AI content and translation tools. Some language service providers list translation management there. An AI content tool may sit in more than one lot. Read the lot descriptions and the service definitions.

Before signing, run vendor due diligence on the supplier's data practices, subcontractors and exit terms. A framework gives you a route, not a guarantee.

Accessibility, equality and inclusive AI content

Public sector content must be accessible. In Scotland, that means meeting WCAG 2.2 AA and the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. AI content tools can help or harm. They can generate alt text, simplify language and check reading age. They can also produce biased or exclusionary text.

The Equality Act 2010 applies to public bodies in Scotland. It covers the provision of services and the exercise of public functions. AI content that discriminates against a protected group can breach the Act. Bias can enter through training data, prompts or the way staff use outputs.

Test AI content tools for bias before launch and after updates. Use representative content, including Gaelic and English examples. Check how the tool handles names, accents and cultural references. Keep a record of tests and fixes.

Accessibility is not only about disability. It covers language, literacy and digital confidence. Bilingual content in English and Gaelic widens access. Plain language helps everyone. AI content tools can support both if staff review the output. Work through a market entry checklist before you commit budget to a supplier that has never handled public content.

Inclusive content also means representing Scotland's communities accurately. AI tools may default to generic UK or US examples. Edit for local context. A Scottish public body should sound like it serves Scotland.

Governance and records for Scottish public content

Governance turns a tool into a system. Scottish public bodies need named owners, written rules and a review cycle. Decide who approves AI content tools, who monitors output and who handles complaints.

Records matter. The Freedom of Information Act 2000 gives the public a right to request information from UK-wide public authorities; the Freedom of Information (Scotland) Act 2002 covers Scottish public authorities. That includes information about AI content operations. Keep records of procurement decisions, DPIAs, supplier assessments and content reviews. If you cannot find the record, you cannot rely on it.

Set retention rules for drafts and prompts held in AI content tools. Some content is a record, some is not. A published notice is a record. A discarded draft may not be. The National Records of Scotland's retention schedules often set six years for procurement records. Keep DPIAs for the life of the processing and review them annually.

Review contracts annually. AI content tools change quickly. A supplier may add features that affect data protection or Gaelic support. Build a review point into the contract.

Train staff and keep the training current. Governance fails when people do not know the rules. Combine policy, training and audit into one cycle. For a wider view of buying decisions, see this tools and supplier guide, then set a date for your next contract review.

Common questions