Compare Corporate Antitrust Compliance Program Against Doj And Ftc Guidelines

---
name: compare-corporate-antitrust-compliance-program-against-doj-and-ftc-guidelines
task_id: antitrust-competition/compare-corporate-antitrust-compliance-program-against-doj-and-ftc-guidelines
description: Closes gaps in organizing issues within a recognized antitrust compliance evaluation framework, identifying high-risk personnel categories requiring specialized training, and connecting material compliance events to program update obligations.
activates_for: [planner, solver, checker]
---

# Skill: Antitrust Compliance Gap Analysis

## 1. Subject-matter triage

- Treat the assignment as a comparison of a corporate antitrust compliance program against the DOJ/FTC compliance-evaluation framework, not as a generic policy summary.
- Separate design, implementation, and effectiveness issues; do not blend them into a single narrative.
- If the source set contains multiple entities, business lines, geographies, or time periods, enumerate them up front and analyze each materially distinct one separately.
- If only one entity or program is truly in scope, say so expressly and explain why.

## 2. Failure modes the skill is correcting

- The analysis collapses the program into a flat issue list instead of mapping each gap to the relevant compliance-prong analysis.
- The analysis fails to tie each issue to the specific source material that reveals it, leaving conclusions unsupported.
- The analysis identifies deficiencies but does not connect them to risk scale, interacting documents, or downstream consequences.
- The analysis omits the compliance significance of a material enforcement event, investigation, or related incident that should have triggered a program review.
- The analysis misses employee populations that require tailored antitrust training because of their role, market exposure, or transaction involvement.
- The analysis notes a deficiency without saying what should be changed, who should do it, and when it should happen.
- The analysis uses labels like “urgent” or “important” without an explicit ordinal severity scale.
- The analysis states legal conclusions without naming the controlling DOJ/FTC framework or other authority supporting the proposition.

## 3. Legal frameworks / domain conventions that apply

- Use the DOJ/FTC antitrust compliance evaluation framework as the organizing standard, with separate attention to program design, implementation, and effectiveness.
- Evaluate whether the program has clear governance, senior-management and board visibility, reporting lines, monitoring, discipline, and periodic review.
- Assess whether training is role-based and risk-based, with enhanced coverage for sales, pricing, procurement, M&A, trade-association participants, joint-venture personnel, and other high-contact market-facing teams.
- Consider whether foreign operations, acquired businesses, or local distribution channels are integrated into the program on a timely basis.
- Treat live or interactive reinforcement, audit coverage, hotline responsiveness, and policy refresh cadence as relevant effectiveness markers where the source materials bear on them.
- Use ordinary antitrust compliance terminology and cite the DOJ/FTC guidance or other controlling authority referenced in the source materials when stating a legal proposition.
- When the materials describe an investigation, enforcement action, or other material event, assess whether the compliance program was updated in response and whether the absence of an update itself creates a gap.

## 4. Analytical scaffolds

1. Build the analysis issue by issue under the three prongs:
   - Design gaps
   - Implementation gaps
   - Effectiveness gaps
2. For each issue, include all of the following:
   - a unique issue identifier
   - a concise statement of the gap
   - the source document or documents showing the gap
   - an explicit severity rating from a single ordinal scale defined once at the top of the memo
   - a short rationale for that severity
   - a specific remediation recommendation
   - a timing anchor for implementation
3. Close each issue by tying it to:
   - the scale or magnitude shown in the source materials, where available
   - the related policy, training, audit, or event record that interacts with it
   - the resulting compliance, operational, or enforcement consequence
4. Where the materials show a material event, compare it against the update history and identify whether the event led to a program, training, or governance change.
5. Where the materials identify employee populations, separate general populations from higher-risk groups and note any missing tailored content.
6. Where the record shows monitoring or audit activity, assess whether the coverage is periodic, documented, and capable of detecting repeat issues.
7. Avoid conclusory statements that are not anchored to a named authority, framework provision, or source document.

## 5. Vertical / structural / temporal relationships

- Use the program’s own structure to test internal coherence: governance should support training; training should reflect risk; monitoring should feed remediation; remediation should update the program.
- Track whether new facts in the source set post-date the last policy review, last training cycle, or last board report.
- Treat a failure to refresh the program after a material event as a temporal gap, not merely a historical fact.
- Compare central policy language against local practice, subsidiary practice, or business-line practice where the materials permit.
- If the materials show different treatment across regions, functions, or entities, identify the inconsistency and explain why it matters.
- If a source set has only one relevant time slice, state that no meaningful temporal comparison is possible.

## 6. Output structure conventions

- Begin with a short executive summary that states the overall risk posture and defines the severity scale once.
- Follow with three main sections:
  - Design gaps
  - Implementation gaps
  - Effectiveness gaps
- Within each section, use a compact issue register with one row or subheading per issue.
- For each issue entry, include:
  - issue ID
  - severity
  - source basis
  - gap description
  - rationale
  - remediation
  - timing
  - consequence
- Include a final Recommended Actions block that lists concrete next steps in imperative form, naming the responsible role or function and a timing anchor tied to the program cycle, board cycle, audit cycle, or regulatory milestone.
- If the source materials identify controlling DOJ/FTC guidance, statutory references, or other authorities, cite them by name and section or part when making the relevant legal point.
- Use conventional memo prose rather than a checklist dump; the memo should read as a professional gap analysis, not an outline of raw observations.
- Keep the deliverable focused on comparative analysis; do not reproduce source text except where a brief quotation is necessary to preserve a legal point and is otherwise permitted.