Community manager guide to bilingual communities in Wales

What to take away

This guide is for teams that run or buy community-management software and services. The Welsh Language Standards shape how you configure intake, moderation queues, bilingual templates and language reporting.

A platform is not neutral. If it routes Welsh posts slowly or stores only English templates, the service gap is yours. The sections below connect Welsh language compliance to the tools this site covers.

How Welsh language duties affect community services

The Welsh Language Standards are the operational rules that flow from the Welsh Language (Wales) Measure 2011, which gave the Welsh language official status in Wales. Public bodies, and some others funded by the Welsh Government, must comply with the standards they are issued.

Standards are set out in regulations made under the Measure, including the Welsh Language Standards (No. 1) Regulations 2015. The applicable numbered duties depend on the regulations and compliance notice for the organisation; there is no single list that applies to every body. Standards include service delivery, policy making, operational and record-keeping duties. Examples relevant to online communities include offering services in Welsh, handling Welsh correspondence and publishing information bilingually. Check the body’s notice and the Commissioner’s published standards for the exact standard numbers, wording and any exemptions before configuring the service.

The standards cover service delivery, policy making, and internal operations.

For community services, the standards bite hardest on how members are served. If a housing association runs a residents' forum, or a council runs a tenant panel, the standards can require that Welsh speakers receive the same service without asking for it. That includes correspondence, notices, and digital spaces.

A compliance notice sets out which standards apply to a named body. The notice is specific, so two organisations in the same county can have different duties. A community manager should know which standards appear in their own notice before designing any workflow.

The Welsh Government publishes policy context for the standards and the wider goal of a million Welsh speakers. That context helps explain the policy direction, but a community manager should use their organisation's compliance notice to identify the duties that apply.

Standards do not usually name a forum or a chat channel. They name activities: dealing with the public, publishing material, and providing services. A community platform falls under those activities when it is used to deliver them. The medium does not exempt the duty.

There is also an equality dimension. Bilingual provision is often framed as a language duty, but it sits alongside wider equality and human rights obligations. The Welsh Government groups these concerns under its equality and human rights guidance, which is worth reading if your community serves protected groups.

In practice, the first task is a mapping exercise. List every community touchpoint: welcome messages, moderation notices, surveys, event invitations, complaint responses. Mark which are covered by your standards notice. That list becomes the backbone of everything else.

The Welsh Language Commissioner's duties and how they reach moderation

The Welsh Language Commissioner is the regulator. The Commissioner promotes the use of Welsh, monitors compliance with the standards, and investigates complaints from members of the public. The office can also conduct its own inquiries into a body's provision.

A complaint does not have to come from a Welsh speaker who was refused a Welsh service. It can come from anyone who believes a body has failed to comply. That makes moderation decisions visible in a way many teams do not expect.

Consider a typical case. A member posts in Welsh in a housing association forum. A moderator replies only in English and closes the thread. The member complains. The Commissioner asks the body to explain its policy and its practice. If the body cannot show a bilingual process, the gap is hard to defend.

Moderation reaches the Commissioner through the service, not through a separate channel. A refusal to engage in Welsh, a slow response to a Welsh-language query, or a published moderation policy that exists only in English can all be framed as service delivery failures.

The Commissioner's remit also covers promotional work. Bodies are expected to encourage Welsh use, not merely tolerate it. A community that actively invites Welsh posts and visibly welcomes them is in a stronger position than one that waits.

Enforcement tools include compliance notices, requirements to produce action plans, and, in serious cases, financial penalties. Most bodies resolve matters through an agreed improvement plan. The reputational cost of a public inquiry usually matters more than the penalty.

For a community manager, the practical takeaway is documentation. Keep a record of Welsh-language interactions, response times, and any policy changes made in response to a complaint. This is the same discipline covered in our guide to governing a community under UK rules, where evidence of process is what regulators ask for first.

Bilingual moderation workflows: triage, escalation and appeals

A bilingual moderation workflow is a written sequence that handles both languages at every stage. It should cover how posts are triaged, who reviews them, how decisions are escalated, and how a member appeals. Each stage needs a Welsh and an English path that are genuinely equal.

Start with triage. Every incoming post, report or message is logged with a language flag. Welsh posts go to a moderator with Welsh competence, or to a bilingual queue if the first moderator cannot assess tone or intent. Tone is the hard part: a phrase that reads neutral in English can read abrupt in Welsh, and the reverse.

