Most versions of an ITIL 4 Foundation study plan 30 days assume you can give it two hours a night. Real people cannot. This plan assumes 45 minutes on weekdays and 90 minutes on one weekend day — about 20 hours total, which is genuinely enough for Foundation if the hours are spent well.
Foundation is a 60-minute, 40-question multiple-choice exam with a 65% pass mark — 26 out of 40. It is a vocabulary and framework exam, not a judgement exam. That matters enormously for how you should study it: precision of definitions beats depth of understanding.
Before day 1: the one thing to get right
ITIL 4 Foundation punishes people who paraphrase. The exam asks things like "which of these is the definition of a service?" and offers four plausible-sounding sentences, one of which is the ITIL definition and three of which are how a normal person would describe it. Your job for 30 days is to replace your intuitive vocabulary with ITIL's exact vocabulary.
So: whenever you learn a term, learn it in ITIL's words, not your own. This is the opposite of my usual study advice and it is correct here.
Week 1 — the spine (days 1–7)
The goal this week is the skeleton: the Service Value System, the four dimensions, and the seven guiding principles. Everything else hangs off these.
- Day 1: Key concepts — service, product, utility, warranty, outcome, output, cost, risk, value. Write each definition out longhand. These reappear all exam.
- Day 2: Value co-creation, service relationships (provider, consumer, and the three consumer roles: customer, user, sponsor). The three roles are heavily tested and easily confused.
- Day 3: The four dimensions — organisations and people, information and technology, partners and suppliers, value streams and processes. Learn what each covers and one example of neglecting it.
- Day 4: The Service Value System overview — inputs (opportunity/demand), governance, practices, continual improvement, outputs (value).
- Day 5: The service value chain and its six activities: plan, improve, engage, design and transition, obtain/build, deliver and support. Know that it is not linear.
- Day 6: The seven guiding principles, one by one.
- Day 7 (long session): First cold practice block, 40 questions, timed to 60 minutes. Expect something in the 40–55% range. This is diagnostic, not a verdict.
Week 2 — the guiding principles properly (days 8–14)
The principles are worth their own week because the exam tests them situationally: "a team is doing X, which principle are they applying?" You need to distinguish between them, not just list them.
- Day 8: Focus on value; Start where you are. The distinction that catches people: "start where you are" means assess the current state before discarding it, not "don't change anything".
- Day 9: Progress iteratively with feedback; Collaborate and promote visibility.
- Day 10: Think and work holistically; Keep it simple and practical.
- Day 11: Optimise and automate — specifically, that you optimise before you automate.
- Day 12: Scenario drilling. Take 20 short situations and label each with a principle. Where two principles both seem to fit, write down what would make one more right.
- Day 13: Continual improvement model — the seven steps and their questions ("what is the vision?", "where are we now?", and so on).
- Day 14 (long session): Practice block, principles-weighted. Then re-read only what you missed.
Week 3 — the practices (days 15–21)
There are 34 practices; Foundation examines a subset in detail and the rest at the level of "what is its purpose". Do not try to learn all 34 deeply. Learn the examinable ones properly and the rest as one-line purposes.
- Day 15: Incident management and service desk. Know the difference between restoring service and finding the cause.
- Day 16: Problem management — and the three phases: problem identification, problem control, error control. Known error and workaround definitions are exam favourites.
- Day 17: Change enablement — the three change types (standard, normal, emergency) and who authorises each. Very commonly tested.
- Day 18: Service request management and service level management. SLM's focus on the whole service experience, not just metrics, comes up.
- Day 19: Continual improvement practice, monitoring and event management, information security, relationship management, supplier management.
- Day 20: IT asset management, service configuration management, release management, deployment management, service desk revisited. Release versus deployment is a classic confusion — learn it as a pair.
- Day 21 (long session): Full timed practice set. You want to be at or above 70% by now.
Week 4 — precision and pace (days 22–30)
Content is done. This week is about eliminating the specific errors you keep making.
- Days 22–24: One timed 40-question set per day. After each, sort misses into "didn't know" versus "misread". Fix the first with targeted reading; fix the second by slowing down at the question stem.
- Days 25–26: Definitions blitz. Every key term, self-tested. If you cannot produce ITIL's definition, it goes on a flashcard.
- Day 27: Weak-practice day. By now you will know which two or three practices will not stick. Only those.
- Day 28: Full set under strict conditions — no pausing, no lookups, phone in another room.
- Day 29: Light review of your flashcard pile only. No new material.
- Day 30: Exam. Do not cram in the morning.
Practical notes on the loop
For the daily blocks I used the free bank at ExamCert's ITIL 4 Foundation free practice test and checked coverage against the syllabus areas listed on the ITIL 4 Foundation exam page. Any decent bank works; what matters is that you have enough questions to avoid memorising the set. If you find yourself remembering that "the one about the coffee shop is B", you have exhausted that bank and your scores are now fiction.
Three things that reliably cost marks
Confusing outputs with outcomes. An output is a deliverable; an outcome is a result for a stakeholder enabled by that output. The exam tests this directly.
Treating the value chain as a sequence. It is not. Activities can be combined in many value streams, in any order, and questions are built to catch people who assume a left-to-right flow.
Answering from workplace experience. If your organisation calls something a "change request" that ITIL would call a service request, your instinct will be wrong. When your job and the syllabus disagree, the syllabus wins for 60 minutes.
The realistic bottom line
Foundation is passable in 30 days at 45 minutes a day, comfortably, provided you spend at least a third of that time answering questions rather than reading. The people who fail it almost never fail on comprehension — they fail on precision, because they studied by reading until it felt familiar. Familiar is not the same as known. Test yourself early enough to find out which one you have.
Top comments (0)