Skip to content

Capture and Conflict Audit

Investigative audit — instantiates Institutional Rule–Role Stabilization

A periodic investigation that checks whether an institution has quietly started serving narrow interests, and surfaces the role conflicts and conflicts of interest that let it happen.

A Capture and Conflict Audit is a point-in-time investigation that hunts for capture — the slow drift by which an institution comes to serve insiders or a dominant faction rather than its stated purpose — and maps the conflicts of interest and overlapping roles that enable it. Its defining feature is that it looks backward and deep: it samples what actually happened and follows the relationships behind it, producing findings and evidence rather than a live score or a routine ritual. It exists because capture is nearly invisible from inside — it feels like normal practice to the people living it — so someone has to go looking on purpose.

Example

A city's contracting office keeps awarding work to the same three vendors. An audit pulls a sample of awards and traces the people behind them: who sat on the evaluation panels and what ties they had to bidders; where a single official held both the role that wrote the specifications and the role that chose the winner (a role conflict that concentrates power); and whether "emergency" no-bid exceptions cluster around particular firms. The findings name two evaluators with undisclosed prior consulting for a winning vendor and a deputy director who both drafted specs and chaired awards. The output is evidence and a recommendation — separate those two roles, stand up a recusal register — handed to whoever has the standing to act. It is not itself a verdict.

How it works

What distinguishes it: adversarial sampling (follow the money and the relationships, not the paperwork's self-description), role-overlap tracing (find where one person or clique holds mutually-checking roles), exception-pattern testing (does discretion bend toward the same beneficiaries?), and a written findings record. It investigates the past; it does not run continuous meters, and it does not decide the remedy.

Tuning parameters

  • Auditor independence — internal versus external. An outsider sees capture that insiders have normalized, but costs more and may miss context.
  • Depth vs. breadth — a deep dive on a few cases or a shallow scan across many.
  • Trigger — a fixed calendar, or fired by dashboard red flags and complaints.
  • Disclosure scope — findings to the board only, or public. Public bites harder but chills candour.
  • Conflict threshold — how close a tie has to be before it counts as a conflict worth logging.

When it helps, and when it misleads

Its strength is naming what the institution cannot see about itself: an independent, investigative look is often the only thing that turns "this feels off" into evidence of regulatory capture[1]. Its failure modes: it is retrospective (by the time it finds the drift, the damage is done); it can itself be captured (an auditor beholden to the audited); and it finds the documented conflicts while the real arrangements stay off the record. The classic misuse is commissioning an audit designed to exonerate — scoping it narrowly enough to miss the problem. The discipline is to guarantee the auditor's independence, route findings to an actor with real teeth, and pair it with continuous monitoring so trouble surfaces before an audit cycle comes round.

How it implements the components

  • capture_and_legitimacy_monitor — the audit is the investigative instance of this monitor: it actively detects drift toward narrow-interest service.
  • role_conflict_register — it surfaces and records the conflicts of interest and role overlaps that concentrate power against the institution's purpose.

It does not run continuous at-a-glance indicators — that's the Institutional Health Dashboard; it does not perform the routine legitimacy-renewal cadence — that's legitimacy_review_cycle; and it maps conflicts but does not itself hear the affected parties — that's the Affected-Party Review Panel.

References

[1] Regulatory capture — George Stigler's account of how a body created to regulate an industry can come, over time, to advance that industry's interests instead. The term is used here for institutional capture in the general sense, not regulation alone. ↩