Retention, Blanket Orders, and a Help-Desk Email
A statute governing licensed importers provides: "Each licensee shall retain records of every transaction for not less than three years from the date of the transaction." Your records team purges at the end of the third calendar year after the year of the transaction - for a January transaction, destruction lands at about 35 months. The agency's public FAQ says records must be kept "three years from the end of the calendar year in which the transaction occurred." A compliance analyst emailed the agency's public help desk and received the reply "your approach is fine." Two competitors were recently fined for failure to retain after producing incomplete records. The company also uses blanket purchase orders where releases and deliveries span several months. Six weeks remain before the next scheduled purge, and the deletion list has already gone to IT.
1. Interpret the retention trigger using the statute's text and structure, and resolve the blanket-purchase-order problem.
Read the worked answer
Text. The trigger is "the date of the transaction," not the end of a calendar year. "Not less than three years from" that date sets a floor measured backwards from destruction: destroying at 35 months for a January transaction is short by roughly a month, and for a February transaction by nearly two. The clause is a minimum, not a target, so the safest reading of the floor is preservation for at least 36 months after the last component of the transaction.
Structure and purpose. The FAQ inserts words ("end of the calendar year") that the legislature did not use and, for most of the year, shortens the obligation. An informal FAQ cannot override statutory text; at most it signals the agency's enforcement posture, which here would be wrong.
Blanket orders. Where a single purchase order generates multiple releases, shipments, and invoices, each release plausibly constitutes a separate "transaction" for records purposes. The conservative interpretation - retain from the earliest release until three years after the latest - is the only one that cannot produce a gap. Tying the clock to the order date alone risks purging delivery records still within the window.
Action. Suspend the purge today, before IT executes the list; a hold is reversible, deletion is not. Re-baseline the schedule as: latest underlying event + 36 months + a buffer for tolling, investigation, and lookback periods.
2. How much weight can the company place on the help-desk email, and what should replace it?
Read the worked answer
Weight: very little - and negative value if mishandled.
- It is informal staff advice, not a formal interpretation, opinion, or no-action position. It does not bind the agency, and estoppel against a regulator on the basis of staff error is rarely available.
- It is discoverable. Rather than a defense, it may be used to show the company knew the requirement was ambiguous and chose the reading that let it delete records sooner.
- Its author may have had no authority over retention policy at all.
What it is good for: evidence of good faith only if paired with a written, reasoned policy decision and evidence that the company sought clarity through the proper channel.
Replace it with:
- A written request for a formal interpretation or advisory opinion, framed around the blanket-order question so the answer is useful.
- An industry-association comment or petition if a formal route is unavailable.
- A contemporaneous internal memo recording the statutory analysis, why the conservative reading was adopted, and the residual risk accepted.
Framing for the board: the email is a data point about the agency's informal view, not an assumption the company can build a deletion program on.
3. Design the next six weeks of actions, including how to handle the open competitor enforcement trend and any exposure from records already deleted.
Read the worked answer
Weeks 1–2 - stop the bleeding. Halt the pending purge in writing; require dual approval and a documented legal/compliance sign-off before any future deletion job runs. Preserve everything relating to the current calendar year and prior two.
Weeks 2–4 - quantify. Sample already-deleted records to estimate which transaction types and periods fell short; separate "early purge" from "no record exists." For the blanket orders, build a data extract that maps releases to orders so the revised schedule can be automated.
Weeks 3–5 - fix the policy and the system. Rewrite the retention rule as event-driven (latest underlying event + 36 months + buffer), hard-code it in the records system, and add a pre-deletion exception check against holds.
Weeks 4–6 - communicate and document. Train the records team, notify the business units, and produce a memo recording the interpretive reasoning, the change, and the residual exposure.
On the competitor enforcement trend: treat it as a signal that the agency is testing this exact control. Do not self-report speculative gaps in the abstract; do prepare a factual summary so that if an information request arrives you can respond accurately and quickly. If a specific request touches a period where records were purged early, disclose the gap rather than let the agency discover it - incomplete production is the aggravating fact in the competitor cases, not the retention shortcut alone.