Glossary
Handover
A handover in Kasura is the moment an asset changes between the business and the customer, recorded through a dedicated guided process.
In Kasura
Handover is the umbrella concept in Kasura for the moment an asset changes between the business and the customer, recorded through a dedicated guided process rather than a simple status change. It specializes into four workspace-specific forms: pickup and return for vehicle workspaces, check-in and check-out for accommodation workspaces. Pickup is the process in which staff record payment, deposit and the vehicle's condition before the customer takes it; return is the process in which staff record the vehicle's condition on its way back, apply any fees, and resolve the deposit. Check-in is the process in which a guest takes occupancy of a unit, with payment and deposit state recorded; check-out ends that occupancy, optionally records notes and photos, and resolves the deposit while moving the unit into a readiness state. What connects all four is not that they are the same operation — they are fachlich distinct, with different fields, different outcomes, and different downstream states (a vehicle returns to the fleet, a unit enters a readiness state) — but that they share the same configurable field-visibility mechanism, letting each workspace decide which fields are visible or required at each handover stage.
Why this exists
Handover exists as a single umbrella concept because pickup, return, check-in and check-out are all the same fundamental moment — an asset changing between business and customer — expressed differently per workspace type.
Related terms
- Return — Return is one specific form of Handover.
- Check-out — Check-out is one specific form of Handover.
- Field Visibility — Handover is configured through Field Visibility.
- Setting — Handover is configured through Setting.
- Operational Thinking — Handover is part of Operational Thinking.
Part of: Handover and Condition, Operational Workflow Design
← Back to Glossary