Mail merge
Learn the core concepts and decision-making in Cambridge 9626 Topic 18, then practise recall, application and transfer with fictional scenarios.
Section Paper 4 · Advanced Practical · 2 hours 30 minutes · 90 marks · 25% A Level
Exam scope and assessment notes
This is original StudyForA teaching and fictional practice based on Cambridge syllabus outcomes, not copied syllabus text, an official question, a required software brand or a Cambridge mark scheme. Practical software tasks here are planning and reasoning exercises; StudyForA does not inspect files created in spreadsheet, database, graphics, audio/video or animation software, simulate the practical exam environment, award official marks or predict a grade. Follow the software and file-format requirements issued by your centre for your exam year.
Before you begin
- Check whether your route is AS Level (Topics 1–11) or full A Level (Topics 1–21).
Work on paper. Try each question before revealing help, and explain why your method works.
Quick readiness check
Before Topic 18: mail merge
What you will learn
- Explain when a mail merge is suitable and the roles of a data source and master document
- Create and edit source data and master letters, labels/custom labels and directories
- Insert and format fields, preview records and check layout
- Sort/filter recipients and use If Then Else, Skip Record If and Next Record If rules
One master document can produce personalised outputs
The data source stores fields and records, such as recipient name, address and due date. The master document contains shared text and merge fields. Letters suit individual messages, labels suit physical addressing, and a directory combines records in a structured listing. Prepare consistent field names and types, remove duplicates, and check that each source record belongs in the intended audience.
Preview and rules prevent the wrong output
Insert fields where personal data should appear and preview multiple records, including blanks and long values. Sorting and filters select recipients; conditional rules can include text, skip records or move to the next record based on a field. Check spacing, page/label alignment, privacy and output count. A merge can rapidly multiply an error, so test a small sample before generating all documents.
Sources for this lesson
Pause and explain
Which approach best demonstrates secure, reliable IT practice in mail merge?
Worked example
A school sends overdue-book notices only to learners with Balance > 0. Outline the merge setup and checks.
Show the worked solution
- Prepare a data source with learner and balance fields.
- Create the shared notice and conditional recipient filter.
- Preview zero, positive and blank balances, then verify output count and privacy.
Answer Use a source with unique learner IDs, names, contact details and balance. Filter for Balance > 0, insert appropriate fields into the master letter, then preview a positive balance and records with zero or missing values. Check that no non-recipient receives a notice, labels/addresses are correct and printed copies are handled confidentially.
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.
A master letter should say 'Dear title surname' and omit a sentence when an address is outside the delivery region. Which fields and rule are needed?
Give me a hint
Personalise the greeting and make the region condition control a block of text.
Compare my reasoning
- Provide Title, Surname and Region fields in the data source.
- Insert the greeting fields.
- Use an If…Then…Else rule for the conditional sentence and preview both cases.
The data source needs consistent Title, Surname and Region fields. Insert Title and Surname in the greeting. An If…Then…Else condition on Region can include the delivery sentence for qualifying regions and omit or replace it for others. Preview both values, including blank title/surname cases, before producing the full merge.
Look for these in your work
- Maps fields to output
- Uses a conditional rule
- Tests both branches
A label sheet has the correct first row but later labels repeat the first learner. What should be checked?
Give me a hint
The merge must advance through records for each label.
Compare my reasoning
- Inspect the label layout and record-advance field.
- Check Next Record placement and field order.
- Preview several consecutive records, including the last label on a page.
Check that a Next Record rule is correctly positioned for each label after the first and that merge fields reference the current record. Preview several labels across page boundaries. A misplaced record-advance instruction can repeat or skip recipients and must be tested before printing.
Look for these in your work
- Identifies record advancement
- Checks placement
- Previews across a page boundary
A club has 500 records but only 120 are eligible. Describe a safe recipient-selection and reconciliation process.
Give me a hint
Count and verify the filtered audience before producing or sending documents.
Compare my reasoning
- Sort/filter by the eligibility rule and verify source values.
- Check the selected count against the expected 120.
- Preview a sample and reconcile excluded records.
Filter using the documented eligibility field, inspect the selected records for data errors and confirm the count is 120. Preview representative outputs and check excluded records are excluded for the intended reason. Generate the final documents only after the count and sample are verified, then handle them under the club's privacy rules.
Look for these in your work
- Uses a defined filter
- Reconciles the count
- Protects recipient data
Common mistakes
- Assuming field names guarantee correct values
- Failing to preview blank or unusually long fields
- Sending all generated documents without confirming the filter
What can you explain now?
A master letter should say 'Dear title surname' and omit a sentence when an address is outside the delivery region. Which fields and rule are needed?
Compare with the explanation
The data source needs consistent Title, Surname and Region fields. Insert Title and Surname in the greeting. An If…Then…Else condition on Region can include the delivery sentence for qualifying regions and omit or replace it for others. Preview both values, including blank title/surname cases, before producing the full merge.
Personalise the greeting and make the region condition control a block of text.
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
What roles do the master document and data source play in a mail merge?
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.