Study guide
12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking
TOGAF Enterprise Architecture Practitioner OGEA-103
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Mechanics & Foundation Overview
1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise
2 Chapter 2: Preliminary Phase & Establishing the EA Capability
2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools
3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)
3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
4 Chapter 4: Business Architecture (Phase B)
4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates
5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)
5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements
6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)
6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions
7 Chapter 7: Technology Architecture (Phase D)
7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models
8 Chapter 8: Opportunities and Solutions (Phase E)
8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management
9 Chapter 9: Migration Planning (Phase F)
9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps
10 Chapter 10: Implementation Governance (Phase G)
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists
11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management
11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict
12 Chapter 12: Architecture Governance, Boards, and Dispensations
12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts
13 Chapter 13: Architecture Content Framework & Architecture Repository
13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
14 Chapter 14: EA Capability, Tailoring, and Iteration
14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security
12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking
Key Takeaways Explain This Topic AI
TOGAF describes a dispensation, also known as a waiver, as the alternate route to interim conformance when a compliance assessment is rejected.
Dispensations are granted for a given time period with identified service and operational criteria that must be enforced while they last; they are never indefinite.
A dispensation leaves the standard in force for everyone else, while an architecture change request revises the architecture or standard itself.
A practical lifecycle runs from identification and formal request through risk analysis and Board decision to monitoring and remediation closure.
Dispensation decisions and their rationale are recorded in the Governance Repository, and repeated similar dispensations should prompt a review of the policy or standard.
Last updated: October 2026
12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking
In an ideal enterprise, every software application, infrastructure platform, and operational process would achieve 100% compliance with defined target architecture models and enterprise standards. However, enterprise architecture operates within commercial realities characterized by aggressive competitor deadlines, supply chain disruptions, legacy dependencies, and mergers and acquisitions (M&A).
When a delivery project cannot achieve full compliance with enterprise standards, the TOGAF Standard provides a formal governance mechanism: the Architecture Dispensation . For practitioners preparing for the OGEA-103 examination, mastering dispensations requires a comprehensive understanding of when a dispensation is warranted, how it differs from an architecture change, the end-to-end dispensation lifecycle, and why certain standards are strictly non-negotiable.
What is an Architecture Dispensation?
An Architecture Dispensation is formally defined as a granted, time-bound, and auditable relief from the obligation to comply with a specific enterprise architectural standard, principle, policy, or target specification.
TOGAF's governance framework describes the dispensation (also known as a waiver) process. When a Compliance Assessment is rejected because the subject area (design, operational, service level, or technology) is not compliant, the subject area can either be adjusted or realigned to meet the requirements or request a dispensation . Dispensations are granted for a given time period and a set of identified service and operational criteria that must be enforced during their lifespan. They are not granted indefinitely, and their time-bound nature makes them a major trigger in the compliance cycle. On the Board's agenda, TOGAF describes a dispensation as the mechanism for requesting a change to existing architectures, contracts, or principles outside normal operating parameters, for example deploying non-standard technology for a specific business initiative.
Dispensations prevent two destructive organizational anti-patterns:
Unsanctioned Architectural Drift (Shadow IT) : Teams secretly bypassing standards without management knowledge, creating untracked security and operational liabilities.
Bureaucratic Gridlock : Projects being halted indefinitely because an inflexible standard cannot accommodate an urgent, transient business situation.
Dispensation vs. Architecture Change Request
Candidates frequently confuse dispensations with architecture change requests on the practitioner examination. The distinction is fundamental:
Attribute Architecture Dispensation Architecture Change Request (Phase H)
Nature of Deviation Temporary exception granted to a specific project or system. Permanent revision to the enterprise standard or baseline architecture.
Validity of Standard The enterprise standard remains valid and mandatory for all other projects. The underlying standard is acknowledged as obsolete, flawed, or superseded .
Duration Strictly time-bound with a mandatory expiration date (e.g., 90 to 180 days). Permanent until the next scheduled architecture revision cycle.
Remediation Requirement Mandatory, funded remediation plan required to restore compliance before expiry. No remediation required; the new standard becomes the compliant target state.
Governance Action Recorded in the Governance Repository (decision log and compliance assessments). Updates the relevant repository content, such as the Standards Library , principles, or baseline.
The 6-Stage Architecture Dispensation Lifecycle
TOGAF defines the dispensation concept; a practical six-stage lifecycle that implements it is: 1. Identification & Trigger ==> 2. Formal Request Submission ==> 3. Architectural & Risk Analysis
- ||
- 6. Remediation Verification <== 5. Active Monitoring in Log <== 4. Board Adjudication & Decision
- Stage 1: Identification & Trigger
Non-compliance is typically identified during early architecture reviews in Phase E or Phase F, or during formal Architecture Compliance Reviews in Phase G. The project solution architect and delivery lead recognize that meeting an enterprise standard (e.g., migrating to a corporate database standard) is physically, financially, or temporally impossible before the required deployment date.
Stage 2: Formal Request Submission
The project manager and solution architect complete a standardized Dispensation Request Form , documenting:
The exact standard, policy, or building block from which deviation is requested.
The commercial or technical justification necessitating the deviation.
The estimated cost and schedule impact of complying immediately versus deferring compliance.
The proposed duration and explicit expiration date of the dispensation.
Proposed compensating technical controls to mitigate operational and security risks.
An initial remediation strategy detailing how and when compliance will be achieved.
Stage 3: Architectural and Risk Analysis
The relevant Domain Architect and Information Security Architect evaluate the submission. They analyze:
Blast Radius : Does the deviation expose other interconnected enterprise systems to risk?
Technical Debt Accrual : How much additional engineering rework will be required to remediate the deviation later?
Adequacy of Compensating Controls : Are firewalls, tokenization, or manual monitoring sufficient to contain transient risk?
Stage 4: Architecture Board Adjudication
The Architecture Board reviews the request and renders one of three formal determinations:
Approved with Conditions : The dispensation is granted for a strictly defined period. The board attaches non-negotiable operational conditions (e.g., mandatory weekly audit log exports, penetration testing, and pre-allocated remediation budget).
Rejected : The dispensation is denied. The board determines that the deviation introduces unacceptable enterprise risk. The project must redesign its solution to achieve compliance prior to release.
Deferred / Returned for Clarification : Additional data, risk modeling, or vendor roadmaps are required before a determination can be made.
Stage 5: Active Monitoring and Registration in the Governance Repository
Upon approval, the dispensation is assigned a unique identifier (e.g., DISP-2026-088 ) and recorded in the Governance Repository of the Architecture Repository. The governance secretariat monitors active dispensations, generating automated 60-day and 30-day alerts to the project owner as the expiration date approaches.
Stage 6: Remediation Verification and Closure
Prior to the expiration date, the project team executes its committed remediation plan (e.g., upgrading the software, refactoring APIs, or cutting over to the approved corporate platform). A follow-up Compliance Review verifies full conformance. Once verified, the Architecture Board formally closes the dispensation in the Governance Repository. If remediation is not complete and no renewal is approved, the system falls into unauthorized non-compliance, triggering escalation to executive leadership.
Non-Negotiable Standards: When Dispensations Cannot Be Granted
A critical scenario-based exam concept centers on non-negotiable architectural standards . While the Architecture Board possesses substantial authority, it does not hold the legal or ethical right to waive certain categories of enterprise standards:
Statutory and Legal Mandates : Compliance with external laws (e.g., Sarbanes-Oxley, Health Insurance Portability and Accountability Act [HIPAA], Payment Card Industry Data Security Standard [PCI-DSS], General Data Protection Regulation [GDPR]). Granting an internal dispensation to violate external criminal or civil law is legally invalid and exposes the enterprise to catastrophic financial penalties and prosecution.
Fundamental Information Security Controls : Cryptographic baselines (e.g., prohibiting unencrypted plaintext transmission of customer passwords or banking data), multi-factor authentication (MFA) for administrative access, and perimeter isolation.
Life-Safety and Critical Infrastructure Policies : In industrial, medical, or aerospace architectures, life-safety automation and fail-safe shutdown protocols cannot be compromised for commercial deadlines.
If a project requests a dispensation that breaches statutory regulations or core cybersecurity controls, the Architecture Board is obligated to reject the request outright .
Recording Dispensations in the Governance Repository
In the TOGAF 10 Architecture Repository, dispensations and their rationale belong in the Governance Repository , whose decision log records standards deviations and Change Request decisions. TOGAF's Board responsibilities also include considering a policy change when similar dispensations keep being requested. A complete dispensation record contains:
- Field Description Example Entry
- Dispensation ID Unique tracking identifier DISP-2026-104
- Requesting System / Project System name and project code Global Payment Gateway (Project Atlas)
- Standard Deviated From Normative standard reference STD-SEC-044 : Mandatory TLS 1.3 Encryption
- Nature of Deviation Specific technical exception Temporary retention of TLS 1.2 for legacy POS terminals
- Business Justification Commercial imperative 2,400 legacy retail hardware terminals awaiting firmware update
Compensating Controls Risk mitigation mechanisms Dedicated isolated VLAN, WAF rate-limiting, daily anomaly scanning
- Board Approval Date Date of formal board decision October 4, 2026
- Strict Expiration Date Enforceable deadline for closure February 1, 2027 (Strict 120-Day Limit)
- Remediation Plan Owner Individual accountable for delivery VP of Retail POS Engineering
- Remediation Budget Allocation Financial commitment $350,000 committed in Q1 Engineering Budget
- Current Status Active lifecycle phase Active (Remediation In-Progress)
- Worked Practitioner Scenario: The Black Friday Trading Freeze
Scenario : Titan E-Commerce operates an online retail platform generating $40 million daily during the November-December holiday shopping season. In August, the enterprise architecture team publishes an updated Technology Standard mandating that all relational database clusters be upgraded to PostgreSQL v16 to address a low-severity query performance issue.
Project Mercury (the core checkout engine) is scheduled for code freeze on October 15. The database migration requires 4 weeks of schema testing, which would push database cutover directly into the peak Thanksgiving Black Friday shopping freeze.
Practitioner Decision Path :
The Project Manager and Solution Architect submit an emergency Dispensation Request to delay the PostgreSQL v16 upgrade until January 15.
Risk Evaluation : The vulnerability in PostgreSQL v15 is non-exploitable behind Titan's internal network perimeter. Conversely, executing a major database engine upgrade during Black Friday introduces extreme availability risk.
Board Determination : The Architecture Board unanimously approves a 90-Day Dispensation expiring on January 31. The board mandates compensating controls: 24/7 dedicated database monitoring during peak hours and pre-authorized Q1 budget allocation to complete the migration in January.
Outcome : Peak trading proceeds with 99.999% uptime. On January 20, the database migration is executed and verified. The Architecture Board formally closes DISP-2026-042 in the Governance Repository.
Common Exam Traps & Pitfalls
Trap 1: Believing Dispensations Can Be Permanent : An exam answer suggesting an "indefinite dispensation" or "permanent exception" is always incorrect. A permanent deviation is either an unapproved architectural defect or an unacknowledged Architecture Change Request.
Trap 2: Assuming Project Managers Can Grant Dispensations : Only the authorized Architecture Board (or its delegated domain sub-board) holds the authority to approve dispensations. Project managers cannot self-authorize waivers.
Trap 3: Waiving Regulatory or Security Mandates for Cost : Questions often depict a project running over budget and requesting a waiver on mandatory data privacy encryption. The Architecture Board must reject such requests; cost overruns never justify regulatory non-compliance.