Draft Response To Information Document Request

Skill: Draft Response to Information Document Request (Multi-Issue Examination)

1. Subject-matter triage

• Treat the task as a two-document drafting exercise: a formal agency-facing IDR response letter and a separate privileged internal tax memorandum.
• Start by mapping each request item to one of three paths: produce, object/clarify, or seek extension/hold for later production.
• If the IDR spans multiple tax themes, enumerate them first and draft one response path per issue rather than collapsing them into a single generalized response.
• Keep any internal risk assessment, legal strategy, or privilege analysis out of the response letter.

2. Failure modes the skill is correcting

• Merging the production letter and the internal analysis into one document, which breaks the privilege boundary.
• Responding to requests narratively without tying each request item to a specific production, objection, or timing status.
• Omitting a production index or similar tracking structure that shows what was produced for each request.
• Failing to separate issue-specific tax standards and instead applying a single generic merits test across all requested topics.
• Failing to identify and protect work product or attorney-client material prepared in anticipation of dispute or examination.
• Leaving withheld materials off the privilege log or describing them too vaguely to support the claim.
• Reaching legal conclusions without naming the controlling authority that supports the position.

3. Legal frameworks / domain conventions that apply

• Two-document structure: The formal response letter is an external record of compliance and objections; the internal memo is a privileged advisory document addressing audit risk, corrective actions, and strategy.
• Item-by-item response convention: An IDR response should mirror the request sequence, with each item answered distinctly and with no hidden cross-references that force the reader to infer the production.
• Production appendix practice: Use a production schedule or appendix that identifies each request item, the materials produced, and Bates ranges or other location references.
• Privilege and work product: Attorney-client communications and materials prepared in anticipation of litigation or adversarial proceedings may be withheld or redacted if the protection applies. State the basis for the claim and keep the analysis in the internal memo.
• Privilege log practice: For each withheld item, list enough non-substantive information for the reviewing party to assess the claim: document type, date, author, recipients, protection asserted, and a neutral description.
• Research-credit conventions: For software, development, or systems work, distinguish baseline research analysis from internal-use software analysis where a heightened standard may apply; migration, platform, and infrastructure work often require that separate lens.
• Intercompany / transfer-pricing conventions: For related-party services or charges, identify the governing agreement, the pricing method, and the principal support materials used to substantiate the charge.
• Controlling authority convention: Each tax or privilege position should be anchored in a named authority, such as the Internal Revenue Code, Treasury Regulations, IRS guidance, or the Federal Rules where applicable.

4. Analytical scaffolds

• Document triage

  • Enumerate each IDR item and assign it a status: produce in full, produce in part, object, request clarification, or request additional time.
  • For each item, determine whether the underlying documents are responsive, privileged, or both.
  • If multiple project types, periods, entities, or transaction streams are in scope, address each one separately rather than using a representative sample.

• Response letter scaffold

  • Open with a professional acknowledgement, a reservation of rights as appropriate, and a brief statement that the response is organized item-by-item.
  • For each request item: state the response status, identify the responsive materials, note any objection or limitation, and reference the production appendix.
  • Where documents are withheld, reference the privilege log without revealing protected substance.
  • Keep substantive tax analysis out of the letter unless needed to explain a narrow objection or production limitation.

• Audit-risk memo scaffold

  • Organize by issue area, not by document source.
  • For each issue, identify the audit risk, the governing tax framework, the facts that increase or reduce exposure, and the likely practical consequence if the IRS disagrees.
  • Include corrective actions that improve the record before, during, or after the examination.
  • Address privilege status separately from merits analysis when recommending whether documents should be withheld or redacted.
  • End with a short action plan assigning ownership and timing.

• Issue-specific tax analysis

  • For software or development claims, distinguish internal-use functions from customer-facing or product-development functions, and evaluate the heightened standard where relevant.
  • For related-party charges, analyze the agreement, pricing methodology, and corroborating support for each stream independently.
  • For uncertain deductions, credits, reserve positions, or capital-versus-expense questions, state the governing rule and the practical evidentiary gap before recommending a response posture.

• Privilege/work-product analysis

  • Identify whether a document was created for legal advice, examination defense, or anticipated dispute.
  • Distinguish business documents from legal analyses.
  • If a document is only partially protected, consider redaction rather than full withholding where feasible.

5. Vertical / structural / temporal relationships

• Preserve the separation between the external response and the internal memo at all times; the response letter should not preview confidential strategic reasoning.
• Track how each request item relates to the production set, the underlying transaction or project period, and any later supplement that may be needed.
• Where a request reaches across multiple tax years, projects, entities, or transaction phases, keep those streams distinct in both the response and the memo.
• Align the timing of recommendations with the examination posture: immediate preservation steps, near-term production clean-up, and longer-horizon remediation should be distinguished.

6. Output structure conventions

• Deliver exactly two documents:
  • a formal IDR response letter for the IRS, and
  • a privileged internal tax memorandum.
• The response letter should:
  • follow the request sequence;
  • use short, formal paragraphs or a numbered response table;
  • include a production appendix or schedule with item-by-item document references;
  • reference any privilege log for withheld materials;
  • avoid substantive internal strategy analysis.
• The privileged memo should:
  • be labeled privileged and confidential;
  • organize analysis by issue area;
  • identify audit risks, applicable authorities, and likely consequences;
  • include concrete corrective actions and strategic recommendations;
  • contain a final recommended actions section with responsibility and timing.
• Use conventional tax-and-examination drafting style, with precise terminology and no extraneous narrative.