Plain Answers, Not Paperwork: Giving Members Usable AI Signposting in 2026

Artificial intelligence has become a standing item in member conversations, but the question is rarely “what is our policy?”. More often it is narrower and more immediate: can I use this tool for this task, what should I check before I do, and whose guidance should I trust? Those are practical questions, and they deserve a practical response.

The BGOA Member Hub is not a regulator, a law firm or a procurement authority. It is a place where members should be able to find a calm starting point. That distinction matters. A member-first AI guide should not attempt to settle every legal question. It should help members recognise the question they are actually asking, point them to the right official source and make clear where professional advice is needed.

Start with the questions members are already asking

A useful guide begins with evidence, not assumption. Rather than drafting a broad statement about AI and waiting for members to read it, the Hub can run a short, rolling question collection. This need not be elaborate. A simple form, a standing item in regional meetings and a named inbox can gather the phrases members use in their own words.

Questions should be logged in a light register with four fields: the question as asked, the type of task involved, the likely source of assurance and the date reviewed. Over a quarter, patterns will emerge. Members may be asking about drafting customer emails, summarising meeting notes, screening supplier proposals, using AI features embedded in existing software or handling personal data in prompts. Each raises different considerations.

The register also prevents the Hub from answering imaginary questions. If no member has asked about model training or automated decision-making, that does not mean those topics are unimportant. It means the published guide should prioritise what members are actually trying to do, while keeping a route for specialist queries to be escalated.

Separate the answer into three usable buckets

Members benefit from a simple structure. Three buckets are usually enough: what can be used with normal care, what must be checked before use, and what the Hub cannot answer.

The first bucket covers low-risk, everyday uses where the member remains in control and the output is reviewed by a person. Examples might include brainstorming, rephrasing internal notes or creating a first draft that is checked against source material. The guide should still be honest about limits: confidential information, personal data and anything intended for publication need a second look.

The second bucket covers uses that require a specific check. This is where the Hub signposts rather than decides. If personal data is involved, the Information Commissioner’s Office guidance on data protection should be the first port of call. If the question touches consumer-facing claims, competition or market conduct, the Competition and Markets Authority may be relevant. If the member operates in a regulated sector, their sector regulator’s guidance takes precedence. For general UK policy context, GOV.UK pages from the Department for Science, Innovation and Technology are a sensible starting point.

The third bucket is equally important. The Hub should say plainly when a question needs legal advice, a data protection officer, a sector specialist or the member’s own professional indemnity insurer. That is not a failure of service. It is a sign that the guide knows its limits.

Publish a signposting page, not a policy statement

The published page should be short enough to use in a working day. A brief introduction should state what the page is and is not. A table or list can then set out common tasks, the checks that apply and the official source to consult. Vendor material can be referenced only where it helps explain a product feature, and it should be clearly separated from regulatory guidance.

Language matters. Avoid implying that the association has approved a tool, certified a supplier or interpreted the law. Use phrases such as “members should check”, “official guidance is available from” and “this page does not replace professional advice”. These are not hedges. They are accurate descriptions of the Hub’s role.

The page should also include a date and a review owner. A guidance page without a review date ages badly. A page with a date but no owner ages worse, because members cannot tell whether it is maintained.

Review quarterly, but do not chase every headline

A quarterly review is a reasonable rhythm for a member hub. It allows the page to reflect new official guidance, recurring member questions and changes to commonly used tools without turning every news cycle into a rewrite. The review should ask three questions: have official sources changed, have member questions moved, and is any wording now misleading?

Changes should be recorded briefly so members can see that the page is maintained. A short changelog is more useful than a long commentary. Where a question cannot yet be answered, the page can say so and invite members to contribute through the question form. That keeps the guide honest and gives the association a legitimate reason to keep listening.

Keep the Hub’s role clear

The value of this approach is not that it produces a definitive answer to every AI question. It is that it gives members a trusted route through the noise. The Hub can collect real questions, publish plain-English signposting, separate official guidance from vendor claims and review the page on a fixed cycle. It can do all of that without pretending to be a regulator or a substitute for professional advice.

For members, that is often exactly what is needed: not another policy document, but a clear place to start, a named source to check and a route to escalate when the question goes beyond the ordinary.