Core, Series Guides, Library, and certification map

A common early mistake is to speak about the TOGAF Standard, the Series Guides, the Library, and the certification programme as if they were all the same layer. They are not. Each layer has a different purpose, a different level of authority, and a different rate of change.

The standard (Fundamental Content) tells you what the framework is. It defines the canonical concepts, the ADM, the techniques, the content framework, and the governance model. This is the backbone.

The Series Guides explain how to deepen or configure the backbone for a specific context. They carry authority within their scope but are designed to be selected based on the problem, not read exhaustively.

The Library supports the broader ecosystem with practical aids, reference material, and companion documents. It is official but supportive, not normative.

The certification portfolio defines recognised learning paths and assessments built from selected bodies of knowledge. It tests understanding. It does not define the boundary of what TOGAF contains.

Getting these four layers clear in your mind is the prerequisite for using any of them well. When someone quotes a "TOGAF rule," the first useful question is: which layer does that claim come from? A statement in the Fundamental Content carries more weight than a recommendation in a Series Guide, which carries more weight than a suggestion in Library material, which carries more weight than a simplification in a training slide.

The Open Group help article updated 24 December 2025 identifies these TOGAF Standard, 10th Edition certifications:

TOGAF Enterprise Architecture Foundation

Foundation is the entry-level certification. It validates that you understand the basic concepts, the structure of the standard, and the vocabulary of enterprise architecture as TOGAF defines it. The exam tests knowledge of the ADM phases, the Fundamental Content volumes, and the key terms. It is a multiple-choice exam that can typically be prepared for through a structured course or self-study programme.

Foundation is useful because it enforces a common vocabulary. When everyone on a team has Foundation-level understanding, conversations about phases, deliverables, and governance become more precise. The limitation is that Foundation tests recognition and recall, not application. Passing Foundation does not mean you can set up and run architecture work in a real enterprise.

TOGAF Enterprise Architecture Practitioner

Practitioner is the advanced certification. It validates the ability to apply the method, not just recognise the vocabulary. The exam uses scenario-based questions that require you to make judgement calls about how to use TOGAF in realistic situations. You might be given a description of an enterprise problem and asked which ADM phase should be emphasised, which technique should be applied, or which governance mechanism should be invoked.

Practitioner is harder because it tests judgement. You cannot pass it by memorising definitions. You need to understand why the ADM works the way it does and how to adapt it to different contexts. Most candidates sit the Practitioner exam after completing Foundation.

TOGAF Business Architecture Foundation

This certification focuses specifically on business-architecture knowledge aligned to the TOGAF Standard. It covers capabilities, value streams, business scenarios, organisation mapping, and business models. It draws from both the Fundamental Content (Phase B) and the business architecture Series Guides (G176, G178, G18A, G206, G211, G233).

Business Architecture Foundation is useful for practitioners who spend most of their time in the business layer rather than in technology or data architecture. It validates that you can use TOGAF to shape strategy, operating models, and capability investment.

Bridge path from TOGAF 9

The Open Group provides a bridge path for people already certified in TOGAF 9 who want to update their credentials to the 10th Edition. The bridge recognises that the core method has not changed fundamentally. What changed is the structure and the publishing model. The bridge exam focuses on the structural differences, the Series Guide ecosystem, and any updates to the core content.

The official naming article makes a useful distinction that many practitioners miss. The Open Group uses two different terms: certifications and credentials. They are not the same thing.

Certifications are the main TOGAF qualifications. They use multi-day learning paths and comprehensive exams. The three main certifications (Enterprise Architecture Foundation, Enterprise Architecture Practitioner, and Business Architecture Foundation) fall into this category.

Credentials are shorter, more focused qualifications that address specific specialist topics. As of the same official article, the TOGAF credentials include:

• Integrating Risk and Security in a TOGAF Enterprise Architecture (aligned to Series Guide G152)
• TOGAF Framework: Digital Specialist (aligned to the digital enterprise guidance)
• TOGAF Framework: Agile Specialist (aligned to the enterprise agility and agile architecture guidance)
• TOGAF EA Leader (aligned to the leadership and capability guidance)

