Cannabis Record Retention: How Long to Keep Batch Records and Why

A batch record proves how a cannabis lot was produced, tested, and released, and the rule on keeping it is short, strict, and easy to fail: hold it for at least two years and be able to hand it to Health Canada quickly.

Cannabis record retention is the discipline of keeping every batch record long enough, and in a ready enough state, to satisfy a Health Canada request. Under the Cannabis Regulations, a Canadian licensed producer must keep its production and batch records for a minimum of two years and retrieve them within a reasonable time frame when the regulator asks. This page explains what the two-year minimum means, what “retrievable within a reasonable time” looks like in practice, why destroying records early is treated as a serious finding, and how to build a retention schedule and backup policy.

Retention is the last phase of the batch record lifecycle covered in our wider batch record keeping guide, the part that decides whether all the documentation upstream can still be produced when it counts.

What Is the Cannabis Record Retention Requirement in Canada?

The cannabis record retention requirement is the legal duty to keep batch and production records for a defined period and make them available on request. Under the Cannabis Regulations (SOR/2018-144), made under the Cannabis Act, a licensed producer must maintain records sufficient to allow complete reconstruction of how any cannabis product was produced, tested, and distributed. Those records must be kept for a minimum of two years and be retrievable within a reasonable time frame when Health Canada requests them, a duty reinforced by Health Canada’s good production practices guide.

Two years is the floor, not a target. Because a single lot moves through cultivation, harvest, testing, release, packaging, and distribution over many months, the practical effect is that you keep the full file well past two years from the seed, not two years from the day the batch number was assigned. When in doubt, keep longer. Over-retention is never penalised, and a longer hold protects you against recall and excise queries that can reach back further than the cannabis file alone.

The duty applies to the whole batch record package: the Certificate of Analysis, the QAP release sign-off, the cultivation and environmental logs, the harvest weights, the packaging records, and the distribution trail. It is the same evidence an inspector walks through at audit, and all of it must survive in a retrievable state for the full period. For everything that belongs in a complete file, see our cannabis batch record template.

What Does “Retrievable Within a Reasonable Time” Actually Mean?

The retrieval standard is the part of cannabis record retention that trips up producers who assume a stored record is a safe record. Keeping the file is only half the duty. The other half is producing it, complete and legible, within a reasonable time when Health Canada asks. The regulation does not pin a number of hours or days to “reasonable,” and that is why it has teeth: the inspector judges it in context. A lot record assembled from a searchable system in an afternoon reads very differently from one that takes a week of digging through archive boxes. In practice, “retrievable within a reasonable time” means three things hold true for any archived batch at any moment:

• The record exists in full. Every component of the batch file, from propagation source to distribution trail, is present. A retrieved record with gaps is not complete, and an inspector reading gaps treats the file as unreliable.
• The record is findable by batch or lot number. You can locate the entire package from the unique lot identifier alone. A consistent batch number across every document is what makes this possible.
• The record is legible and readable. Paper has not faded or been damaged, and digital files open in software you still run. A record you cannot read is, for audit purposes, a record you cannot produce.

This is where the paper versus digital question stops being academic. A digital system that indexes every lot and lets you pull the full file in minutes meets the reasonable-time standard comfortably. A physical archive can meet it too, but only with a disciplined index and well-controlled storage. We compare the two approaches in electronic batch records for cannabis.

It is worth separating retention from version control, because the two are often confused. Retention governs the batch records, the lot-specific history of what was actually made. SOP version control governs the procedures that told staff how to make it. They answer different questions: the batch record proves what happened to this lot, the SOP archive proves which version of the procedure was in force when it happened. A retention schedule that forgets the procedure versions referenced inside its batch records leaves a gap an inspector will find.

Why Is Destroying Records Early a Serious Compliance Finding?

Destroying a batch record before the retention period ends is one of the more serious findings a Health Canada inspection can raise, and it sits in a different category from a missing initial or an undated log entry. Most batch record deficiencies are problems of quality: a gap in the environmental log, a correction without a notation, a Certificate of Analysis filed away from its production data. Those are fixable. Destroying a record early removes the evidence entirely, in breach of an explicit retention duty.

It lands so hard because the inspector cannot un-destroy the record. A documentation gap has a path to corrective action: tighten the procedure, retrain the team, show the control is now in place. With a destroyed record, the lot’s history is simply gone, and the ability to reconstruct how that product was produced, tested, and distributed is lost with it. That reconstruction ability is the entire point of the recordkeeping duty, so its loss is treated as a direct failure of the obligation, not a quality near-miss.

