What is an IDR in an IRS audit?

An Information Document Request, Form 4564, is the IRS's standard written request for records and explanations during an examination. IDRs are not self-enforcing — a taxpayer who does not respond faces an escalation process (delinquency notice, pre-summons letter, then an administrative summons) rather than an immediate penalty. Most exam disputes are shaped by how IDRs are scoped and answered.

Can you negotiate the scope of an IDR?

Yes. IRS procedures direct examiners to discuss each IDR with the taxpayer before issuing it, state a single issue per IDR, and agree on a reasonable response date. Taxpayers routinely narrow date ranges, substitute samples for full populations, and clarify ambiguous terms. Negotiation happens before the IDR is finalized; once issued, the response date drives the enforcement clock.

What happens if you ignore an IDR?

Under the IRS's enforcement process, a missed IDR deadline triggers a delinquency notice with a new short deadline, then a pre-summons letter escalated to taxpayer management, then an administrative summons. A summons is enforceable in federal district court, and contesting it is expensive and rarely successful. Silence converts a document dispute into a compulsory-process dispute.

Should you screen documents for privilege before responding to an IDR?

Yes, before every production. Attorney-client privilege, the Section 7525 practitioner privilege, and work-product protection can all be waived by voluntary disclosure to the IRS. A privilege screen identifies protected material, logs it, and withholds it deliberately. Producing first and asserting privilege later usually means the protection is gone.

How are IDRs different in an R&D credit exam?

R&D credit exams typically open with a broad IDR seeking the credit computation, the business component list, and supporting documentation for qualified research expenses, then narrow to a sample of business components examined in depth. Negotiating the sample — its size, selection method, and how results extrapolate — is often the most consequential scoping decision in the exam.

IDR strategy: managing the information flow in an IRS exam

An Information Document Request — Form 4564 — is the basic unit of an IRS examination. Almost everything the exam team learns, it learns through IDRs, and almost every proposed adjustment traces back to what was produced, what was not, and how the production was framed. Managing the IDR flow is therefore not clerical work; it is the core of exam defense. This guide covers how IDRs are scoped and negotiated, the enforcement path when responses stall, the privilege screen every production should pass through, and the IDR patterns specific to specialty claims like the research credit and cost segregation.

It assumes you know the basic architecture of an exam; if not, start with how an IRS exam works.

What an IDR is, and what it is not

An IDR is a written request from the exam team for documents, data, or explanations. It is not compulsory process. The IRS's compulsory tool is the administrative summons under Section 7602, which requires court enforcement; the IDR is the cooperative instrument that precedes it. That distinction matters because it defines the taxpayer's real obligations: respond in good faith on the agreed schedule, or expect the escalation machinery to start.

IRS large-case procedures (originating in LB&I directives and now general practice) impose discipline on examiners too. Each IDR is supposed to state the issue being examined, be discussed in draft with the taxpayer, cover a single issue, and carry a response date set in consultation with the taxpayer. Examiners do not always follow this, but the procedures give taxpayers a legitimate basis to push back on omnibus, undated, or issue-less requests.

An IDR response is also an advocacy document. The examiner will read what you produce; a short cover narrative that explains what is attached, how it is organized, and how it answers the stated issue shapes the file the examiner writes from — and the file that IRS Appeals will eventually read. See the Appeals process overview for why the exam file matters downstream.

Opening conference: set the rules before the first IDR

The opening conference is where IDR practice for the whole exam gets established, and most taxpayers underuse it. Items worth agreeing on the record:

A single point of contact. All IDRs flow through one person (in-house tax director or outside representative under a Form 2848 power of attorney). No examiner interviews of employees without arrangement.
Draft IDRs before issuance. Ask that every IDR be shared in draft and discussed. This is consistent with IRS procedure and prevents scope surprises.
Response-time norms. A default response window (often 30 days for routine requests, longer for data-heavy ones) agreed up front avoids per-IDR fights.
Format conventions. Electronic production formats, Bates or control numbering, and how voluminous data (payroll extracts, general ledger detail) will be delivered.
The exam plan and timeline. Which issues, which years, and a target completion date. The statute of limitations is the backdrop to everything; see statute extensions and Form 872 for how the assessment clock interacts with exam pacing.

None of this is binding in a contractual sense. All of it changes examiner behavior.

Negotiating scope: the levers that actually move

When a draft IDR arrives, four levers are usually available.

Issue and relevance. An IDR is supposed to tie to a stated issue. A request for "all documents relating to research activities" in an exam nominally about one credit year invites a narrowing conversation: which business components, which cost categories, which period.

Time period. Requests routinely default to "all years" when the exam covers one or two. Confine productions to the years under exam unless a specific computational rule (base-period gross receipts, for example) genuinely requires history.

Population versus sample. For any request covering hundreds of items — projects, invoices, assets — propose a sample with an agreed selection method. Sampling is standard IRS practice in credit exams; the negotiation is over size and extrapolation, discussed below.

Form of response. A written narrative answering a question is often better for the taxpayer than a document dump the examiner characterizes unilaterally. Conversely, existing contemporaneous documents are better than after-the-fact narratives when credibility is the issue — a theme covered in audit-readiness documentation.

The enforcement escalation path

When IDR responses stall, the IRS follows a structured escalation process rather than moving straight to compulsion. The steps and typical timing:

