Presenting Evidence Clearly in Cambridge 0417
// A practical guide to file naming, evidence capture and formatting in Cambridge 0417.
By Abdurrahman Tolay ·
Cambridge IGCSE ICT (0417) practical preparation involves more than software familiarity. Students also need to present clear evidence of their work and adapt to the task in front of them. Always check the current official syllabus and published marking guidance.
In classroom preparation, I ask students to check whether their submitted files and evidence show the required work clearly. An unreadable formula or missing screenshot makes that work harder to assess.
Make the evidence of your work easy to read and verify.
Beyond memorising definitions
Definitions matter, but applying them to unfamiliar scenarios matters too. Use the current syllabus and past papers to see how questions ask for explanations and choices in context.
A useful practice question might ask which technology best fits a stated constraint such as cost, bandwidth or security. Discuss why plausible alternatives are less suitable.
What this changes in the classroom
- Distractor analysis becomes a teaching activity in its own right. Students should be able to say why the other three options fail, not just why theirs succeeds.
- Definitions must be taught with use cases attached. A definition without an application context is now nearly worthless under this format.
- Timing matters. Practice under timed conditions and leave space to review evidence.
A student should be able to explain why a solution fits the scenario, not only define its parts.
Strategic Topic Variety in Practice Exams
Repeated practice with the same question order can encourage pattern memorisation. Vary topic order while keeping practice aligned with the current syllabus.
How to build a resilient mock
One practical approach:
- Mix questions from different syllabus areas rather than repeating a fixed sequence.
- Rotate the substitution each cycle so that no two mocks in a term share the same topic distribution.
- Include less familiar topics where they are covered by the current syllabus.
- Occasionally reverse the paper order entirely so candidates practise beginning cold on an unfamiliar topic.
The goal is not to make practice harder for its own sake. Topic variety helps students apply what they know without relying on question order.
Evidence Document Mastery
In practical work, students should check both the completed task and the evidence they submit.
Auto-fit every column before printing formulas
Before submitting a formula printout, adjust column widths so cells do not display as ##### and formula text remains visible. Check current published assessment guidance for evidence requirements.
The sequence should be automatic: switch to formula view, auto-fit all column widths, set the page to landscape, fit to one page wide, confirm that every formula is visible end to end, then print or export.
Candidate details on every single printed page
Not the first page. Not most pages. Every page. Name, candidate number, and centre number belong in the header or footer, inserted as a document-level header so that they propagate automatically to any page the document expands to. Students who type their details manually into the top of a sheet lose them the moment content reflows onto a second page.
The rest of the evidence checklist
- Filenames match the specification character for character, including capitalisation and underscores.
- Screenshots show the required view, not the result. A query design grid is not the same as a query output.
- Screenshots are legible at print size; avoid a shrunk full-desktop capture.
- No row or column is hidden or truncated in printed database or spreadsheet evidence.
- Page orientation and margins follow the stated instruction literally.
Reserve the final ten minutes of every practical paper for evidence checking only. Not for improving work. For proving it.
Theory Precision
Precise technical vocabulary helps communicate an answer clearly. Review the current published mark schemes for how terminology is used.
- Instead of "a hacker got in", describe unauthorised access and its cause.
- Instead of "someone stole the data in transit", explain data interception.
- "The computer got a virus" is weak. Malware infection, with the specific type named, is stronger.
- Distinguish validation, which tests data against rules, from verification, which checks accurate entry.
- Instead of "fake email", describe phishing and the impersonation involved.
Command words still decide structure
- State / Identify: one precise fact per mark, no elaboration.
- Describe: the feature plus a detail that demonstrates understanding.
- Explain: a reason joined to a consequence. The word "because" usually belongs in the sentence.
- Compare: both sides within the same sentence, using a comparative connective.
- Evaluate: advantages, limitations, and a justified conclusion tied to the scenario given.
Match the depth of your response to the command word and available marks.
What Preparation Should Look Like in 2026
Practise under submission conditions as well as task conditions. Build a habit of checking the evidence before submitting practical work.
Combine scenario-driven questions with practical tasks and feedback. Students should learn both the software and how to present their work clearly.
Show your work clearly and check it against the task instructions.