What the NEA is
NEA stands for Non-Examined Assessment. At A Level the student plans, builds, tests and evaluates a substantial program for a real problem and a real or realistic user. It is marked by the school, moderated by the exam board, and worth 20% of the A Level.
Where the marks come from
OCR H446 (70 marks)
| Section | Marks |
|---|---|
| Analysis of the problem | 10 |
| Design of the solution | 15 |
| Developing the solution | 25 |
| Evaluation | 20 |
AQA 7517 (75 marks)
| Section | Marks |
|---|---|
| Analysis | 9 |
| Documented design | 12 |
| Technical solution | 42 |
| Testing | 8 |
| Evaluation | 4 |
Always check the current specification and your school's internal deadlines.
A realistic timeline
| When | Milestone |
|---|---|
| Summer term, Year 12 | Brainstorm three ideas, find a real user, check the idea is complex enough. |
| September, Year 13 | Analysis complete, with measurable success criteria. |
| October | Design complete: decomposition, algorithms, data and test plan. |
| November to January | Iterative development with evidence of each stage. |
| February | Final testing and user feedback. |
| March | Evaluation and final write-up. |
What help is allowed
Usually fine
- Discussing ideas and the problem
- Explaining the mark scheme
- Teaching programming concepts in general
- Acting as a test user
Not allowed
- Writing or fixing the project code
- Writing or editing the report
- Detailed corrections to specific parts
- Submitting AI-generated work as the student's own
Any help from outside school should be shared with the student's teacher.
Recovering a stalled project
- List what exists: report sections, code, tests and evidence.
- Compare it with the mark scheme to find the sections worth most.
- Cut scope to a version that can be finished and tested.
- Agree a weekly plan with the teacher.
- Document as you build.

