A-level Computer Science Past Papers: How to Get Real Help

A-level computer science past papers help is some of the highest-value revision your child can do, because the two written papers reward exactly the skill past practice builds: reading and correcting code under time pressure, tracing algorithms, and explaining how a machine actually works. The core theory — data structures, algorithms and complexity, computer architecture, networks, Boolean algebra, the theory of computation — is stable from year to year, so a paper from an earlier series rehearses a skill your child will still meet this summer. Two things make A-level different from GCSE, though, and both change how you use past papers: the questions are harder and more application-heavy, and a fifth of the A-level is a standalone programming project that no past paper can rehearse at all. If you bring in a tutor to run that practice, the harder question is whether the person you are paying is any good. On Tutorwise you can see a tutor's credibility as a computed score, built from checks they cannot write for themselves, before you book rather than after the first invoice.

This guide sets out which A-level computer science past papers exist, how to use each one so it lifts the grade instead of filling time, the part of the A-level that past papers deliberately leave out, and how to judge a tutor on evidence rather than a confident profile.

Why A-level computer science past papers earn their place

In essay subjects a past paper ages quickly, because it is built around set texts that change. Computer science does not work that way. The specification is built on concepts, and those concepts are stable: converting between number bases, working through a trace table, analysing the time complexity of an algorithm, walking a binary tree, explaining the fetch-decode-execute cycle, reasoning about a hash table or a stack. These appear in some form every year, so an A-level past paper is a genuine rehearsal rather than a one-off sample.

That stability means the marginal value of doing more papers stays high. In a subject where the underlying questions recur, the sixth timed paper still teaches your child something the first did not, because it surfaces a concept they have not yet locked down — often a proof-style question on complexity, or an unfamiliar data structure, or a longer written answer on the consequences of computing that needs structure rather than recall. The limit is not the supply of useful papers; the boards publish years of them free. The limit is how honestly each paper is marked and acted on.

The board decides which papers count

This is the part families get wrong, and it matters more at A-level than at GCSE. Almost every board assesses A-level computer science through two written papers plus a non-exam assessment — the programming project. AQA (specification 7517), OCR (H446), Pearson Edexcel and WJEC Eduqas all follow that shape, but the detail differs enough that mixing boards up wastes your child's time.

The split between the two papers is board-specific. Under OCR's H446, Paper 1 is Computer Systems — architecture, data, networks, and the legal and ethical side — while Paper 2 is Algorithms and Programming, built around computational thinking and problem solving. AQA's 7517 splits differently again, and its Paper 1 is sat on screen as a practical programming exam, where your child writes and corrects real code against a preloaded skeleton, not on paper. That single fact changes how you rehearse: for an on-screen paper, reading past questions is not enough — your child has to practise at a keyboard, in the board's environment, against the clock.

The second board-specific trap is the reference language. Each board writes its algorithm and pseudocode questions in its own conventions and expects answers in them. OCR publishes an Exam Reference Language; AQA sets out its own pseudocode in a guide alongside the specification; others lean on a named programming language. A "write an algorithm" or trace-table question from one board can look almost identical to another's and still lose marks, because the conventions the examiner is looking for are not the ones your child has practised. So the first job, before downloading anything, is to confirm the exact board and specification code your child is entered for, then use only that board's papers, mark schemes and published reference language.

The part past papers cannot rehearse: the NEA project

Here is the A-level-specific point that catches families out. Unlike current GCSE computer science, which folded programming into the written papers, A-level keeps a substantial non-exam assessment — an independent programming project your child designs, builds, tests and documents over months. According to the AQA and OCR A-level computer science specifications, that project is worth 20 per cent of the A-level. No past paper touches it. You cannot revise it the night before, and a shelf of downloaded papers gives a false sense of readiness if the project is drifting.

So treat the two halves of the A-level as two different jobs. Past papers, mark schemes and examiner reports are the right tool for the written papers — the bulk of the marks, and the part that timed practice genuinely moves. The project needs something else entirely: steady progress against the mark scheme's own criteria for analysis, design, technical solution, testing and evaluation, and honest feedback on real code long before the deadline. This is exactly where a good tutor earns their fee, because a second pair of eyes catches the design flaw or the missing test evidence that quietly costs marks, and does it while there is still time to fix it. When you plan revision, plan the project separately — do not let a stack of past papers convince you the whole grade is under control.

How to use a past paper so it actually raises the grade

