Compliance · Aug 5, 2026 · 11 min read

NYC TLC Licensing for Black Car Operators: What Your Software Has to Record (2026)

By Limozoft Editorial · Reviewed by Limozoft operator research team.

Compliance #compliance #NYC TLC #records #black car #United States

Illustration of a black car in front of the New York skyline next to a clipboard of trip records

Short answer: A New York City black car base licensed by the Taxi & Limousine Commission must be able to produce, on request, a complete record of every dispatch: who ordered it, which TLC-licensed driver took it, which TLC-plated vehicle was used, the pickup and drop-off times and locations, and the fare charged. Your dispatch software should store those fields on the booking itself, retain them for the period your base licence requires, and export them as a date-ranged spreadsheet in one click. If a record only exists in a driver's text messages, it does not exist.

Who does TLC record-keeping actually apply to?

If you dispatch for-hire trips in the five boroughs, you are almost certainly operating under a TLC base licence — black car, livery, or luxury limousine. The base is the licensed entity, not the vehicle and not the driver, and the base is what gets audited.

The practical consequence is that the regulator's questions land on you, the operator, even when the driver owns the car and the affiliate took the job. Your dispatch system is the only place that can answer them consistently.

Black car bases: prearranged, account-based work, no street hails.
Luxury limousine bases: prearranged, typically hourly and event work.
Livery bases: community car service work, prearranged only.
All three dispatch only to TLC-licensed drivers in TLC-plated vehicles affiliated to the base.

Which trip records does a base have to be able to produce?

Treat the trip record as the atomic unit. Every dispatched job should carry a complete, immutable set of fields from the moment it is assigned. In practice, the fields below are the ones that come up in every base audit and every passenger complaint investigation.

The test is simple: pick a random trip from six months ago and try to answer 'who, what car, what driver, what time, what route, what fare' without phoning anyone. If you can't, your record set is incomplete.

Trip / dispatch number, unique and non-reusable.
Date and time the trip was requested, and by whom (passenger or corporate account).
Pickup address and time, drop-off address and time.
TLC driver licence number of the driver dispatched.
TLC vehicle licence (plate) of the vehicle used.
Fare charged, itemised: base rate, wait time, tolls, gratuity, surcharges and taxes.
Payment method and settlement reference.
Whether the job was performed in-house or farmed out, and to which affiliated base.

Why does the farm-out field matter so much?

Farm-outs are where record chains break. The passenger booked with you, so the complaint comes to you, but the trip data sits in someone else's system. If your dispatch record does not name the receiving base and its trip reference, you cannot reconstruct what happened.

Store the affiliate's name, the affiliate trip reference and the agreed net rate on the booking itself. It takes one extra field and it resolves most disputes in a single email.

How long should you retain trip records?

Retention periods are set by the TLC rules in force for your base licence type, and they interact with your tax and insurance obligations, which usually run longer. Most operators land on a practical rule: keep full trip detail online for at least three years, and keep archived exports for seven.

Confirm the current requirement against the TLC's own rulebook before you set a deletion policy — it is the one number you should never take from a blog post, including this one.

What driver and vehicle records does your system need to track?

Trip records prove what happened. Driver and vehicle records prove you were allowed to let it happen. A base that dispatches to a driver whose TLC licence lapsed last Tuesday has a problem no trip log can fix.

The fix is expiry-aware records: every credential stored with an expiry date, and a dispatch board that flags or blocks assignment when something has run out.

TLC driver licence number and expiry date.
State driver licence (DMV) number and expiry.
Defensive driving / TLC-required course completion where applicable.
Drug testing compliance status per the current TLC programme.
Vehicle: TLC plate, VIN, make/model/year, seating capacity.
Vehicle inspection date and next-due date.
Insurance certificate (COI) with carrier, policy number, limits and expiry.
Affiliation record linking the vehicle and driver to your base.

How should accessibility and passenger-service records be handled?

Accessible-service obligations vary by base type and change over time, but the record-keeping principle does not: if a passenger requests a wheelchair-accessible vehicle, that request, the response, and the outcome should be on the booking.

The same applies to service refusals and complaints. A dated note with the dispatcher's name attached to the trip is worth more than a perfect policy document nobody can tie to an incident.

Accessibility requested: yes/no, captured at booking, not inferred later.
How the request was fulfilled — own WAV, affiliate, or dispatch to a partner programme.
Any refusal or cancellation, with reason and timestamp.
Complaint log entries linked to the trip number, with resolution and date.

What does a congestion, toll and surcharge audit look like?

New York adds layers to the fare that most software outside the market handles badly: state congestion surcharges on for-hire trips in the relevant zone, MTA-related charges, tolls, and sales tax treatment that differs between transportation services and other charges.

Auditors do not object to complexity — they object to fares that cannot be decomposed. Store each component as its own line, never as a rolled-up total, and never let a driver hand-edit a total without an audit trail.