The steps below describe a workable sequence for a mid-sized community team.

Escalation should be time-bound. If a Welsh-language item cannot be assessed within the shift, it moves to a named bilingual lead. That lead owns the decision and the reply. Leaving an item in limbo is itself a compliance risk.

Appeals need the same treatment. A member who appeals in Welsh should receive the outcome in Welsh, with the reasoning available in both languages. The appeal route should be published in both languages and reachable from the community itself.

Staffing is the usual constraint. Not every moderator will be fluent. The answer is not to route all Welsh work to one person indefinitely, but to build a rota with at least one Welsh-capable moderator on each shift, backed by a bilingual escalation lead.

Written policies should state how language is handled in enforcement. This is close to the work of writing a disclosure policy that moderators can enforce, because both depend on clear, testable rules rather than good intentions.

Content and campaign planning for Welsh and English members

Content workflows should treat Welsh as a production language, not a translation afterthought. That means planning Welsh posts alongside English ones, with their own schedule, owners and review.

A simple model works for most teams. Each campaign has an English track and a Welsh track. Both are drafted from the same brief, but the Welsh version is written or reviewed by a Welsh speaker rather than passed through machine translation alone. Publishing only one track is a visible gap.

Language choice in campaigns should follow the audience. In areas with high Welsh-speaking populations, such as parts of Gwynedd, Ceredigion and Carmarthenshire, Welsh-first publishing is often the norm. In other parts of Wales, bilingual publishing with Welsh visible is the safer baseline.

Use the Office for National Statistics' Census data on Welsh language ability to understand the local profile. It can inform channel planning, but should be combined with what members tell you and does not determine an individual member's language preference.

Campaign calendars should mark Welsh-language dates and events, and give them the same prominence as other content. A Welsh Language Rights Day post should not be an afterthought added the day before.

Tone matters as much as language. Welsh-language community content often reads better when it is written directly for the audience rather than translated from an English original. Cultural references, place names and humour do not always carry across.

Measure both tracks. Track engagement, response times and complaint rates by language. If Welsh posts consistently get slower moderation responses, that is a workflow problem, not an audience problem.

Tools and AI support for bilingual community management

Software can reduce the load, but it cannot carry the duty. Platform features such as language tagging, bilingual templates and separate moderation queues are useful. They should be configured to match your standards notice, not the vendor's default.

The Welsh Government has invested in Welsh-language AI through a partnership with Cosine, aimed at better bilingual digital services. This does not show that any particular community-management product supports Welsh; ask vendors to demonstrate the workflows you need.

Even so, translation tools should not be the final word on moderation decisions. A machine translation can miss sarcasm, dialect or a coded insult. For enforcement, a Welsh-speaking human should confirm the decision before a sanction is applied.

Useful tooling includes language detection on intake, automatic routing to bilingual queues, bilingual response templates, and dashboards that report by language. These are ordinary features, but they need deliberate setup.

AI can help with drafting and summarising at scale, particularly for long threads. It should be used with a review step, and the review should be done by someone competent in Welsh. That is the same principle as the daily community workflow, where automated steps sit inside a human-owned process.

Procurement is where compliance is won or lost. Ask vendors how their tool handles Welsh, whether it stores data in the UK, and how it supports the standards. Get the answers in writing before signing.

Recording bilingual provision as evidence of compliance

Evidence is what turns good practice into a defensible position. If the Commissioner asks how your community serves Welsh speakers, a log answers faster than a memory.

A compliance log should capture the language of each significant interaction, the response time, the language of the reply, and any policy or workflow change made. It does not need to be elaborate. A spreadsheet with consistent fields is enough for most teams.

The checklist below covers the minimum records worth keeping.

Review the log quarterly. Look for patterns: slow Welsh responses, gaps in shift coverage, policies that exist in one language only. Fix the pattern, not just the individual case.

Training records matter too. If moderators have completed Welsh-language awareness or policy training, note it. Regulators tend to accept a body that can show it is actively improving.

Finally, publish what you can. A short bilingual statement explaining how the community handles both languages builds trust and reduces complaints. It also shows the Commissioner that the duty is understood, not merely endured.

Common questions