The cause rarely matters as much as the absence. An over-zealous archive purge, a box discarded in an office move, a file lost to a failed drive with no backup, and an intentional deletion all leave the same hole, and the producer carries the burden of explaining why a record that should exist does not. The discipline that prevents all four is the same: a retention schedule paired with a backup policy. It is also why the data integrity rule never to delete or overwrite an entry extends to never destroying the whole record early, the subject of our guide to cannabis batch record data integrity.

How Do You Build a Cannabis Record Retention Schedule and Backup Policy?

A retention schedule is a written policy stating, for each record type, how long it is kept, where it lives, who controls it, and how it is eventually destroyed. It turns the two-year minimum into an operational rule the whole team follows, and paired with a backup policy it is the strongest defence against the early-destruction finding. A workable schedule answers the same questions for every category of record:

The backup line deserves emphasis, because the most defensible schedule fails if the only copy of a record lives on one unbacked-up drive or in one cardboard box. The aim is simple: no single failure, whether a fire, a flood, or a dead hard drive, should be able to destroy a record before its retention period ends. The closing step of any schedule is the archive itself, where the record is closed, indexed, and held for the minimum period. A controlled archive with an accessible index is exactly what the audit-readiness checklist calls for, and it makes the retrieval test a non-event. The record that authorises the lot for sale, the QAP batch release, must survive in that archive; for how that sign-off is created, see our guide to cannabis batch release.

When batch records live in a seed-to-sale operations platform, retention and retrieval stop being a manual filing problem. Every sensor reading, feed log, and QAP sign-off is timestamped and linked to the batch, the archive is indexed by lot number, and backups are part of the system. What used to take days to assemble for an inspector takes minutes. GrowerIQ is cannabis seed-to-sale and operations software used by 200+ licensed facilities across 9 countries.

Frequently Asked Questions

How long must a cannabis licensed producer keep batch records in Canada?

A Canadian licensed producer must keep batch and production records for a minimum of two years under the Cannabis Regulations. Two years is the floor, not a target. Because the records must also be retrievable within a reasonable time, and because recall and excise matters can reach back further, many producers hold their batch records well beyond the minimum. Over-retention is never a compliance finding. Destroying a record before the period ends is.

What does “retrievable within a reasonable time” mean for cannabis records?

It means you can produce a complete, legible batch record on request from Health Canada without an unreasonable delay. The Cannabis Regulations do not fix a number of hours or days, so an inspector judges it in context. In practice the full record exists, it is findable by batch or lot number alone, and it is readable, on paper or digitally. A record pulled from an indexed system in minutes meets the standard; one that takes a week of digging through archive boxes does not.

Why is destroying cannabis batch records early treated as a major violation?

It removes the evidence of how a lot was produced, tested, and distributed, which is the entire purpose of the recordkeeping duty. Unlike a documentation gap that can be fixed with retraining and a tightened procedure, a destroyed record cannot be recovered, so the lot’s history is permanently lost. The cause rarely matters as much as the absence: an accidental purge, a lost box, a failed drive with no backup, and an intentional deletion all leave the same hole an inspector treats as a serious breach.

Is cannabis record retention the same as SOP version control?

No. Record retention governs the batch records, the lot-specific history of what was actually made, tested, and shipped. SOP version control governs the procedures that told staff how to do the work. They answer different audit questions: the batch record proves what happened to a specific lot, while the SOP archive proves which version of a procedure was in force at the time. Both belong in a retention schedule, because a batch record references the procedure versions used.

What should a cannabis record retention schedule and backup policy contain?

A schedule should name every record category, state the minimum retention period of at least two years for batch records, define the storage location and format with an index keyed to the lot number, and set out a controlled destruction step authorised and documented only after the period has elapsed. The backup policy should protect against single points of failure: routine digital backups with an off-site or separate copy, controlled duplicates or digitisation for critical paper, and a restore process that is actually tested.

Get the Full Batch Record Keeping Guide

The free guide maps the two-year retention rule to the full lifecycle of a cannabis batch record, from the anatomy of a compliant lot file and the data integrity correction rule to the QAP release sign-off and an audit-readiness checklist your quality team can run before the next Health Canada inspection.

Download Free Guide