Building an Audit-Ready Classification File: Evidence, Citations, and Version History

An audit-ready classification file is a dated, self-contained evidence package that lets a reviewer who has never seen the product identify the article as imported, verify the facts relied on, repeat the General Rules of Interpretation analysis against the HTSUS revision in force for the entry, inspect the authorities cited, trace the decision to the entries that used it, and read every later change without any earlier version having been overwritten.

No regulation prescribes that package as one form. It is assembled from three layers: records required under 19 U.S.C. § 1508 and 19 CFR Part 163, the facts CBP says it needs to classify, and the controls CBP asks about in a Focused Assessment.

The Deadlines the File Is Built Backward From

Design the file for the proceeding that will test it, because each one runs on a different clock and asks a different question.

The first two triggers often get confused. The 30 days on Form 28 runs from the date of the request. The 30 calendar days under § 163.6(a) run from receipt. An extension under § 163.6 must reach CBP before the due date, state a requested period, and explain the circumstances, and it takes effect only if approved. Failing to produce a demanded entry record carries exposure under 19 U.S.C. § 1509(g), where the negligence penalty for each release does not exceed $10,000.

The Control Record That Opens Every Decision

Each decision should open with a read-only manifest. Nothing in it is analysis. Its job is to make the decision addressable, so a sampled entry resolves to exactly one version of one decision.

• Unique decision ID, plus the prior-decision and superseding-decision IDs.

• Product master ID, SKU, model, style, and the aliases suppliers and invoices actually use.

• Importer of record, business unit, manufacturer, and supplier.

• Status: draft, approved, active, suspended, superseded, or withdrawn.

• Preparer, technical reviewer, approver, and approval timestamps.

• Decision date, effective-from date, effective-through date, and next-review date.

• The 10-digit number, article description, units of quantity, base rate, and any separately analyzed Chapter 98 or Chapter 99 provision.

• The HTSUS edition and revision applied, with the archived release file.

• The affected entry population, or a query rule that reproduces it.

• The broker-instruction version, proof of transmission, and legal-hold status.

Keep the Chapters 1 through 97 classification separate from additional duties, exclusions, preference claims, admissibility, origin, and marking. The tariff number drives those outcomes, but each carries its own analysis and data, and collapsing them into one field is how a Chapter 99 overlay ends up undocumented.

Product Facts a Reviewer Cannot Infer

A reviewer should never have to work out the imported condition from a marketing name. 19 CFR § 177.2 sets the benchmark: a full description, and where germane, chief use, commercial or technical designation, relative quantity by weight and volume and value of materials, prices, drawings, samples, and laboratory analysis. CBP’s eRulings requirements name the same territory, adding component materials, principal use, flow charts, chemical analysis, and CAS number.

Translated into file contents, the evidence section holds:

• A plain-language description of the article as imported, covering assembly state, classification-relevant packaging, accessories, and whether the item is complete, unfinished, unassembled, a mixture, composite, set, part, accessory, or multi-function article.

• Function and operation, and principal or class-or-kind use wherever a candidate provision is use-controlled.

• Composition with percentages by weight, volume, quantity, and value where legally relevant, plus every specification threshold named in the candidate provisions or notes.

• Bills of material, drawings, datasheets, laboratory reports, photographs, labels, and packaging, each carrying its source, author, issue date, and revision number.

• Written answers from engineering, sourcing, or the supplier, preserving the question, the respondent’s role, and the date.

• The variants the decision covers, and an express statement of which are excluded.

Generic labels do not clear this bar. CBP’s cargo-description guidance treats “auto parts,” “plastic goods,” and serial numbers alone as unacceptable, asking instead for a description that identifies the commodity’s characteristics.

The gap is usually upstream of compliance. A global logistics company brought Gaia Dynamics’ classification platform a catalog whose descriptions were too thin to classify at scale. One original description was the single word “Module,” which received a Gaia description score of 5 out of 100.

From an importer name, a shipper name, and that one word, Gaia’s Description IQ feature produced a full electronic and optical module assembly description plus a reasoning block enumerating the missing determinants: material composition, physical characteristics, manufacturing process, function and end use, and essential character. It also recorded why confident classification beyond chapter level was impossible without them. Recording what was missing is stronger evidence than asserting a code.

