Office Administration Fundamentals
The Office Administration Fundamentals domain tests whether you understand the operating spine of an office - structures, workflows, systems and the boundaries of an administrator's authority - rather than isolated clerical tasks. Expect scenario questions where the correct answer depends on documented policy, priority, and who owns the next step.
Core rules
- Authority is delegated, not assumed. An administrator may commit spend, release records or approve leave only to the limit set in policy or a written delegation.
- Every workflow needs a single owner, a defined trigger and a handoff record, so work cannot fall between desks.
- Triage by impact multiplied by deadline, not by who asked loudest. A fixed external deadline carrying a penalty outranks an internal preference.
- Keep a bring-forward (BF) diary: anything dated in the future is filed under the date it must be actioned, not the date it arrived.
- Assets and supplies belong on an inventory register with reorder thresholds and a named custodian.
Worked example
At 16:40 a courier request arrives for a signed contract that must be received tomorrow; at the same moment a manager asks you to reformat a slide deck for next week. Reasoning: the contract has a fixed external deadline and a financial consequence; the deck does not. Book the courier, send the tracking number to the sender, record the cost, and tell the manager when the deck will be ready. Do not silently drop either item.
Traps that cost marks
- Treating a verbal instruction from a senior person as policy.
- Confusing urgent with important and abandoning the diary and logs.
- Escalating nothing - or escalating everything, which trains people to ignore you.