Independent NHS careers guidance.

NHS Information Analyst Supporting Statement: Evidence and Example

Map analyst criteria to technical, data-quality and communication evidence, with an annotated fictional non-patient project extract.

Written by NHS Careers Guidance TeamPublished 22 October 2026Last reviewed 22 October 2026
Report a correction

Applies to: UK-wide

Make the analytical evidence easy to find

An NHS information analyst supporting statement should show how you turn a question into a dependable result. It needs evidence of defining the work, checking data, using relevant tools and explaining limitations. A list of software or a claim to be 'passionate about data' cannot establish those capabilities on its own.

Use the actual person specification and application instructions. Identify whether the post expects a developing analyst, an established reporting practitioner or someone leading specialist work. Required qualifications, accepted experience alternatives and technical tools can differ. An application for a job is also distinct from an application to an apprenticeship or course.

All examples in this guide are original and fictional. The project uses synthetic office-supply records, not patient or staff data. Use your own truthful evidence, protect confidential information and follow the employer's limit and instructions on writing assistance. You should be able to discuss every claim beyond the wording of your statement.

Separate essential criteria from a desirable tool list

Copy each essential requirement into a private planner. Record your qualification or experience evidence directly, then identify examples of your work. Keep desirable criteria separate. If an employer accepts 'Power BI or similar', explain the relevant platform and tasks accurately; if the specification requires prior SQL work, do not replace that with an unrelated course certificate.

A closed Newcastle Hospitals information analyst advert reviewed for this guide specified qualification or experience alternatives and required previous SQL and Power BI or similar work. It listed R scripting as desirable. This illustrates the need to read the actual distinction, rather than declare every NHS analyst must know all three.

If an alternative experience route is unclear, ask the named contact a focused question. 'Equivalent experience' does not mean any period of employment, and a degree does not automatically establish the practical skills named elsewhere. Be precise about the level and nature of the evidence you offer.

Plan a criterion-to-evidence map

A planning table helps you allocate space. For each requirement, choose an event or output that shows your own contribution and the checks behind it. One strong example may address several connected criteria, but make those connections explicit. Do not expect a reader to infer your stakeholder skills merely because a dashboard existed.

Criterion to checkEvidence to selectAvoid
Qualification or experience routeExact award or relevant experience accepted by the wordingInventing equivalence
Technical toolTask, transformation and checks you completedNaming software without evidence
Data qualityA defined risk, check and correctionAssuming plausible totals prove correctness
CommunicationDecision, audience and limitation explainedClaiming a chart caused improvement
Organisation and learningAgreed priorities, review and change in practiceUnsupported productivity percentages

You can use short headings if the application allows, or organise connected paragraphs around related criteria. Give essential qualification and technical evidence where requested rather than burying it in a closing sentence. Remove the planning table from the actual submission unless the employer welcomes that format.

Annotated fictional project extract

This fictional early-career applicant completed a self-directed synthetic project. The extract demonstrates reasoning and learning, not employment in an NHS reporting service. It would only be appropriate where the vacancy accepts that kind of evidence, and cannot replace a required period of specialist work.

Fictional extract using a wholly synthetic non-patient project

I developed a self-directed project using invented office-supply orders and deliveries to practise producing reliable analytical information. I defined an order separately from a delivery, documented the promised-date measure and checked for missing dates before calculating a late-delivery proportion.

My first join repeated some order values because one order could have several delivery rows. I identified the problem by comparing row counts and reconciling totals before and after the join. I corrected the method to match the question, tested it on a small set of known fictional cases and recorded the assumptions so another reader could follow them. I did not remove repeated rows merely to make the total look plausible.

I produced a simple chart and a short explanation showing both the count and denominator, including the limitation created by missing promised dates. Feedback from a study peer helped me put the main finding before the technical detail. This demonstrates my developing analysis, checking and communication skills. It is a personal practice project, not NHS reporting experience, and I would still need to learn the service's sources, definitions and review arrangements.

  1. Context: the dataset is wholly invented and contains no patient or staff records.
  2. Technical evidence: the applicant identifies a specific join problem and reconciles the result.
  3. Judgement: the method follows the question rather than a preferred total.
  4. Boundary: the extract does not recast a personal portfolio as live NHS reporting responsibility.

The extract is useful because the reader can identify the question, definition, check, corrected error and output. It does not claim that a personal project improved a real service. Your own example should preserve the same distinction between demonstrating a skill and holding responsibility for live reporting.

Explain technical work through decisions

For a tool criterion, state what you used and what you did with it. For SQL, relevant evidence might concern selecting the right records, joining tables at an appropriate level and reconciling the result. For a spreadsheet or business intelligence platform, describe the transformation, calculation or presentation and how you verified it. Keep terms you can explain plainly at interview.

