Should Welsh procurement rules change sales enablement content in Wales?

What to take away

How Welsh Government procurement routes differ from England-only buying

Welsh Government procurement routes are not simply England's rules with a different logo. Public sector buyers in Wales work under the Wales Procurement Policy Statement.

The UK-wide public procurement policy guidance still shapes thresholds and transparency, which you can read in the Public procurement policy - GOV.UK. That means a bid team selling into Cardiff or Bangor may face different notice routes, different evaluation weightings and different language requirements from a deal in Bristol or Leeds.

Start with the notice. Welsh public bodies advertise contracts above £25,000 on Sell2Wales, and above the thresholds in the Public Contracts Regulations 2015 on the Find a Tender Service. Contracts Finder is the England-only below-threshold route, so a bid team that monitors only Contracts Finder will miss Welsh notices. Buyers notice that gap.

A typical notice pattern makes this concrete. A health board advertising a software support contract posts it on Sell2Wales, the national procurement portal, and the same notice reaches Find a Tender once it clears the UK threshold.

Below the headline routes, the practical differences show up in how you evidence social value and community benefits. Welsh frameworks let through Welsh Government Commercial Delivery (WGCD) often ask for community benefits plans that reference local supply chains and Welsh language outcomes. A generic England-only case study will not answer that question.

You need a named Welsh reference or a credible plan to build one.

Another difference is the treatment of small and medium-sized suppliers. Welsh procurement policy places emphasis on accessible routes for SMEs and third sector bodies, which can change how you package your offer. Instead of one large enterprise proposal, you may need modular sales content that lets a smaller buyer adopt one module at a time.

Finally, name the buyer. A health board such as Betsi Cadwaladr University Health Board and a Welsh Government sponsored body such as Natural Resources Wales may each apply the rules differently from a county council. Before you write a word, confirm who is buying, under which framework, and whether the Welsh Language Standards apply to them.

That single check saves rework later. You can reuse the same discipline you would apply to a market entry checklist for any new region.

Welsh Language Standards duties that change published sales content

The Welsh Language Standards are not a slogan. They are duties placed on named public bodies in Wales, and they can affect what those bodies must publish, answer and provide in Welsh.

The standards sit under the Welsh Language (Wales) Measure 2011 and are monitored by the Welsh Language Commissioner. A compliance notice from the Commissioner names the body and sets out which standards apply, covering service delivery, policy making, operational and promotion duties.

If your sales content is hosted on a public body's site, or if you are supplying a service to that body, your content may fall inside the scope of their Welsh language scheme or standards.

For enablement teams, the practical effect is that bilingual content stops being a nice extra. A Welsh language version of a product page, a form or a support article may be required, not optional. The buyer's compliance team will ask how you handle Welsh language requests, and they will expect a named process rather than an assurance.

This reaches into advertising too. The CAP Code applies to marketing communications in the UK, including bilingual sales content, and claims must be clear and substantiated in whichever language they appear.

A Welsh headline that promises more than the English body copy can be a problem. The Advertising codes - ASA | CAP set out the rules that apply, and they apply to Welsh language campaigns as much as English ones.

Substantiation is the second trap. If you claim that a product is "fully bilingual" or "Welsh language ready", that claim needs evidence.

The AdviceOnline Library - Advice for Marketers - ASA | CAP is the reference marketers use to check whether a claim like that can be supported. If your Welsh language duty statement is vague, fix it before a buyer or a regulator asks.

The wider regulatory context matters too. Advertising in Wales sits inside the same UK system described by the About regulation - ASA | CAP, so there is no separate Welsh advertising code to learn. What changes is the language duty, not the honesty standard.

Building bilingual content inside sales enablement software

Bilingual content production fails when it is treated as a translation task at the end of a campaign. It works when the sales enablement software treats Welsh and English as two published variants of the same asset, with one owner and one review cycle.

