The Consented Example: Building a Member Evidence Bank That Can Be Used, Not Just Cited

When a UK consultation closes or a regulator asks for a view at short notice, associations rarely suffer from a shortage of opinion. The harder task is producing a small number of concrete, consented examples that can be checked, described accurately and reused without creating risk for the member who supplied them. A policy evidence bank is not a larger survey. It is a modest, governed collection of member experience, held in a form that can inform a response in 2026 and still stand up to scrutiny afterwards.

Why a bank, not another survey

Surveys are useful for measuring prevalence. They are less useful for explaining mechanism: what actually happened, in what sequence, and what would have made a difference. A member evidence bank captures that second layer. Each record is a short account of a real experience, supplied with consent and stored against a policy theme. The aim is not to compile a comprehensive dataset. It is to ensure that when BGOA is invited to comment on a consultation, a Select Committee inquiry or a regulator’s call for input, the organisation can reach for examples that have already been offered, rather than issuing an urgent request for stories.

The discipline matters. Anecdotes repeated in private conversation can be persuasive, but they are fragile when they reach a public document. A consented example, recorded in a consistent way, gives the association something firmer: a traceable source, a clear permission boundary and a date.

The intake unit: one example per record

The most practical design is also the least burdensome. Members should be able to contribute one example in a few minutes, without preparing a case study or disclosing commercial secrets. A short online form can ask for:

• the broad sector, region and size band of the organisation;
• what happened, in no more than 150 words;
• roughly when it happened;
• what would have helped, or what changed as a result;
• the level of consent the member is giving for reuse.

Free text should be encouraged, but the form should make clear that the member should not include personal data, named clients, commercially sensitive figures or information that is subject to a live dispute. A simple prompt such as “describe the issue, not the identity” is often enough. The record can then be tagged by the policy lead with a theme, a date and a review date.

This is deliberately not a survey. There is no obligation to answer every field, and no expectation that a member will contribute regularly. The bank grows through ordinary contact: a bulletin item, a practice note, a regional meeting, or a prompt in a committee update. The invitation should be continuous and low-key, not a crisis appeal.

Consent that is specific and revocable

A single membership consent does not cover policy use. Consent should be recorded at the point of contribution, with clear choices. A workable model offers three levels:

1. Internal use only — the example informs BGOA’s understanding but is not quoted externally.
2. Anonymised external use — the substance may be used in a consultation response, regulator meeting note or industry update, with identifying details removed.
3. Attributed external use — the member agrees to be named or quoted, subject to a final check before publication.

The default should be anonymised external use, because it is useful and easier to grant. The form should also state how a member can withdraw consent, and what happens if they do. Withdrawal should be straightforward: the record is marked inactive, removed from future drafts and, where practicable, noted in any published material that has already used it. The association should keep the consent wording, the date and the version of the form that was used. That is not bureaucracy for its own sake; it is the difference between a usable evidence bank and a folder of uncertain permissions.

Anonymisation that preserves usefulness

The purpose of anonymisation is to protect the member without stripping out the detail that makes the example worth using. Names, client names, exact locations, precise financial figures and unique combinations of facts should go. Sector, broad region, size band, timing and the nature of the issue can usually stay.

“A small manufacturer in the North West” may be sufficiently precise for policy purposes. “A 42-person precision engineering firm in a named town, owned by a named family, supplying a named customer” is not. The risk of jigsaw identification is real in small sectors, and reviewers should ask whether someone with local knowledge could identify the organisation from the combination of details. Where there is doubt, the policy lead should consult the member before use rather than over-redact by default.

A review rhythm that matches UK policy cycles

A bank that is never reviewed becomes a store of old frustrations. A light rhythm is enough. Monthly, the policy lead should triage new records, check consent and tag themes. Quarterly, a small group — perhaps the policy lead and two committee members — should review which themes are thin, which examples are ageing and which upcoming consultations or regulator engagement might need evidence.

Each record should carry a review date. An example supplied in 2023 may still be relevant as history, but it should not be presented as current experience without a check. In 2026, with consultations and regulatory work moving at pace, the bank should be able to answer three questions quickly: what do we hold, how old is it, and what may we do with it?

Showing members where their evidence went

Members are more willing to contribute when they can see the result. A short evidence trail in the member hub is more effective than a general thank-you. After a consultation response or regulator meeting, BGOA can publish a brief note: the issue, the date, the themes informed and whether anonymised member examples were used. It should not reveal confidential detail or imply that every contribution changed a decision.

A quarterly “where your evidence was used” item can list the main engagements and explain what happened next. Where appropriate, members who gave attributed consent can be thanked by name. The rest can be thanked collectively, with a clear statement that their examples informed the association’s position. This closes the loop without turning the bank into a publicity exercise.

A small governance envelope

A workable evidence bank needs an owner, a retention rule and an escalation route. The owner is usually the policy lead. Retention should be no longer than necessary, with a default review after two years and deletion or re-consent thereafter. Any request to use an example in a way that falls outside the recorded consent should go to the owner, not be settled informally by whoever is drafting the response.

None of this requires a large system. A restricted spreadsheet or a simple database with access controls will do. The important assets are the consent record, the anonymisation check and the review date.

Start with ten examples

A bank with ten well-consented, accurately dated examples is more useful than three hundred unverifiable comments. The first step is to draft the short form, agree the consent wording and identify two or three policy themes where member experience would genuinely help. Then ask once, in plain language, through the channels members already use. The bank will not replace judgement, but it can replace the last-minute scramble for a credible example. For a member association, that is a practical improvement worth making in 2026.