1. Ambulance Fleet Management
  2. Features
  3. Review and Evidence
Feature · Review and Evidence

Review and Evidence

Trace readiness decisions and supporting files to the actual recorded outcome of unit-release work.

OverviewOperation Exceptions
Ambulance Fleet Management · Review and Evidence

Operation Exceptions

Operation receipts

New
ParentActionOperation keyExpected revisionResult stateOccurred at
TRN-50644ACT-402OK-762930Pending13 Oct
TRN-99945ACT-460OK-64970Failed12 Oct
TRN-87218ACT-369OK-281700Needs review12 Oct
TRN-66887ACT-193OK-661720Pending09 Oct
TRN-98791ACT-369OK-459390Failed03 Oct
6 of 6 records
ACT-402Operation receipts · OR-17753
Pending
ParentTRN-50644
Operation keyOK-762
Expected revision930
Occurred at13 Oct
Effect referencesER-385
Example screen with sample data

What you can do

Keep the decision and its outcome understandable

A readiness decision identifies the check revision considered by the Fleet Supervisor. It records the reviewer, decision date and reason, with a link to the readiness check and an optional transport reference. This gives the next shift a way to understand why the unit-release work advanced or needed correction.

Operation receipts record the action, expected revision and result. The result shows whether the operation is pending, completed, failed or needs review. The Fleet Supervisor compares that result with the check and decision evidence before explaining it to the Dispatcher. Attachments provide supporting files linked to the transport, with an uploader and visibility choice.

How the work is organized

  • Retain the review reason. The Fleet Supervisor records Approve, Reject or Return against the intended readiness check. Keep the source revision visible so a decision on earlier evidence is not mistaken for a decision on later changes.
  • Inspect operation exceptions. Read the action and failure reason before choosing a follow-up. A Pending receipt needs investigation; it should not be treated as proof that the unit-release operation completed.
  • Handle supporting files deliberately. The authorized team member names the attachment, identifies its evidence type and chooses Internal or Shared visibility. Keep the file associated with the transport whose operating history it explains.

What to agree during setup

Agree what a useful decision reason contains and which evidence the Fleet Supervisor needs for a release decision. Define who investigates failed or disputed receipts and how the result is communicated to the Dispatcher. Keep the original operation identity available during follow-up so the team can distinguish an investigation from another release attempt.

Establish attachment naming and visibility rules for the service. Decide who can inspect supporting files and rehearse that access with real user identities. The Auditor needs the authorized operating history while editing and approval responsibilities remain with the roles that own the work.

Check the handoff on an actual case

Use a submitted readiness check whose equipment notes require clarification. The Fleet Supervisor records a Return decision with a reason. The Crew Lead corrects the evidence under the agreed process, and the supervisor reviews the current revision. Compare the decision history so the correction remains understandable.

The Fleet Supervisor then inspects a release receipt flagged for review and identifies the claimed action, revision and failure explanation. The supervisor compares it with the readiness check and decision before choosing the follow-up. The Dispatcher adds the relevant transport evidence using the intended visibility, and the Auditor reads the final record. The rehearsal should leave a clear explanation of the decision and result without rewriting earlier evidence.

What your team sees

  • Operation Exceptions — Pending or failed operations and operations needing review, with their revision and failure explanation.
  • Readiness Decision History — Decisions linked to the readiness check and source revision considered.
  • My Transport Evidence — Files uploaded by the signed-in team member, with their transport and visibility.

Follow the work through

Rehearse readiness and unit release and use completion and evidence to distinguish release evidence from the transport outcome.

What it keeps track of

Data model
Review decisions
Independent approval decisions on frozen revisions
Operation receipts
Stable receipts for every guarded operation
Record attachments
Uploaded evidence files linked to loads
Crew readiness checks
Crew and equipment readiness checks supporting ambulance unit release
Transports
Plan and track ambulance patient transports from Draft through Delivered, with promised delivery, transport charge and linked evidence.

Who uses it

Permissions
Fleet Supervisor
, Dispatcher, Crew Lead, Fleet Maintenance Tech, Auditor.
The Fleet Supervisor owns independent decisions and exception investigation; authorized preparers supply evidence, and the Auditor reads the retained history.

Set up Ambulance Fleet Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started