Separate a guided exercise from work you designed yourself. If a colleague supplied a query or model, explain what you contributed instead of claiming the whole output. If you worked as part of a reporting team, identify the source, definition, checking or communication responsibility you actually held. A fair account of shared work is more credible than overstated ownership.

Where a number appears in your statement, be able to explain its basis. Do not invent a percentage improvement, time saving or accuracy score to make an example sound stronger. A reproducible process, an identified discrepancy or a stakeholder clarification can be a valuable supported outcome.

Show quality before presentation

A quality paragraph should explain what could have gone wrong and how you checked it. Ask yourself: what does one row represent, which dates define the period, are keys unique, what is missing and what total should reconcile? Then describe the checks relevant to your actual task. A long checklist with no connection to the example is less useful than a clear account of one important risk.

NHS England's data quality material places assurance across collection, storage, sharing and use. Its provider framework has an organisational purpose in England. Your application can show that you understand this responsibility without claiming that reading a framework certifies your work or authorises access to confidential information.

If you found an error, explain the action, appropriate review and correction. Include how you communicated any effect on a shared result and what changed in subsequent practice. Do not make the original error disappear from your story if its handling is the evidence of your judgement.

Demonstrate communication and useful interpretation

Select an example where someone needed an answer rather than another chart. Explain how you clarified their decision, adapted the explanation and checked whether the output met the need. In a fictional supplies analysis, distinguishing a number of late orders from a late-order rate would show why definitions and denominators matter. Keep the example explicitly synthetic if using practice work.

Explain limitations alongside findings. A changed definition, incomplete period or missing field can affect a comparison. State what the data supports, what remains uncertain and what next check would help. Do not turn association into a causal claim or suggest a dashboard alone delivered an operational improvement.

For an experienced post, show proportionate responsibility for review, maintenance or stakeholder decisions. If leadership is required, explain how you allocated work, supported colleagues or agreed priorities. Do not assume seniority is established merely by naming a large dataset.

Address NHS experience honestly

If you have NHS experience, explain the relevant context without disclosing confidential material. Identify the definitions, reporting duties or communication processes you actually used. Experience in one organisation does not mean every service uses the same systems or national arrangements.

If you are applying from another sector or study, name that setting. Transferable analysis, quality checks and communication can be valuable where the criteria allow them. Acknowledge the service knowledge you would need to develop. Do not relabel a synthetic portfolio as an NHS project, or describe familiarity with public information as authorised use of an internal system.

The NHSScotland profile describes a varied career and education pathway. It is context for career exploration, not a replacement for the essential qualifications or experience in your particular vacancy. Preserve the employer's actual wording throughout your application planning.

Check the finished statement against the role

Read every essential criterion and locate its evidence in your draft or the relevant form field. Check the employer name, tool claims, qualification status and employment dates. Remove repeated adjectives, unsupported impact numbers and statements that confuse awareness with experience. Confirm that examples are yours and that any portfolio content is suitable to share.

A brief closing can connect your evidence with the service's work and your development needs. Keep it specific rather than promise to transform reporting before understanding its sources. Save the submitted version and use the partner interview page to practise explaining the method, checks and limits behind each paragraph. The career guide helps you compare entry routes if the eligibility review reveals a more suitable next step.

Frequently asked questions

Only where the specification permits that evidence. Present it as a personal project and describe its strengths and limits. It does not automatically meet a required period of specialist reporting experience.

State only the tools and tasks you can evidence. Explain accepted similar-platform experience honestly and keep awareness, guided practice and independent working experience distinct.

Use a figure only if it is supported and you can explain its basis. A corrected method, reproducible check or clarified requirement is useful evidence without inventing impact.

Was this page helpful?

Your feedback helps us improve our guidance.

Report a problem with this page

NHS Recruitment Starter Kit with printable application evidence and interview worksheets.

Your free preparation workbook

Give your next NHS application a stronger start.

Ready-made worksheets to organise your evidence, shape your supporting statement and practise interview answers.

  • Turn the person specification into a clear plan
  • Prepare stronger examples from your experience
  • Know what to work on next

Email me the free starter kit

Tell us where you want to go next. Get the workbook, then choose whether you would also like relevant careers guidance and membership offers.

Choose a career area first.

Choose a pay band only if it applies to your role. Medical careers have their own grades.

Get your NHS Starter Kit now, then receive practical application and interview tips tailored to your role, plus NHS Recruitment Vault offers. Choose how often we email you. Unsubscribe at any time.

The free starter kit is available with either option.

We use the details you provide to deliver your workbook and, only if you choose them, relevant careers emails. Intelligent HQ Ltd. Suite 4, 2 Mount Sion, Tunbridge Wells, Kent, TN1 1UE. Privacy information.

Your cookie choices

We use essential cookies to keep the website working. With your permission, we also use Google Analytics to understand visits to our public guides, starter-kit requests and verified membership purchases. You can use the website with analytics switched off and change your choice at any time.

Read our cookie policy