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 approved for delivery, with starts from 10 December 2025. Earlier cohorts may use earlier versions. Confirm the applicable assessment plan rather than transferring requirements between versions.
View the official standard and assessment plan ↗What this occupation demonstrates
For apprentices who turn requirements into maintainable, tested software. The occupational context can include web, mobile and other applications across many sectors. Strong preparation helps apprentices explain the development decisions behind their code: how they understood the requirement, designed the solution, managed changes, tested behaviour and considered security. Providers should encourage a clear account of personal responsibility within the wider team. A finished feature matters, but so does the reasoning that makes it supportable and appropriate for its users.
Providers preparing application, web and software developers working in product teams, internal development departments and consultancy businesses.
- Translate a requirement into a reasoned, maintainable implementation.
- Explain test choices, defects discovered and how changes were verified.
- Demonstrate secure handling of code, data and collaborative development work.
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.
- Maintain a sanitised development story linking requirement, design, implementation, review and testing. Screenshots of a finished interface should support evidence of the process rather than replace it.
- Practise explaining a difficult debugging decision and a trade-off. Ask what the apprentice rejected, why and how they checked that the chosen approach met the need.
- Agree the treatment of source code and intellectual property before sharing evidence. Use controlled examples and remove keys, credentials, personal data and confidential client material.
Plan a useful handover.
Compare organisations using the development practices apprentices actually encounter: product teams, internal systems and consultancy work produce different evidence constraints. Supply cohort versions, common languages and environments, remote-working arrangements and employer rules for source disclosure. Ask how the service explores requirements, design, implementation, testing, security and collaboration as one development story. The provider owns curriculum and version alignment; the employer engineering owner approves a safe evidence route; a named coordinator resolves access or intellectual-property issues before they delay readiness.
A realistic evidence conversation
Illustrative, not a prescribed requirement: an apprentice adds validation to a customer workflow after tracing an intermittent defect. The pack links the requirement, rejected approaches, a focused code extract or equivalent explanation, tests that reproduce the defect, review feedback, deployment control and verification. Repository history supports personal contribution but no keys, customer records or proprietary source leave the employer without approval. Ask a prospective partner how it would handle a restricted-code employer, distinguish team review from apprentice judgement and recover if the chosen feature is cancelled.
Handover checks
- Programme owner verifies version-specific requirements and provides varied development opportunities.
- Employer engineering owner approves code, intellectual-property and personal-contribution evidence rules.
- Readiness owner confirms a complete requirement-to-verification narrative before any submission.
Questions to ask before buying
- How can an apprentice evidence software decisions when source code cannot leave the employer?
- How do you verify individual contribution in pair programming and shared repositories?
- What checks prevent an earlier cohort's assessment assumptions being applied to version 1.2?
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. A feature meets the written specification but users still cannot complete their task. What would you do?
Explore a response structure
Investigate the workflow and user feedback before proposing a fix. Explain whether the gap concerns the requirement, the implementation or the way it was tested. Set out an acceptance check that reflects the user’s actual goal.
2. How would you investigate a defect that appears only for some users?
Explore a response structure
Compare environments, permissions, inputs and execution paths. Explain how you would reproduce the issue safely, gather useful diagnostic information and avoid exposing personal data. Describe how you would test the fix and relevant neighbouring behaviour.
3. When would you refactor working code?
Explore a response structure
Explain the maintenance problem, the risk of change and a practical scope. Discuss tests that protect existing behaviour and how you would review the result. Acknowledge when a small targeted fix may be more proportionate than a broad redesign.
Questions about this standard
Are public code repositories required for preparation?
Do not publish employer source code or client information for convenience. Agree an authorised way to demonstrate the work. A private, sanitised or otherwise controlled example may be appropriate depending on the assessment requirements and employer permission.
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: Software Developer ↗660 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.