Inbound driver
Booking, carrier, driver, vehicle, trailer, load reference, staging, inbound dock, and gate exit.
Coordinate drivers, carriers, suppliers, contractors, auditors, and office visitors with bookings, vehicle context, gate checks, staging, dock handoff, exceptions, detention risk, and exit.
The visitor record becomes useful when it follows the carrier or guest through the gate-to-dock handoff and keeps no-booking, vehicle, document, dock, and delay exceptions visible.
A driver, contractor, auditor, and office guest do not need the same fields or destination.
Booking, carrier, driver, vehicle, trailer, load reference, staging, inbound dock, and gate exit.
Pickup reference, vehicle, release condition, loading point, coordinator, and completion.
Work scope, site host, area, readiness evidence, equipment, schedule, and closeout.
Purpose, appointment, host, destination, arrival instruction, and departure.
The gate should know who owns the next move and why the vehicle is still waiting.
Capture carrier, purpose, driver, vehicle, load or pickup reference, arrival window, gate, dock, and coordinator.
Expected-arrival board is populated.Confirm booking, driver, vehicle, documents, and current dock availability.
Check result and exception are recorded.Record gate, staging area, dock, queue position, and current coordinator.
The next handoff is visible.Assign no-booking, dock unavailable, vehicle mismatch, missing document, host delay, or detention risk.
One owner and response target.Record loading or delivery outcome, departure, and unresolved follow-up.
The gate list and history are accurate.A metric should open the booking, vehicle, dock, host, or exception behind it.
Approved bookings and gate arrivals by window
Prepare gates and docks for the next arrival peak.Arrived visits without completed dock or host handoff
Assign staging, dock, coordinator, or exception response.Open gate exceptions by type and severity
Resolve, reschedule, redirect, or deny according to policy.Open gate visits beyond expected completion
Confirm dock status, detention reason, and exit plan.Keep transport, warehouse, yard, and door-control work in their dedicated systems when those capabilities are required.
The need is configurable bookings, approvals, arrival forms, handoffs, exceptions, dashboards, related business records, and frequent operating changes.
Native carrier scheduling, yard moves, transport planning, warehouse execution, freight rating, inventory, or dock optimization defines the operation.
Gate barriers, credentials, readers, license recognition, identity verification, and security controls define physical entry.
Yes. Use a distinct arrival path for booking, carrier, driver, vehicle, trailer, reference, gate, staging, dock, coordinator, exception, and exit.
Create a visible no-booking exception with vehicle and carrier context, response owner, staging instruction, next decision, and closeout.
Not when native yard moves, dock optimization, carrier scheduling, vehicle positioning, or transport execution defines success. Jodoo can coordinate the configurable records and exceptions around those systems.
You can track arrival, handoff, expected completion, actual exit, delay reason, owner, and response. Contractual detention calculation or carrier settlement may belong in TMS or finance systems.
Yes. Keep the mobile job focused on booking lookup, check result, gate or dock assignment, exception, evidence, and exit rather than the full management dashboard.
Test no booking, vehicle mismatch, missing document, unavailable dock, host delay, detention risk, and overdue exit with real gate users.