A downloaded paper your child reads through and nods along to changes nothing. Three habits turn a past paper into marks.

First, pair every paper with its mark scheme and its examiner report. The mark scheme shows how marks are split — at A-level the gap between a mid and a top answer is usually the working, not the final value: every pass of a trace table, the named technique, the correctly reasoned complexity, the step shown rather than assumed. The examiner report is the most under-used free resource in the subject. It tells you, in plain terms, where students across the country lost marks that series — typically on longer algorithm questions, on precise definitions, and on the discipline of showing steps rather than jumping to an answer.

Second, work under real conditions. A timed paper with no notes, marked honestly against the scheme, tells you the truth; a relaxed run-through with the answers open tells a comforting story. For an on-screen paper, "real conditions" means at a keyboard in the board's environment, not reading questions on a sofa. After marking, sort the lost marks into a short list — a definition not recalled, an algorithm mistraced, a complexity misjudged, a written answer that rambled — and choose the next paper to hit the weakest one. Timed, marked and targeted beats skimming ten papers back to back.

Third, treat the programming and algorithm questions as the priority. They are where marks move fastest with practice and where the board's conventions bite hardest. Writing out an algorithm by hand in the board's reference language, then checking it against the mark scheme, builds exactly the habit the examiner is grading. Take a common style of question: "the following code should return the largest value, but it contains an error — identify and correct it," or "complete the trace table for this algorithm." A child who has only read the topic writes the right final number and stops. The mark scheme rewards the steps: the value of each variable at each pass, the exact line where the fault sits, and a correction written in the board's own conventions. Practising that on real past papers is what separates a middling answer from a strong one.

How to judge a tutor on evidence, not a confident profile

Here is the problem with hiring help for any of this: anyone can write a persuasive bio. A profile that says "examiner" and "ten years' experience" costs nothing to type, and you usually find out whether it was true only after you have paid for a few sessions. That asymmetry — the tutor knows their real track record, you do not — is what most tutoring sites leave you to shoulder.

Tutorwise is built to close that gap. Instead of trusting a self-written summary, you see a tutor's credibility as a computed score — a number the platform works out from real signals the tutor cannot fake in their own favour. It combines verified identity and DBS checks, confirmed qualifications, the outcomes they have actually delivered, and genuine reviews from families who booked them. Delivery, meaning real teaching that earned real reviews, carries the most weight; verification and credentials sit behind it. A tutor cannot buy their way up the score, and they cannot write it themselves.

Look at how that plays out in practice. Two A-level computer science tutors both claim they can help with the OCR papers and the project. On an ordinary directory you compare two equally confident paragraphs and guess. On Tutorwise you compare two earned scores: one tutor has verified identity, a confirmed degree, and a run of recent reviews from families whose children sat A-level computer science; the other has an unverified profile and no delivery record behind the claims. The score does not tell you everything — it cannot know whether this tutor suits your child's board or teaching style — but it tells you which of the two has evidence behind the words, before any money changes hands. The platform handles the trust; you keep the judgement about fit, which you settle with two or three direct questions: does this tutor know your board, its reference language, its two papers and the project, and can you trust them with your child.

For tutors: the search is happening now

If you teach A-level computer science, families are searching for exactly this help in the run-up to the summer papers, and that is when demand peaks. Every empty slot in that window is teaching time, and income, you will not get back. The same model that reassures parents rewards you for doing the right things: completing identity and DBS verification lifts your trust signals straight away, confirming your degree strengthens the credentials evidence, and teaching well to earn honest reviews builds the delivery signal that no shortcut replaces. You cannot buy your way up Tutorwise — but a credible, complete profile is what turns a search like "A-level computer science past papers help" into a booked session with the family that would otherwise have found the tutor beside you.

Where to start

If your child is working through A-level computer science past papers, do four things this fortnight: confirm the exam board and specification code so you download the right papers and the right reference language; pair every paper with its mark scheme and examiner report; put the bulk of the written-paper time into timed algorithm and programming practice, on screen if the board sets an on-screen paper; and plan the NEA project on a separate track, because no past paper will rehearse it. If you want help running any of that, choose a tutor on evidence rather than on a confident bio. You can read more on what A-level computer science revision should actually look like, on preparing for the papers and the project, and on finding an A-level computer science tutor you can trust. If you would rather learn online, the same credibility score applies to an online computer science tutor — so you can compare like for like and decide on what really matters: does this tutor know your board and its papers, and can you trust them with your child.