← Equipment management glossary
Also called: booking vs checkout, reservation and checkout.
The lens was reserved for Thursday. On Thursday it was already gone — someone had taken it on the Tuesday without booking, and the booking had no way of knowing.
A reservation is a claim on future time. A checkout is custody now. They answer different questions, which is why a system offering only one always feels like it is missing something.
Future claim, present custody
A claim on time
From Tuesday to Thursday, this item is promised to this person or project. Nothing has physically moved.
prevents double-bookingCustody now
The item has physically left, this named person holds it, and it is due back at a stated time.
can become overdueWhat goes wrong with only one
Reservations only and you know what was promised but not what actually happened. Equipment reserved and never collected reads as unavailable, so it sits idle while someone is told they cannot have it.
Checkouts only and you have accountability with no planning. Availability is unknowable in advance, so allocation becomes first-come-first-served and the person who needed it most finds out too late.
The gap between them is a metric
When both are recorded, comparing planned against actual is one of the more revealing things you can measure. Reservations that never became checkouts mean over-booking — people reserving defensively because they do not trust availability. Checkouts with no reservation mean the booking process is being bypassed, usually because it is slower than just taking the thing.
Either pattern is a process signal, and neither is visible if you only run one half.
What goes wrong without it
Running reservations without checkouts means idle equipment looks busy; running checkouts without reservations means nobody can plan, so allocation becomes whoever asks first.
How Itefy handles it
Itefy runs both on one registry, converts a reservation into a checkout in a click with the details carried over, and reports planned against actual. Read more.