The two driver programmes every California carrier must join

These two requirements share a property that makes them unusually easy to get wrong: neither is something you do. Both are states you have to remain in. An operator can complete every step correctly and still fall out of compliance six months later without taking any action at all, simply by ceasing to maintain something.

That is a different shape from most of what a new operator handles during licensing, and it is why these two get their own page rather than a line in a checklist.

Two programmes, two agencies, one operator

The split across agencies is itself an operational hazard. There is no single place where an operator can confirm both are in good standing, no combined renewal, and no shared notification if one lapses. Two relationships have to be maintained independently, and the only thing connecting them is somebody in the business remembering that both exist.

The DMV Employer Pull-Notice programme

The CPUC lists participation in the DMV Employer Pull-Notice System among the basic requirements for passenger motor carriers, and its licensing instructions direct applicants to complete and submit form INF 1104, noting that it may take approximately six weeks to receive a Pull Notice contract.

The mechanism is what makes it valuable. Rather than the employer periodically going to look, the DMV pushes notification when an enrolled driver's record changes. The employer finds out because something happened, not because someone remembered to check.

Which surfaces the question that matters more than the enrolment: who reads the notices?

We have seen this failure repeatedly and it is worth naming precisely. An operation enrols, satisfies the requirement, and the notifications route to an address that belonged to whoever handled licensing — a person who has since changed roles, or a generic inbox nobody owns. The programme functions perfectly. The information arrives. Nothing happens with it.

That operation is technically enrolled and practically unprotected, and the gap is completely invisible until a driver with a suspended licence is dispatched. The requirement is enrolment; the point is knowing.

The CPUC drug and alcohol testing programme

The CPUC states that carriers must be enrolled in a controlled substance and alcohol testing programme, and describes its own programme as established under Public Utilities Code sections 1032.1 and 5374(a)(2) and (b)(1)(I), with requirements set out in Commission Resolutions TL-18716 and TL-18760. The Commission describes the programme as substantially similar to federal drug testing regulations, and notes that it includes requirements for pre-employment and random testing among others.

Two features are worth drawing out.

Pre-employment and random are different obligations. Pre-employment testing is an event tied to hiring, and it is the one operators reliably do, because it sits inside a process that already exists. Random testing is a continuing programme requirement with no natural trigger — nothing in the business prompts it. That asymmetry is why random testing is the half that lapses.

"Substantially similar to federal" is not "the same as federal". The Commission's phrasing is careful and so should ours be. An operator cannot assume that satisfying one regime automatically satisfies the other, and an operator running interstate work may be inside both. The resolutions are the authoritative statement of what the CPUC programme requires, and we are pointing at them rather than paraphrasing their contents — a summary of a testing programme is exactly the sort of thing that should not be taken from an article.

The 15-passenger line in the testing rule

The CPUC describes its testing programme as applying to drivers who operate vehicles with a seating capacity of 15 persons or less. This deserves a moment because the number 15 appears twice in California charter-party regulation and it is doing something different each time.

The practical consequence of the overlap is a tidy one for a typical operator: if your fleet sits under a Class P permit, your drivers are within the range the CPUC's testing programme describes. The two requirements arrive together.

It also means that an operator scaling past the P ceiling is not simply exiting one rule — they are changing their position under several at once, including insurance banding and CHP inspection. We map the thresholds against each other in TCP permit classes explained.

Why these are conditions, not steps

Most of licensing has the shape of a project: an application, a fee, a decision. These two do not. They are conditions that have to keep being true, and the difference has a practical consequence worth stating directly.

A project fails loudly. You submit an application and it is rejected; you know. A condition fails silently. Nothing announces that a testing programme enrolment lapsed at renewal because a card expired, or that Pull-Notice notifications have been going to a mailbox nobody opens since March. The business keeps running, which is precisely the problem — the absence of consequence is not evidence of compliance.

Both programmes are examined at inspection

These are not requirements that sit unexamined. CHP's description of what a terminal inspection covers lists Employer Pull Notice first among driver records, alongside driver timekeeping records, driver proficiency records and the driver employment application.

And Controlled Substances and Alcohol is one of the Behavioral Analysis and Safety Improvement Categories that CHP uses to select terminals for inspection under the Basic Inspection of Terminals programme — where, in CHP's description, a score at or above the federal intervention level in any one of the relevant BASICs selects all of a carrier's California terminals.

Put those two facts together and the position is clearer than most operators realise: performance in one of these areas influences whether you are inspected, and records in both are examined when you are. They are connected to each other through the inspection system, which we set out in CHP terminal inspections.

Building an operation that stays enrolled

Six things, none of them clever, all of them the difference between enrolled and actually protected.

1. Start Pull-Notice enrolment early. Approximately six weeks for the contract means it belongs near the front of a licensing timeline, not the end.
2. Route Pull-Notice notifications to a role, not a person. People change jobs. The notifications should arrive somewhere that survives that.
3. Give someone the job of acting on a notice. Receiving is not the requirement's purpose. Reading and acting is.
4. Diarise the testing programme renewal. It is the enrolment most likely to lapse quietly, because nothing in the business depends on it day to day.
5. Treat random testing as a running programme. Pre-employment testing has a natural trigger; random testing has none, and that is exactly why it is the half that slips.
6. Keep the records producible. Both programmes generate records that are examined at inspection. A record you cannot produce is, for inspection purposes, a record you do not have.

None of that is a compliance programme, and we are not presenting it as one — an operation with real exposure should be taking advice from people who do this professionally. It is the operational half: the part that determines whether the compliance you have arranged actually functions once the business gets busy.

Which is the throughline across this whole cluster. The rules are knowable and mostly not complicated. What defeats operators is that compliance has to survive contact with a working business, and working businesses are distracted. Building for that is a design problem, and it is the problem we work on.