Draft Response To Ofac Pre

---
name: its-draft-ofac-ppn-response
task_id: international-trade-sanctions/draft-response-to-ofac-pre
description: Drafts a formal OFAC Pre-Penalty Notice response that checks the transaction list against internal records, tests the penalty calculation methodology, evaluates available compliance and reliance arguments, and presents alternative penalty scenarios for settlement advocacy.
activates_for: [planner, solver, checker]
---

# Skill: Draft Response to OFAC Pre-Penalty Notice

## 1. Subject-matter triage

- Treat the notice, source records, and compliance history as separate source layers; reconcile them before drafting any advocacy position.
- If the notice groups conduct by program, theory, or time period, enumerate those groups first and analyze each on its own terms.
- If the response is intended for a formal agency submission, prioritize accuracy, citation discipline, and a settlement-facing tone over narrative flourish.

## 2. Failure modes the skill is correcting

- Accepting the agency’s transaction count without independently verifying each listed transaction against internal records, which can leave duplicates, missing items, or misclassified entries unchallenged.
- Treating the proposed penalty as fixed instead of testing the governing penalty framework, eligibility criteria, and any stepwise calculation the agency used.
- Collapsing distinct legal theories into a single argument, which can obscure program-specific defenses and weaken the response.
- Relying on generic mitigation language without tying it to source documents, controls, certifications, escalation practices, or other record support.
- Presenting only one settlement number when the facts support multiple advocacy scenarios with different assumptions.
- Stating legal conclusions without naming the controlling authority that supports them.

## 3. Legal frameworks / domain conventions that apply

- Transaction verification: compare each listed transaction against internal ledgers, order records, screening records, and correspondence; identify items that are absent, duplicated, aggregated, misdated, or otherwise not fully supported.
- Penalty methodology: apply the governing sanctions penalty framework for the alleged conduct, reconstruct the calculation from the operative guidance, and test whether the agency used the correct base, tier, and adjustment methodology.
- Program-by-program analysis: separate allegations by sanctions program, restriction type, and theory of liability; for any narrower restriction, test the specific elements the rule requires rather than assuming a full-blocking standard.
- Compliance and reliance defenses: evaluate whether contractual screening duties, certifications, controls, approvals, or escalation channels support a good-faith reliance or mitigation argument under the relevant compliance-factor framework.
- Mitigating and aggravating factors: review the notice’s treatment of history, willfulness, cooperation, remediation, management awareness, and control environment; identify factual or evidentiary errors and tie corrections to the governing factors framework.
- Settlement advocacy: present alternative penalty scenarios that reflect distinct assumptions, including accepted items with corrected methodology, disputed items removed, legal theories narrowed, and a best-case combined position.
- Authority discipline: cite the controlling statute, regulation, guidance, or other authority by name and section for every legal proposition relied on.

## 4. Analytical scaffolds

1. Enumerate the transaction sets, allegation groups, and legal theories in scope before analysis.
2. Reconcile each listed transaction to source records; note whether it is supported, unsupported, duplicated, or disputed, and state the downstream effect on exposure and violation count.
3. Reconstruct the penalty calculation under the applicable framework; compare the agency’s proposed amount to a stepwise recalculation using the correct assumptions.
4. Test each defense independently: program-specific element failure, reasonable reliance, lack of knowledge, remediation, cooperation, and any other source-supported mitigation.
5. Align each factual correction to a specific exhibit, record, or internal document; do not make unsupported factual assertions.
6. Evaluate the notice’s aggravating and mitigating factors against the governing factors framework and correct any misstatements.
7. Build multiple settlement scenarios with explicit assumptions, then identify the advocacy position that is strongest on the record.

## 5. Vertical / structural / temporal relationships

- Track conduct by transaction date, screening date, shipment date, payment date, notice date, and remediation date when those dates matter to liability or mitigation.
- If one source document supersedes, clarifies, or conflicts with another, explain the hierarchy and the consequence for the response position.
- Where a counterparty, distributor, agent, or internal function had a screening or certification obligation, identify who had the duty, when it arose, and how the duty affects the reliance or mitigation analysis.
- If the notice spans multiple sanctions programs or phases of conduct, preserve that separation in both analysis and drafting so later settlement discussions can focus on the strongest subset of issues.

## 6. Output structure conventions

- Draft a formal pre-penalty notice response in a lawyerly tone with a clear introduction, factual background, legal arguments, response to the notice’s penalty analysis, requested relief, and conclusion.
- Use a numbered or otherwise clearly segmented structure that separates transaction verification, legal defenses, mitigation, and settlement position.
- Include a penalty scenario table with stated assumptions and results; each scenario should reflect a distinct analytic posture rather than a minor wording variation.
- Include a settlement-position discussion that explains why the requested resolution is supported by the record and applicable authority.
- Close with an explicit Recommended Actions block that identifies the next steps, the responsible role, and the timing anchor for submission or negotiation.
- Ensure the final deliverable file name is the named output artifact and that it contains operative response text, not a summary of what should be done.