The distinction matters because it explains why there is no single all-purpose "TOGAF 10 Foundation" label. The 10th Edition is broad and modular, so the certification structure is role-based and skill-based rather than version-stamped. A security architect might pursue the Risk and Security credential. A business architect might pursue the Business Architecture Foundation certification. A delivery lead working in an agile context might pursue the Agile Specialist credential. Each path validates a different slice of the body of knowledge.

This is a direct consequence of the modular standard. Because the Series Guides exist as separately identifiable bodies of knowledge, the certification programme can create focused credentials around specific guides without trying to test everything in a single exam.

Certification and deep understanding of enterprise architecture are related but not identical. Certification validates that you have reached a defined level of knowledge as measured by a structured assessment. Understanding means you can apply that knowledge to messy, ambiguous, real-world problems where the textbook answer does not directly apply.

Foundation certification validates vocabulary and structural awareness. It confirms that you know what the ADM phases are, what the Fundamental Content volumes contain, and how the key terms relate. This is genuinely valuable. It creates a shared language that makes team conversations more precise. When everyone on a team can distinguish a deliverable from an artefact from a building block, communication about architecture outputs becomes clearer.

Practitioner certification validates application and judgement. It confirms that you can read a scenario and make a reasonable decision about which ADM phase to emphasise, which technique to apply, or which governance mechanism to invoke. This is harder and more useful than Foundation because it tests thinking, not just recall.

But neither certification tests the full range of skills needed for real enterprise architecture practice. Real practice involves navigating stakeholder politics, designing a repository that actually works, adapting the method to an enterprise that has never done architecture before, and sustaining the practice through leadership changes and budget pressures. These skills come from experience, mentoring, and deliberate study beyond the certification boundary.

The practical advice is straightforward: pursue certification because it enforces vocabulary and structure, and because it provides recognised credentials that matter for career development. But do not stop there. Study the Series Guides that your enterprise needs. Build repository discipline. Practise stakeholder communication. These are the skills that separate a certified architect from an effective one.

The Open Group uses publication codes and document references throughout the certification ecosystem. Understanding these codes helps you navigate the official material without confusion.

C220 is the publication code for the TOGAF Standard, 10th Edition Fundamental Content. When you see "C220 Part 1," that refers to the ADM volume of the core standard.

X2202 is the publication code for the TOGAF conformance requirements document. This is the syllabus. It defines the learning outcomes for each certification and the depth of understanding expected. Training providers use X2202 to design conformant courses. Exam developers use it to write questions.

G-prefixed codes (such as G184, G186, G211) are Series Guides. Each guide has its own publication code and can be referenced independently.

02.1 is the BOK Guide, the navigation document that maps the entire TOGAF body of knowledge.

The credential system works as follows. You enrol through an Accredited Training Course (ATC) provider or self-study, prepare using the syllabus (X2202), sit the exam through a Pearson VUE test centre or online proctored exam, and receive your credential from The Open Group upon passing. Your certification is then verifiable through The Open Group's online certification registry.

The credentials are not permanent in the traditional sense. The Open Group has a certification maintenance programme. Certified individuals must demonstrate continuing professional development to maintain their active status. This ensures that certified architects stay current as the standard evolves.

The current naming is deliberate. The portfolio is expressed as Enterprise Architecture Foundation, Enterprise Architecture Practitioner, and Business Architecture Foundation, rather than by stamping every credential with the number 10 in the title.

That naming choice matters for two reasons. First, it signals that the certifications are tied to maintained bodies of knowledge and learning paths, not just to a casual version label used in conversation. The body of knowledge evolves as new corrigenda are applied and new guides are published. The certification evolves with it.

Second, it prevents the confusion that plagued TOGAF 9 certification, where people would say "I am TOGAF 9 certified" as if the version number were the important part. The important part is what you can do: understand the concepts (Foundation), apply the method (Practitioner), or work in the business layer (Business Architecture Foundation).

