Textbook/Unit 06

Compliance by design

Obligations, consumer protection, fair lending, privacy, and partner oversight.

Unit 06 / The big picture

Make every obligation traceable.

A four-step descending traceability ladder connects obligation, control, evidence, and outcome. Questions at each step identify scope, required system behavior, proof events, and customer remedy. Each step connects to its policy, control, data, or service owner. A feedback arrow carries exceptions, complaints, and testing back toward correction.

Enlarge to read every label and explore the connections

A rule becomes reliable only when it maps to a control, observable evidence, and a customer outcome. Each link needs an owner and a tested correction path.

  1. Read down from the obligation to the customer result.

  2. Follow each row to its accountable owner.

  3. Use complaints and tests to find breaks in the chain.

Inside this unit

5 chapters
A queued notice is not a completed duty
6.1 / 14 min read

Compliance architecture and policy as code

Connect legal requirements to product behavior and retained evidence.

Read chapter
One report, two distinct processes
6.2 / 15 min read

Consumer protection, errors, and complaints

Design a clear path from customer report to a supported resolution.

Read chapter
Explain the decision that actually happened
6.3 / 15 min read

Fair lending, explainability, and adverse action

Evaluate decision quality and communicate the actual reasons.

Read chapter
Move useful evidence, not copies of secrets
6.4 / 15 min read

Privacy, payment data, and secure evidence

Protect the information that makes risk decisions possible.

Read chapter
Make the handoff accountable
6.5 / 15 min read

Sponsor banks, vendors, and third-party risk

Keep accountability visible across the financial-service supply chain.

Read chapter