These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Ambulance Fleet Management
- Features
- Transport Planning
Transport Planning
Prepare an ambulance transport with its receiving facility, responsible dispatcher and planned stop windows.
OverviewDelivered Transports×
Ambulance Fleet Management · Transport Planning
New
Delivered Transports
Transports
| Transport number | Receiving facility | Promised delivery at | Actual pickup at | Actual delivery at | Transport charge USD | |
|---|---|---|---|---|---|---|
| TRN-53635 | RF-8684 | 17 Oct | 25 Oct | 28 Oct | 960 | |
| TRN-77941 | RF-4929 | 15 Oct | 21 Oct | 27 Oct | 110 | |
| TRN-25216 | RF-6793 | 22 Oct | 24 Oct | 26 Oct | 680 | |
| TRN-23615 | RF-2285 | 23 Oct | 31 Oct | 08 Nov | 680 | |
| TRN-16676 | RF-1709 | 15 Oct | 18 Oct | 20 Oct | 920 |
6 of 6 records
RF-8684Transports · TRN-53635
DeliveredPromised delivery at17 Oct
Actual pickup at25 Oct
Actual delivery at28 Oct
Transport charge USD960
What you can do
Give the transport a clear operating record
The Dispatcher starts with a transport number and a summary that the operating team can recognize. The record identifies the receiving facility, owning organization and responsible team member. A promised delivery date provides the reference for later comparison with the actual receiving-facility outcome.
Stops describe the pickup and transfer sequence. Each stop can hold its address and planned window, followed by actual arrival and departure information as the work progresses. Keeping those details with the transport helps the Dispatcher distinguish a change in destination from a change in the time the team expects to arrive.
How the work is organized
- Confirm the destination. The App Administrator maintains receiving-facility codes, contacts and eligibility notes. The Dispatcher checks the intended facility and organization before preparing the transport, especially when similar names appear in different operating areas.
- Prepare the stop sequence. The Dispatcher records each address and window in the intended order. Check the pickup and receiving-facility stops together so a later reader can follow the planned movement without reconstructing it from attachment titles.
- Move the plan into operations. Once the details have been checked, the Dispatcher moves the transport from Draft to Planned. The driver assignment and unit-readiness decision remain related work that must be reviewed before dispatch.
What to agree during setup
Agree what belongs in the transport summary and how the team identifies the requested unit type. Use the receiving-facility record for destination details that should be maintained centrally. Decide who resolves a disputed contact or address before the Dispatcher uses it in another transport.
Set the operating organization’s time zone and explain how planned windows and actual events are recorded. Also agree how the USD transport charge is maintained and who checks it. A recorded charge provides operational context; invoicing and payment handling should be connected through the customer’s chosen financial process.
Check the handoff on an actual case
Prepare a pilot transfer with a pickup stop and a receiving-facility stop. The Dispatcher selects the correct facility, records the planned windows and sets the promised delivery date. Have another team member read the record and explain the intended sequence before the plan moves forward.
Change the receiving-facility address during the rehearsal. Check which stop information needs an explicit update and confirm the Dispatcher can still explain the current plan. Then move the transport to Planned and open its assignment schedule. The plan should remain identifiable while the crew readiness check and named driver assignment are prepared. A planned status alone should not be used as the unit-release decision.
What your team sees
- Transport Planning Queue — Draft and planned transports with receiving facilities, promised dates and responsible owners.
- My Transports — Transport work assigned to the signed-in team member.
- Transport Status Board — The operating workload grouped by its current transport status.
Follow the work through
Continue with transport planning and dispatch, then use completion and evidence to compare the plan with the recorded outcome.
What it keeps track of
Data model- Transports
- Plan and track ambulance patient transports from Draft through Delivered, with promised delivery, transport charge and linked evidence.
- Transport stops
- Pickup, receiving-facility and transfer stops for ambulance transports.
- Receiving facilities
- Hospitals and other receiving facilities eligible for ambulance transports.
- Organizations
- Operating organizations that own ambulance fleet records
- Team members
- Named members of an organization with role scope
Who uses it
Permissions- Dispatcher
- , App Administrator, Fleet Supervisor, Auditor.
- The Dispatcher prepares the operating plan, the App Administrator maintains facility and organization details, and the Fleet Supervisor reviews follow-through.
Set up Ambulance Fleet Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.