Analyze Ofac Investigative Demand And Related Transaction Records

---
name: its-analyze-ofac-investigative-demand
task_id: international-trade-sanctions/analyze-ofac-investigative-demand-and-related-transaction-records
description: Produces an issues memorandum in response to an OFAC investigative demand that analyzes potential civil and criminal exposure, evaluates compliance-program and mitigation considerations, and outlines immediate preservation and response steps.
activates_for: [planner, solver, checker]
---

# Skill: Analyze OFAC Investigative Demand and Related Transaction Records

## 1. Subject-matter triage (only if applicable)

- Treat the subpoena, investigative demand, transaction records, screening logs, internal communications, and any voluntary disclosure materials as a single record set.
- Identify all potentially implicated entities, business lines, officers, and transaction clusters before analyzing exposure; if only one entity or one transaction family is in scope, say so expressly and explain why.
- Separate three questions at the outset: what happened, who knew or approved it, and what remedial or disclosure steps were taken and when.
- Preserve all records immediately and frame the response around the agency deadline, any extension request window, and any document-retention hold needs.

## 2. Failure modes the skill is correcting

- Calculating civil exposure using only one penalty method when multiple methods may apply, or failing to compare methods entity by entity before aggregation.
- Listing compliance-control weaknesses without tying each one to the responsible-compliance-program mitigation argument.
- Treating disclosure timing as background rather than as a factor that can expand, reduce, or foreclose mitigation credit.
- Describing individual involvement without assessing whether the facts support separate personal exposure or separate counsel.
- Ignoring how screening configuration, designation dates, and transaction dates interact to show potential post-designation activity.
- Ending issues at description instead of closing each issue with scale, cross-reference, consequence, and recommendation.
- Stating sanctions conclusions without naming the governing statutory, regulatory, or enforcement authority.

## 3. Legal frameworks / domain conventions that apply

- Civil penalty analysis should compare every potentially applicable enforcement measure under the governing sanctions authority, including transaction-based and per-violation approaches where available, then apply the higher exposure as relevant to each entity and sum only after entity-level analysis.
- Voluntary self-disclosure analysis should address timing, completeness, and whether submission preceded agency action, because those facts bear on mitigation under the applicable enforcement framework.
- Criminal exposure analysis should assess whether any person directed, authorized, knowingly participated in, or concealed the conduct under the applicable sanctions statute and related criminal provisions.
- Compliance-program analysis should evaluate whether screening, escalation, training, ownership review, policy maintenance, and audit controls were designed and operating effectively; a gap matters most when it weakens a mitigation argument recognized by OFAC’s enforcement guidance.
- Egregiousness analysis should be organized under OFAC’s General Factors framework, including management knowledge, willfulness, harm to sanctions objectives, concealment, and the entity’s role in the transaction chain.
- Screening-log analysis should compare matching logic against aliases, transliterations, partial names, ownership data, and date triggers to test whether controls would have captured the relevant transaction set.
- Governing authority should be cited by name and section where possible, including the International Emergency Economic Powers Act, OFAC regulations in 31 C.F.R. chapter V, and OFAC’s Economic Sanctions Enforcement Guidelines in 31 C.F.R. part 501, appendix A.

## 4. Analytical scaffolds

1. Build an entity-and-transaction inventory: list each implicated entity, period, transaction family, and control trigger before analysis; if the record shows only one relevant entity or one relevant period, state that explicitly.
2. For each entity, analyze exposure under each potentially applicable civil-penalty method, identify the controlling authority, and compare the entity-level results before any aggregation.
3. For each transaction cluster, cross-reference the payment records, designation dates, screening logs, and escalation records to determine whether the conduct is pre- or post-designation, blocked, rejected, processed, or otherwise controlled.
4. For each disclosure event or non-disclosure, reconstruct the timeline, identify the responsible decision-maker, and assess the impact on mitigation credit under the relevant enforcement guidance.
5. For each officer or employee implicated by the record, assess involvement, knowledge, direction, approval, concealment, or delay, and analyze whether the facts support individual exposure or a separate counsel recommendation.
6. For each compliance gap, state the control weakness, identify the documents showing it, connect it to the mitigation factor or aggravating factor it affects, and explain whether it undermines or merely reduces mitigation.
7. For each violation or gap, close the issue with: a scale or threshold grounded in the record, a cross-reference to the interacting document or control, and the downstream consequence for the client.
8. Apply OFAC’s General Factors framework issue by issue, using the documentary record to separate aggravating from mitigating facts and to support any egregiousness discussion.
9. End with a recommended-actions block that prioritizes preservation, internal investigation, disclosure assessment, remediation, and deadline management.

## 5. Vertical / structural / temporal relationships (only if applicable)

- Compare transaction date to designation date, blocking date, escalation date, and any disclosure date; the order of those dates often controls whether an event is remediable, reportable, or aggravating.
- Map entity relationships, ownership, and payment flow to determine whether conduct at one level creates exposure for another entity in the group.
- Where screening or payment routing is repeated over time, distinguish isolated events from a pattern of conduct and note how that pattern affects severity and mitigation.
- Track whether policy, system, or ownership changes occurred before or after the relevant transactions, because post-incident fixes do not cure pre-change exposure but may support remediation credit.

## 6. Output structure conventions

- Write a partner-ready issue-identification memo with an opening summary that states the implicated entities, the core exposure themes, and any immediate preservation or response deadlines.
- Define a simple ordinal severity scale once near the top and apply it consistently to every issue entry.
- For each issue, use a consistent mini-structure: severity, issue statement, governing authority, record support, exposure analysis, mitigation or aggravation analysis, consequence, and recommendation.
- Include a separate section for individual exposure if any officer or employee appears implicated, with a separate-counsel recommendation where the record supports it.
- Include a compliance-program section that ties each control gap to the responsible-compliance-program mitigation analysis rather than listing gaps in isolation.
- State penalty exposure carefully: identify the relevant method, show the entity-level comparison, and then state the aggregate only after the comparison is complete.
- Include a closing Recommended Actions block with imperative action verbs, the responsible role, and a deadline or urgency anchor tied to the agency response or preservation need.
- Use the documents’ terminology for the conduct and entities where helpful, but do not reproduce short verbatim internal quotations except when a direct quotation is necessary to capture the record accurately.