Failed tests, recalls, and destruction requests in Nevada

Most cannabis waste is routine: trim, returns, expired shelf pulls, handled on a schedule. Then there is the other kind: the failed batch, the recall, the product the CCB is watching. Those destructions are events, with more eyes on them and less room for improvisation.

This guide covers how formal destructions work in Nevada: what triggers them, the CCB's Destruction Request channel, and how the physical event should run so the paperwork closes clean.

What turns waste day into a destruction event

• Failed lab testing. Product that fails state-mandated testing and is not eligible for another path exits the system under the same rendering standard as all cannabis waste, with its package tags carried through the record.
• Recalls. Product pulled back from shelves has to be accounted for unit by unit, held securely, and then destroyed with documentation that closes the recall loop.
• Expired or unsellable inventory at scale. A one-off return is routine; clearing an entire discontinued line is an event worth running formally.
• Board-directed destructions. When product sits under CCB scrutiny, nothing about its destruction is casual: timing, method, and records follow what the Board expects to see.

The formal channel: the Destruction Request

Nevada runs licensing and compliance submittals through the CCB's Accela portal, and destruction has its own submittal type there: the Destruction Request, DST in the Board's shorthand. Per the CCB's own guidance, a DST comes with three attachments:

• A Destruction Plan: how, where, and by what method the product will be rendered unusable
• The list of items to be destroyed
• Supporting documentation for why

Read that list as a template for how the Board thinks. Even for destructions that do not flow through a formal DST, the same three questions decide whether your records hold: what exactly died, why, and by what method. A facility that can answer those in writing before the grinder starts is a facility that does not dread the follow-up questions.

Holding product before it dies

Between the trigger and the destruction, product waits, and how it waits matters. Keep held product segregated and clearly marked, inside camera coverage (Nevada requires around-the-clock recording of limited access areas with at least 30 days of retention), with its METRC status telling the truth about why it is not for sale. The gap between "pulled from the menu" and "physically destroyed" is exactly the window an auditor reconstructs later, so make it reconstructable: who moved it, where it sat, who had access.

The destruction itself

A formal destruction runs like any compliant destruction, with the volume turned up on documentation:

• Notice through METRC before rendering and disposal, never after
• Weights on calibrated scales, reconciled against the METRC entries and the item list from the plan
• Rendering to Nevada's standard: ground and incorporated with non-cannabis waste until cannabis is less than 50 percent of the mixture by volume (the full mechanics are in our render-unusable guide)
• A witness present, and inside the City of Las Vegas, two employee signatures on the record
• The five state-required record fields closed out the same day (our waste log guide lists them)
• A certificate of destruction that references the batch, the reason, and the plan it executed

Why batch references matter more here

On a routine pickup, the record proves pounds left the system. On a failed batch or recall, the record proves that these specific packages left the system. The certificate and log should name the package tags, not just the weight, so that when someone asks "where did lot 4471 go," the answer is one document with that number on it. Vague records that would pass on trim waste fail on a recall.

The short version

• Failed tests, recalls, bulk clearances, and Board-directed events are formal destructions, run tighter than routine waste
• The CCB's Accela portal has a Destruction Request submittal, and its three attachments (plan, item list, supporting documentation) are the template for how the Board thinks about any destruction
• Held product stays segregated, on camera, and honestly labeled in METRC while it waits
• The event itself follows the standard sequence: METRC first, calibrated weights, rendering past the 50 percent line, witnessed, certified, closed the same day
• Records carry package tags, not just pounds

CropLine runs formal destructions for Las Vegas facilities as scheduled events: plan documented, weights reconciled, witness present, certificate referencing every batch. When something has to die on the record, this is the service. Request a quote or call (702) 907-1425.

This article is educational and not legal advice. Verify current requirements in NAC 678B, the CCB's guidance and Accela submittal instructions, and with the Board before acting.