What is the Computer Science NEA?
The A-Level Computer Science NEA is a practical programming project where students solve a realistic problem or investigate an area of interest. It usually involves analysis, design, development, testing and evaluation.
AQA describes the NEA as a computing practical project. OCR lists the programming project as 70 marks and 20% of the A-Level. Exam-board details vary, so students should check their official specification and school guidance.
JCQ guidance says students are normally required to authenticate submitted NEA work and should ask their teacher if they do not understand the rules.
What students often struggle with
- Choosing a project idea that is realistic but not too simple
- Breaking the project into manageable stages
- Writing clear analysis and design documentation
- Testing properly
- Explaining technical decisions
- Managing time
- Keeping evidence organised
- Evaluating the final solution honestly
Example NEA project idea categories
These are not projects to copy. They are starting points for thinking about the type of problem a student might investigate or solve.
Revision quiz system
Could involve question banks, scoring, user accounts and progress tracking.
Complexity: moderate. Adapt it to a real learner or subject need.Booking or appointment system
Could involve calendars, validation, roles and availability rules.
Complexity: moderate to high. Base it on a real user’s workflow.Inventory management system
Could involve stock levels, searching, reports and data persistence.
Complexity: moderate. Make the scenario specific, not generic.Fitness or habit tracker
Could involve goals, logs, graphs and personalised reminders.
Complexity: moderate. Tie it to a clear user problem.Library or resource management system
Could involve loans, reservations, users and overdue item logic.
Complexity: moderate. Avoid copying a common tutorial structure.Flashcard application
Could involve spaced repetition, topic filtering and progress analysis.
Complexity: moderate. Add a real need and sensible scope.Educational game
Could involve levels, scoring, feedback and learning analytics.
Complexity: variable. Keep gameplay achievable and purposeful.Data analysis dashboard
Could involve importing data, filtering, charts and decision support.
Complexity: high. Use a meaningful dataset and user question.Small business stock or order system
Could involve customers, orders, stock updates and reports.
Complexity: high. Scope tightly around a real process.Personal finance or budgeting tool
Could involve categories, budgets, trends and warnings.
Complexity: moderate. Adapt it for a specific user’s habits.NEA planning templates
These downloadable resources are placeholders for now and will be added as separate PDFs/files later.
Project idea checker
Questions to test whether an idea is realistic, personal and complex enough.
Download placeholderClient interview questions
Prompts for gathering user requirements without leading the client.
Download placeholderAnalysis section planner
A structure for turning the problem into clear requirements.
Download placeholderSuccess criteria template
A way to write criteria that can be tested later.
Download placeholderDesign documentation checklist
A reminder of designs, diagrams and explanations students may need.
Download placeholderTesting table template
A format for recording tests, expected results and actual results.
Download placeholderEvaluation structure
Prompts for evaluating strengths, weaknesses and future improvements.
Download placeholderDevelopment log template
A simple format for tracking progress and decisions over time.
Download placeholderWhat examiners are usually looking for
Without reproducing mark schemes, strong projects usually show clear problem analysis, suitable design decisions, evidence of development, testing against success criteria, technical understanding, evaluation of strengths and weaknesses, and independence and authenticity.
What support is allowed?
I can help students understand the NEA process, plan their time, think through project scope, debug their own work, and understand relevant programming concepts. I cannot write code, produce documentation, complete assessed sections, or tell students exactly what to submit.
If anything about the rules is unclear, students should ask their teacher before acting.
Common NEA mistakes
- Choosing a project that is too big
- Choosing a project that is too simple
- Leaving documentation until the end
- Not gathering clear user requirements
- Weak testing evidence
- Screenshots without explanation
- Evaluation that only says “it works”
- Not backing up work
- Not checking exam-board guidance
How tutoring can help with NEA confidence
Tutoring can provide structure and support without taking ownership of the project. The focus is on helping students understand what they are doing, plan sensibly, debug independently and communicate their thinking clearly.
Need help understanding the A-Level Computer Science NEA?
Book a free consultation to discuss what support is appropriate and how I can help without compromising the student’s independence.