Working on Hart-Scott-Rodino Filing Document Checklist? The so what is simple: if the file cannot show authority, version, evidence, threshold, deadline and owner, the final legal or commercial decision is harder to trust. If you use Caira, upload the relevant files and turn the record into a reviewable checklist.
Open Caira
Start with the decision the file needs to support. Then build the evidence index before conclusions harden. Separate missing information, business decisions, legal assumptions and filing mechanics. Keep dates, document versions and named owners visible from the start.
Official Data Points To Anchor The File
Use these source-backed checks to make the page practical rather than generic.
HSR filing analysis starts with transaction structure, acquiring and acquired persons, size tests and exemption review.
Item 4 documents include certain studies, surveys, analyses and reports prepared by or for officers or directors to evaluate the transaction.
HSR files should track drafts, board materials, banker books, ordinary-course analyses and filing-control decisions separately.
So What
Hart-Scott-Rodino Filing Document Checklist matters because the risk is usually not one missing paragraph. It is traceability. You need to organize antitrust filing inputs before a transaction team starts chasing exhibits, while keeping source authority, operative documents, approval mechanics, evidence ownership and unresolved assumptions separate.
The goal is not to replace a source document with a summary. The goal is to make the record easier to inspect: what was requested, what rule or contract term controls it, what was approved, what evidence supports it, what is missing, what has been escalated and what still needs a responsible decision.
Practitioner Note
HSR work can look like a form exercise until someone asks why a particular officer presentation, banker book or market-share analysis was included or excluded. The file needs to answer that question without reconstructing the process from inboxes weeks later.
The better approach is to treat filing control as its own workstream. Keep transaction structure, Item 4 review, revenue data, exemptions and draft filing materials distinct, but connected by one decision log.
Common Issues This Solves
This issue usually shows up in practical ways. Deal teams need entity, control and revenue data before final form preparation. Board and strategy materials can be collected too late.
It also creates review friction later. Transaction-value changes can affect fee and filing support. Final exhibit packages need reconciliation to the submitted form.
Documents To Collect
transaction agreement and structure chart
acquiring and acquired person entity lists
revenue, NAICS and financial statements
prior acquisitions and minority holdings
Item 4-style studies, analyses and board materials
HSR form draft and filing-fee support
Authorities And Records To Check
Start with the authority or record that controls the issue, then check the actual document set in front of you. Where state, agency, court or county rules differ, keep the jurisdiction-specific authority and the reviewed document together.
For this page, the authority check should stay tied to the actual file. FTC premerger notification sources and HSR form instructions anchor the document checklist. The first task is to map the transaction parties and control relationships. Revenue and entity data should be version-controlled. Filing exhibits should be tracked from first collection through final submission.
Review Points For The File
Use this as a compact review table. It keeps the legal source, the working document and the final disposition in the same line of sight.
Check | What To Confirm |
|---|---|
Authority | Identify the governing statute, rule, form, agency guidance, court record, county rule or contract provision before drafting. |
Version | Lock the document draft, exhibit set, source page or PDF, review date and signer or filing status. |
Issue type | Tag each point as approval, filing, notice, closing condition, confidentiality, deadline, monetary exposure, control failure or remediation. |
Evidence quality | Distinguish primary documents from summaries, screenshots, management explanations, review notes and unresolved assumptions. |
Disposition | Record the owner, authority reference, document cite, proposed action, final decision and date closed. |
How To Use This Checklist
Work from one index before any memo, filing, notice or redline is finalized. Create a column for source authority and a separate column for the actual file or exhibit that supports the point. Mark each gap as factual, legal, commercial, filing, notice, approval or evidence-quality so the next reviewer knows what kind of problem it is.
Keep a short decision log for items closed by business judgment, risk acceptance, revised drafting or further review. Flag stale materials explicitly before reuse. That gives the next reviewer a clean path from source material to decision.
Questions To Ask Caira
Useful prompts are narrow and document-based; they should force the file into a table, timeline or exception list. Which entities are within each filing person. What transaction structure is being reported.
What financial and revenue data supports the form. Which studies, analyses or board materials need exhibit review.
Short FAQ
What should be collected early? Entity charts, revenue support, transaction documents and board or strategy materials.
Why version control board decks? Filing review can turn on which transaction analysis was final or circulated.
Should exhibit control wait until filing week? No. Build the exhibit tracker during collection.
Red Flags To Separate
The warning signs are easiest to miss when they appear as small recordkeeping problems. Entity chart inconsistent with the agreement. Revenue source files not dated.
Board materials collected late. Transaction value changes without a fee-support update. Final filing package not reconciled to the submitted form.
Practical Output
A good finished file should be small enough to review quickly and detailed enough to reconstruct later. Keep source documents, working notes and final outputs separated so the trail stays clean. In practice, that usually means producing HSR input request list, entity and control map, revenue support table, exhibit collection tracker and final filing package index.
