Claude Certification Blog

A two-week CCAO-F study plan, sized to the exam's own weights

A two-week CCAO-F study plan that is not just the 30-day plan with days deleted. The fortnight is allocated the way the exam allocates its questions, which means the days are deliberately uneven.

14 days~1 hour a day60 items, 720 to pass

6 min read

A two-week CCAO-F study plan works out as one baseline day, ten domain days and three days of mocks and repair. The ten domain days are split by published weight rather than evenly, so output evaluation, workflow design and governance take two days each and the remaining four domains take one. Day 14 ends on a timed mock, and the result — not the calendar — decides whether you book.

The shape of the fortnight

Fourteen days is a compression, and what a compression protects tells you what it is for. Whether it is the right length for you depends on how long you actually need. This one keeps every domain pass and both timed mocks, and spends its savings on the practice depth a longer plan would add.

Day 1 is the cold baseline, days 2 to 11 are domain passes, days 12 to 14 are mocks and repairFOURTEEN DAYS, TWO WEEKS1234567891011121314Day 1 · baseline, sat coldDays 2–11 · domain passesDays 12–14 · mocks and repair
Two weeks removes the spare capacity, not the measurement. The two timed mocks are the last things to go, never the first.

Why the days are uneven

The Claude Certified Associate – Foundations blueprint publishes an approximate weight per domain, and they are nowhere near equal. Splitting fourteen days evenly across seven domains would give the same calendar time to a domain worth 21% of the exam as to one worth 10%.

So the rule here is simple enough to rebuild yourself: ten domain days, and the three heaviest domains take two of them each.

Domain weight decides the day allocation: the three heaviest domains take two days each, the other four take oneWEIGHT DECIDES THE DAYSD1 Prompting1dD2 Output evaluation2dD3 Product & model1dD4 Workflow design2dD5 Configuration1dD6 Governance & risk2dD7 Troubleshooting1d
Weights are approximate and the day counts are a rounding of them — but the ordering is stable, and that is what the allocation actually depends on.

The day-by-day CCAO-F study plan

The last column is the part that matters. Each day has to leave something behind, or it did not happen — a written rule, an audited Project, a cleared checkpoint.

DayFocusWhat must exist by the end
1BaselineOne full-length set sat cold, and a miss log tagged by domain
2D1 · Prompting and task executionEach rule rewritten as a trigger condition in your own words
3–4D2 · Output evaluation and validationA claim-level check run on a real draft, plus the section checkpoint
5D3 · Product and model selectionA written rule for the lightest configuration that clears your quality bar
6–7D4 · Workflow integration and designOne workflow mapped, with each step marked automate, augment or human-only
8D5 · Configuration and knowledgeA Project built and audited: instructions, knowledge, and what wins on conflict
9–10D6 · Governance, risk and responsible useAn authorisation screen you can apply to a new workflow from memory
11D7 · Troubleshooting and optimisationA failure traced to its layer before any prompt was touched
12Mock 1, timedAn error log naming the rule behind every miss, not the topic
13Repair the two weakest domainsBoth section checkpoints re-run closed-book and cleared
14Mock 2, timed, and logisticsA readiness decision on evidence, and an early stop time

What one study day looks like

About an hour, in four passes, in the same order every day: learn the decision rules and rewrite each as a trigger condition; build something small that exercises them; sit that section's checkpoint closed-book; then repair each miss by naming the rule, not the topic. The Claude certification study guide covers the rhythm in full.

10domain days, by weight
2timed mocks, both fresh
28objectives to tick off

Twenty-eight published objectives sit under those seven domains. Keeping a visible checklist of them from day one is the cheapest way to notice that a domain you enjoyed reading is still unticked on day nine.

The gate on day 14

Day 14 is not a finish line, it is a measurement — and exam day itself is a separate set of logistics to get right. Ready means at or above 90% on both timed mocks with no domain below 80%. Below 85%, or any domain under 75%, means the plan needs another pass before you book — and that is a better outcome than discovering it at the test centre.

The calendar does not decide, the mock does

A plan that ends on day 14 regardless of the day 14 result is a schedule, not preparation. Extend by two or three days and keep a fresh set in reserve; that costs far less than a retake and its waiting period.

Two of the five full-length sets stay untouched under this plan, which is deliberate — how many mock tests you sit matters less than how many unseen ones remain. For what those percentages do and do not predict, see the 720 passing score. And if you have not settled on CCAO-F yet, the guide to choosing a Claude certification compares all four.

Key takeaways

  • One baseline day, ten domain days, three for mocks and repair. That is the whole fortnight.
  • Allocate by published weight. Output evaluation, workflow design and governance take two days each; the rest take one.
  • Sit day one cold. The miss log is what makes the other thirteen days targeted.
  • Every day leaves evidence — a written rule, a built Project, a cleared checkpoint.
  • Day 14 is a measurement, not a deadline. Extend rather than book on a number you did not hit.

Every CCAO-F domain, objective by objective

The full Associate – Foundations blueprint with all seven domains and twenty-eight published objectives, plus study guides, checkpoints and five full-length practice sets.

See the CCAO-F blueprint

Questions

Frequently asked

The follow-up questions people search next.

Is two weeks enough to prepare for CCAO-F?

It is if you already use Claude in your work and can give it an hour a day. Two weeks is a compression of the fuller 30-day routine, so it protects the domain passes and the two timed mocks and cuts the labs and the spare capacity, not the measurement.

How should I split the days between domains?

By published weight, not evenly. The three heaviest domains — output evaluation at 21%, workflow design at 16% and governance at 15% — take two days each; the other four take one. That is ten domain days out of the fourteen.

What is the first thing to do in a CCAO-F study plan?

Sit a full-length set cold, before you have read anything. It feels wasteful and it is the most useful two hours in the fortnight, because the resulting miss log tells you which domains deserve the extra day rather than which ones you enjoy.

How many mock exams fit in two weeks?

Three sittings of a five-set bank: one cold on day 1 and two fresh timed ones on days 12 and 14. That leaves two sets untouched, which is the margin you want if the day 14 result comes in under the bar.

What if I cannot finish the plan in fourteen days?

Extend rather than compress. Borrow from the lightest domain — troubleshooting at 10% — before you borrow from any of the two-day domains, and never drop a timed mock to stay on the calendar. Sixteen honest days beat fourteen rushed ones.

Keep reading

Related posts

Not affiliated with, or endorsed by, Anthropic or Pearson VUE. Details are summarised from publicly published program information and can change — always confirm against the official exam guide before booking.

We use cookies and privacy-friendly analytics to understand usage and improve Cred Farmer. Essential features work either way. See our Cookie Policy.