Mail Merge, Exceptions and Data Security Under Deadline
You are a junior assistant in the Directorate of Education. At 11 a.m. you must email and print 300 appointment letters by 1 p.m. The Word template has a date field, address block, and a table of pay details. The Excel source has 300 rows; you find one duplicate record (same candidate ID, different spelling), four rows with blank PIN codes, and two rows where the bank account number is 9 digits instead of 11. The shared Windows PC was last used by a colleague who left an Excel file named 'beneficiary_accounts.xlsx' open on the desktop and walked away. The printer is shared over the office LAN and is currently showing 'offline'. You need 50 hard copies for dispatch and 250 PDFs by email. The office has a policy that personal data must not be left on the desktop and that mail merge outputs must be checked before sending. Your typing speed is 38 wpm; retyping all letters is not feasible.
1. Sequence your actions from 11 a.m. to 1 p.m., including what you do first about the open file and the offline printer.
Read the worked answer
11:00-11:10 - secure the shared desktop. Do not read or copy the open file. Lock the screen or log off, note the filename and time, inform the colleague's supervisor/office IT, and move the file (with permission) to a restricted folder or report it for secure handling. This follows the policy that personal data must not be left on the desktop. 11:10-11:20 - fix the printer path. Check the printer's power, LAN cable, and queue; set it as default; clear stale jobs; restart the spooler only if you have rights. Print a one-page test. If it remains offline, start the PDF/email work immediately and use an alternate printer for the 50 copies. 11:20-11:40 - clean the Excel source. Remove the duplicate by candidate ID, flag the four blank PINs and two 9-digit accounts, and do not guess. Apply a filter so the main merge uses only validated rows. 11:40-12:10 - merge and check. Merge to a new Word document, preview 3-5 records, check date field, address block, and pay table. Save as PDF. 12:10-12:50 - send and print. Email in small batches with correct subject line and no full recipient list in 'To'; print 50 copies from the checked PDF. 12:50-1:00 - verify counts, log exceptions, and report the file incident.
2. How do you handle the four blank PIN codes and two 9-digit account numbers without delaying the whole batch?
Read the worked answer
Treat them as exceptions, not as permission to invent data. Put the six rows on a separate exception sheet with candidate ID, missing/wrong field, and source document. Send the 294 validated letters on time; do not hold the whole batch for six records. For the PIN codes, check the original application/office master; if still blank, issue the letter but mark dispatch 'address confirmation required' and contact the candidate. For the 9-digit accounts, do not pad with zeros or copy a number from another row; send the letter without the bank field or with a 'bank details under verification' note, and refer the case to the accounts section. Log who checked each exception and by when. This keeps the deadline while preserving auditability and avoiding wrong payments.
3. What security controls do you apply to the merged files and the shared PC before leaving for the day?
Read the worked answer
Data minimisation: keep only the validated source and final PDFs in the approved folder; delete temporary merge files and downloaded copies after upload. Access control: lock/log off the PC, use a password-protected screen saver, and do not share credentials. File protection: password-protect or encrypt the PDFs if emailing outside; send individualised letters rather than one file containing all candidates' bank details; use BCC or mail merge for bulk email. Audit: record the open-file incident, the exception list, and the number sent/printed. Physical: collect the 50 printed letters, count them, and lock them; do not leave them on the shared printer. Reporting: inform the supervisor about the colleague's left-open file and the printer issue so the office can fix the process, not just this batch.