If you don’t see this in your navigation, your administrator can switch the module on under Administration → Modules, or it may not be included in your plan.


What a booking can hold
Kinds of booking
Every booking has a kind, which decides what it may hold, who it may be charged to, and how much setting-up time is kept free before and after. A new organisation starts with these defaults, which your administrator can change under Configuring bookings:
The time kept free counts wherever it falls. A hire that runs to the end of a day with two hours kept
free after it holds the asset until 02:00 the next day, so the next day’s calendar shows it as booked
until then. People are never given setting-up time.
Bookings are made in whole days. A booking runs from the start of its first day to the end of its
last, and any part of a day counts as a day of hire.
The register
The header
When a booking is due for check-out, a Due for check-out panel lists it with when it was due
out, and Issue (where it has an asset on it) or Release beside each. When something is due for check-in, a Due for
check-in panel lists it with when it was due back, and Extend or Receive beside each. When
charges could not be priced, a panel lists them with Fix the rate cards. A charge with no rate is
banked with no amount rather than nought, so it cannot be mistaken for something priced at zero.
Filters
Columns
Status
These are the statuses a booking moves through. The register’s cells and its status filter use the same words. Due for check-out and Due for check-in are never set by anybody: they are read off the booking’s dates, so a booking becomes due the minute its start or its end passes and stops being due the minute something is handed over or taken back.
Where a collection rule sets reminder days, whoever raised a booking and whoever it is for are emailed
before it starts, while nothing has been handed over, and before it is due back, while it is out.
Whether a booking needs approving is a published workflow rather than a setting on the kind, so the
workflow can name who approves. Confirm runs that workflow if one is published. A booking cannot
be confirmed with nothing on it. Confirming is not needed before a hand-over: a booked booking with an
asset on it can be issued straight away, and only one still awaiting approval is held back.
Raising a booking
New booking on the register, Book it on an asset’s Bookings tab, Book on the asset register’s bulk bar, or a selection on the availability calendar, all open the same form.

Rate cards and booking defaults are set up under Configuring bookings.
Raise it creates the booking and everything it holds together. If one line clashes, nothing is
held at all — you never end up with half a booking. More can be added later with Hold something
on the booking.


Changing a booking
Until something on it has been handed over, a booking is still a plan and can be changed. Edit on the booking (shown while it is awaiting approval, booked or confirmed) opens the same form, titled Change booking number, carrying its lines — so correcting a date, who it is for, who pays, the site or what it holds no longer means releasing it and raising it again. Kind is shown but cannot be changed, because the number, the allowances and the approval the booking went through were all decided under it; a different kind is a different booking. Save changes saves it.

Inside a booking


Changing how a line is billed
While a booking is still open, the pencil beside a line’s Billed opens How it is billed:Actions
At Take it back, the Site opens on where the asset is now and says which site the booking is
for. Choose where it was actually received, and the asset is moved there — a note beside it says
Stays at the site or Moves from one site to the other. If you cannot move assets, it goes
back to where it is now.
Handing it over
Issue opens Hand it over: one table with a row for every machine still waiting to go out on the booking, or on every booking you chose to issue together. Anything fitted to a machine is listed under its row, marked goes with it, and goes out with it.
Below the table are any Parts going with them, the Checklists going out, and who pays —
asked once for all of the bookings, because only bookings with the same payer go out together. A
booking charged to a Cost Center goes out on that Cost Center, shown with its Indirect project and
Indirect task and not changeable here; where a requisition raised the booking, the hint says
As that requisition charged it. A change made here is recorded on each booking under
Changed at hand-over. The footer counts how many rows are still to scan or complete, and
names a machine that still has checklist questions to answer.
A booking handed over before the day it starts shows Going out before the booking starts: handing
it over moves its start to now, and what goes out is held and charged from then. The booking records
it as Started early.
Swapping a machine
The machine at the counter is not always the one booked. Swap under a row offers Another category at this site, free for the whole booking:- Scan the machine you have in your hand. If the line can take it, it is swapped in and proved in one step.
- Or pick it from Choose the machine. The line is swapped at once, and the row shows where to fetch the machine from until you scan it.
Issuing several bookings together
A crew going to one job often takes machines from several bookings. Tick the bookings on the register and choose Issue together: they open in one Hand it over table, so the person taking them and who pays are answered once. Only booked or confirmed bookings with an asset on them can be ticked, and only bookings with the same payer and the same project tasks go out together.Checklists at hand-over and return
Where your organisation has set a checklist for an asset under Configuring bookings, it is asked as the asset goes out and as it comes back — at Hand it over, at Take it back, and when an asset is issued or returned without a booking. Each row shows how many of its questions are answered, and clicking that opens the checklist below the table. Required questions must be answered before you can confirm. Photographs and signatures are not taken at the counter. A failed answer asks What is wrong. The answers are kept with the booking line: Checklists on the booking says whether each passed, or how many questions failed.Deposits and charges
Hold a deposit records an Amount held against the booking. A deposit is not a charge and does not appear on the ledger: Give it back returns it with nothing recorded, and Keep it (with Why it is being kept) turns it into a charge. Handling deposits needs Hold, return and keep hire deposits. Every other charge appears on the ledger, priced from the rate cards. A reservation that is merely held costs nothing and has no entries until something is spent.What is free — the availability calendar
Availability answers the question the list cannot: what is free, and when.

Rows are classes of thing — an asset category, a tool type, a place, a role — with what is in each
underneath, so a fleet of two hundred still opens on a readable grid. Each cell is a day, and the
number in a class row is how many in that branch are free for the whole day. The legend under the
grid reads all free, some out, few left, none free, this one is held and
returned; a place booked for part of a day shows as partly free. Days are cut at midnight on the site’s own clock, and
the time a booking kind keeps free before and after counts, even when it runs past midnight into the
next day. Assets your organisation keeps out of bookings are not counted at all, so a yard with three
machines to hire and three it is selling reads three, not six. Move between months, or This month
to come back.
What the calendar counts as out:
- A hire still out past the end of its booking stays held up to today, and the day’s detail says overdue, still out beside its planned end.
- A hire that has been received is drawn up to the day it came back, as returned, and frees the days after it.
- An asset issued without a booking is held until it is Required until, and the day’s detail says Issued without a booking.
Booking several assets at once
Each machine’s row has a tick box, and so does each category’s row — ticking a category ticks every machine in it that is free for the days you dragged. The ticks collect in a tray under the grid, which shows the days and asks whether every machine ticked is free for every one of them. It names any that are not, so you can untick them or change the days. Book N opens the form as New bookings and raises one booking for each machine with the same answers — who it is for, who pays and the rest. They are raised together or not at all; a clash marks the machine it was on.On an asset
An asset’s Bookings tab lists every booking line ever held against it — not just upcoming ones, because a finished hire is what a utilisation figure is made from — with Book it, What is free, and Issue or Return. Below it, Issued and returned lists every time the asset went out and came back, with or without a booking. See inside an asset. An asset can also go out with no booking at all, from the asset register — see issuing and returning.Who can do what
Configuring bookings
What your organisation books at all, what each kind of booking may hold and be charged to, and
rate cards.