Writing an Analysis Someone Else Can Repeat

The memorandum has to be reproducible rather than conclusory. In Nature’s Touch Frozen Foods (West) Inc. v. United States, No. 2023-2093 (Fed. Cir. 2025), the court described classification as a two-step inquiry, first construing the tariff terms and then deciding whether the goods fall within them, and applied the General Rules of Interpretation in order. A file that jumps to essential character without disposing of GRI 1 has skipped a step a reviewer will notice.

Eight elements carry the weight:

• State the question presented as the exact product in its exact imported condition.

• State the proposed result: the 10-digit statistical reporting number, the legal description, and the HTSUS revision applied.

• List only the material facts that drive inclusion, exclusion, or the choice between competing provisions, each linked to its evidence item.

• Name every candidate heading seriously considered, not only the winner.

• Identify the first GRI that resolves the heading, and say why earlier rules did or did not resolve it.

• Quote the operative language of each relative section, chapter, or Additional U.S. note, recording “none identified” only after a documented check.

• Map each legal element to a verified fact, state why each rejected alternative fails, and apply GRI 6 against provisions at the same level.

• Label each authority by weight: binding legal text, a binding ruling for the recipient on matching facts, precedential opinion, persuasive ruling, nonbinding Explanatory Note, or agency guidance.

Record the conditions the result depends on and the change trigger attached to each. Preserve reviewer comments and their disposition rather than deleting them once resolved, because an argument raised and answered is itself evidence that a control operated.

How to Cite Authority So It Can Be Retraced

A citation that cannot be retraced forces the reviewer to redo the research, and a reviewer who redoes the research may reach a different answer.

Tariff text: Cite the edition, the revision, the release date, and the exact legal unit, then archive the release file. The live schedule changes during the year: the USITC archive listed 2026 Revision 18, dated September 2, 2026, while the live site still displayed Revision 17.

A complete tariff citation includes:

• HTSUS edition, revision number, and release date.

• GRIs applied (e.g., GRI 1 and GRI 6).

• Section and chapter notes cited (e.g., Section XVI, Note 2(a)).

• Heading and subheading cited separately, with article description excerpt.

• Archived release PDF and the date checked.

Rulings: Capture the prefix and exact number, date, title, stable CROSS URL, the HTSUS edition the ruling used, the facts material to the holding, and a comparison against the current product.

CBP Headquarters Ruling H301778 (June 4, 2024): issue and holding at pinpoint in saved copy, CROSS URL, status checked [date].

Under 19 CFR § 177.9 a ruling represents CBP’s position for the transaction described, and persons other than the recipient should not assume it governs another transaction. When a relied-on ruling is modified or revoked, keep both. Under 19 CFR § 177.12, final modification or revocation of a ruling in effect for 60 or more days generally takes effect 60 calendar days after final publication in the Customs Bulletin, a date to record separately from the date the team found out.

Cases and regulations: Give the case name, docket, court, year, pinpoint, and the proposition the pinpoint supports, then note the subsequent-history check. For regulations, cite the smallest operative paragraph and the currency date (19 CFR § 163.5(b)(2)(i) rather than § 163.5 at large). And do not cite the HTS table of contents, index, chapter titles, or informational footnotes as though they were operative: legal text runs to the GRIs, Additional U.S. Rules, General Notes, legal notes, and headings and subheadings through the 8-digit level.

Why an Approved Decision Is Never Edited in Place

CBP’s Focused Assessment pre-assessment questionnaire asks, in terms, whether a classification database archives previous versions and how long those versions are kept. No primary source sets a required schema or duration, so the defensible design is the conservative one: treat every approved decision as immutable and open a new version for any substantive change.

Each version event should record five things:

• Old and new tariff number, description, rate, and units.

• Change type: whether a schedule amendment, a ruling issued or revoked, a court decision, a design change, an error correction, or a CBP instruction.

• Five separate dates: identification, source publication, legal effect, internal approval, and entry implementation.

• Authorities added or superseded, with archived copies.

• Affected SKUs, brokers, and entry population, together with the treatment of unliquidated and liquidated entries.

