ITIL 4 Foundation remains available in 2026 even though PeopleCert has also launched ITIL Foundation Version 5. PeopleCert’s current transition guidance says ITIL 4 modules are planned to sunset on December 31, 2027, so candidates targeting ITILFND V4 still have an active certification route. The exam itself remains 40 multiple-choice questions, 60 minutes, closed book, with a 65% passing score.
The current PeopleCert product page emphasizes service management concepts, the Service Value System, the four dimensions, the seven guiding principles, the Service Value Chain, ITIL practices, continual improvement, service level agreements, and metrics/KPIs. Those topics reflect the classic ITIL 4 Foundation syllabus and remain the correct basis for an ITIL 4 Foundation study plan.
Service management starts with value, outcomes, costs, and risks
Foundation candidates need to understand service, service management, service provider, customer, user, sponsor, service offering, service relationship, utility, warranty, outcome, output, cost, risk, and value. These terms establish how ITIL describes cooperation between providers and consumers.
The framework is not about optimizing internal process for its own sake. It is about co-creating value through products and services that help stakeholders achieve desired outcomes while managing cost and risk.
Utility and warranty explain why a service can be useful but still fail
Utility is commonly described as “fit for purpose”: what the service does to support a need. Warranty is “fit for use”: whether the service has sufficient availability, capacity, continuity, and security.
A service can have strong utility but weak warranty. For example, an application may provide exactly the needed business function yet remain unusable because it is unreliable or insecure.
The seven guiding principles shape decisions across the framework
ITIL 4 Foundation expects candidates to know the guiding principles: focus on value; start where you are; progress iteratively with feedback; collaborate and promote visibility; think and work holistically; keep it simple and practical; and optimize and automate.
These are not steps performed once. They are recommendations that can be applied together when improving services, practices, value streams, or organizational behavior.
The four dimensions prevent one-sided service-management design
The four dimensions are organizations and people; information and technology; partners and suppliers; and value streams and processes. Effective service management considers all four rather than optimizing only technology or process.
A change to a service can fail because people lack skills, a supplier cannot meet the need, information quality is poor, or the value stream contains unnecessary handoffs—even when the technology works.
The Service Value System connects governance, principles, practices, and improvement
The ITIL Service Value System explains how organizational components and activities work together to facilitate value creation. It includes guiding principles, governance, the Service Value Chain, practices, and continual improvement.
The important Foundation skill is seeing the framework as a system. Practices support value-chain activities; governance directs the organization; guiding principles influence decisions; and continual improvement operates across everything.
The Service Value Chain describes six connected activities
The six activities are Plan; Improve; Engage; Design and Transition; Obtain/Build; and Deliver and Support. Value streams combine these activities in different sequences depending on the product, service, request, or improvement being delivered.
The value chain is not a fixed linear lifecycle. Different demand and opportunities can trigger different combinations of activities.
Continual improvement operates at every level
Continual improvement applies to products, services, practices, value streams, technology, and organizational methods. ITIL 4 uses a continual-improvement model that moves from vision and current state through target state, action, measurement, and sustained momentum.
Candidates should understand that improvement is evidence-driven and iterative, not a periodic project performed only after failure.
Foundation covers the purpose of multiple ITIL practices
The syllabus historically expects awareness of 15 practice purposes and deeper understanding of seven core practices. The seven commonly emphasized Foundation practices are continual improvement, change enablement, incident management, problem management, service request management, service desk, and service level management.
The exam tests what the practices are trying to achieve and how they contribute to value, not exhaustive procedure manuals.
Incident, problem, and change are deliberately different
Incident management restores normal service quickly. Problem management reduces likelihood and impact by identifying causes and managing workarounds or known errors. Change enablement evaluates and authorizes changes so beneficial changes happen with acceptable risk.
These practices interact closely, but confusing their purpose leads to weak scenario answers.
ITIL 4 is active, but candidates should know the transition context
PeopleCert now offers ITIL Foundation Version 5 and a Foundation Bridge for existing ITIL 4 holders. At the same time, ITIL 4 Foundation is still listed and current transition guidance plans sunset for ITIL 4 modules at the end of 2027.
PeopleCert’s current ITIL 4 Foundation page also lists a three-year certification renewal cycle and 60 CPD points as the membership-based renewal route. Candidates do not need to memorize renewal administration for the exam syllabus, but the policy reinforces that ITIL credentials are intended to remain current rather than be treated as lifetime certificates. The service-management discipline continues to evolve as operating models and technology change.
The service relationship model is another important Foundation concept. Providers and consumers cooperate through service provision, service consumption, and service-relationship management. Customers define service requirements and take responsibility for outcomes, users consume the service, and sponsors authorize budgets. One person can occupy more than one role, but the distinctions help explain stakeholder perspectives.
Outputs and outcomes should also be separated carefully. An output is a tangible or intangible deliverable from an activity; an outcome is a result enabled for a stakeholder. A deployed service desk tool is an output. Faster restoration and better user satisfaction may be outcomes. ITIL focuses on whether outputs enable valuable outcomes, not merely whether work was completed.
Cost and risk can be removed from consumers, introduced to consumers, or shared between provider and consumer. Cloud services illustrate this well: customers avoid some capital and maintenance costs but may accept provider dependency, usage charges, and new security or contractual risks. Service value is therefore a balance, not a simple benefit score.
Governance inside the Service Value System is commonly described through evaluate, direct, and monitor responsibilities. The governing body evaluates stakeholder needs and conditions, directs priorities and policy, and monitors performance and compliance. Governance should not be confused with day-to-day management; it provides direction and oversight across the service-management system.
The “start where you are” principle does not mean resisting change. It means objectively assessing existing services, processes, data, people, and capabilities before replacing them. Existing measurements can be useful evidence, but candidates should also understand that inaccurate assumptions or obsolete practices should not be preserved merely because they already exist.
“Progress iteratively with feedback” and “collaborate and promote visibility” often reinforce each other. Smaller improvements create earlier feedback, while transparent work helps stakeholders understand progress and contribute information. Large hidden projects can accumulate risk because users only see the result after major assumptions have already been built into the solution.
“Keep it simple and practical” does not mean oversimplify complex services. It means remove steps, controls, reports, or handoffs that do not contribute enough value to justify their cost. “Optimize and automate” follows the same logic: understand and improve the work before automating it, otherwise technology can scale inefficiency.
Beyond the seven deeper practices, Foundation candidates should recognize the purpose of other practices such as information security management, relationship management, supplier management, IT asset management, monitoring and event management, release management, deployment management, and service configuration management. The exam’s emphasis is purpose and contribution to value, not advanced procedures from the separate practitioner modules.
Because Version 5 is now available, candidates should check the exact voucher and training product before scheduling. ITIL 4 Foundation and ITIL Foundation Version 5 are separate current offerings with overlapping but different terminology and learning structures. This article intentionally preserves ITIL 4 framing because the source plan and ExamLabs target are ITILFND V4.
The Service Value Chain deserves special attention because candidates sometimes confuse it with older lifecycle language. ITIL 4 intentionally uses flexible value streams built from six activities rather than a mandatory sequence of service lifecycle stages. A new service, incident response, user request, or improvement can combine the activities differently according to the work required.
Change enablement is also worth learning with its modern purpose. ITIL 4 does not define successful change management as adding maximum approval. The practice aims to maximize successful service and product changes by ensuring risks are assessed, changes are authorized to proceed, and schedules are managed. Proportionate control is more aligned with the framework than bureaucratic delay.
Service desk is another concept that Foundation candidates should not reduce to a ticketing tool. It is the entry point and communication channel between service provider and users. A strong service desk captures demand, communicates clearly, and supports user experience even when other teams ultimately resolve the incident or fulfill the request.
Because ITIL 4 and Version 5 currently coexist, source discipline matters. Training written for the new Version 5 may introduce different structures or terminology. Candidates registered for ITILFND V4 should use ITIL 4 official materials and verify that mock exams, eLearning, and study notes are labeled for the same version.
For exam readiness, candidates should be able to rebuild the ITIL 4 picture from memory: value and service relationships, seven principles, four dimensions, the SVS, six value-chain activities, continual improvement, and practice purposes. If those pieces connect, detailed wording becomes much easier to place accurately.
Within the broader ITIL certification portfolio, that means ITILFND V4 remains valid preparation for candidates whose exam voucher and path specifically target ITIL 4. Study the ITIL 4 terminology and syllabus, while being aware that the wider qualification scheme is evolving.