Using Consultation Submissions to Demonstrate Policy Expertise

Show an authorized public submission and distinguish your argument, evidence and personal contribution from institutional endorsement.

A consultation submission demonstrates policy expertise when a reader can separate four things without guessing: the question you answered, the argument you advanced, the evidence you used, and the part of the work that was yours. Publication by a government department, committee or regulator shows that a response entered a public process. It does not show that the argument was accepted, that your employer endorses your interpretation, or that the recommendations changed an outcome. The practical device below is an annotation guide for one authorised submission — a companion to a CV, not a replacement for it.

What a published response can and cannot establish

A consultation response is written to a specified question, usually within a word limit and a deadline, and often published alongside submissions from organisations with opposing views. That structure is the source of its value. A reader can see how you handled a bounded question under real constraints, whether you answered what was asked, and whether your evidence carries its dates, jurisdiction and uncertainty with it.

It establishes familiarity with the consultation's subject, the ability to read a call for evidence and respond to its actual questions, and drafting suited to a policy audience. It does not establish that the analysis was independently reviewed, that a client or employer shares your view, that you could deliver the same work at project scale, or that you have commissioned or managed research. One response is one artefact. Claims about range are stronger when similar reasoning appears across separate pieces of work written for different audiences.

Formal consultation is one of several routes through which academic and technical expertise reaches policy practice; the UK Government's academic engagement toolkit describes engagement from the perspective of policy officials. It is guidance for the officials commissioning engagement, not a standard against which an individual submission is assessed, and it should not be read as evidence that any particular response influenced a decision.

The endorsement question

Submissions are frequently made on behalf of an organisation. The organisation's decision to respond is a corporate position; your drafting is a contribution to it. The two sometimes coincide and sometimes do not, and the difference should be stated rather than left for a reader to infer. A response listed in a department's evidence annex records receipt. It does not record agreement, adoption or approval, and it does not certify the author's competence.

Selecting the submission to annotate

Choose one document and annotate it properly rather than listing several at a glance.

  • Public and locatable. Prefer a response published with a stable reference or URL, so a reader can check the questions asked and the text submitted.
  • Close to the work you want considered. A narrow response on a technical standard may serve technical work better than a broad strategy response, even where the latter sounds more impressive.
  • Attributable. You can state your role without ambiguity: sole author, joint author, drafting contributor, or signatory.
  • Traceable evidence. The sources you relied on can be named, dated and located.
  • Current. Your position still holds, or you can say plainly where it has moved.

An argument you no longer hold is not a defect in a work sample. An unexplained one is. If a submission reflects a position you have since revised, record the revision in the annotation rather than quietly omitting the document.

The public-submission annotation guide

The guide records what a reader cannot see from the published text alone. One page per submission is usually enough; the fields can be adapted for a select committee response, a regulatory call for evidence or a departmental consultation.

Field What to record Why a reader needs it
Consultation and publishing body Title of the consultation, the body that ran it, the closing date, and a reference or link to the published response Lets a reader find the primary document and read the questions asked
Publication status Whether the published version is your full response, an extract, a summary, or only a list of respondents Prevents a reader assuming more was published than was
Authorship and capacity Sole or joint, named or anonymous, personal capacity or organisational response, and who signed Separates your drafting from collective sign-off
The question addressed The consultation question or questions you answered, and those you did not Shows you responded to the question asked rather than a neighbouring one
The argument One or two sentences, in your own words, stating the position taken Gives the claim before the supporting detail
Evidence and its limits Principal sources, their date and jurisdiction, and the main uncertainty or gap Makes the evidential basis and its boundaries visible
Your contribution Analysis, drafting, data work, convening, revision, or a specific annex Turns an implied contribution into a checkable one
What is not yours Institutional positions, co-author analysis, data supplied by others, secretariat editing Prevents attribution drift
Outcome and currency What the consulting body published in response, any use you can point to, and where your view has since changed Converts speculation into record and signals current judgement

The last field matters most and is the one most often left blank. "The authority's published response said eligibility would be kept under review" is a verifiable statement. "Our submission shaped the policy" is not, unless a published document says so.

A fictional annotated entry

