Proofing, validation and verification
Reduce errors with automated tools and deliberate visual checks while choosing the right validation and verification method.
Exam scope and assessment notes
Cambridge IGCSE Information and Communication Technology 0983, for exams in 2026, 2027 and 2028. Examples, datasets and practice are original StudyForA material; they are not Cambridge questions, source files, mark schemes or grades. Practical lessons teach transferable operations, but learners must perform them in locally available office and web-authoring software and inspect their own files. This site does not reproduce a Cambridge practical examination or award an official grade. The separate 2029 syllabus is not mapped here. Cambridge states that IGCSE 0983 has the same subject content as IGCSE 0417, with 9–1 grading. This StudyForA pathway maps the 2026–2028 syllabus only. This 9–1 graded qualification is available only in a limited number of administrative zones. Confirm that your centre can enter you for this code and exam series with Cambridge International. Cambridge has published a separate syllabus for 2029. StudyForA has not reconciled that version yet; this page supports exams in 2026, 2027 and 2028 only.
Before you begin
- No previous ICT course is assumed. Read each scenario carefully and justify a tool or method by connecting it to the task, user and constraints.
Work on paper. Try each question before revealing help, and explain why your method works.
Quick readiness check
Which method checks that a typed address matches the user's original form?
What you will learn
- Use spelling and grammar tools, visual proofing and validation to reduce errors in produced work.
- Recognise transposed numbers, spelling, character spacing, case, line spacing, blank pages, widows/orphans and style inconsistencies.
- Explain validation checks and distinguish validation from verification, including visual check and double data entry.
Automated proofing helps but needs judgement
Spell-check and grammar-check tools suggest corrections; they can miss correctly spelled wrong words or propose an unsuitable change. Read the final work in context. Check transposed digits, spacing, case, line breaks, blank pages, widows/orphans and consistent style application; inspect tables and lists so they are not split awkwardly.
Validation restricts what can be entered: presence, range, character, length, type, format or check-digit checks. Each tests a different rule. A valid date format can still be the wrong date, so validation does not prove accuracy.
Verification compares with a source
Verification checks that data matches the original source, for example by visual checking or entering data twice and comparing the copies. Validation checks whether data is acceptable under defined rules. Both can be used together: a plausible but mistyped value may pass a range check and still fail verification.
After an automated edit or export, inspect the actual output. Proofread on screen and in print preview where pagination matters; correct errors and recheck affected pages rather than assuming a tool has fixed every issue.
Sources for this lesson
Pause and explain
A product code must contain exactly eight characters and match a printed source. What checks are appropriate?
Worked example
A birth-date field accepts 31/02/2010. Explain which checks could reject it and how the entered date could be verified.
Show the worked solution
- A format check can confirm the required date pattern.
- A validity/calendar check can reject an impossible date; a range check may limit years.
- Compare the value with the source record to verify the actual date.
Answer A format check can enforce the required date pattern, and a calendar/date validation rule should reject 31 February as impossible. A permitted year range may reject an out-of-range date. Verification still requires comparing the entered date with the source record, because a valid date can be the wrong person's date.
Try a topic test
Choose Easy, Normal or Difficult. Save your answers and open worked review after finishing.
Test this topic →From guided practice to a new situation
Write your answer and reasoning first. Use a hint only if you are stuck. The model solution is for self-checking; your written work is not automatically marked.
Choose a validation check for (a) an age from 11 to 18, (b) a required field, (c) a five-character code and (d) a date in DD/MM/YYYY format.
Give me a hint
Match the rule to the property being checked.
Compare my reasoning
- Allowed numeric boundaries need a range check.
- Required input needs a presence check; exact size needs a length check.
- A specified date pattern needs a format check, plus a valid-date check where available.
(a) Range check; (b) presence check; (c) length check; (d) format check plus a valid-calendar check. These checks enforce rules but do not establish that the values are true or belong to the correct person.
Look for these in your work
- Matches rules with check types
- States the limit of validation
A proofing tool changes 'public access' to 'pubic access'. How should a learner review automated corrections?
Give me a hint
Read for meaning as well as spelling.
Compare my reasoning
- Inspect the changed phrase in its sentence.
- Compare it with the original meaning and task instructions.
- Undo unsuitable suggestions and proofread the rest manually.
The learner should notice that the correction changes meaning, undo it and restore 'public access'. Automated suggestions need contextual review because software can select a correctly spelled but incorrect word; proofread the entire document for other changes.
Look for these in your work
- Uses context to reject a bad suggestion
- Does not rely only on the tool
A 12-page report gains a blank page after a style change. Give a focused proofing sequence before export.
Give me a hint
Check page and section breaks, pagination and the output preview.
Compare my reasoning
- Review paragraph marks and page/section breaks near the blank page.
- Check headers, tables, lists and widows/orphans after removing or adjusting the break.
- Preview the exported file and confirm all pages remain present and readable.
Inspect formatting marks and remove or correct an unintended page or section break. Then review pagination, tables, lists, headers and widows/orphans because removing a break can shift content. Export again and inspect the full preview before submitting.
Look for these in your work
- Locates likely layout causes
- Rechecks the entire output
Common mistakes
- Equating validation with correct data
- Accepting every spell-check suggestion
- Checking only the first page after a document-wide style change
What can you explain now?
How do validation and verification differ?
Compare with the explanation
Validation checks data against rules; verification checks that it matches the original source.
A value can be valid in form but still be inaccurate, so validation and verification solve different problems.
After trying it yourself, choose your next review. This is your self-assessment.
Your review choice appears on Today. Sign in to sync it across devices.
Make it stick
Give an example of a valid but inaccurate value, then name one validation and one verification method.
If you needed the solution, close it and solve the problem again from a blank page. A correct answer is stronger when you can explain the reason for each step.