Study a little every working day rather than in long weekend sessions. Spend about five weeks: Foundations first, then the eight Operator modules, listening to lessons on your commute and taking each module test at a desk. Put extra effort into depth, provenance and usage. On the day, forty decision questions in sixty minutes, with thirty-two correct needed to pass.
Why does a daily routine suit administrative assistants?
Administrative work is interrupted by nature. Long study blocks rarely survive a week of diary changes and urgent requests. Lessons in the Academy can be read or listened to as audio, with highlights and notes, so twenty or thirty minutes a day on the way to work can carry most of the reading. Save labs and module tests for two short desk sessions a week.
The exam itself is the first half of Certified Pryme Operator. It has 40 questions in 60 minutes and a pass mark of four in five. Questions describe a situation and ask what to do. What is on the AI operator exam explains the format in more depth, and the guide to AI operator certification shows how the exam leads to the practicum.
Where are you already strong, and where are the gaps?
Administrative assistants tend to do well on questions about human review: whether a draft may go out, whether the recipient and tone are right, whether something should be escalated. You check other people's drafts constantly, and the instinct carries over.
The usual gaps are three. First, depth and bounds: why an agent may draft but not send, or execute one thing but only hold another. Second, provenance: the difference between sealed, signed, declared and external sources, and why an external claim cannot authorise a payment. Third, usage and billing: what a business pays for and how to read a sudden change. Plan your weeks around those.
What workflow should you picture when you read a question?
Most administrative scenarios fit a flow like this one. Place each question on it before you answer.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Sorting the inbox | Reads and sorts | 1 | Spotting what is urgent or unusual |
| Drafting replies | Drafts | 2 | Approving before anything is sent |
| Internal room bookings | Books within rules | 3 | Setting the rules; sampling |
| Travel or purchases | Prepares and holds | 4, held | Approval by the budget holder |
| Request from outside to send money | Refuses or holds | none or 2, held | Verification; never on the email alone |
| Repeated errors in drafts | Nothing on its own | none | Changing the agent's sources or brief |
What does a five-week plan look like?
- You, week 1: Foundations, about four hours over six modules, mostly as audio. Take notes on the decision chain and on depth.
- You, week 2: Operator modules on how a governed agent decides and on human review. Take both module tests at a desk.
- You, week 3: teaching the agent and keeping knowledge current. Do the labs in a free Build workspace so you see a source with its provenance stamp.
- You, week 4: reading the workspace, when something goes wrong, usage and billing. These are the furthest from admin work; give them an extra desk session.
- You, week 5: running the rhythm, then retake every module test and review your list of wrong answers before booking the exam.
If a week collapses under work, move the plan by a week rather than cramming. Steady progress sticks better.
How should you use module tests?
Module tests are set in your own industry and role, so the scenarios look like diaries, client letters and office spend. That makes them the best practice there is. For each wrong answer, write one line: the situation, what you chose, what was right and why. Read the list again in week five. Patterns appear quickly, such as always choosing to edit a draft when the right answer was to fix the source behind it.
What should you do on exam day?
- Pace yourself at about ninety seconds a question, and do not let one difficult scenario use up time for two easier ones.
- Find the decision first. Read the final sentence, then the scenario.
- Ask who the source is. Many questions hinge on whether a fact came from the firm's own system or from outside.
- Ask which bound decided. Role scope, certificate, sources, the business's own limits or the platform guardrails; the lowest wins.
- Leave hard questions and return. Answer the ones you know first.
Sit the exam somewhere quiet, at a time with no meetings either side. Administrative assistants are often interrupted by habit; switch notifications off.
Where do administrative assistants lose marks?
- Choosing the polite option. The most courteous reply is not always right; sometimes the right answer is to hold and escalate.
- Fixing one draft when the cause is upstream. If several drafts share an error, change the source or the brief.
- Mixing up refused and withheld. A refusal is about this agent's bounds; withheld is a platform floor for every agent.
- Skipping usage and billing. It is a full module, and its questions are not guesswork.
Freelance assistants preparing at the same time can compare notes with how virtual assistants can prepare for the AI operator exam. After the exam, how administrative assistants can complete the operator practicum covers the second half, and AI operations careers for administrative assistants in Australia shows how one market looks.
Questions people ask
Do I need to know anything technical before I start?
No. Foundations assumes no technical background. It explains why agents must be governed, how decisions are made and what depth means.
Can I take the exam without finishing every module?
You should not. Questions draw on all eight Operator modules, and gaps show quickly under time pressure.
Does the exam cost anything?
Lessons, labs and tests are free. A professional certificate carries an issue fee, paid when it is issued, never to sit or pass.