Set up your content model first. Each asset should carry a language field, a Welsh language reviewer and a status that shows whether the Welsh version is draft, reviewed or published. Without that field, your team will lose track of which pages are compliant and which are English-only.

Record the buyer's standard on the same record, so the Welsh page can be traced to the duty it serves.

Next, decide what gets translated. Not every asset needs a Welsh version. Priority goes to anything a public sector buyer must read to buy, use or complain: product pages, pricing explanations, forms, support articles and complaint routes. Internal sales decks can usually stay in English unless the buyer asks otherwise.

Then build the workflow. A simple sequence works for most teams.

Use a checklist before anything goes live.

A worked example helps. Suppose you sell a case management tool to a Welsh local authority. Your English page says the tool is "used by councils across the UK". The Welsh page must say the same thing, not a stronger claim.

You record the reviewer, publish both pages on the same day, and add a line to your bid response explaining how Welsh language support requests are handled. That is the whole job, done once and reused.

Your channel strategy should treat Welsh and English as two channels with one source of truth, not two separate campaigns.

The evidence Welsh public sector buyers expect

Public sector buyers in Wales are not looking for enthusiasm. They are looking for evidence that you understand their language duties, their procurement route and their reporting lines. The evidence they expect is specific and checkable.

First, they expect a named person or team responsible for Welsh language content. A supplier who says "we will translate as needed" without naming who does it reads as a risk. A supplier who names a reviewer and a review cycle reads as a safe pair of hands.

Second, they expect examples. If you have delivered bilingual content for another Welsh public body, say so, with the buyer's permission. If you have not, say what you will do instead and when. Buyers in Wales have heard vague promises before, and they can tell the difference.

An illustrative example shows the shape of a strong answer. Picture a supplier pitching a patient booking tool to Cardiff and Vale University Health Board.

The bid names the standard that covers the health board's service delivery duties and points to the asset record, where the Welsh page is marked reviewed on a set date. This example is drawn to show the shape of a good answer, not a reported bid.

Third, they expect your claims to survive scrutiny. Keep a file of evidence for every claim you make, in both languages.

Fourth, they expect you to know the notice route. If the contract was advertised through Sell2Wales or a Welsh framework, show that you found it there. If it is on the Find a Tender Service, show that too. Route awareness is a cheap signal of competence.

Finally, they expect you to respect the buyer's own standards. A Welsh health board or a government sponsored body will have its own Welsh language scheme or compliance notice, and your content should fit it rather than compete with it.

Ask for the scheme, read it, and mirror its language in your response. That is the difference between a compliant bid and a rejected one.

This is also where your target audience work pays off. A Welsh public buyer is not the same persona as an English private buyer, even if both use the same job title.

Should UK-wide enablement teams localise for Wales or standardise?

There is no single right answer, but there is a defensible decision process. Localise when the buyer is a Welsh public body, when the contract is advertised through a Welsh route, or when the Welsh Language Standards apply to the buyer.

Standardise when the buyer is a private Welsh company with no Welsh language duty and no Welsh language requirement in the tender.

Use a simple test. If a Welsh language version is required by the buyer's standards, localise. If it is requested but not required, localise the buyer-facing pages and leave internal assets in English. If it is neither required nor requested, standardise and revisit at the next framework renewal.

Record the decision. A short note in the asset record explaining why an asset is English-only protects your team later. It also stops the same debate recurring every quarter.

Keep the localisation narrow. You do not need a full Welsh site to win a Welsh contract. You need the pages a buyer must read, a named reviewer, and a review cycle that holds. That is a small, repeatable cost, and it is cheaper than losing a framework because a form was English-only.

Finally, treat Wales as a market with its own rules, not as a suburb of England. Teams that apply the same rules and ethics across the UK still need to check the Welsh language duty separately, because it is a duty, not a preference.

Do that, and your sales content will hold up in Cardiff, Bangor and everywhere between.

Common questions