What governance approach is described as best for preventing omissions of requirements?

• A. Strict penalties
• B. Public awareness campaigns
• C. A team approach
• D. Individual accountability

Answer: (C)

A team approach emphasizes collective oversight and shared responsibility, which helps ensure no requirement gets overlooked. When multiple people review plans, their different areas of expertise and perspectives create built-in redundancy. One reviewer’s blind spots are caught by another, and the group can cross-check compliance against codes and standards, catch ambiguities, and raise questions early. This collaborative process encourages thoroughness, improves communication, and formalizes checks through shared procedures like design reviews and checklists, so omissions are less likely to slip through.

Strict penalties focus on punishing mistakes after they happen, which can deter carelessness but doesn’t help prevent omissions in the first place. Public awareness campaigns aim at external audiences rather than internal review quality. Focusing on individual accountability places the burden on a single person and may fail when that person is overwhelmed or unavailable, leaving gaps. The team approach, by distributing responsibility and enabling ongoing verification, provides proactive protection against missing requirements.