The following example is fictional. It is used to show the format and does not describe a real consultation, organisation or person.

  • Consultation and body: "Design of a regional skills investment fund" (fictional), run by a fictional regional authority; closed 14 March 2025; response published in an online annex.
  • Publication status: full text published with the author's name, alongside several other responses.
  • Authorship and capacity: sole-authored in a personal capacity; a university research office checked factual accuracy but did not approve the argument.
  • Question addressed: question 4, on eligibility for training providers. Questions 1 to 3 were not answered.
  • Argument: eligibility should attach to provider accreditation rather than to a fixed list of qualifications, because the qualification list would date faster than the accreditation cycle.
  • Evidence and limits: published accreditation statistics for the region, 2022 to 2024, and the authority's consultation document. No primary interviews. The analysis cannot establish how many providers would apply.
  • Contribution: all drafting, the accreditation comparison, and a two-page annex.
  • Not yours: the university's separate institutional response, which took no position on question 4, and the statistics, which were collected by the authority.
  • Outcome and currency: the authority's published response stated that eligibility would be kept under review; no adoption is recorded. The author has since withdrawn an estimate of application volume as unsupported.

A reader of that entry knows what was argued, on what basis, by whom, and with what result. Nothing in it requires the reader to trust a summary.

Separating argument, evidence and position

Three checks resolve most ambiguity, and each should be answered in writing rather than assumed.

Whose words are these? If a communications team edited the text, or a director signed it, say so. Editing for house style can change emphasis, and a reader comparing the published version with your account will notice.

Whose evidence is this? Distinguish data you collected and analysed from data supplied by the consulting body, a co-author or a partner organisation. Where the submission reproduces a dataset you did not compile, the annotation should say which parts you verified.

Whose position is this? An institutional response is a corporate decision taken through whatever internal process the organisation uses. A personal submission is not an institutional statement, even when the author's affiliation is printed at the top. Institutional permissions and sign-off arrangements are individual matters to check in your own circumstances; there is no general framework that certifies an individual's authority to speak for an organisation.

Presenting the annotation

Keep the CV line short: the consultation, the body, the date, your role, and a pointer to the annotated entry or published text. Reserve the detail for the annotation or work-sample page. Link to the published response where a stable public link exists; do not paste the full text. Where a response was never published, describe the question, the date, the body consulted, your argument and your role, and keep any unpublished text out unless you hold permission to circulate it.

Do not describe a consultation response as peer-reviewed, as a commissioned report, or as independent research. It is a submission to a public process, and its standing depends on that process. Descriptions of work published by a firm, including the anonymised engagement notes on Policy Expert Network's About page, are first-party accounts rather than independent audits; the same caution applies to how you present your own submission.

Limitations to state plainly

Consultation responses have no methods section, no peer review and a word limit that often forces compression. Publication practice varies: some bodies publish every response, some publish summaries, some publish nothing beyond a list of respondents. Policy questions close, and a response that was timely in 2024 may read as historical in 2027. Joint submissions blur contribution until someone resolves it. And a single response cannot show range; two or three addressing different questions can show more, provided each is annotated with the same discipline.

Frequently asked questions

Can I show a submission made in a previous role?

Often, if it is public and you can describe your role accurately. Check any confidentiality or employment terms that applied at the time, and state whether the response was institutional and who signed it. Where the work was done for an employer, the position expressed may not be yours.

What if the response was never published?

Describe it without quoting: the question, date, consulting body, your argument, your evidence and your role. Attach the text only where you hold permission to share it, and do not characterise an unpublished submission as public evidence.

Next step

If you are assessing participation in an expert network, an annotated submission is a useful supplement to a CV because it shows reasoning under a real constraint. Policy Expert Network's participation guidance is at /experts/. The current application form at /experts/apply/ asks for your name, contact email, a CV, acknowledgement of the terms and consent to processing; it forwards the CV to the applications mailbox and does not provide email verification, online status or automatic review. The Applicant Privacy Notice explains how that information is handled. Submitting an application or an annotated work sample does not create an assignment, and no listing or application guarantees work.

No advertising or analytics cookies are used. Your preference and application receipt may be stored in this browser; CV files are not.

Read the storage explanation