A team wants entity types for “anything we might audit someday,” in…

Question

A team wants entity types for “anything we might audit someday,” including inactive side projects with no current program. What alignment should leadership enforce?

Accepted Answer

Align entity types to agreed in-scope populations for active programs, not speculative someday lists. — “Someday audits” make a wonderful wish list and a terrible entity-type backlog. Build types for populations active programs already agreed to govern. Speculative shelves of empty types just confuse admins and never get owned.

Answer

Build entity types for every speculative future audit topic before programs exist.

Answer

Disable entity types entirely until the next external audit letter arrives.

Answer

Create empty entity types with no table so future audits can fill them ad hoc.

A team wants entity types for “anything we might audit someday,” including inactive side projects with no current program. What alignment should leadership enforce?

Short Explanation

Full Explanation