References
Start with the exact load identity.
Require dispatch's load reference. Keep customer and broker numbers separate.
- Internal load or shipment ID.
- Customer, broker, purchase order, or bill-of-lading reference.
- Reporter and timestamp.
Describe your freight workflow and Makeform creates a load tracking form for dispatchers and drivers. Capture references, stops, status updates, exceptions, and delivery confirmation in one flow.
Route load updates to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a workflow, edit the prompt, and send it to the Makeform builder. Each structure is an example you can tailor.
Audience
Dispatchers entering newly assigned freight
Format
Master load intake with route and assignment details
Prompt size
233 chars
Example form structure
Master load intake with route and assignment details
Load ID and customer reference
Commodity, weight, pieces, and pallets
Driver, tractor, and trailer assignment
Pickup and delivery appointments
Current load status
Suggested routing tags
At pickup
In transit
Exception
Delivered
Use a required load ID on every update. It is the stable key dispatch needs to match pickup, in-transit, exception, and delivery submissions.
Step 1
Create
load ID, freight, stops, and assignment
Step 2
Update
location, milestone, time, and ETA
Step 3
Escalate
delay, damage, rejection, or breakdown
Step 4
Close
delivery time, receiver, and documents
Why structured tracking
Calls and messages omit references, event times, or the next update. A load tracking form asks for the same facts at every milestone.
A required load number ties assignment, pickup, check calls, exceptions, and proof of delivery to the same freight movement.
Conditional fields can request seal details at pickup, recovery plans for delays, and receiver details only after delivery.
Route a selected exception to dispatch immediately while routine in-transit updates continue into the normal tracking record.
Built for freight workflows
Start with a driver check call, dispatcher record, or stop log, then adjust labels and routing.
Record tractor, trailer, seal, pickup, delivery, current location, and ETA against one load number.
Repeat arrival, dock, completion, and departure milestones for each numbered pickup or delivery stop.
Keep broker references and customer-safe status notes beside the carrier's operational load reference.
Capture out-for-delivery status, recipient details, delivery result, photos, and a reason when delivery fails.
Tracking workflow
Turn existing milestones into a focused form for dispatchers and drivers.
Choose assigned, dispatched, arrived, loaded, in transit, delivered, and exception events.
Require the load ID, event timestamp, location, and reporter so an update can be matched and understood without a follow-up call.
Show detention minutes, damage photos, rejected quantities, or breakdown details only when the selected milestone requires them.
Notify dispatch about exceptions and route updates for sorting by load, status, and ETA.
Form vs calls vs spreadsheets
A form does not replace a transportation management system. It gives teams and outside drivers consistent intake for dispatch facts.
Field guide
Build around stable identifiers, scheduled stops, actual milestone times, and actionable exceptions. These six sections keep a freight update specific without making it slow to submit.
References
Require dispatch's load reference. Keep customer and broker numbers separate.
Freight
Capture details needed to spot a pickup or delivery mismatch.
Stops
Compare appointment windows with actual arrival and departure times.
Status
Pair a controlled status list with location and ETA.
Exceptions
Ask what happened, its impact, who must act, and when to expect an update.
Closeout
Record the actual outcome and only the documents your workflow needs.
Related tools
Create focused forms for delivery, inspection, incidents, equipment checkout, and maintenance alongside your load status intake.
Record recipient details, delivery outcomes, and supporting documents at the final stop.
Open toolCreate a pre-trip or post-trip condition checklist for tractors and trailers.
Open toolStandardize recurring condition reviews across multiple vehicles in a fleet.
Open toolCollect a structured account, location, people, photos, and follow-up details after an incident.
Open toolSend driver-reported defects and repair needs into a maintenance intake queue.
Open toolTrack assigned scanners, straps, tools, and other gear that travels with a driver or load.
Open toolFAQ
Practical answers for dispatchers, carriers, brokers, and logistics coordinators building a consistent freight status workflow.
It records freight status events from dispatchers, drivers, or carriers. A load ID connects each milestone, location, event time, ETA, exception, and delivery outcome.
Require load ID, status, event time, location, reporter, and ETA. Add a stop number for multi-stop freight and cause, impact, recovery plan, and next update for exceptions.
Yes. Use dropdowns for milestones and reveal longer fields only when needed. Drivers can open a shared link, enter the reference, choose a status, add times or photos, and submit.
Use one load ID and require a stop number on every event. Capture appointment, arrival, dock, completion, and departure separately to create a clear stop sequence.
Yes. Conditional questions can cover detention, breakdown, damage, shortage, overage, rejection, or missed appointments. Ask for impact and next action, then route the submission to dispatch.
Yes. Add uploads to delivery and exception branches for proof of delivery, receipts, seal photos, freight condition photos, or another supporting file.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier only removes the Makeform badge.
No. A form is structured intake, not telemetry or a transportation management system. It helps people report milestones consistently and route them into another operational tool.
Replace scattered check calls with structured updates.