The Open Group help article on certification syllabuses points to document X2202 as the syllabus document for certifications based on bodies of knowledge drawn from the TOGAF Standard, 10th Edition.

Specifically, X2202 covers the learning outcomes for TOGAF Enterprise Architecture Foundation, Enterprise Architecture Practitioner, the Practitioner Bridge (from TOGAF 9), and Business Architecture Foundation. For each certification, it lists the knowledge areas, the learning outcomes within each area, and the depth of understanding expected (recall, comprehension, or application).

What X2202 is for: X2202 is the formal syllabus and conformance reference. Training providers use it to design courses. Exam developers use it to write questions. Candidates use it to understand the scope of what the exam will test. It defines the boundary of the exam, not the boundary of the framework.

What X2202 is not for: X2202 is not the TOGAF framework itself. It does not replace the Fundamental Content, the Series Guides, or the Library. It does not contain the detailed explanations, techniques, or guidance that you need for real architecture practice. If you study only X2202, you will know what the exam expects, but you will not necessarily know how to set up and run architecture work in a real enterprise.

The practical discipline is to treat X2202 as a study-boundary document. Use it to structure your preparation. Then trace every important topic back to the core standard or the specific guide it came from. That way, you learn the framework, not just the exam.

The following study discipline keeps certification useful without letting it become the whole story:

1. Use the certification portfolio to understand the recognised learning path and level boundary. Know whether you are aiming for Foundation (vocabulary and concepts), Practitioner (application and judgement), or Business Architecture Foundation (business-layer depth).
2. Use X2202 to see what knowledge areas and learning outcomes are expected. This tells you the scope of the exam. It does not tell you everything you need to know for real architecture work.
3. Trace every important topic back to the core standard or the specific guide it came from. When X2202 mentions gap analysis, go to Part 2 of the Fundamental Content and read the technique in full. When it mentions business capabilities, go to G211 and understand how capability mapping works.
4. Study the guides that your enterprise problem needs, even if they sit outside the narrowest exam focus. If your organisation is dealing with data quality issues, read G234 (Metadata Management) even if the Foundation exam does not emphasise it heavily. Real architecture work does not stop at the exam boundary.
5. Use practice questions to check vocabulary and judgement, not to replace reading or architecture thinking. Practice exams are useful for identifying gaps in your understanding. They are not a substitute for understanding the material deeply enough to apply it.

Study discipline in practice

Here is how the study discipline works in a concrete scenario. Suppose you are preparing for the Enterprise Architecture Practitioner exam while also supporting a real transformation programme at your organisation.

Week 1-2: Foundation vocabulary. Use X2202 to identify the knowledge areas. Read Part 0 and Part 1 of the Fundamental Content to establish the conceptual model and the ADM cycle. At this stage, you are building the shared vocabulary that the exam and the real work both require.

Week 3-4: Techniques and content. Read Part 2 (techniques) and Part 4 (content framework). Focus on gap analysis, stakeholder management, and the relationship between deliverables, artefacts, and building blocks. These are heavily tested in the Practitioner exam and heavily used in real work.

Week 5-6: Application and governance. Read Part 3 (applying the ADM) and Part 5 (capability and governance). Study how iteration works, how the architecture landscape connects strategic and segment architectures, and how compliance reviews and waivers operate.

Ongoing: Guide-level depth. In parallel with exam preparation, read the Series Guides that your enterprise problem requires. If your programme involves business capability mapping, read G211 and G233. If it involves information architecture, read G190 and G234. These guides will not all be tested in the exam, but they will make you effective in the real work.

Practice exams: Calibration, not curriculum. Use practice questions to check where your understanding is weak, then go back to the source material. Do not memorise answers. Understand why the correct answer is correct and trace the reasoning back to the Fundamental Content or the relevant guide.

