Office Automation Systems and Productivity Software
Office automation covers the software that creates, routes, stores, and retires office documents. The exam tests governance of productivity tools rather than menu locations: template control, spreadsheet model integrity, mail merge, macro security, collaboration, accessibility, and records retention.
Core rules
- Separate content from formatting. Use heading styles and templates so navigation, accessibility, and automatic tables of contents work; direct formatting does not survive template changes reliably.
- Keep one authoritative copy with version history. Name and store drafts by version, and lock final records against editing.
- Build spreadsheet models in layers: inputs, calculations, outputs. Put assumptions in labeled cells; avoid hard-coded constants inside formulas; use structured tables.
- Match format to purpose: CSV for plain interchange, XLSX for live formulas, PDF/A for archival, ODF where a standard is mandated.
- Sign and document macros; disable unsigned macros by default through trust-center policy.
Worked example
An HR officer must issue 480 offer letters with a personalized start date and salary band, then retain an auditable copy. Put recipient data in one table with a unique ID. Compute salary band in the data source with a lookup table, not inside the letter, so the rule is testable. Run mail merge with conditional fields, preview one record, merge to PDF, and store the data source, template, and output under version control. Manual paste-ups would break traceability.
Traps that cost marks
- Relying on VLOOKUP default approximate match for an exact ID; use exact match or XLOOKUP.
- Using merged cells in data ranges; they break sorting, filtering, and mail merge.
- Treating a spreadsheet as a relational database with repeating rows and no keys.
- Enabling unsigned macros or ignoring macro security prompts.