
The work happens between lock-up and dawn and it is sold by the contract, not the job. Set the run once and every night of the term is already on the board.
Online booking
A builder who needs a yard watched from tomorrow does not ring at nine in the morning. Your page takes it, priced, while the site is already dark.
Learn moreSmart scheduling
Set the hours the crew actually work and the board draws the night from lock-up to dawn, instead of a day that has finished before you clock on.
Learn moreA client signs for two patrols a night for twelve months. That is not a booking, it is a pattern, and it should go on the board once.
Set the pattern once and end it on a date at the end of the contract. Visits are generated ahead, so the run is on the board before anybody asks where it is.
Two patrols a night is two standing arrangements against the same site, each its own booking with its own time and its own guard.
Repeating bookings are on every plan. Move one night and you choose whether the rest of the term follows it or stays where it is.
A tool built around nine to five is no use here: the first job starts at ten at night. Hours are set per guard, so the board draws the real shift.
Each guard has their own weekly hours and their own nights off, and nobody is offered a shift that falls outside them.
Drag a patrol onto a different guard or a different hour when somebody calls in sick, and the whole run moves before the shift starts.
Two jobs cannot sit on one guard at one time. The database refuses the overlap, so a clash is caught when it is made rather than at two in the morning.
Bookables is not a licence register and will not pretend to be one. What it holds is which services each guard is assigned, and only a guard carrying that service is ever offered the work.
A trip out at half past one is not the contract rate with a different name on it. Run it as its own service so it is booked, priced and billed as the separate thing it is.
On Pro one document carries three versions of the same site: one patrol a night, two, and two with a lock-up on the end. The client picks the one they want and accepts it by typing their name.
The gate code, where the panel sits and who to ring at two in the morning belong on the site, not in somebody's phone. Every patrol, every callout and every payment lands on the same record, so the guard covering it for the first time knows what the last one knew.
Built for your trade
A run of sites checked two or three times a night, each patrol its own standing arrangement so the whole term sits on the board from day one.
A trip at three in the morning, booked as its own service at its own price rather than swallowed by a contract rate that never covered it.
Close a site at night and open it at first light, two short bookings against the same record, so there is a note of who locked up and when.
A fixed-term run for the length of the build, ending on the date the fence comes down, with its own hours and its own guards.
Car park and loading dock checks between close and open, repeating every night of the week the centre asked for and no others.
A weekly drive-by on a property nobody lives in, priced per visit, with the access notes and the agent to ring on the site record.
One guard on one site for a set number of nights, booked as a block with the hours it actually runs rather than as a string of callouts.
A weekend of guards on a site with its own hours, quoted as a document the organiser accepts before anybody is rostered on.
Holding keys for a business over the shutdown, with the alarm code and the keyholder to ring kept on the same record as every visit.
A managing agent with six addresses is one record with six sites under it, each with its own history and its own standing arrangement, and one balance across the lot.
Cover for a new site is won on paper before anybody drives it. Each one shows whether it has been opened and whether it has been accepted, so a renewal that has gone quiet is visible rather than assumed.
A contract client pays monthly and a one-off callout is settled the same week. Both are the same kind of record here, billed differently.
Record a transfer against the job by hand in a few taps. That is free on every plan and it always has been.
Send a payment request as a link the client opens and settles, and card money is paid out to your own account rather than held here.
Every booking carries its own paid and outstanding figure, and an invoice comes off it as a PDF the moment the client asks for one.
A patrol run is bounded by what one vehicle can drive in a shift. The areas you claim decide which sites your page will even take on.
A new address is matched against your areas first, so nothing lands confirmed for a yard nobody was ever going to reach in time.
Guards are assigned to areas, so the far end of the run goes to whoever is already working that side rather than whoever answered.
A site outside your areas is not turned away flat. It waits on a yes from you instead of taking a slot on its own.
Nobody rings a patrol company at a convenient hour. What arrives while the crew is out should not be a voicemail with half an address on it.
The request carries the address, what tripped and when they rang, so a guard is moving before anybody has been rung back.
One tap turns the request into a real booking on the night, assigned to whoever is out that way, and the thread stays with it.
A site you do not cover gets an answer instead of silence, and either way the thread stays on that client record.
The rear roller door alarm has gone again and nobody here can get across tonight. Can somebody attend and secure it?
Add your whole team and get booking for nothing.
As you grow with us you can go Pro.
One app for the whole job
Bookables does not hold licence numbers or watch expiry dates. What it holds is which services each guard is assigned, and the scheduler only offers a guard who carries the service the job needs. Take that service off a guard whose state licence has lapsed and they are out of tonight straight away.
Yes, and it is the way to run this. Each patrol in the run is a standing arrangement with its own pattern, weekly or every few weeks, ending on a date at the end of the term. Visits are generated ahead so the whole contract is on the board, and standing arrangements cost nothing on any plan.
It becomes its own booking against the site, priced as an alarm response rather than absorbed into the contract rate. If it comes in through your page out of hours it lands as a request in the inbox with the address already attached, and accepting it puts a real booking on the night.
No. There is no checkpoint scanning, no live tracking and no incident reporting in Bookables, and we will not pretend otherwise. What it keeps is a booking for every patrol, a record per site with your access notes, the thread with the client and the invoice at the end of the month.
Yes. Cash and bank transfer are recorded by hand against the job and cost nothing on any plan, and a payment request is a link the client opens and settles themselves. Card payments come with Pro, and the money goes to your own Stripe account rather than sitting with us.
On the site. Each one is its own record with its own address, and notes and photos sit on that record, so the code for the side gate and the number to ring at two in the morning are in the same place as every visit ever made there.
Set up online bookings around your services, prices, travel and availability so customers can book while you're busy doing the job.
ReadChoose a booking lead time that allows for preparation, staff and travel, with practical examples for mobile services, venues and classes.
ReadReduce appointment no-shows with clear confirmations, useful reminders and easy rescheduling. Includes a sample reminder and a simple measurement method.
Read