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 Completion
Transport Completion
Record actual pickup, stop events and receiving-facility completion against the transport plan.
OverviewTransport Exceptions×
Ambulance Fleet Management · Transport Completion
New
Transport Exceptions
Transports
| Transport number | Transport summary | Receiving facility | Owner | Promised delivery at | Actual pickup at | |
|---|---|---|---|---|---|---|
| TRN-99994 | TS-853 | RF-2021 | 03 Oct | 08 Oct | ||
| TRN-73550 | TS-403 | RF-2220 | 15 Oct | 20 Oct | ||
| TRN-24800 | TS-525 | RF-3965 | 18 Oct | 21 Oct | ||
| TRN-89528 | TS-140 | RF-2402 | 15 Oct | 19 Oct | ||
| TRN-50650 | TS-225 | RF-1410 | 21 Oct | 25 Oct |
6 of 6 records
TS-853Transports · TRN-99994
ExceptionReceiving facilityRF-2021
Promised delivery at03 Oct
Actual pickup at08 Oct
Actual delivery at11 Oct
What you can do
Compare the operating plan with what happened
The Dispatcher records the actual pickup and delivery events on the transport. Stop records provide more detail through actual arrival, departure and proof references. These records let the Fleet Supervisor examine a completed movement alongside the promised delivery date and the windows recorded during planning.
Delivered describes the transport outcome. Completed describes the related assignment when that assignment has finished. A readiness check may also be Completed, but that state concerns the unit-release work. Keeping these events distinct helps the team avoid reading a release receipt as evidence that the receiving facility has received the transport.
How the work is organized
- Record pickup progress. As the operating team confirms pickup, the Dispatcher records the pickup actual and relevant stop events. Move the transport from Dispatched to In Transit when that reflects the reported event.
- Confirm the receiving-facility outcome. Record the actual delivery date and the relevant stop proof reference. Mark the transport Delivered and the assignment Completed when their respective events are confirmed.
- Review timing and exceptions. Compare promised and actual delivery information without inventing dates for incomplete records. Use Exception when the transport requires operational follow-up and retain the evidence needed to explain it.
What to agree during setup
Agree who supplies actual event information and who enters it in the record. Define the meaning of pickup, arrival, departure and delivery for the team’s operating procedure so the same event is recorded consistently across shifts. Establish how corrections are explained when an event date was entered incorrectly.
Decide what a proof reference identifies and where its supporting evidence is retained. If events arrive from an external dispatch or location system, agree that connection and its event mapping before relying on it. The transport record should make the receiving-facility outcome understandable without claiming a live location feed from manually entered dates.
Check the handoff on an actual case
Take a pilot transport with planned stop windows and a promised delivery date. Record pickup, the actual stop events and the receiving-facility completion. Have the Fleet Supervisor compare the final delivery actual with the promise and explain the timing using the stop information.
Repeat the exercise with a transport that reaches Exception before completion. Keep the recorded actuals that genuinely occurred and identify the outstanding operating question. The Dispatcher should not fill an unknown completion date just to close the record. Finally, inspect the assignment and readiness check so the team can identify which work is complete and which record still requires attention.
What your team sees
- Delivered Transports — Receiving-facility outcomes with promised and actual delivery information.
- Stops Due — Stops whose planned windows have ended, with recorded arrival and departure dates for review.
- Transport Exceptions — Transports requiring operational follow-up before their outcome can be explained.
Follow the work through
Follow completion and evidence and revisit transport planning and dispatch when an operating change affects the original plan.
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.
- Transport assignments
- Driver and vehicle assignments for ambulance transports.
- Record attachments
- Uploaded evidence files linked to loads
Who uses it
Permissions- Dispatcher
- , Fleet Supervisor, Auditor.
- The Dispatcher maintains operating progress, the Fleet Supervisor reviews timing and exceptions, and the Auditor follows the supporting record.
Set up Ambulance Fleet Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.