A California carrier has only a handful of genuinely dated obligations: renewal every three years ($100), and PUCTRA filings — annually by 15 January if gross intrastate operating revenue is $100,000 or less, otherwise quarterly. Everything else is a condition that must stay continuously true: insurance on file with the Commission, Pull-Notice participation, testing-programme enrolment, and an authority that still matches what you actually operate. The conditions are what lapse, because they have no date attached.
This page is the hub for the rest of this cluster. Every figure in it is sourced on the page that covers that subject in depth, and linked from here.
It exists because of a pattern worth naming. Across this cluster, almost nothing is intellectually difficult. The rules are knowable and mostly short. What defeats operators is that compliance has to survive contact with a working business — and working businesses are busy, distracted and staffed by people whose job description does not mention any of this.
Two kinds of obligation, and only one has a date
Sorting the obligations by shape rather than by subject is the most useful thing this page does.
| Dated obligations | Continuous conditions | |
|---|---|---|
| Examples | Renewal every three years; PUCTRA filings | Insurance on file; Pull-Notice participation; testing enrolment; authority matching the fleet |
| How they fail | You miss a date | Something quietly stops being true |
| How you find out | A deadline passes | Usually from someone else, at the worst moment |
| Fix | A calendar entry | A named owner and a periodic check |
| Which actually go wrong | Rarely — they are easy to diarise | Most of the time |
That bottom row is the point. Operators who build a compliance calendar tend to fill it with the left-hand column, because those items have dates and dates fit in calendars. Then they are surprised when the failure comes from the right.
The calendar itself
| When | What | Detail |
|---|---|---|
| Every three years | Renew the TCP certificate or permit | $100. PSC certificates do not require renewal. Diarise it the day authority is granted, with a reminder a quarter out. |
| By 15 January, annually | PUCTRA report and any fees due | Applies if annual gross intrastate operating revenue is $100,000 or less. Currently 0.3% of revenue. |
| Quarterly | PUCTRA report and any fees due | Applies to all other carriers. Crossing $100,000 moves you onto this calendar. |
| Annually | Confirm the insurance filing, not just the policy | Ask your broker to confirm the Commission holds a current electronic filing. Buying coverage and satisfying the requirement are two different events. |
| Annually | Renew the testing-programme enrolment | The enrolment most likely to lapse quietly, because nothing day to day depends on it. |
| Twice a year | Look yourself up on the CPUC carrier portal | Free, about a minute. The authoritative statement of your status. |
| Twice a year | Check your published CHP carrier inspection results | Public. You should not learn what they say from a customer. |
| Quarterly | Review the fleet against the authority and insurance bands | Seating capacity drives both. One vehicle added can move the operation. |
| Ongoing | Act on Pull-Notice notifications | Enrolment is the requirement; reading them is the point. |
| Ongoing | Run random testing as a programme | Pre-employment testing has a natural trigger. Random testing has none — that is why it slips. |
We have separated those two things deliberately in the caption. It would be easy to present every row here as though the Commission mandated the cadence. It does not. The obligations are continuous; the intervals are a practical way of catching drift, and you should feel free to run them more often.
The event-driven half
Some obligations are triggered by something happening in the business rather than by a date. These are the ones no calendar catches, so they need to be attached to the event instead:
- Hiring a chauffeur → add them to Pull Notice; pre-employment testing; keep the employment application, because it is examined at a terminal inspection.
- Buying a vehicle → check seating capacity against the insurance bands and the CHP inspection trigger. If it is a modified limousine, it is in scope whatever it seats — see modified limousine rules.
- Crossing $100,000 in annual revenue → your PUCTRA filing frequency changes from annual to quarterly. The trigger for this is a good year, which is why nobody notices it.
- Changing insurer → a new electronic filing must reach the Commission. A replaced policy with no fresh filing leaves the record describing something untrue.
- Taking on work outside California → federal rules may engage. See when federal hours-of-service rules apply.
- Selling the business → TCP permits of types P, S and Z are not transferable. Establish that before the transaction, not during it.
The revenue one deserves emphasis because of its shape. Every other trigger on that list is a deliberate decision somebody makes. That one happens to you, as a consequence of doing well, and it changes a filing obligation silently.
Owners, not reminders
The diagnosis in the driver programmes page applies to this whole cluster: these obligations fail because they belong to nobody's job. They generate no work in the normal course, and the only signal that one has lapsed is a signal nobody is listening for.
Three rules that matter more than any calendar tool:
- Assign each item to a role, not a person. A three-year renewal outlasts jobs.
- Route official correspondence to a role mailbox. The classic failure is notifications arriving perfectly at an address belonging to whoever handled licensing two years ago.
- Make one person accountable for the whole list. Distributed ownership of a ten-item list reliably becomes nobody's.
This is the pattern we find most often when we come into an existing operation to build software, and it is almost never carelessness. It is the result of obligations having no home. The fix is boring and it works: give each one an owner and a date that appears somewhere people already look. We would rather an operator did that in a spreadsheet they actually open than bought a system they do not.
A fifteen-minute quarterly review
If you take one thing from this cluster, take this. Once a quarter, answer nine questions in writing:
- What does our record on the CPUC carrier portal say right now?
- Is insurance currently on file with the Commission — confirmed by the broker, not assumed?
- Does the coverage amount still match our largest vehicle's seating capacity?
- Is the testing-programme enrolment current, and has random testing actually run?
- Is every current chauffeur enrolled in Pull Notice, and has anyone read the notices?
- Has the fleet changed in a way that crosses a threshold — 15 for a Class P permit, 10 including the driver for CHP inspection, 8 and 16 for insurance bands?
- What is our gross intrastate operating revenue against the $100,000 PUCTRA line?
- What do our published CHP carrier inspection results say?
- How far away is renewal, and who owns it?
Any of those that cannot be answered from memory or a document in under a minute is your actual compliance risk. Not the ones you answered — the ones you had to go and find out.
Where this belongs
Most of these are facts a well-run operation already holds somewhere: vehicle seating capacities, driver records, insurance dates, revenue. The failure is rarely that the information does not exist. It is that it lives in four places and nobody compares it to a threshold.
We are not going to claim software makes an operator compliant — it cannot, and anyone selling that is overselling. What a system can do is narrower and genuinely useful: hold the seating capacity next to the insurance band, surface a renewal date before it arrives, and notice a revenue line being crossed. Those are the three failures in this cluster that are mechanical rather than judgemental, which makes them the three worth building for.
The judgement calls — which authority fits work that is changing shape, how chauffeurs are engaged, whether a specific vehicle is a modified limousine — stay with the Commission, CHP and your advisers. That division is the honest one, and it is how we approach the work.
Sources
- California Public Utilities Commission — Passenger Carrier FAQs (renewal, PUCTRA, basic requirements)
- California Public Utilities Commission — Licensing requirements for charter-party carriers
- California Public Utilities Commission — Transportation Carrier Portal (status lookup)
- California Highway Patrol — Carrier Inspection Results search
- California Highway Patrol — Basic Inspection of Terminals (performance-based selection, records examined)
Questions we actually get asked
Is this a substitute for professional advice?
No. It is a scheduling aid built from the CPUC, CHP and federal sources cited across this cluster. An operation with real exposure should have its position reviewed by people who do this professionally — particularly on worker classification and anything involving a sale.
What a calendar does is narrower and still valuable: it stops the failures that happen because nobody was watching a date, which in our experience is most of them.
Why is renewal not the most important item?
Because it is the one with a fixed date and a $100 fee, which makes it the easiest to diarise and the cheapest to satisfy. The expensive failures are the continuous conditions — insurance that must stay on file, testing enrolment that must stay current, an authority that must still match what you operate.
Renewal is a checkpoint. The conditions are the obligation.
What is the single highest-value habit here?
Looking your own carrier record up on the CPUC portal on a schedule. It is free, it takes about a minute, and it is the authoritative statement of your status.
The gap between what an operator believes the record says and what it actually says is where every unpleasant surprise lives — and it is the same check your next corporate client will run.
We are a two-person operation. Is this overkill?
The opposite. A large operator has someone whose job includes this. A two-person operation has nobody, which is precisely why the obligations with no natural trigger — random testing, the PUCTRA threshold, the insurance filing — are the ones that lapse.
Small operations need the calendar more, not less. It can live on one page.