Worker Application

[emoss08]

Our current worker management system requires significant enhancements to meet FMCSA compliance requirements and improve user experience. This project aims to implement comprehensive features for driver management, compliance tracking, and streamlined onboarding processes.

Objectives

• Enhance regulatory compliance capabilities
• Streamline driver onboarding process
• Improve driver retention through better management tools
• Implement comprehensive qualification tracking

Core Components

1. Driver Qualification File Management

• Implementation of document tracking system
  • Create document type classifications aligned with FMCSA requirements
  • Implement document status tracking (valid, expired, pending review)
  • Add document versioning for audit purposes
  • Implement CFR requirement mapping for each document type
• Control file api #13
  • Build expiration date tracking system
  • Create configurable reminder system for document renewals
  • Implement retention period management based on document type
  • Add validation checks against CFR requirements

2. Mobile-First Driver Onboarding Portal

• User Interface Development
  • Create responsive design for mobile, tablet, and desktop
  • Implement step-by-step guided onboarding flow
  • Design intuitive document upload interface
  • Add progress tracking indicators
• Onboarding Process Implementation
  • Implement document validation workflows
  • Create real-time validation feedback
  • Implement save and resume functionality

5. Leave Management System

• PTO Management
  • Implement accrual tracking
  • Create leave request workflow
  • Add calendar integration
  • Implement approval system
• Schedule Management
  • Create availability tracking
  • Implement conflict detection
  • Add coverage analysis tools
  • Create schedule optimization features

[emoss08]

We may want to reconsider the worker on-board client.

The recommended self-hosted approach for Trenova is for the core application to be secured behind a firewall with VPN access. We'll need to implement a separate public-facing onboarding portal that has it's own subdomain.

This will allow organizations to keep the main app behind a secure firewall, expose the onboarding functionality through a subdomain (onboarding.trenova.local).

We'll need to create a document that shows organization how to configure their firewall to restrict the core app access to VPN users only, allow external access to just the onboarding subdomain.

[emoss08]

Additionally organizations will need to configure the caddyfile with a registered domain name.

[emoss08]

This is currently paused, we need to focus on adding the new shipment experience, then we'll come back to this along with all other tasks and finalize them.