The Filing Is an Evidence Package, Not a Questionnaire
The KKR enforcement matter makes one point difficult to ignore: an HSR filing can exist as a file and still fail as an account of a transaction. The central issue here is how the Form's assertions are supported by financial reports, affidavits, certifications, estimates, transaction documents, and a bounded document search. Seeing those parts as one evidence package helps a reader distinguish a technically submitted document from a complete and reliable representation.
A filing speaks through the evidence attached to it
The HSR Form is the part that readers see, but the agencies receive a larger package. The instructions direct parties to submit the completed Form together with documentary attachments to the FTC's Premerger Notification Office and the DOJ's premerger unit. The filing person is the ultimate parent entity, or UPE, yet the information behind the Form may come from controlled operating entities, the acquired assets, transaction counsel, finance teams, and deal decision-makers. The Form is therefore an interface between a legal representation and many underlying records.
That interface has a legal voice. An affidavit must attest to the good faith of the person filing to complete the transaction. Outside a Section 801.30 transaction, the affidavits from the filing parties must also attest that a contract, agreement in principle, or letter of intent has been executed and that the parties intend in good faith to complete the transaction. In a Section 801.30 transaction, the acquiring person's affidavit has a different set of attestations, including notice to the issuer or unincorporated entity, public announcement in the case of a tender offer, and good-faith intent. The point is not that every deal uses the same affidavit. The point is that the signature is tied to the transaction posture and to a representation made by the filing person.
The certification is another link between the package and the person responsible for it. The instructions require notarization or the statutory language for an unsworn declaration under penalty of perjury. That requirement is meaningful only if the people signing can connect the certification to the scope decisions, data sources, document collection, and qualifications in the filing. A signed page does not independently prove that the response is complete. It makes the quality of the underlying process more consequential.
The instructions provide a controlled way to deal with information that is not exact. If a filer cannot answer an item fully, they must provide the information available and a statement explaining the non-compliance. If an exact answer cannot be given, the filer may enter a best estimate, but must identify its source or basis and mark the item with “est.” Financial information is expressed in millions of dollars and rounded to the nearest one-tenth of a million. These are not invitations to guess. They are rules for making the limits of the evidence visible instead of hiding them behind a blank field or an overly precise number.
This distinction matters in the KKR context because the public enforcement materials describe alleged incomplete or inaccurate filings, while not supplying the internal records or decision path behind each transaction. A reader can understand why an evidence trail matters without claiming to know which person made which decision. A process that preserves the source and basis of an estimate can be reviewed and corrected. A silent omission gives the reviewer no equivalent way to tell whether the information was unavailable, overlooked, considered irrelevant, or never sought.
The dynamic PDF reduces some mechanical risk but does not take ownership of the legal judgment. The FTC's Form Tip Sheet says that the Form can fill redundant fields, expand as needed, and offer dropdowns for common responses. It also displays a list of missing mandatory items. But the same guidance calls that list merely a guide and says the filing party remains responsible for submitting a complete, accurate filing. The attachment page similarly helps link documents to Items 4(b), 4(c), and 4(d), but a dropdown cannot decide whether the underlying document belongs in the response or whether the description identifies it adequately.
The form's behavior can even create new points of failure if people mistake automation for proof. The tip sheet warns that certain attachment-description formatting can interfere with dropdown menus, that some fields may need to be reentered, and that the document should be saved often and rechecked because of the form's complexity. The current filing guidance adds a more basic boundary: submitted documents must be separate searchable PDFs or Excel files, must not be password-protected or restricted by permissions, and must be free of viruses or malware. A scanned document may require optical character recognition so a reviewer can search and copy its text.
These requirements connect mechanics to agency usability. A file that cannot be searched, opened, or associated with the correct item does not convey the evidence as intended. The electronic-submission guidance requires first-page markings identifying the filing person, the document identifier used in the Form, and the date of the Form. It also gives naming conventions for the Form, affidavit, certification, cover letter, and item-numbered attachments. Those conventions do not decide whether a filing is substantively accurate, but they make the package traceable: a reviewer can move from an assertion to a file and from that file back to the filing's date and identity.
A useful model is not “form plus miscellaneous attachments,” but “claim plus support plus accountability.” The claim is a response in the Form. The support may be a report, a transaction document, a revenue record, or an analysis. Accountability comes through the affidavit, certification, item description, document metadata, and retained copy. If one component changes, the relationship among the others needs to remain intelligible.
The diagram's relationships explain why scope errors travel. If the filing person or acquired perimeter is wrong, the evidence population can be wrong. If the evidence population is wrong, the attachments and certifications describe an incomplete picture even when every required field is colored or every file has a valid extension. The agencies' ability to review the transaction depends on the links between these components, not merely on their presence in the same upload.
Item 4 asks why a document belongs, not whether it contains a keyword
The most revealing evidence boundary appears in Item 4. Item 4(c) covers studies, surveys, analyses, and reports prepared by or for relevant officers or directors to evaluate or analyze the acquisition in relation to market shares, competition, competitors, markets, potential sales growth, or expansion into product or geographic markets. The question is not whether a document contains the word “market.” It is whether the document's content, purpose, authorship, and context place it inside the defined transaction-analysis population.
The FTC's Item 4(c) guidance gives investment committee memoranda and board presentations as common examples. A document that discusses the pros and cons of an acquisition or the target's fit with a buyer's business can be responsive when the other criteria are met. Management presentations may also qualify. The common thread is analytical use in evaluating the acquisition, not a particular file name or department.
Purpose and context can change the answer. An ordinary-course competitor overview created for a company's quarterly business review does not normally become an Item 4(c) document simply because an officer later consults it while considering an acquisition. The original reason for creating it matters. But the same kind of ordinary-course material can become part of a responsive document if it is circulated with transaction-specific analysis or placed in a deal notebook with other responsive materials. The PNO guidance also describes a buyer's use of a seller's ordinary-course material in a data room: if an officer of the buyer removes, prints, or downloads the material, and it contains the relevant analytical content, it may be responsive for the buyer under the circumstances described.
Email creates another context problem. If an email contains Item 4(c) content, the email and its attachments are submitted together when the other criteria are met, even if an attachment does not independently contain that content. If the email has no such content but an attachment does, the attachment may be submitted separately. A reply or forward need not be added merely because it continues the chain, unless it contains additional responsive content. The PNO's example treats a chain with responsive material as one document and calls for the relevant date range and authors and recipients in the log.
This is why both under-collection and over-collection can be symptoms of a weak process. A keyword sweep can miss a presentation whose title says little but whose analysis evaluates competition. It can also collect a due-diligence request list that merely asks for a market snapshot without analyzing the market. Public-announcement materials such as a press release or investor presentation are not responsive merely because they discuss the transaction; the guidance says they were created to announce the deal, not to evaluate it. A final document generally controls, but a draft sent to the Board can itself become responsive if it meets the other criteria.
Item 4(d) is related to 4(c), but it is not a duplicate category. The formal instructions and PNO guidance divide it into three bounded populations. The first is a confidential information memorandum, or CIM, prepared for relevant officers or directors of the acquiring or acquired person and specifically related to the sale of the acquired entity or assets. The second is a study, analysis, or report prepared by an investment banker, consultant, or other third-party adviser for those decision-makers for the purpose of evaluating the acquisition. The third covers studies or reports evaluating merger-specific synergies or efficiencies.
The boundary is important for both scope and time. The first two Item 4(d) categories are limited to documents produced up to one year before the filing date. That one-year rule does not automatically erase older transaction analysis: the PNO says an older document responsive to Item 4(d) may still be responsive to Item 4(c), which has no stated time limit in the instructions. A search that applies the one-year limit to every transaction document can therefore be under-inclusive.
Nor does Item 4(d)(i) mean that every document in a data room is a CIM. If a genuine CIM exists for the transaction within the relevant period, the guidance says to provide it. If no CIM exists, the question is whether the seller gave the buyer a document specifically intended to serve that function, not whether every ordinary due-diligence file was shared. A series of presentations covering topics usually found in a CIM may be relevant under Item 4(c) without becoming a CIM under Item 4(d)(i). The seller may still need to provide a CIM even if it was not given to the actual buyer, while multiple CIMs prepared for different bidders do not all become the actual buyer's CIM for this purpose.
Third-party material has a similarly bounded search. Item 4(d)(ii) reaches adviser work prepared during an engagement or while seeking an engagement when it meets the purpose and transaction-specific criteria. The guidance gives bankers' books or pitchbooks as common examples but says other proposed-option analyses can qualify. It also says the item does not require a separate search of every third party, such as every investment banker or law firm involved in a transaction. The relevant officers and directors identified in the Item 4(c) search help define the people whose files and requests need attention.
Synergy documents require more than a label. A document that merely says a deal will create synergies, without a quantified amount, is not automatically responsive under the PNO guidance. A financial model without stated assumptions is also insufficient for Item 4(d)(iii); the document needs narrative explaining the assumptions. A tax-synergy reference alone is not merger-specific, although a document that combines tax synergies with merger-specific synergies may be responsive. These distinctions protect against a search that either treats every financial model as evidence or dismisses a substantive analysis because it lacks a familiar title.
Finally, responsiveness has to remain traceable when documents overlap or information is withheld. The instructions require title, preparation date, and authors and titles for Item 4(c) and 4(d) documents, with further details for privilege logs. If a document responds to both items, it is listed only once under one of them. Item 4(c) documents use identifiers such as 4(c)-1, while Item 4(d) documents use 4(d)-1 without encoding the subcategory in the number. If a responsive document is withheld or redacted for privilege, the filing person must provide a log describing the document and the factual basis for the claim in enough detail for agency staff to assess it without revealing the protected material.
The practical standard is therefore bounded completeness. The team should be able to explain why it searched particular decision-makers and advisers, why a document was included or excluded, which time window applied, how an estimate was sourced, and how each attachment maps to the Form. That standard does not require attaching everything, and it does not make a privilege claim automatically correct. It requires the evidence package to preserve the reasoning behind its boundaries. Once those boundaries are set, the next challenge is to make the business data inside the package reconcile with the ownership and competitive-overlap picture the agencies must assess.