The most useful ICT revision is built from your own mistakes. Record each one, name its cause, and come back with a fresh task a few days later. Re-reading a full set of notes spreads effort across topics you already handle.
This page gives a method you can start today, a worked log, and a way to keep your revision inside the current scope.
Why does ICT revision go wrong?
Two habits cause most of the trouble.
First, students revise by watching a tutorial again. The clicks look familiar, so the topic feels known. A blank task sheet asks a different question: which choice comes first, and how will I check it?
Second, practice happens on one software version while the exam centre uses another. The skill transfers, but only if you have learned it as a task and not as a menu path. The module on practical workflow and software versions trains this.
How do I build a mistake log?
Use one row per mistake, with four columns: the task, what went wrong, the cause type and the next action. Sort causes into four types so patterns show up.
| Cause type | What it looks like |
|---|---|
| Concept gap | You cannot explain why a choice fits the scenario |
| Workflow slip | The steps were right but in the wrong order |
| Unchecked output | The file was never reopened or tested |
| Version mismatch | The feature was in a different place or had another name |
The mistake log and retest queue keeps entries on your own device and schedules a fresh problem for each error type. Nothing is sent anywhere.
Worked example: four log entries
Here is a log from an original practice week. Each entry has a cause and a next action.
| Task | What went wrong | Cause | Next action |
|---|---|---|---|
| Sales sheet, tax column | Tax column showed 0 from row 3 | Workflow slip: relative reference | Redo with a locked rate cell, see spreadsheet formulas |
| Flyer export | Table was cut at the right edge | Unchecked output | Check print preview before export |
| Theory: validation | Wrote “checks it is correct” | Concept gap | Write range, type and presence checks with one example each |
| Database import | Price sorted as 10, 100, 9 | Concept gap | Compare field types, see database structure and validation |
Two entries share the cause “unchecked output” in spirit: the file looked right on screen and was never tested. That is the first repeated habit to fix. The next retest should be a fresh document task with a built-in trap, such as a table slightly wider than the text area. Reusing the same file would only test memory.
What should a revision week look like?
A sensible week has three kinds of session.
- Retrieval: close the notes and write terms with a meaning and a scenario. Use the terminology guide to check confusing pairs.
- Practical repeat: redo one task from your log on a new file, then reopen and test the result.
- Mixed practice: one task that joins theory and practice, from the original practice section.
How do I keep revision inside the current scope?
Write your topic list from the Cambridge page for your exam year, not from an old book. Anything that is not there goes on a “check” list for your teacher. The assessment guide shows what to confirm, and the study route shows how to share your time.
When is a teacher worth adding?
Consider it when the same cause type returns after you have retested twice, or when you cannot tell whether a mistake is a concept gap or a slip. A teacher watching the task can separate them quickly. Online one-to-one ICT tuition starts with a paid one-hour trial, from RM80 at the assigned teacher’s confirmed rate.