The IDR enforcement timeline runs from missed deadline to court in a matter of months, with each step shortening the taxpayer's runway.

Stage	Trigger	Typical window	Who is involved
IDR issued	Scoping discussion complete	Agreed response date (often 30 days)	Examiner and taxpayer contact
Delinquency notice	Response date missed or response incomplete	New deadline, generally 10–15 business days	Examiner, with manager awareness
Pre-summons letter	Delinquency deadline missed	Roughly 10–15 more business days	IRS territory management; taxpayer executives copied
Administrative summons	Pre-summons deadline missed	Set appearance date	IRS counsel involvement begins
Summons enforcement	Non-compliance with summons	Government petition in district court	Department of Justice

Measured from the original response date, the runway is short:

Business days from a missed IDR deadline to each enforcement stagedays

Illustrative, based on the standard LB&I enforcement timeline; exact windows are set case by case.

Two features of this path deserve emphasis. First, it is largely mandatory on the IRS side once triggered — examiners in large cases have limited discretion to let a delinquent IDR drift, which means a taxpayer cannot assume an informal relationship will absorb a missed deadline. Second, each escalation raises the audience: the pre-summons letter goes over the tax department's head to company management, and a summons brings IRS counsel and eventually the Justice Department into what had been an accountant-to-accountant conversation. The standards a court applies to enforce a summons are minimal; see IRS summons enforcement and the Powell standards for why fighting at that stage rarely succeeds.

The strategic conclusion: fight about scope before the IDR issues, and about extensions before deadlines pass. The escalation path punishes silence far more than it punishes disagreement.

The privilege screen: before anything is produced

Every production should pass through a privilege review, however brief, because the protections at stake are fragile. Three doctrines matter:

Attorney-client privilege covers confidential communications with counsel for the purpose of legal advice. It does not cover the underlying facts, and it generally does not cover accounting work.
The Section 7525 practitioner privilege extends attorney-client-type protection to federally authorized tax practitioners — but only in noncriminal matters before the IRS or in federal court, and not to communications promoting participation in tax shelters. It is meaningfully narrower than the attorney-client privilege it mimics.
Work-product protection covers materials prepared in anticipation of litigation. Documents prepared in the ordinary course of compliance — including most credit-study workpapers — usually fail this test.

The critical operational point: voluntary production to the IRS generally waives these protections, and in most circuits waiver as to one document can reach related documents on the same subject. A privilege screen means someone with authority reviews the production set, pulls protected material, and records withheld items on a log provided to the examiner. Deliberate, documented withholding preserves the argument; inadvertent production usually ends it. The doctrinal detail — including why specialty-credit workpapers are the recurring casualty — is in privilege in tax matters.

Specialty-claim IDR patterns

R&D credit exams: the sampling negotiation

Research credit exams under Section 41 follow a recognizable IDR arc. The opening IDR requests the credit computation, the Form 6765 detail, the list of business components, and a description of the documentation supporting qualified research expenses. A second wave selects a sample of business components for deep examination — project records, technical interviews, wage allocations, contracts for any contract research.

The sample is where the exam is won or lost, because examiners extrapolate sample results across the population. Three things to negotiate before agreeing:

Selection method. Random or stratified selection defensible to both sides — not examiner cherry-picking of the weakest-looking projects, and not taxpayer selection of showcases.
Sample size relative to population. A five-project sample from a 400-project population produces wild extrapolation swings; push for a size that gives stable results or for stratification by dollar value.
Extrapolation ground rules. Agree in advance how a sustained disallowance percentage in the sample maps to the population, and whether qualitatively unique projects sit outside the extrapolation pool.

A fuller treatment of the substantive defense is at R&D credit audit defense.

Cost segregation exams: the component challenge

Cost segregation IDRs track the IRS's own Cost Segregation Audit Techniques Guide: the study itself, the preparer's qualifications and methodology, construction cost detail or purchase-price allocations, and support for specific asset reclassifications. The characteristic pattern is the component challenge — the examiner accepts the study's framework but disputes individual items (electrical distribution allocated to 5-year equipment loads, site improvements, decorative millwork) as structural components of the building.

The IDR-management implication: produce the study with its full workpaper trail intact, because a study whose allocations cannot be traced to source cost data invites wholesale rather than item-by-item challenge. And screen carefully — study drafts and provider correspondence are routinely requested, rarely privileged, and sometimes contain candid language the taxpayer would prefer not to explain.

Managing the record for Appeals and beyond

Every IDR response becomes part of the administrative file. Two disciplines protect the taxpayer's position downstream:

Answer the question asked, completely. IRS Appeals will discount arguments that depend on facts never given to the examiner, and new material introduced at Appeals can be routed back to exam for review, costing months. If the case goes further, the choice of forum — Tax Court before payment, or refund litigation after — is covered in Tax Court versus the refund forum.

Keep a parallel log. Maintain a running index of every IDR, its issue, the response date, extensions, what was produced, and what was withheld on privilege grounds. When the exam ends in a 30-day letter and the case moves to protest, that log is the skeleton of the file — and the proof, if it matters later, that the taxpayer cooperated.

The Taxpayer Bill of Rights includes the right to challenge the IRS's position and be heard, and the right to retain representation. In the IDR context those rights are exercised early and in writing — at the opening conference, in the draft-IDR discussion, and in the privilege log — not at the summons hearing, where they are worth very little.