Data Entry: Two Small Changes to a Rule You Already Follow (Proposed DCC Track-and-Trace Reporting, 4 CCR § 15049)
Status: Part of the DCC’s proposed track-and-trace overhaul, DCC-2026-02-R (noticed June 5, 2026). These are proposed amendments to the track-and-trace reporting section (§ 15049) and are not yet adopted law. Public comment is open through July 20, 2026; hearing scheduled for July 21. [1]
Of the six changes in the proposed track-and-trace overhaul, this is the one most operators will read and think: I already do this. Section 15049 governs what you put into the track-and-trace system and when. The proposal touches it in exactly two places, and neither one adds a field you don’t already record. What changes is when you enter an activity, and whether your unit of measurement has to match the one that was sent to you.
Where Track-and-Trace Stands Today
The daily discipline is already the law. Under current § 15049, every activity in the list—receiving cannabis, rejecting a transfer, manufacturing, internal quality-control use, destruction, packaging, laboratory sampling and testing, and sale or donation—must be recorded in the track-and-trace system within 24 hours of occurrence. For each entry, you already record the type of product, its weight, volume, or count, the date, the UID, and the brand name of the cannabis goods. [4]
The section already reaches further than the headline fields. When a product is destroyed, current law already requires notes naming the employee, the reason, and the method of disposal. A package adjustment already requires a written description of why the quantity changed. A partial rejection of a shipment already has to be recorded. None of that is new. This is the same recordkeeping muscle behind the 30-day reconciliation cycle we mapped in No. 02. If your CCTT already reconciles against your physical inventory every month, you are already living inside § 15049.
What the Proposed DCC Rule Changes
The proposal makes two substantive changes, both aimed at data accuracy rather than adding work. [1]
Record after the activity, not before (§ 15049(b)). Today the rule reads “within 24 hours of occurrence.” The proposal changes that to “within 24 hours after occurrence.” The Department’s stated reason is that some licensees enter activities up to 24 hours before they happen, so the record predicts the future instead of describing what actually occurred. If the expected activity does not occur, the licensee’s records are simply inaccurate. The fix is one word—“after”—and it expressly forbids pre-entering. [2]
Accept a transfer in the sender’s unit of measurement (new § 15049(c)(2)(A)). When you accept a transfer, you must record it using the same unit of measurement the initiating licensee used. The Department notes that receiving licensees sometimes accidentally enter different units—such as receiving 10 pounds but entering 10 grams—which causes significant data discrepancies. You can still repackage into a different unit after the cannabis is accepted into your inventory. The rule only governs the moment of acceptance, so the two sides of a transfer finally agree. [2]
The rest of the edits to § 15049 are housekeeping, not new obligations. Destruction of immature and mature plants is carved out of the 24-hour rule to resolve a conflict with § 15049.1(a)(3). A phrase pointing to a subsection that doesn’t exist is deleted. A typo in the authority note pointing to Business and Professions Code section 26169 instead of 26069 is corrected. Finally, the word “shall” becomes “must” throughout the text. None of these change what you do. [2]
Comparing the Entry Rules
Two rows carry a real change. Every other row reads “no change”—which is the point.
| Entry element | Current law | Proposed DCC-2026-02-R |
|---|---|---|
| When you record | Within 24 hours “of occurrence.” | Within 24 hours “after occurrence”—no entering an activity before it happens (§ 15049(b)). |
| Unit of measurement on acceptance | Not specified—a receiver can enter a different unit than the sender used (e.g., 10 lb → 10 g). | Must accept in the sender’s unit; repackaging to another unit is allowed after acceptance (§ 15049(c)(2)(A)). |
| Fields recorded | Type, weight/volume/count, date, UID, brand name. | No change. |
| Destruction notes | Employee, reason, method of disposal. | No change. |
| Package-adjustment description | Required—explain the reason for the adjustment. | No change. |
| Partial-rejection recording | Required under existing regulations. | No change. |
Regulations Are Optimizers in Disguise
A regulation is a forcing function. The old story is that a stricter entry rule is one more thing to get wrong. The Freed Up frame is that these rules reveal what the business was already missing. These two updates remove the exact entry errors that quietly make everything downstream lie: a record entered before the fact, and a unit that doesn’t match what was sent.
A record entered before the activity happens isn’t a record. It’s a prediction—and the system has no way to know it came true.
A future-dated entry and a unit mismatch are the precise discrepancies that turn a clean reconciliation into a week of chasing ghosts. Closing them is cheaper than the reconciliation, the amended manifests, and the Department questions a bad entry invites. Clean data at the point of entry is what a locked batch stands on.
The Standing Practice for Data Entry
The operators who will barely feel this proposed shift are the ones who already enter what happened, when it happened, in the unit it happened in.
The standing practice is short: record each activity after it occurs, never before. On every incoming transfer, accept in the unit the sender used and reconcile the number before you touch it. Keep the destruction, adjustment, and rejection notes you already keep. An operation already running the monthly reconciliation and holding an inspection-ready standing file has almost all of this muscle. The proposal just names two habits the disciplined operators already have.
Weighing In on the Public Record
Because this is still a proposed rule, the final text is not set. If the “after occurrence” wording collides with a legitimate workflow—say, a genuine operational reason your team stages an entry before a scheduled activity—that is exactly the operating reality the public record exists to capture. Written comment is open through July 20, 2026, with a hearing on July 21. [1]