Finalize AWS BOL/POD Automation
Budget: $60 – $61 USD
We are continuing Phase 2 of an existing MVP for a trucking document automation system.
The system already includes:
• Dispatcher, Driver, Reviewer, and Admin roles
• Load creation
• Rate Confirmation (RC) upload
• BOL upload by drivers
• Automated OCR + rule-based review
• Auto-send vs block logic
• Reviewer override flow
• Search & audit logs
This contract is ONLY for completing the agreed Phase 2 scope below.
Phase 2 Scope (FINAL) RC-based load creation (automation) • Automatically extract only the following fields from Rate Confirmation:
• Load number
• PO number (if present)
• Pickup city/state/date
• Delivery city/state/date
• No penalty clause parsing
• No accessorial logic
• No semantic interpretation beyond field extraction
• Dispatcher should NOT manually type these fields
2. BOL image quality enforcement
• Detect:
• missing corners
• unreadable images
• poor crop / blur
• If quality fails → driver is required to re-upload
• Goal: factoring-ready, high-clarity scanned output
3. POD output quality
• Ensure final generated PDF is:
• clean
• readable
• suitable for brokers and factoring companies
4. Elastic IP / deployment stability
• Ensure EC2 instance has stable Elastic IP
• No hardcoded localhost / dev URLs
• System accessible consistently
5. Bug fixes & polish limited to Phase 2
• Fix issues directly blocking Phase 2 functionality
• No new features outside scope
DELIVERABLES (WHAT “DONE” MEANS)
Phase 2 is considered complete when:
• Dispatcher can create a load without manual typing using RC
• Driver upload quality is enforced (bad images rejected)
• Reviewer logic works exactly as demonstrated
• Elastic IP is stable
• System is review-ready for production testing
The system already includes:
• Dispatcher, Driver, Reviewer, and Admin roles
• Load creation
• Rate Confirmation (RC) upload
• BOL upload by drivers
• Automated OCR + rule-based review
• Auto-send vs block logic
• Reviewer override flow
• Search & audit logs
This contract is ONLY for completing the agreed Phase 2 scope below.
Phase 2 Scope (FINAL) RC-based load creation (automation) • Automatically extract only the following fields from Rate Confirmation:
• Load number
• PO number (if present)
• Pickup city/state/date
• Delivery city/state/date
• No penalty clause parsing
• No accessorial logic
• No semantic interpretation beyond field extraction
• Dispatcher should NOT manually type these fields
2. BOL image quality enforcement
• Detect:
• missing corners
• unreadable images
• poor crop / blur
• If quality fails → driver is required to re-upload
• Goal: factoring-ready, high-clarity scanned output
3. POD output quality
• Ensure final generated PDF is:
• clean
• readable
• suitable for brokers and factoring companies
4. Elastic IP / deployment stability
• Ensure EC2 instance has stable Elastic IP
• No hardcoded localhost / dev URLs
• System accessible consistently
5. Bug fixes & polish limited to Phase 2
• Fix issues directly blocking Phase 2 functionality
• No new features outside scope
DELIVERABLES (WHAT “DONE” MEANS)
Phase 2 is considered complete when:
• Dispatcher can create a load without manual typing using RC
• Driver upload quality is enforced (bad images rejected)
• Reviewer logic works exactly as demonstrated
• Elastic IP is stable
• System is review-ready for production testing
Related categories:
PHP
Python
Cloud Computing
Software Architecture
Amazon Web Services
OCR
Automation
API Development