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.


The stat strip counts kinds of booking, rate cards in force and the resource kinds priced by
nothing. When something is priced by nothing, a banner names it — for example tools, places, people
have no rate card in force.
Who can change this. Kinds of booking, booking defaults, collection rules, the assets not offered
and what this organisation books need
Add configuration entries and Edit configuration entries. Rate cards need Add booking rates
and Edit booking rates.
What this organisation books
The product reserves five kinds of thing: Assets, Tools, Parts, Places and People. Untick the ones your organisation does not book and they stop being offered — on the New booking form, on the availability calendar and in what a kind of booking may hold. Anything already booked stays booked; what this refuses is the next one. A booking that tries to hold anything unticked is refused at the counter, whichever screen it came from. Save keeps the change and Discard throws it away.Assets not offered for booking
Shown on General while your organisation books assets. A register usually holds more than is for hire — the workshop, fixed plant, machines being sold — and every one of them would otherwise be offered on the New booking form and counted as free on the availability calendar. Assets matching any one of these rules are left off the New booking form and the availability calendar, and refused if somebody tries to book one another way. Anything already booked stays booked.
Any one rule is enough to keep an asset out; there are no combined conditions and no per-asset
exception. The section says how many assets are kept out, or Every asset is offered for booking.
Save keeps the change and Discard throws it away.
Checklists at issue and return
Shown on General while your organisation books assets. A checklist chosen here is asked at the counter as an asset goes out and as it comes back — at a booking’s hand-over and return, and when an asset is issued or returned without a booking. See checklists at hand-over and return. Until a rule is added, the section says No checklist is asked at issue or return. Each rule is a row:
Where several rules fit one asset, the most specific is used: a site before any category, a deeper
category before its parent, and a named status before any status. Add a rule adds a row, and
Save keeps the rules.
Which checklist would this asset get? answers for one asset you choose, going out and coming back,
or says No rule fits. It answers from the saved rules, not changes you have not saved yet.
Booking defaults
How a booking line opens: how often it is billed, whether it is charged, and which rate cards are offered for it. A site’s rule beats its business unit’s, which beats its company’s, which beats the organisation’s; at one place, a rule for a narrower asset category wins. A setting a rule leaves empty comes from the wider rule, setting by setting. Every line can still be changed on the booking itself, and an asset’s own answers about whether it is chargeable and which rate cards it is offered on beat these rules. A new asset’s form fills both in from the rule that applies to it.
Search booking defaults finds a rule, and Filter narrows the list by any column. Add opens a
new rule; click a rule to edit it.


Collection and reminders
When a booking nobody collects is written off as a no-show, and when whoever raised a booking and whoever it is for are reminded by email to collect it and to bring it back. Each rule is for a place: a site’s rule beats its business unit’s, which beats its company’s, which beats the organisation’s, and a setting a rule leaves empty comes from the wider rule. Where nothing says, a booking is written off an hour after it starts, no reminders are sent, and reminders that are sent go out at 08:00.
A setting a rule leaves to the wider one reads as the wider rule. Add opens a new rule; click a
rule to edit it.
A rule must set at least one of the four. Each reminder is sent once for a date, so a booking moved to
another day is reminded again.
Rate cards
One price per card: what an hour, a day or a meter unit of something costs, and who it costs that much for. Each card belongs to a business unit. To charge the same thing by the day and by the week, add a card for each, and choose between them on the booking’s line. A card naming a category prices anything in it that has no default of its own; one naming no category is chosen rather than matched — set as a machine’s default rate card on the asset, or picked on a booking’s line.
Find by name, code or unit searches the cards, and Filter narrows them by any column.


Kinds of booking
What somebody picks first when they raise a booking, and what the product then does about it. The defaults are Equipment hire, Hire to customer, Person booked, Room booking and Tool booking.

What this kind of booking is
What it is opens two lists, saved together:

Nothing ticked is the widest setting, not the narrowest. The registers behind cost centres,
departments, business units and projects are under organisation structure,
and customers under vendors and contracts.
Whether a booking must be approved before it is confirmed is not set here. It is a published
approval workflow, which can also say who approves it.

