A new regulation out of British Columbia is putting a hard deadline on dash cam requirements for commercial vehicles: by November 28, 2026, qualifying trucks operating in or passing through the province must carry a compliant camera system, with defined standards for video resolution, footage retention, and night visibility. As written, the mandate targets heavy-duty units over 26,000 lbs, so most light-duty and service fleets won't fall under it directly.

That narrow scope doesn't make the mandate irrelevant. It's a preview of where video compliance is headed across the industry, and fleet managers who wait for a rule to name their vehicle class specifically tend to find themselves scrambling once one does. Here's what the BC mandate reveals about the direction of dash cam regulation, and what light-duty fleet operators can do to get ahead of it.

What the mandate requires

Regulations like this one tend to converge on three technical baselines, and BC's is a clean example:

• Road-facing video captured at 1080p resolution
• Continuous footage retention covering 72 hours
• Functional night vision for low-light and overnight driving

Most commercial dash cam systems on the market today can hit 1080p and offer night recording as a standard feature. The retention window is where fleets run into trouble, and it's worth understanding why.

The storage math

Dash cam footage at 1080p consumes storage fast, and a camera's advertised card size rarely lines up with how long it can hold onto that footage in practice. A standard 128GB card, paired with a road-facing camera alone, might cover somewhere in the 40–55 hour range. Add a second camera angle — a cabin-facing lens for driver monitoring, say — and that same card can drop to under 24 hours of coverage, sometimes into the teens depending on bitrate and frame rate settings.

Against a 72-hour retention requirement, a 128GB setup falls short in nearly every real-world configuration. Fleets that assumed their existing hardware was "close enough" are discovering the gap only when a regulator, insurer, or claims adjuster asks for footage that's already been overwritten.

The fix is straightforward: a 256GB card typically clears the 72-hour threshold with room to spare, and multi-camera or higher-resolution configurations may call for 512GB or cloud-backed storage to stay safely inside the window.

The jurisdictional patchwork problem

Fleet compliance rarely arrives as one national standard. It arrives province by province, state by state, sometimes city by city, with each jurisdiction defining its own resolution floor, retention window, and enforcement timeline. A fleet running routes across multiple regions can end up managing several overlapping standards at once, each with a different deadline and a different definition of "compliant."

BC's mandate is a useful case study in how quickly this can move from proposal to enforcement. Reseller ordering windows, hardware bundles, and allocation controls all got built around a fixed date, which left carriers a narrow runway to audit their existing camera fleet, identify gaps, and place orders before supply tightened. Fleet managers who track regulatory movement only after a deadline is announced tend to be competing with everyone else for the same hardware at the same time, on the same short runway.

The practical takeaway is to build a standing process for reviewing where your vehicles operate, which jurisdictions govern those routes, and what technical standards those jurisdictions are trending toward — reviewed on a regular cadence.

Why this matters even if the mandate doesn't touch your fleet

Three trends make this worth tracking regardless of vehicle weight class:

• Mixed fleets cross the line more often than people expect. A company that runs primarily light-duty vans and pickups may still operate a handful of heavier service or delivery trucks, or contract with carriers that do. Any of those units traveling through a regulated jurisdiction needs to meet the local standard, which means fleet managers need visibility into which vehicles in their mix are subject to which rules.
• Insurance and liability pressure moves faster than legislation. Long before a jurisdiction mandates dash cams by law, insurers are already rewarding fleets that carry them, and courts are already treating footage gaps unfavorably in liability disputes. A fleet that upgrades its retention and resolution standards ahead of any legal requirement is protecting itself on both fronts at once, well before a compliance deadline forces the issue.
• Once one jurisdiction sets a technical bar, others tend to follow it. Regulatory standards rarely emerge in isolation. When a province or state defines specific resolution and retention thresholds, those numbers become a reference point other regulators reach for when they draft their own rules. Fleet managers who track early movers like BC's mandate get a meaningful head start on whatever comes next, rather than a scramble once a deadline lands closer to home.

What to look for in a compliant camera system

Not every dash cam marketed as "fleet-ready" will clear a compliance bar, and resolution is the easiest spec to check but not the only one that matters. When evaluating hardware — whether upgrading existing units or sourcing new ones — a few criteria are worth putting in front of any vendor:

• Recording resolution under real conditions, not just the number printed on the box. Some systems drop resolution automatically to conserve storage once a card nears capacity, which can quietly undercut a 1080p requirement during the footage window you need.
• True retention hours per camera configuration, calculated against the specific number of lenses, bitrate settings, and card size the fleet plans to run — road-facing only, road-and-cabin, or multi-camera setups all produce very different numbers from the same card.
• Low-light and night performance. Night vision quality varies widely between hardware tiers, and footage that's technically captured but too dark to identify a vehicle, plate, or driver won't satisfy most compliance standards or hold up in a claims dispute.
• Storage architecture that scales, whether that means a straightforward path to a higher-capacity card, cloud offload for older footage, or a hybrid approach that keeps recent footage local and archives the rest. A camera locked into a fixed, non-upgradable card size is a liability the moment a retention requirement tightens.
• Data handling and driver privacy practices, particularly for cabin-facing cameras. Compliance and driver trust aren't separate conversations — a rollout that ignores how footage is stored, accessed, and used tends to generate pushback that slows adoption regardless of what the regulation requires.

A readiness checklist for fleet managers

Whether or not your fleet is currently in scope for a mandate, these are the questions worth answering now:

• Audit current hardware against resolution and retention baselines. Pull the actual specs on the cameras and cards already installed, not the marketing claims from when they were purchased.
• Calculate real retention hours per configuration. Run the math for each camera setup in the fleet — single-camera, dual-camera, high-bitrate — rather than relying on a single blended estimate across the whole fleet.
• Map vehicle classes against known and pending regulations. Identify which units, routes, or jurisdictions could put a vehicle in scope for a compliance requirement, including cross-border or cross-provincial travel.
• Build storage upgrades into the replacement cycle. Card and camera upgrades are cheap relative to a compliance failure or a lost claim; folding them into routine maintenance avoids an expensive emergency retrofit later.
• Loop in the insurance conversation. Ask the fleet's insurer directly whether current or upgraded dash cam coverage affects premiums or claims handling.

Turning footage into a compliance record

Meeting a resolution and retention standard is only half the compliance picture. The other half is being able to produce the right footage, for the right vehicle, within the window a regulator, insurer, or attorney asks for it — and doing that reliably across a fleet of any real size means treating dash cam data as part of a broader telematics and reporting system, not a standalone camera sitting on a windshield.

That means footage needs to be tied to vehicle ID, driver, date, and route in a way that's searchable rather than something someone has to dig through hours of raw video to find. It means retention policies need to be enforced automatically, so footage isn't quietly overwritten by a card that fills up faster than expected. And it means whoever manages fleet compliance — safety, operations, or risk management — has a clear, repeatable process for pulling footage on request.

The bigger shift behind the headline

Dash cam mandates are part of a broader pattern in fleet compliance: regulators are moving from general safety expectations toward specific, auditable technical standards. Hours-of-service rules went through the same evolution with electronic logging devices. Emissions requirements went through it with telematics-based reporting. Video compliance is following the same arc, and the fleets that treat each new regional mandate as a data point rather than a one-off are the ones that aren't caught flat-footed when the rule finally applies to them directly.

For now, BC's Bill M217 is a heavy-duty story. The underlying standard it sets — real-time resolution, multi-day retention, reliable night performance — is a fair description of where dash cam expectations are heading for commercial fleets of every class.