Fix NEMT Trip Workflow Bugs
Budget: $30 – $250 USD
I have a NEMT transportation web-app whose “take trip” workflow for drivers and the accompanying AI scheduling logic are misbehaving. Right now drivers often can’t start a trip, completed trips refuse to close out, and occasionally a trip jumps back to a previous status altogether. These state-management glitches are blocking daily operations, so I need them resolved quickly and cleanly.
You’ll dive into the existing codebase, trace the logic that moves a trip through its lifecycle, and patch whatever is causing these three pain points:
• A driver presses “Start” and nothing happens
• A finished trip will not transition to “Completed”
• Trips randomly revert to an earlier status
The fix must persist across all AI-generated schedules, meaning your changes can’t break or bypass the automated dispatcher that assigns rides.
Deliverables
1. Clean, well-commented code or pull request that fully resolves the three issues.
2. A concise change log describing which files, functions, or database triggers were updated.
3. Proof of success: screenshots or a short screen-capture showing a driver starting and ending a trip without any status rollback, plus confirmation that AI scheduling still works.
I can provide repo access, a staging database, and test credentials for a driver account the moment we start. If this goes smoothly, there’s plenty more enhancement work waiting in the pipeline.
You’ll dive into the existing codebase, trace the logic that moves a trip through its lifecycle, and patch whatever is causing these three pain points:
• A driver presses “Start” and nothing happens
• A finished trip will not transition to “Completed”
• Trips randomly revert to an earlier status
The fix must persist across all AI-generated schedules, meaning your changes can’t break or bypass the automated dispatcher that assigns rides.
Deliverables
1. Clean, well-commented code or pull request that fully resolves the three issues.
2. A concise change log describing which files, functions, or database triggers were updated.
3. Proof of success: screenshots or a short screen-capture showing a driver starting and ending a trip without any status rollback, plus confirmation that AI scheduling still works.
I can provide repo access, a staging database, and test credentials for a driver account the moment we start. If this goes smoothly, there’s plenty more enhancement work waiting in the pipeline.