Separating those dates is the point. “Decision date” does not answer when a code legally or operationally applies, which is why the status vocabulary has to distinguish approved-but-future from active, and superseded from withdrawn. A superseded version stays valid as the authority for entries filed inside its window. A withdrawn version should never have been used at all, and its affected-entry population is the input to any prior disclosure analysis counsel later runs.

Superseded versions stay locked and searchable rather than archived out of reach, because a reviewer sampling a three-year-old entry needs the version that governed it, not the current one. Add a conspicuous banner and a successor link to the old memorandum, but never swap out source documents, alter timestamps, or clean up reasoning that was actually used at the time.

Storing the File So It Still Counts as a Record

Under 19 CFR § 163.5(a), covered persons keep required records for the full retention period as original records, in paper or electronic form, unless an alternative storage method is adopted under § 163.5(b). Original is not a synonym for paper. An email, a database record, an electronically signed approval, or a born-digital specification can be an electronic original. Scanning a paper original and discarding the paper is alternative storage, and it carries conditions.

Those conditions are specific. The recordkeeper gives Regulatory Audit advance written notice at least 30 calendar days before implementation and states that the method complies with § 163.5(b)(2). Written procedures must preserve integrity, readability, and security, with standardized retrieval and indexing. Importers keep entry records in original format through the specified 120-calendar-day post-release or redelivery period, packing lists excepted. System testing runs yearly, hard-copy reproduction happens at the recordkeeper’s cost, and one working copy plus one backup stay in a secure location for the full retention period.

Two points are worth correcting in your own procedures. The 120 days is an original-format rule inside the alternative-storage regime, not the retention period. And the regulation lists machine-readable data, CD-ROM, and microfiche as examples rather than an approved-product list, so no primary source blesses PDF, a named cloud platform, or any document-management system as automatically compliant.

Retention triggers deserve equal care, because 19 CFR § 163.4 does not run one clock.

A classification master record often supports entries filed years after it was written, so calculate destruction eligibility from the last supported entry, not the memo’s creation date.

Running a Production Drill on a Single Entry

The only reliable way to find out whether the file works is to pick an entry line at random, hand it to someone who did not write it, and set a deadline shorter than CBP’s. Require the output as a hard copy restored from the backup set rather than assembled from the working copy, because § 163.5(b)(2) asks for both a hard-copy reproduction capability and a backup kept available for the full retention period. Then log every step that depended on someone remembering something, since each is a control that exists only in a person.

Drills fail in three predictable places: the evidence carries no revision or date, the ruling was cited by number with no fact comparison, and the current code has overwritten the one actually filed. The first two are fixed by capture discipline at the point of decision, including a dated record of the precedent search that found nothing on point as well as the one that did. The third is fixed only by architecture, and it has to be fixed before the entry that gets sampled.

See how Gaia Dynamics helps teams build and maintain audit-ready classification files at scale. Start a free trial.

Frequently Asked Questions

Is a classification memorandum legally required?

No primary source requires every importer to create a standalone classification memorandum with prescribed fields. What is required is broader: records made or normally kept that pertain to entry, under 19 U.S.C. § 1508 and 19 CFR Part 163. Specifications, drawings and approval records sit inside that universe.

How long should superseded versions be kept?

CBP’s pre-assessment questionnaire asks whether prior versions are archived and for how long, without stating a duration. The period follows the underlying record: five years from the date of entry for entry-related records under 19 CFR § 163.4, subject to its exceptions and to other Title 19 provisions.

Does a binding ruling replace product evidence?

No. Under 19 CFR § 177.9 a ruling governs the transaction it describes, and application depends on the actual goods matching the described facts and conditions. The file still needs evidence proving that match, the ruling’s own HTSUS edition, and a dated status check, since rulings can be revoked.

Can the file live in a database?

Yes. No regulation mandates a folder structure, a PDF, or any named platform. A database or document-management system meets the objective if it preserves relationships, integrity, access history, prior versions, retrieval within a reasonable time, and the required source formats. Conversion of paper originals still follows 19 CFR § 163.5(b).

What should the file record when nothing changed?

Record the negative findings and date them. A check that found no relative chapter note, a CROSS search returning nothing on point, and a review confirming the tariff text was unchanged are all evidence that a control operated. A file with no negative results looks like one nobody read.