Business Analyst

Business Analyst.
Level 4 assessment.

For apprentices who help organisations understand a problem before committing to a change. Business analysts examine how work happens, listen to different stakeholders, clarify requirements and evaluate options.

ST0117Level 4Planned assessment
ST0117 · Level 4Business Analyst preparation focusDigital Leadership · Planned assessment
  1. 01
    Investigate a business problem and distinguish symptoms from underlying needs.Use authentic work to explain decisions and individual contribution.
  2. 02
    Develop traceable requirements through appropriate stakeholder engagement.Use authentic work to explain decisions and individual contribution.
  3. 03
    Compare options and explain benefits, constraints, risks and success measures.Use authentic work to explain decisions and individual contribution.

Illustrative preparation focus from this guide, not an assessment method sequence or official rubric. Confirm the applicable registered version.

Confirm the route before you plan.

Planned portfolio only. Avenor’s approved scope, applicable standard version, assessor capacity, fees and service dates must be confirmed before booking. The standard’s Skills England approval is not approval of Avenor.

Checked 19 October 2026: version 1.2 is available for starts through 12 April 2027. A revised standard and assessment plan are scheduled from 13 April 2027. Assessment planning must follow the apprentice’s registered version.

View the official standard and assessment plan ↗

What this occupation demonstrates

For apprentices who help organisations understand a problem before committing to a change. Business analysts examine how work happens, listen to different stakeholders, clarify requirements and evaluate options. In digital projects, this provides the connection between business objectives and the systems or processes that support them. Useful preparation shows investigation and judgement, not just the production of documents. Providers should help apprentices explain why a requirement mattered, how disagreement was handled and how the proposed change would be judged after implementation.

Providers supporting analysts involved in systems change, process improvement, digital transformation and service redesign.

  • Investigate a business problem and distinguish symptoms from underlying needs.
  • Develop traceable requirements through appropriate stakeholder engagement.
  • Compare options and explain benefits, constraints, risks and success measures.

Prepare for a fair assessment

Use the applicable plan as your starting point. The following are preparation prompts, rather than additional gateway requirements or a substitute for the assessment specification.

  1. Keep an example of a requirement changing through investigation. Show the original assumption, the evidence gathered and the effect on scope or priorities.
  2. Build a clear account of stakeholder engagement. Include different perspectives, unresolved concerns and the reasoning behind agreed decisions, rather than only final approval.
  3. Practise explaining how a model or document helped someone make a decision. A process map should reveal something meaningful about the work rather than exist only as a diagram.
Provider buying guide

Plan a useful handover.

Buy this route around investigation and decision quality, not a catalogue of document templates. Share the types of change apprentices encounter, the stakeholder access employers can provide and whether work is product, process or service focused. Ask how the organisation tests traceability from problem to requirement and from requirement to proposed benefit, including situations where stakeholders disagree. The provider should own version mapping and readiness; employers should identify appropriate sponsors; an evidence owner should ensure commercial material can be used safely.

A realistic evidence conversation

Illustrative, not a prescribed requirement: a team requests a new reporting feature, but interviews reveal inconsistent source processes are the underlying problem. The apprentice records the initial request, stakeholder perspectives, an as-is model, prioritised requirements, options considered, unresolved assumptions and agreed measures of success. A sponsor verifies the apprentice's role and approves a sanitised pack. Use this example to ask a prospective partner how it would examine judgement and traceability, accommodate confidential transformation work and avoid treating the existence of a process map as proof of competence.

Handover checks

  1. Provider lead confirms the registered version and maps learning to investigation, requirements and evaluation.
  2. Employer sponsor identifies change work with genuine stakeholder access and a bounded apprentice role.
  3. Evidence owner checks traceability, contribution statements and safe redaction before submission.

Questions to ask before buying

  • How do you explore stakeholder conflict and changing requirements without expecting one fixed template?
  • What evidence can substitute when an employer cannot release commercially sensitive change documents?
  • How will you communicate the April 2027 transition without moving existing learners to the wrong plan?
Original preparation material

Think it through.
Explain your decisions.

These are original learning prompts. They are not live assessment questions, an official mock paper or a prediction of your result.

1. An employer asks for a new app because staff are making too many errors. What would you investigate first?

Explore a response structure

Explore the process, information quality, incentives, training and existing tools before assuming software is the answer. Ask what counts as an error and how often it occurs. Explain how you would establish an objective baseline.

2. Two influential stakeholders want incompatible requirements. How would you move forward?

Explore a response structure

Clarify the underlying needs and constraints, make the conflict visible and identify decision authority. Consider options and trade-offs using agreed criteria. Record the decision and its rationale so the team does not repeatedly reopen the same disagreement.

3. How would you know that a process improvement had delivered its expected benefit?

Explore a response structure

Define a measure, baseline, owner and review period before implementation. Consider side effects such as extra workload elsewhere. Explain how you would distinguish a realised benefit from a favourable assumption in the original business case.

Open practice studio

Questions about this standard

Does this guide cover general business administration?

It focuses on the Business Analyst standard in the Digital route. The appropriate standard depends on the actual occupation, including the level of investigation, requirements work and change analysis expected from the apprentice.

Which assessment methods apply?

Use the published assessment plan for the apprentice’s registered version and option. Methods, timings, gateway documents and grading rules can differ between versions. These original practice prompts are learning resources, not live assessment questions or a prediction of an assessment outcome.

Can we book with Avenor?

This standard is in Avenor’s planned portfolio. Ask us to confirm our approved scope, the applicable version, assessor capacity, fees and dates before making a booking. Publication of this guide does not establish Avenor approval.

Sources and review

Guide updated 20 October 2026; official source reviewed 20 October 2026. Standard titles, versions and requirements can change. Always check the linked official record for the apprentice’s start date.

Skills England: Business Analyst ↗

1,930 starts in 2023/24, published in the ICT-related apprenticeship data. Historic starts inform our portfolio; they do not establish today’s demand or our availability.