Sec Examination Audit Findings Memo

Skill: Audit Findings Memorandum for SEC Examination Deficiency Letter

1. Subject-matter triage (only if applicable)

• Treat the assignment as a privileged board-level issue memo grounded in the examination record, not as a generic summary.
• First separate: (i) alleged conduct that may support an enforcement theory, (ii) disclosure or control gaps that are independent compliance issues, and (iii) any factual assertions in the deficiency letter that may be inaccurate or overstated.
• If multiple findings, identify them all before analysis and keep each finding distinct; do not compress different deficiency types into one blended narrative.
• Where the source record gives dates, periods, client counts, accounts, trades, communications, or amounts, carry those facts into the analysis to show scale and operational reach.
• If the record contains a single item in a category, state that affirmatively; otherwise enumerate the full set of affected items, periods, or counterparties before drawing conclusions.

2. Failure modes the skill is correcting

• Characterizing allocation deficiencies without testing the underlying records for intent, consistency, and favoritism, which can understate scienter and enforcement risk.
• Missing disclosure deficiencies that may stand alone even if related operational findings are disputed.
• Failing to test whether the deficiency letter’s factual premises are accurate against the underlying documents.
• Treating compliance failures as isolated mistakes when the record supports a programmatic or supervision-level defect.
• Omitting how the compliance function’s awareness, inaction, or dual-role status affects both firm and individual exposure.
• Recommending a response without distinguishing findings that should be conceded, corrected, or contested.
• Presenting legal conclusions without naming the controlling authority that supports them.
• Drafting recommendations that do not identify the responsible function and the timing of the next step.

3. Legal frameworks / domain conventions that apply

• Securities fraud and adviser misconduct analysis should distinguish between intent-based theories and negligence-based theories under the applicable federal securities laws and adviser standards, including the anti-fraud provisions of the Advisers Act and any parallel Exchange Act provisions implicated by the record.
• Allocation practices must be tested for fairness, consistency, and adherence to stated policies; evidence of systematic preference, side arrangements, or post hoc rationalization materially worsens exposure.
• Personal trading and front-running analysis turns on timing, instrument overlap, and pattern; repeated trading ahead of clients may support an inference of misuse of material nonpublic or order-flow information.
• Disclosure analysis should check whether the current adviser disclosures, offering materials, and client-facing documents fully describe material conflicts, related relationships, compensation interests, and other decision-relevant facts.
• Marketing and performance issues should be tested for completeness and balance, including whether omitting adverse periods, assumptions, or limitations created a misleading presentation.
• Recordkeeping analysis should assess whether business communications and related records were preserved according to applicable retention requirements and whether failures appear isolated or systemic.
• Compliance program review should compare the manual and procedures against current regulatory obligations, update cadence, implementation evidence, and supervision structure.
• Investor remediation should track who was harmed, how they were affected, and whether notice, correction, reimbursement, or other remediation is warranted.
• The memorandum should cite the controlling authority for each legal proposition relied upon, including the relevant statute, regulation, rule, or recognized doctrine.
• The overall tone should be privileged, practical, and board-facing: identify risk, legal basis, evidentiary support, and response path without overstatement.

4. Analytical scaffolds

• For each finding, state the deficiency, identify the controlling authority, summarize the supporting record, and explain why the issue matters legally and operationally.
• Rank findings by severity using an explicit ordinal scale: Critical, High, Medium, Low. Apply the same scale consistently across all findings.
• For allocation-related findings, test whether the evidence shows a neutral operational error, a recurring pattern, or intentional favoritism; if the record supports intent, say so and explain the enforcement consequence.
• For personal trading findings, compare trade timing, direction, security overlap, and any communications that suggest advance knowledge or coordination.
• For disclosure findings, compare the alleged omission against the current disclosure set and any related internal materials to determine whether the issue is independent, duplicative, or cured.
• For recordkeeping findings, assess scope, retention gaps, and whether voluntary disclosure or remediation would likely improve the posture.
• For compliance manual findings, identify the last revision date, isolate post-revision requirements not reflected in the manual, and characterize the gap as structural if the record supports that conclusion.
• For deficiency-letter accuracy, test each material assertion against the source record and note where the letter appears factually wrong, incomplete, or overstated.
• For remediation, tie the corrective step to the affected population and to the firm function that must execute it.

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

• Intent evidence in allocation or trading findings can dominate the overall risk picture; if present, it should elevate the severity of related findings and inform the response strategy.
• Compliance awareness and inaction can convert a process issue into a supervision issue; address that interaction wherever the record supports it.
• A disclosure gap may persist even if an operational practice is changed, so distinguish forward-looking fixes from retrospective correction.
• If the deficiency letter contains multiple periods or iterations, analyze each period separately before stating whether the problem is persistent, episodic, or remedied.
• If remediation steps depend on board approval, legal review, or regulatory timing, note that dependency explicitly.

6. Output structure conventions

• Draft a privileged audit findings memorandum for the board in a conventional memorandum form, with a short executive overview followed by issue-by-issue analysis.
• Include a brief severity key at the outset and apply the severity field to every finding.
• For each finding, include: the issue, severity, governing authority, evidentiary basis, why it matters, and recommended response action.
• Organize findings in descending severity, but keep closely related findings grouped only if their legal theories and evidence materially overlap.
• Include a section addressing whether the deficiency letter is factually accurate or needs correction in the response.
• Include a section on examination response strategy that distinguishes conceded points from disputed points and addresses the potential value of cooperation credit.
• Include a remediation and investor notification section if clients, accounts, or investors may have been adversely affected.
• End with a Recommended Actions block that uses imperative verbs, identifies the responsible role or function, and states the timing anchor from the record or, if absent, the next regulatory or board milestone.
• If the source materials specify a response deadline, place it prominently in the memorandum.