Download free Computer Science H046 past papers PDFs, mark schemes, examiner reports, grade thresholds, syllabus and specimen papers. Open the latest session first, then work backwards through older years.
Latest session
Coverage
Folders
Files
Open any session to view question papers, mark schemes, examiner reports, inserts, transcripts and grade thresholds where available.
7 files
7 files
Check the official syllabus, specimen papers and supporting documents before you begin timed practice.
1 files
2 files
Upgrade from free AS Level Computer Science past papers into solved papers, topical practice, predicted papers, notes and other premium study resources for the same subject.
Continue with nearby AS Level subjects or the same subject across another qualification level.
Start with recent material, mark it carefully, and move into focused follow-up only where marks are still being lost.
Begin with newer pseudocode questions, theory questions, trace tables, and full past papers so the first past papers reflect current wording, paper balance, and examiner expectations.
Review technical terminology, logic steps, tracing accuracy, and method clarity rather than looking only at the final score.
Use the pattern in your past papers to identify whether loose terminology, skipped logic, or weak trace-table control is the main mark-loss area.
Use another recent paper to check whether the same weakness still appears once the repair work is done.
Computer Science and IT past papers reward exact terms, not approximate everyday language.
Past papers show whether students can follow algorithms, variables, and program flow step by step.
Use mark schemes to check whether systems, networks, data, or security concepts are being applied properly.
Full papers matter because command words and layered explanations still decide many marks.
Computer Science and IT past papers are especially useful because they combine short factual recall with longer algorithmic or systems explanations. Many marks are lost when a student knows the topic but cannot express the method or trace it cleanly.
The most productive review cycle is to finish a recent paper, mark the logic and terminology carefully, and then return to another past paper to check whether those same coding, tracing, or systems weaknesses still appear.
Start with the newest pseudocode questions, theory questions, trace tables, and full past papers first, then work backwards once the latest past papers feel more controlled under time pressure.
Use the mark scheme and examiner report together to review technical terminology, logic steps, tracing accuracy, and method clarity. That review is where the real improvement usually starts.
List the marks lost across the paper, decide whether loose terminology, skipped logic, or weak trace-table control was the main problem, and repair that issue before the next full past paper.
Yes. After the latest past papers are complete, older past papers are still useful for repetition, wider coverage, and testing whether the same mistakes keep repeating.
Use these links to continue with the same subject, qualification level, or a supporting study tool.
Use flash cards for terminology, syntax patterns, algorithm steps, and systems definitions before the next full past paper.
Open linkReturn to the level overview if you are rotating across several subjects in the same qualification.
Open linkUse notes when a weak topic needs rebuilding before the next paper cycle.
Open link