Itemise: base fare, hourly overage, wait time, tolls, congestion surcharge, gratuity, taxes.
Record who applied each adjustment and when.
Keep the original quoted price alongside the final charged price.
Export by date range with all components as separate columns.

How do you configure dispatch software so an audit takes an hour?

Most operators fail audits on retrieval, not on the underlying facts. The data exists — in three systems, two spreadsheets and a WhatsApp group. Consolidation is the whole job.

Set the system up once with the fields above as required at booking, credentials stored with expiry dates, and a date-ranged CSV export that includes every field an inspector could reasonably ask for.

Make TLC driver licence and plate mandatory fields on driver and vehicle profiles.
Block or flag dispatch to any driver or vehicle with an expired credential.
Force farm-out jobs to record the receiving base and reference.
Keep an immutable change log on fare edits and cancellations.
Test the export quarterly by pulling a random month and reading it as if you were the auditor.

How does Limozoft handle this?

Limozoft stores driver and vehicle credentials with expiry dates, warns the dispatcher before a licence, inspection or COI lapses, itemises every fare component on the booking, and exports any date range to CSV with all fields included — on every plan, at $399 one-time plus $10–$40 per month by fleet size.

Nothing here is a New York-only feature; it is the same record model that satisfies TfL in London and the RTA in Dubai, because regulators everywhere ask the same six questions.

TLC record categories and where they should live

Record	Field owner	Expiry-tracked?	Audit frequency
Trip / dispatch log	Booking record	No — retained	Every audit
TLC driver licence	Driver profile	Yes	Every audit
DMV licence	Driver profile	Yes	Every audit
TLC vehicle plate	Vehicle profile	Yes	Every audit
Vehicle inspection	Vehicle profile	Yes	Annual+
Insurance COI	Vehicle / fleet	Yes	Renewal + audit
Complaint log	Booking record	No — retained	On complaint
Farm-out reference	Booking record	No — retained	On dispute

Pros and cons

Pros

A single trip record answers almost every regulator and passenger question.
Expiry-aware credentials stop non-compliant dispatch before it happens.
Itemised fares make surcharge and tax questions trivial to answer.
One-click date-ranged export turns an audit into an afternoon.
The same record model works for TfL, RTA Dubai and most US markets.

Cons

Retrofitting historical records is manual work no software can do for you.
Farm-out partners must cooperate to keep the chain complete.
Rules change — a configuration set in 2024 needs an annual review.
Blocking dispatch on expired credentials creates friction drivers will push back on.

Original data · Limozoft operator research 2026

In Limozoft onboarding calls, 7 in 10 US operators could not produce a complete trip record from 12 months earlier without phoning a driver.

Across demo calls with small US chauffeur and black car fleets, the most common gap was not missing trips — it was missing driver and vehicle attribution on trips that had been reassigned or farmed out at the last minute. Operators who moved assignment changes into the dispatch system closed the gap within one billing cycle.

Keep exploring on limozoft.com

Security & data ownership →

Where your booking data lives and how you get it back.

Dispatch console →

Credential expiry warnings and itemised fares on every job.

Black car solutions →

Corporate black car workflows, PO billing and account reporting.

Book a demo →

See the audit export run on a sample month of trips.

Frequently asked questions

Is this legal advice?+

No. This is operational guidance on how to structure dispatch records. Always confirm current obligations against the TLC's own published rules and your attorney before setting retention or compliance policy.

Do I need TLC records if I only do prearranged corporate work?+

Yes. Black car and luxury limousine bases are prearranged by definition, and the record-keeping obligations apply regardless of whether the client is corporate or retail.

What if the driver owns the vehicle?+

Owner-operator arrangements do not remove the base's obligation. Your system still needs the TLC driver licence, the TLC plate, inspection and insurance details for every vehicle you dispatch to.

How do I handle records for trips I farm out?+

Record the receiving base, its trip reference and the agreed net rate on your own booking. You remain the passenger's counterparty, so you need to be able to reconstruct the trip even though another base performed it.

Can I keep records in spreadsheets?+

You can, but spreadsheets have no audit trail, no expiry alerts, and no link between a trip and the driver credentials valid on that date. Most operators who fail an audit fail on retrieval, which is exactly what spreadsheets are worst at.

How long should I keep trip data?+

Longer than you think, and longer than the minimum — tax, insurance and civil claims usually outlast the regulatory retention period. Many operators keep three years live and seven years archived.

Does Limozoft support TLC-specific fields?+

Yes. TLC driver licence, TLC plate, inspection and COI expiry dates are stored on driver and vehicle profiles with advance warnings, and fares are itemised so surcharges and tolls export as separate columns.

What happens if a credential expires mid-shift?+

Configure the system to flag it at assignment time rather than discovering it at audit time. Limozoft warns ahead of the expiry date so you can rotate the vehicle or driver before the job is dispatched.

Ready to see it live?

Book a 20-minute demo tailored to your fleet.

Same-week launch · month-to-month · everything included.