What OIG Keeps Asking For — and Why ACP Actually Meets the Need

Framing Note

OIG recommendations are deliberately conservative.
They avoid prescribing systems, architectures, or tools.
Instead, they repeatedly call for clarity, consistency, documentation, and communication.

What they do not supply is a mechanism to make those things durable under:

  • rotation,
  • ambiguity,
  • time pressure,
  • and interagency friction.

This section shows where ACP artifacts function as the missing implementation layer.

Pattern 1: “Clarify Roles and Responsibilities”

Typical OIG Language

  • “Management should clearly define roles and responsibilities…”
  • “Staff were unclear about who had decision-making authority…”
  • “Lines of authority were not consistently communicated…”

What This Is Actually About

  • Authority is implicit.
  • Responsibility is diffuse.
  • Decisions rely on custom and personality.

Why OIG Recommendations Often Fail

Because “clarifying roles” is treated as:

  • an org chart update,
  • a staff meeting,
  • or a one-time memo.

None of these survive rotation or stress.

ACP Artifact Alignment

  • Authority Boundary Notes
  • Claim / Non-Claim Ledgers
  • Attribution Discipline Guides

These artifacts:

  • make authority inspectable, not inferred,
  • show where responsibility stops,
  • and prevent silent authority creep.

Net effect:
OIG’s call for “clarity” becomes operational, not rhetorical.

Pattern 2: “Improve Internal Communication and Coordination”

Typical OIG Language

  • “Improve communication between sections…”
  • “Ensure information is shared consistently…”
  • “Strengthen coordination mechanisms…”

What This Is Actually About

  • People do not share the same mental model.
  • “Coordination” fails because priorities are not explicit.
  • Staff are reacting to outputs, not reasoning.

Why OIG Recommendations Often Fail

Because communication is treated as:

  • more emails,
  • more meetings,
  • more reporting.

None of that aligns judgment.

ACP Artifact Alignment

  • Policy Priorities Map (by pillar)
  • Executive Summary (BLUF) Memos
  • Why This Matters / Who Cares sections

These artifacts:

  • encode shared priorities,
  • explain why something matters,
  • and allow different sections to reason consistently without syncing constantly.

Net effect:
Coordination emerges from shared logic, not constant synchronization.

Pattern 3: “Strengthen Oversight and Documentation”

Typical OIG Language

  • “Management did not adequately document decisions…”
  • “Records were incomplete or inconsistent…”
  • “Institutional knowledge was lost after staff turnover…”

What This Is Actually About

  • Decisions are made verbally.
  • Rationales are not preserved.
  • Continuity depends on people, not records.

Why OIG Recommendations Often Fail

Because documentation is treated as:

  • record-keeping after the fact,
  • compliance overhead,
  • or an admin task.

Not as a decision artifact.

ACP Artifact Alignment

  • Source Ledger / Claim Registry
  • Update Tracker (Delta Log)
  • Negative Findings Notes

These:

  • capture what was known and what was not,
  • preserve reasoning across rotations,
  • and create an auditable trail without retroactive reconstruction.

Net effect:
Documentation becomes governance, not bureaucracy.

Pattern 4: “Ensure Consistent Implementation of Department Guidance”

Typical OIG Language

  • “Guidance was applied inconsistently…”
  • “Sections interpreted policy differently…”
  • “Post practices diverged from Department intent…”

What This Is Actually About

  • Guidance is high-level and abstract.
  • Local application requires judgment.
  • Judgment is not scaffolded.

Why OIG Recommendations Often Fail

Because consistency is pursued through:

  • reminders,
  • re-issuance of cables,
  • or enforcement after mistakes.

Not through shared interpretive tools.

ACP Artifact Alignment

  • Terminology & Attribution Guide
  • What We Can Say / Cannot Say Sheets
  • Bounded Language Libraries

These:

  • standardize interpretation without eliminating discretion,
  • reduce drift in public and internal products,
  • and make divergence visible early.

Net effect:
Consistency becomes the default, not an enforcement problem.

Pattern 5: “Improve Training and Onboarding”

Typical OIG Language

  • “Staff lacked sufficient training…”
  • “Onboarding was inadequate…”
  • “Knowledge gaps affected performance…”

What This Is Actually About

  • Training teaches tasks, not judgment.
  • Onboarding is compressed.
  • Knowledge decays under pressure.

Why OIG Recommendations Often Fail

Because training is:

  • episodic,
  • decoupled from daily work,
  • and not reinforced structurally.

ACP Artifact Alignment

  • Artifacts as training anchors
  • Claim-discipline exercises
  • Source-triage rubrics

ACP assumes:

Training fails unless the environment enforces it.

Artifacts do that enforcement.

Net effect:
Training sticks because behavior is constrained afterward.

Pattern 6: “Strengthen Risk Management and Prevent Recurrence”

Typical OIG Language

  • “Post did not adequately identify risks…”
  • “Lessons learned were not institutionalized…”
  • “Similar issues recurred…”

What This Is Actually About

  • Risks are identified informally.
  • Lessons are verbal.
  • No mechanism prevents repetition.

Why OIG Recommendations Often Fail

Because “lessons learned” are:

  • written once,
  • filed,
  • and forgotten.

ACP Artifact Alignment

  • Negative Findings Notes
  • Decision Logs
  • Escalation Threshold Definitions

These:

  • preserve why something was not done,
  • prevent rumor-to-policy creep,
  • and institutionalize restraint.

Net effect:
Prevention replaces post-mortem.

What This Reveals (Quietly)

OIG has been diagnosing the same problems for decades.
Its recommendations are correct — but underspecified.

ACP does not contradict OIG.
It implements what OIG keeps asking for but cannot design.