What it is for. The Library is the supporting layer of the official TOGAF ecosystem. It is where useful aids, supporting material, and broader companion items can live without being confused for the core standard. This includes reference cards that summarise key concepts, pocket guides that provide quick-reference summaries, templates that give starting points for common deliverables, and the BOK Guide (02.1) that navigates the entire publication ecosystem.

What it is not for. It is not a substitute for the core framework, and it is not proof that every item in it carries the same authority as the Fundamental Content. A reference card that summarises the ADM phases is helpful for revision, but it does not replace Part 1 of the Fundamental Content when you need the canonical description of a phase.

How to use it well. Use it after you know whether the answer you need is normative (from the Fundamental Content), contextual (from a Series Guide), or supportive (from the Library). That sequence keeps your learning clean and prevents you from accidentally treating a simplified summary as if it were the full standard.

This course uses the official publication stack more broadly than exam preparation does. It keeps the certification map visible because many learners care about recognition, but it deliberately teaches beyond the narrowest exam boundary.

The point is practical understanding. Later stages need the guide set, repository logic, and governance depth whether or not a particular exam blueprint foregrounds them.

Stage 4 of this course uses information mapping, metadata management, and analytics guidance from Series Guides G190, G234, and G238. These are official publications that deepen a real architecture problem, but they may not appear prominently on the Foundation exam blueprint. The course includes them because the London case demands real information-architecture work, not because an exam question might reference them.

Stage 6 uses enterprise agility (G20F) and agile architecture sprints (G210) to help London Grid delivery teams work in sprints while maintaining architecture discipline. Stage 7 uses compliance review (G19F) and maturity assessment (G1AC) to design governance that is rigorous without being bureaucratic.

In each case, the Series Guide is introduced when the architecture problem demands it, not in a detached catalogue. You learn the guide in context, not in isolation. That is the practical consequence of the modular standard: you configure the core with the guide that fits the problem at hand.

The London case is a guardrail against exam-only thinking. Every Stage 1 topic is tied to a real enterprise consequence: repository design, business pressure, information authority, transition planning, and governance.

That means the certification layer stays useful but never becomes the whole story. The fictional enterprise still needs architecture judgement after the exam page ends.

Consider which certification path different London Grid staff would need:

• The chief architect would pursue Enterprise Architecture Practitioner to validate their ability to run the ADM across all four domains. They would also benefit from the EA Leader credential to demonstrate capability leadership.
• A business analyst moving into architecture would start with Enterprise Architecture Foundation to establish the vocabulary, then pursue Business Architecture Foundation to deepen their understanding of capabilities, value streams, and business scenarios.
• A security architect would pursue the Integrating Risk and Security credential to validate their ability to weave OT security and cyber resilience into the architecture rather than treating security as a separate workstream.
• A delivery lead managing agile teams would pursue the Agile Specialist credential to demonstrate they can integrate architecture into sprint-based delivery without treating TOGAF as a waterfall overhead.
• A data architect would take Foundation for the vocabulary, then study the information-architecture Series Guides (G190, G234, G238) even though no specific data credential currently exists. The knowledge is more important than the credential in this case.

A certification syllabus can tell you that business scenarios matter. The case shows you how they shape the opening architecture problem. A certification path can tell you that deliverables, artefacts, and building blocks differ. The case shows why confusing them breaks governance and reuse. A certification summary can tell you there is a repository. The case shows why a repository must function as live operating memory.

The lesson is that certification and practice are complementary, not substitutable. London Grid's architecture team would ideally have a mix of certifications across the team: some members with Foundation (providing shared vocabulary), at least one with Practitioner (providing method application depth), a business architect with Business Architecture Foundation (providing business layer credibility), and relevant specialist credentials spread across the team based on the enterprise's priority problems. But the certifications would be the starting point for competence, not the end point. The end point is the ability to use the standard, the guides, and the repository to make better decisions for 2.3 million London customers.

The broader point applies to any enterprise. Certification is a floor, not a ceiling. It gives you the language to participate in architecture conversations. The guides, the repository, the governance practice, and the accumulated experience of real architecture work are what make those conversations productive.