Skip to main content
AREPractice Management

Obligation Hierarchy: Public Over Client Over Profession

Examines the tiered structure of an architect's professional obligations, where duties to public health, safety, and welfare supersede obligations to clients, which in turn outweigh duties to the profession itself. Covers when and how architects must prioritize conflicting duties, including whistleblowing obligations and the ethical framework that governs these decisions.

2 min read221 words

Why Public Duty Tops Everything Else

Architecture is one of the few professions where your license exists specifically to protect people who will never sign your contract. The entire regulatory framework rests on a single premise: architects protect public health, safety, and welfare first.

This creates a clear ranking of obligations. Public safety sits at the top. Client interests come second. The profession's interests rank last. That order is not a suggestion. It's baked into licensing laws, NCARB's Model Rules of Conduct, and the AIA Code of Ethics.

Why does this matter for the ARE? Because the exam loves scenarios where these obligations collide. A client wants to cut costs on a fire-rated assembly. A developer pushes back on accessibility requirements. Your employer tells you to ignore a code violation. In every case, the correct answer follows the same logic: public welfare wins.

NCAR's Model Rules state it plainly. The rules exist for the "protection of the public health, safety, and welfare" and explicitly not for "the advancement of the interests of the profession." Architects may be required to "insist on positions that are not in their clients' interest" when public safety is at stake.

This topic connects to nearly every other PcM concept you'll study. Risk management, contract negotiation, project delivery, firm operations. The obligation hierarchy is the ethical backbone that runs through all of it.

Want to track your progress and access more study tools?

Create a free account