Skip to main content

Loan Car Accident/Damage Fleet

Covers accident/damage reported against a Crash Claim fleet (loan car) vehicle itself. The claim is lodged directly from the Fleet Dhtml page rather than the usual client-facing intake, but once the claim exists, its Movement Action sequence is identical to Repair Only — the client's/fleet's own vehicle going in for repair and coming back, driven by Hire_Status1 across pick-up and delivery only.


Entry point: Fleet Dhtml page → Quick Links → Lodge Loan Car Accident/Damage.

Clicking it opens the Add Claim form, asking only for Accident Details and Owner Details. On submit, a new claim record is created, and a note is appended to the fleet vehicle's Fleet_Notes on the Fleet Dhtml page.

Fleet Dhtml page → Quick Links → "Lodge Loan Car Accident/Damage"


Add Claim form opens — Accident Details + Owner Details only


Form submitted


New claim record created (File Number)


Fleet Dhtml page → Fleet_Notes updated:
"Vehicle Accident/Damage Reported. Related File Number: ${filenumber}"

Hire Status → Flow

Hire StatusEntry PointFlow
PendingBook New Job Pickup → Update New Job PickupCC Workflow
Collected from ClientRepair Completion → Fleet Sync
Collected from Client / In RepairsBook Delivery → Update Delivery BookingDelivery/Client Vehicle Drop-off Flow

1. CC Workflow — Hire Status == Pending

Hire Status == Pending


Book New Job Pickup


Update New Job Pickup


Accident Detail Confirmation


Authority to Act


Client Vehicle Pick-Up


Add Fuel Receipt


Client Vehicle Drop-off Location


WORKFLOW COMPLETED ⚠

1.1 Book New Job Pickup — Collection Details form

See Collection Details for the full field reference.

1.2 Update New Job Pickup form

FieldRequired
File Number
Assign the Claim to (Claims Consultant)
Rental Vehicle
Delivery Fee Structure
Rental Drop Off Date-Time
Movement Duration
Reason For Towing
Drop Off Address
Same person who is assigned to the Claim (checkbox)
Drop Off Driver
Chase Driver
Notes

1.3 Accident Detail Confirmation

Opens the Accident Detail Confirmation V1 form — shared across most Movement Action claim types, documented on its own page under Forms.

1.4 Authority to Act

See Authority to Act V1 for the full field reference.

1.5 Client Vehicle Pick-Up

See Client Vehicle Pick-Up for the full field reference.

1.6 Add Fuel Receipt — Add Fuel Receipt V1 form

Do you want to add fuel receipt?

├── Yes ──► Related Hire
│ Upload Receipt
│ Fuel Amount (Inc GST)
│ Payment Method
│ Notes

└── No
FieldRequired
Do you want to add fuel receipt?
Related Hire (shown if Yes)
Upload Receipt (shown if Yes)
Fuel Amount (Inc GST) (shown if Yes)
Payment Method (shown if Yes)
Notes (shown if Yes)

1.7 Client Vehicle Drop-off Location

See Client Vehicle Drop-off Location for the full field reference.


2. Repair Completion → Fleet Sync — Hire Status == Collected from Client

Once the CC Workflow completes and the Job's Hire Status moves to Collected from Client, the Fleet Dhtml page and the Claim Dhtml page's Repair section start syncing with each other:

  • Fleet Dhtml page: Vehicle_StatusIn Repairs
  • Three date fields sync both ways between the fleet vehicle record and the claim's Claims Management Form — Repair Details section:
Fleet Dhtml FieldSynced With (Claims Management Form → Repair Details)
Fleet - Sent to Repair DateDate Sent to Repair (Date_Sent_to_Repairer)
Fleet - Repair ETA DateRepair ETA (Repair_ETA)
Fleet - Repair Completed DateRepair Completed Date (Date_Repair_Completed)

The Claim Dhtml page's Repair section opens the Claims Management Form directly, showing the same three fields (Date Sent to Repair / Repair ETA / Repair Completed Date). Updating any of them from either side — Claim Dhtml → Repair section, or the Fleet Dhtml page — updates the matching field on the other page.

Hire Status → Collected from Client


Fleet Dhtml page: Vehicle_Status = "In Repairs"


Claims Management Form → Repair Details filled in:
Date Sent to Repair / Repair ETA / Repair Completed Date


Synced to Fleet Dhtml page:
Fleet - Sent to Repair Date = Date Sent to Repair
Fleet - Repair ETA Date = Repair ETA
Fleet - Repair Completed Date = Repair Completed Date


Either side edited (Claim Dhtml → Repair section, or Fleet Dhtml page)
→ the other side updates to match

3. Delivery/Client Vehicle Drop-off Flow — Hire Status == Collected from Client / In Repairs

Hire Status == Collected from Client / In Repairs


Book Delivery


Update Delivery Booking


Vehicle Inspection


Add Fuel Receipt


Client Vehicle Condition Sign-Off


WORKFLOW COMPLETED ⚠

3.1 Book Delivery

See Book Return Form V1 for the full field reference.

3.2 Update Delivery Booking

Same form as above — Book Return Form V1.

3.3 Vehicle Inspection

See Vehicle Inspection V1 for the full field reference — this inspects the fleet vehicle.

3.4 Add Fuel Receipt — Add Fuel Receipt V1 form

Do you want to add fuel receipt?

├── Yes ──► Related Hire
│ Upload Receipt
│ Fuel Amount (Inc GST)
│ Payment Method
│ Notes

└── No
FieldRequired
Do you want to add fuel receipt?
Related Hire (shown if Yes)
Upload Receipt (shown if Yes)
Fuel Amount (Inc GST) (shown if Yes)
Payment Method (shown if Yes)
Notes (shown if Yes)

3.5 Client Vehicle Condition Sign-Off

See Client Vehicle Sign-Off V1 for the full field reference.


Video Walkthrough


Full Lifecycle

Fleet Dhtml → "Lodge Loan Car Accident/Damage" → claim created, Fleet_Notes updated


Hire Status: Pending


CC Workflow ──────────────────► WORKFLOW COMPLETED


Hire Status: Collected from Client


Repair Completion → Fleet Sync
(Fleet Dhtml page: Vehicle_Status = "In Repairs"
+ Sent to Repair Date / Repair ETA Date / Repair Completed Date synced)


Delivery/Client Vehicle Drop-off Flow ──► WORKFLOW COMPLETED

  • Movement Action — the general CC / Loan Car Swap / Delivery / PRI-Recto flow reference
  • Repair Only — the equivalent flow this claim type mirrors, lodged the normal way
  • FleetVehicle_Status, Fleet_Notes, and the Repair-sync fields
  • Claims_Management_Form — Repair Details section (Date_Sent_to_Repairer, Repair_ETA, Date_Repair_Completed)
  • JobsHire_Status1 values, per-flow stage fields
  • Vehicle_Movement — movement form field schema