<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>IICTP Standards &amp; TPBOK</title><link>https://iictp.org/</link><description>The Technical Practitioner Body of Knowledge. Each item is the full content of one page of the International Insignia of Certified Technical Practitioners website.</description><language>en</language><copyright>© IICTP. All rights reserved. Use is governed by https://iictp.org/terms</copyright><generator>IICTP site build (scripts/feeds.mjs)</generator><docs>https://www.rssboard.org/rss-specification</docs><ttl>1440</ttl><lastBuildDate>Mon, 19 Oct 2026 19:57:41 GMT</lastBuildDate><image><url>https://iictp.org/favicon.svg</url><title>IICTP Standards &amp; TPBOK</title><link>https://iictp.org/</link></image><atom:link href="https://iictp.org/rss/standards.xml" rel="self" type="application/rss+xml"/><item><title>TPBOK™: Technical Practitioner Body of Knowledge Guide</title><link>https://iictp.org/standards/tpbok</link><guid isPermaLink="true">https://iictp.org/standards/tpbok</guid><pubDate>Mon, 19 Oct 2026 19:57:41 GMT</pubDate><category>Standards</category><dc:creator>IICTP</dc:creator><description>Competence is terrain, and this is the map: one vendor-neutral reference for what technology professionals should know and be able to do, across five domains and four levels.</description><content:encoded><![CDATA[<link rel="preload" as="image" href="/src/assets/logo/iictp-logo-reversed.svg"/><!--$--><div><section><div></div><div><div><div><p>Coming 2027 · The IICTP standard</p><h1>The TPBOK™<!-- --> <br/>Guide Standard</h1><p>Competence is terrain, and this is the map: one vendor-neutral reference for what technology professionals should know and be able to do, across five domains and four levels.</p><form><div><label><span>Your work email</span><input id="notify-hero" type="email" required="" placeholder="Your work email" autoComplete="email" value=""/></label></div><small>We will write once, when the Guide is published. This opens your email app to send the request.</small></form></div><div><div><div><div><i></i>IICTP Standard</div><div>TPBOK<sup>™</sup></div><div>The Guide to the Technical Practitioner Body of Knowledge</div><div><span>First edition</span><span>2027</span></div></div></div><span>Coming soon</span></div></div><div><div><b>5</b><span>Domains</span></div><div><b>4</b><span>Levels</span></div><div><b>1st</b><span>Edition</span></div><div><b>2027</b><span>Planned release</span></div></div></div></section><section id="about"><div><div><div><p>About the Guide</p><h2>A shared language for technical competence.</h2></div><p>The Guide defines the knowledge, skills and evidence that mark each level of practice, so that people, teams and employers mean the same thing by “senior”.</p></div><div><div><small>01</small><h3>Purpose</h3><p>Sets out what competent practice looks like in each domain, in plain, testable statements, independent of any vendor or tool.</p></div><div><small>02</small><h3>Audience</h3><p>Engineers who want a path, managers who need a yardstick, and educators and employers who need a common scale.</p></div><div><small>03</small><h3>Basis for certification</h3><p>Every IICTP credential is assessed against the Guide. Studying the Guide is studying for the exam, and the reverse.</p></div></div></div></section><section id="contents"><div><div><div><p>Inside the Guide</p><h2>Nine parts, one map.</h2><p>Part titles and order are provisional. Each part opens with the same template, so every domain reads the same way.</p><div><div><div><div><i></i>IICTP Standard</div><div>TPBOK<sup>™</sup></div><div>The Guide to the Technical Practitioner Body of Knowledge</div><div><span>First edition</span><span>2027</span></div></div></div></div><span>The map, in your hands</span></div><ol><li><small>I</small><div><b>Foundations</b><span>Principles, scope and how to read the Guide.</span></div></li><li><small>II</small><div><b>The competence model</b><span>The four levels and how progression is judged.</span></div></li><li><small>III</small><div><b>Architecture &amp; systems design</b><span>Structure, trade-offs and long-lived design.</span></div></li><li><small>IV</small><div><b>Engineering governance &amp; agile delivery</b><span>Building, testing, governing and shipping reliably.</span></div></li><li><small>V</small><div><b>Applied AI &amp; emerging tech</b><span>Integrating new technology into real systems, safely.</span></div></li><li><small>VI</small><div><b>Infrastructure &amp; security</b><span>Running platforms, and the threats and controls around them.</span></div></li><li><small>VII</small><div><b>People leadership in engineering</b><span>Leading teams, growing people and owning outcomes.</span></div></li><li><small>VIII</small><div><b>Evidence and assessment</b><span>How competence is shown, scored and renewed.</span></div></li><li><small>IX</small><div><b>Ethics and conduct</b><span>The professional code every holder agrees to.</span></div></li></ol></div></div></section><section id="model"><div><div><div><p>The competence model</p><h2>Four levels, one map.</h2></div><p>The same terrain, read at four altitudes. Every statement is written at all four levels, so progress in any domain is measured the same way.</p></div><div><a href="/#certifications"><span><i></i><i></i><i></i><i></i></span><p>Level<!-- --> <!-- -->1</p><p>Foundations</p><p>Your first role in technology.</p></a><a href="/#certifications"><span><i></i><i></i><i></i><i></i></span><p>Level<!-- --> <!-- -->2</p><p>Practitioner</p><p>Shipping real systems.</p></a><a href="/#certifications"><span><i></i><i></i><i></i><i></i></span><p>Level<!-- --> <!-- -->3</p><p>Professional</p><p>Designing what others build on.</p></a><a href="/#certifications"><span><i></i><i></i><i></i><i></i></span><p>Level<!-- --> <!-- -->4</p><p>Specialist</p><p>Setting direction.</p></a></div></div></section><section id="anatomy"><div><div><div><p>How it reads</p><h2>Every competency, written the same way.</h2><ul><li><em>1</em><span><b>A clear statement.</b> <!-- -->One outcome, in one sentence, with no tool names.</span></li><li><em>2</em><span><b>Four level descriptors.</b> <!-- -->What changes in scope, autonomy and judgement from L1 to L4.</span></li><li><em>3</em><span><b>Evidence.</b> <!-- -->What an assessor accepts as proof at each level.</span></li></ul></div><div><div><span>Part III · Architecture &amp; systems design</span><span>Sample</span></div><h4><small>ARC-3.2</small>Design for failure</h4><p>Systems are designed so that expected faults degrade service gracefully instead of stopping it.</p><table><tbody><tr><th><i></i>L1</th><td>Recognises common failure modes in a given design.</td></tr><tr><th><i></i>L2</th><td>Applies established patterns such as retries and timeouts to a component.</td></tr><tr><th><i></i>L3</th><td>Designs failure handling across services and justifies the trade-offs.</td></tr><tr><th><i></i>L4</th><td>Sets failure-handling standards for an organisation or platform.</td></tr></tbody></table><div><span>Evidence: design review, incident record</span><span>TPBOK™ · sample page</span></div></div></div></div></section><section id="road"><div><div><div><p>Road to release</p><h2>Four stages to the first edition.</h2></div><p>Dates are announced once each stage closes.</p></div><ol><li><small>01</small><h3>Framework</h3><p>Agree the domains, levels and structure.</p></li><li><small>02</small><h3>Drafting</h3><p>Write the nine parts with working groups.</p></li><li><small>03</small><h3>Public review</h3><p>Open the draft for comment from the community.</p></li><li><small>04</small><h3>Publication</h3><p>Release the first edition, with exams aligned to it.</p></li></ol></div></section><section id="take-part"><div><div><div><p>Take part</p><h2>Help shape the first edition.</h2></div><p>The Guide is written with practitioners. Two ways to contribute before it is published.</p></div><div><div><small>Public review</small><h3>Review the open draft</h3><p>Read the draft when it opens and comment on any statement.</p><a href="mailto:standards@iictp.org?subject=Public%20review%3A%20TPBOK%E2%84%A2%20Guide">Register to review</a></div><div><small>Working groups</small><h3>Write a domain</h3><p>Experienced practitioners can join a domain group and help draft and test the statements.</p><a href="mailto:standards@iictp.org?subject=Working%20group%3A%20TPBOK%E2%84%A2%20Guide">Apply to join</a></div></div></div></section><section id="faq"><div><div><div><p>FAQ</p><h2>Questions, answered.</h2><p>Something else? Write to the standards team.</p><a href="mailto:standards@iictp.org?subject=Question%3A%20TPBOK%E2%84%A2%20Guide">Contact the team</a></div><div><details open=""><summary>When will the Guide be published?</summary><p>The first edition is planned for 2027. The date will be announced here once public review closes.</p></details><details><summary>Will the Guide be free to read?</summary><p>Professional members get free digital access to the complete Guide. Access for everyone else will be announced before publication. <a href="/#membership">See membership.</a></p></details><details><summary>How does it relate to the exams?</summary><p>Each IICTP exam is written against the Guide, and exams are updated whenever a new edition is published. <a href="/certifications/atp">See the ATP® exam.</a></p></details><details><summary>Is it tied to any vendor or tool?</summary><p>No. Statements describe outcomes, not products, so they stay valid as tools change.</p></details><details><summary>How often will it be revised?</summary><p>The Board of Global Standards reviews the TPBOK™ every year and validates the exam question banks. <a href="/about/board-of-directors">Meet the board.</a></p></details></div></div></div></section><section><div><h2>Find your place on the map.</h2><p>Leave your email and we will send you the Guide the day it is published.</p><form><div><label><span>Your work email</span><input id="notify-close" type="email" required="" placeholder="Your work email" autoComplete="email" value=""/></label></div><small>We will write once, when the Guide is published. This opens your email app to send the request.</small></form></div></section></div><!--/$-->]]></content:encoded></item></channel></rss>
