TLC docs checker
Driver documents checked before they become dispatch risk
The admin and driver profile flows validate general information, covered areas, fleet, DMV, TLC, tax info, and other licenses. Expiration dates and attachments are treated as required operating data, not loose files.
Compliance workflow
Profile completion, documents, and TLC records in one chain
Drivers are not only names in a list. The platform checks the sections required for operation, calculates progress, validates document fields, stores attachments, and can export TLC trip records from reports.
Validate profile steps
General, covered area, fleet, DMV, TLC, tax info, and other licenses contribute to completion progress.
Check DMV documents
DMV number, expiration, and driver license picture are validated together.
Check TLC documents
TLC number, expiration, and license attachment are required for driver readiness.
Export TLC records
Reports include a TLC Trip Records preset with pickup, drop-off, driver, vehicle, base, and flag columns.
Admin surfaces
Compliance data is collected where teams already manage drivers
The sibling admin repo validates driver profile sections and stores document attachments. Reports also include a built-in TLC Trip Records CSV preset with required trip data columns.
Profile progress
Completion is calculated from resolved versus possible required fields.
DMV validation
DMV number, expiration date, and document picture are checked as a group.
TLC validation
TLC number, expiration, and license image are required for readiness.
Other licenses
Additional licenses require name, expiration, and file attachment.
Image or PDF attachments
Document changes support preview, storage, upload, and deletion paths.
TLC trip export
Reports can export TLC pickup, drop-off, driver license, vehicle plate, base, and service flags.
Controls that matter