Warehouse-to-Truck Loading runs the handoff from a planned transport load to dock verification, truck departure and delivery reconciliation. Loads identify the requested quantity, item, lane, operating organization and transport partner.
Approval conditions
| Record number | Subject | Status | Requested units | Item code | Lane | |
|---|---|---|---|---|---|---|
| LDS-68335 | Reno dock 4 to Boise retail hub | Draft | 720 | APP-TRAIL-210 | Reno to Boise | |
| LDS-37717 | Fresno dock 2 to Oakland depot | Draft | 840 | HOME-BOTTLE-24 | Fresno to Oakland | |
| LDS-19815 | Stockton dock 7 to Portland store | Draft | 30 | TEXT-TOTE-SLATE | Stockton to Portland | |
| LDS-78436 | Sacramento dock 1 to Eugene hub | Draft | 280 | CAMP-MUG-12 | Sacramento to Eugene | |
| LDS-21036 | Reno dock 6 to Salt Lake depot | Draft | 780 | APPR-JACKET-M | Reno to Salt Lake City |
Transport Supervisor independently reviews the dock evidence, loaded quantity and seal for the submitted revision.
Every feature works on the same records. Pick one to see the screen your team works in.
Prepare the load, transport partner and appointment windows before assigning the truck.
Loads
| Record number | Subject | Owner | Planned departure | Planned arrival | Status | |
|---|---|---|---|---|---|---|
| LDS-21646 | Reno dock 4 to Boise retail hub | Mei Laurent | 21 Oct | 26 Oct | Draft | |
| LDS-32518 | Fresno dock 2 to Oakland depot | Imani Okoro | 19 Oct | 22 Oct | Planned | |
| LDS-28661 | Stockton dock 7 to Portland store | Asha Menon | 16 Oct | 18 Oct | Dispatched | |
| LDS-36140 | Sacramento dock 1 to Eugene hub | Mei Laurent | 31 Oct | 05 Nov | Delivered | |
| LDS-17949 | Reno dock 6 to Salt Lake depot | Imani Okoro | 22 Oct | 29 Oct | Exception |
Record the physical load and seal, then put the current loading check before the supervisor.
Approval conditions
| Check number | Parent | Organization | Dock | Loaded at | Loaded pallets | |
|---|---|---|---|---|---|---|
| LC-62358 | Stockton dock 7 to Portland store | Juniper Trail Freight | Reno dock 4 | 28 Oct | 70 | |
| LC-91025 | Sacramento dock 1 to Eugene hub | Juniper Trail Freight | Fresno dock 2 | 26 Oct | 670 | |
| LC-54093 | Fresno dock 2 to Oakland depot | North Lantern Transport | Stockton dock 7 | 25 Oct | 460 | |
| LC-19200 | Fresno dock 2 to Oakland depot | North Lantern Transport | Sacramento dock 1 | 28 Oct | 210 | |
| LC-80507 | Reno dock 4 to Boise retail hub | Harbor Bend Logistics Group | Modesto dock 3 | 13 Oct | 280 |
Match the load to a driver and vehicle over the actual working interval.
Drivers
| Name | Code | Organization | Active | License class | License expiry | |
|---|---|---|---|---|---|---|
| Asha Menon | CW-CAR | Harbor Bend Logistics Group | Active | Class A | 30 Oct | |
| Luis Calderon | HB-FRT | Cedar Way Distribution | Inactive | Class B | 28 Oct | |
| Imani Okoro | SR-LOG | Harbor Bend Logistics Group | Active | Class C | 26 Oct | |
| Evan Park | JT-TRN | North Lantern Transport | Inactive | Non-CDL | 23 Oct | |
| Soraya Haddad | SM-HLG | Willow Gate Delivery | Active | Class A | 23 Oct |
Follow the truck from departure through stop events to delivery evidence.
Tracking events
| Event number | Load | Event type | Occurred at | Location | Source | |
|---|---|---|---|---|---|---|
| TE-80998 | Stockton dock 7 to Portland store | Departure | 12 Oct | Reno distribution center | Driver App | |
| TE-85818 | Fresno dock 2 to Oakland depot | Arrival | 16 Oct | Boise retail hub | Telematics | |
| TE-16337 | Sacramento dock 1 to Eugene hub | Stop Arrival | 11 Oct | Fresno warehouse | Dispatcher | |
| TE-90979 | Bakersfield dock 5 to Las Vegas store | Stop Departure | 12 Oct | Oakland service depot | Partner | |
| TE-60512 | Modesto dock 3 to San Jose branch | Delay | 18 Oct | Stockton crossdock | Driver App |
Review vehicle defects, inspection results and service dates alongside the loading plan.
Defect register
Compare operational outcomes, freight charges and delivery evidence before closing the handoff.
Operation receipts
| Receipt number | Parent | Owner | Recorded at | Occurred at | Result state | |
|---|---|---|---|---|---|---|
| OR-40940 | Reno dock 4 to Boise retail hub | Benito Cruz | 14 Oct | 18 Oct | Pending | |
| OR-97454 | Stockton dock 7 to Portland store | Imani Okoro | 15 Oct | 19 Oct | Completed | |
| OR-26652 | Modesto dock 3 to San Jose branch | Leila Foster | 22 Oct | 27 Oct | Failed | |
| OR-43720 | Stockton dock 7 to Portland store | Evan Park | 16 Oct | 20 Oct | Needs review | |
| OR-74698 | Modesto dock 3 to San Jose branch | Leila Foster | 13 Oct | 16 Oct | Pending |
Planned load to verified handoff ships ready to use. One step needs a named approval before the work moves on: Approve loading (Transport Supervisor).
Prepare the quantity, lane and stop appointments with a named owner.
Review the driver, vehicle and working interval for the planned journey.
Capture the loaded pallets and observed seal at the dock.
Review the submitted physical check and record the decision.
Record the actual handoff and follow the journey through its stops.
Compare delivery proof, freight charges and operational outcomes.
Open any load to see its freight charges, the roles that work on it, its process stages and its approvals on one page.
Requested units, Item code, Lane and Planned departure.
Each line is linked to this load.
Admin, Load Planner and Dispatch Coordinator, each with their own permissions.
Plan load and Dispatch truck, with the role that acts.
Approve loading, with who decides.
APP-TRAIL-210 · Draft
| Charge number | Load | Charge type |
|---|---|---|
| FC-50050 | Stockton dock 7 to Portland store | Linehaul |
| FC-27882 | Modesto dock 3 to San Jose branch | Fuel Surcharge |
| FC-55670 | Sacramento dock 1 to Eugene hub | Accessorial |
Signed in as Transport Supervisor
| Decision | Approver | |
|---|---|---|
| Approve loadingReview the submitted physical check and record the decision. | Transport Supervisor |
Everyone opens Warehouse-to-Truck Loading to the work that is theirs. Pick a role to see what it starts with.
Review eligible revisions independently and reconcile operational evidence.
This is the first screen this role sees.
Load stops · Transport Supervisor
| Stop number | Load | Sequence | Location | Window start | Window end | |
|---|---|---|---|---|---|---|
| LS-51304 | Modesto dock 3 to San Jose branch | 80 | Reno distribution center | 04 Nov | 08 Nov | |
| LS-21800 | Oakland dock 8 to Fresno returns | 90 | Boise retail hub | 29 Oct | 05 Nov | |
| LS-65492 | Bakersfield dock 5 to Las Vegas store | 90 | Fresno warehouse | 18 Oct | 22 Oct | |
| LS-30775 | Oakland dock 8 to Fresno returns | 40 | Oakland service depot | 23 Oct | 25 Oct | |
| LS-29171 | Sacramento dock 1 to Eugene hub | 90 | Stockton crossdock | 01 Nov | 09 Nov |
Maintains organization setup, identities and access for the loading operation.
Prepares transport demand and stop appointments for the loading and assignment workflows.
This is the first screen this role sees.
Load stops · Load Planner
| Stop number | Load | Sequence | Location | Window start | Window end | |
|---|---|---|---|---|---|---|
| LS-51304 | Modesto dock 3 to San Jose branch | 80 | Reno distribution center | 04 Nov | 08 Nov | |
| LS-21800 | Oakland dock 8 to Fresno returns | 90 | Boise retail hub | 29 Oct | 05 Nov | |
| LS-65492 | Bakersfield dock 5 to Las Vegas store | 90 | Fresno warehouse | 18 Oct | 22 Oct | |
| LS-30775 | Oakland dock 8 to Fresno returns | 40 | Oakland service depot | 23 Oct | 25 Oct | |
| LS-29171 | Sacramento dock 1 to Eugene hub | 90 | Stockton crossdock | 01 Nov | 09 Nov |
Coordinates loading checks, resource assignments and physical movement evidence.
This is the first screen this role sees.
Load stops · Dispatch Coordinator
| Stop number | Load | Sequence | Location | Window start | Window end | |
|---|---|---|---|---|---|---|
| LS-51304 | Modesto dock 3 to San Jose branch | 80 | Reno distribution center | 04 Nov | 08 Nov | |
| LS-21800 | Oakland dock 8 to Fresno returns | 90 | Boise retail hub | 29 Oct | 05 Nov | |
| LS-65492 | Bakersfield dock 5 to Las Vegas store | 90 | Fresno warehouse | 18 Oct | 22 Oct | |
| LS-30775 | Oakland dock 8 to Fresno returns | 40 | Oakland service depot | 23 Oct | 25 Oct | |
| LS-29171 | Sacramento dock 1 to Eugene hub | 90 | Stockton crossdock | 01 Nov | 09 Nov |
Reconciles delivery evidence, freight charges and operational outcomes for supervisor review.
This is the first screen this role sees.
Proof of delivery · Evidence Coordinator
Find loading, timing and evidence differences that need an owner.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 41 | ||
| Planned | 21 | 51% | |
| Dispatched | 12 | 57% | |
| Delivered | 7 | 58% |
Sample totals per stage
Which docks have checks waiting for a decision, and which rejected checks still need a corrected physical result?
Where did actual pickup or delivery differ from the planned or promised date?
Which driver and vehicle intervals need review after a late return?
Which stops arrived outside their appointment window or still lack an actual arrival?
Which vehicles have unresolved defects, inspection concerns or service dates that need review?
What charge types and amounts remain under review for each load and currency?
Which captured or disputed delivery records need follow-up?
Which receipts still describe pending, failed or uncertain outcomes?
See how Warehouse-to-Truck Loading fits your kind of team.
Coordinate pallet loading and customer delivery windows at a distribution depot.
Connect the finished-goods loading handoff with transport readiness and delivery proof.
Keep the operating organization, transport partner and loading evidence clear across customer work.
Each stage of planned load to verified handoff names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare loading reviews and investigate operational evidence.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 21 tablesStart with one team and one process, then add the rest once the basics are running.
Choose the depot, lanes and transport partners for the pilot. Name Load Planner, Dispatch Coordinator, Transport Supervisor and Evidence Coordinator. Admin agrees the organization and evidence access policy with them.
Reconcile staff identities, driver eligibility and vehicle unit numbers. Agree the quantity basis and dock naming convention before importing open loads and their stop appointments.
Decide what physical evidence Transport Supervisor needs to approve a loading check. Rehearse an independent decision and a changed seal or pallet quantity that requires another review.
Record the assignment, physical departure, stop arrival and delivery proof. Compare the observed dates with the planned windows and verify which person owns an unresolved delivery document.
Review operation receipts and freight charges with their supporting evidence. Resolve uncertain external outcomes and confirm the next shift can explain the load history before expanding the scope.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Warehouse-to-Truck Loading for your business. Pilot a regular loading lane with recognizable load numbers, current driver and vehicle records, an independent loading reviewer and a receiving contact who can provide delivery proof.
It records the dock, loading time, loaded pallets and seal against the load and operating organization. Dispatch Coordinator prepares the check; Transport Supervisor reviews the submitted revision with the physical evidence.
Transport Supervisor independently approves or rejects the loading check and records the decision rationale. Dispatch Coordinator records the later physical departure. Agree the evidence required for that decision during setup.
Update the loading evidence and put the changed revision before Transport Supervisor. Keep the earlier decision available and identify which review covers the truck that will leave. Resolve the reason for the change with Load Planner.
Dispatch Coordinator reviews eligibility dates, vehicle readiness and the assignment's start and end. Record the availability check and revisit it after an appointment change or late return. Use the fleet authority's evidence where release decisions are maintained elsewhere.
Record pickup, delivery and service stops with appointment windows and actual arrival and departure. Tracking events retain the occurrence time, location and source. Set up the relevant connection for updates from a driver app, telematics service or partner.
Evidence Coordinator captures the delivery time, receiver and signature reference against the load and stop. Captured evidence remains open for verification; use Disputed when the supporting facts need investigation with Transport Supervisor.
Record the charge type, amount and currency against the load. Compare detention or other charges with journey evidence and supporting documents. Configure the finance connection for invoice or payment confirmation and keep those outcomes distinct from delivery.
Bring current partner contacts, driver and vehicle identities, a sample load request and its appointment windows. Rehearse a changed seal, a vehicle replacement and a disputed delivery with the people who will own those actions. Use the implementation plan.
Ordinary manual work and metered machine activity follow the platform's pricing policy, with implementation scoped separately. Review the pricing page using your expected imports, connected activity and retained evidence.
Start free, then use Proto to change fields, steps and approvals before your team goes live.