Skip to content
Ameen Abozaid
Planned lessonARC-035-L04

Exceptions and conditions

  • Lesson 4 of 5
  • Architect
On This Lesson 4 topics

This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.

In this lesson

request design exceptions properly and track board conditions to closure.

Planned topics

  • An exception states the standard, why the solution cannot comply, the risk, the mitigation, an owner, and an expiry date.
  • No expiry date means a permanent exception by default; set a date or a trigger for revisiting.
  • Conditions are commitments: record each with owner, due date, and evidence of closure.
  • Report progress on conditions back to the board; ignoring them after approval costs trust.
Draft outline details

Demonstration

an exception record and a condition tracker, each with owner and date fields and a status column.

Check your understanding

Why must an exception have an expiry?

Show answer

Without one it becomes permanent and the risk is never revisited.

Practice

Apply this lesson with the module's lab, exercises and quiz.

Lab and exercises Quiz

Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.

Continue to next lesson

Type to search levels, phases, modules and lessons.