A-Level CS NEA Project Guide: From Idea to Write-Up

The Non-Exam Assessment (NEA) is the part of A-level Computer Science where marks come from your own project, not an exam room. It rewards planning, problem-solving, and clear technical communication as much as raw coding skill. This guide walks through how to choose a viable problem, structure your work, and write documentation that actually reflects the mark scheme.

Choosing a Problem Worth Solving

The biggest mistake students make is picking a project that's either too trivial (a basic calculator) or too ambitious (a full social network with real-time chat and payments). Examiners want to see a genuine problem with real users or a real use case — even if the "client" is a family member, a local club, or yourself.

Good NEA problems usually involve:

• A clear task that can be broken into smaller sub-problems
• Some form of data storage or processing (files, databases, structured data)
• Room to demonstrate algorithms: searching, sorting, validation, or custom logic
• A believable end-user who can give feedback

Avoid projects that are just wrappers around an API or a GUI with no real logic underneath — there's little to analyse or test, and that hurts your marks in the design and technical solution sections.

Structuring the Project Around the Mark Scheme

Most exam boards split the NEA into stages: analysis, design, technical solution, testing, and evaluation. Treat these as a checklist, not an afterthought written the night before submission.

Analysis should include a problem statement, research into similar existing solutions, an interview or discussion with your client, and a clear set of measurable objectives. Vague objectives like