Custom software · Booking systems

Custom booking system development for rooms, desks, venues and equipment

Spatial Map is browser-based indoor mapping and 3D digital twin software, and it has no booking module. For meeting rooms, desks, event venues and shared equipment, our team does custom booking system development as a client project: your own booking rules, calendar and sign-in integrations and notifications, with the booked, free and in-use state of every space written to the map so people can see it on the floor plan.

Spatial Map: no credit card for the trial, runs in the browser, Pro is $60/month for up to 4 facilities. Explore the live demo

Illustrations of device types — not vendor product photos.

What a booking system usually includes

What gets booked varies — a room, a desk for a day, a hall for a weekend, a vehicle, a piece of lab equipment — but the building blocks repeat:

  • Bookable resources — a catalogue of spaces and assets with capacity, equipment, opening hours, location and who may book them, organised the way your buildings are (site, building, floor, room).
  • Availability rules — minimum and maximum duration, lead time, buffers for cleaning or set-up, blackout dates, and priority for certain teams.
  • Recurring and group bookings — weekly meetings, multi-day events, and several rooms or items reserved together.
  • Approvals — automatic for ordinary rooms, routed to a manager or facilities team for restricted ones.
  • Check-in and release — people confirm on arrival; unclaimed bookings are released after a grace period so the room does not sit empty.
  • Admin tools — blocking a room for maintenance, moving a booking, usage reports by team, room and hour.
  • Room displays — a web page on a tablet by the door that shows the current and next booking.

Where booking systems get used

The same engine is configured differently per setting:

  • Offices and campuses — meeting rooms and hot desks on several floors. See campus and office indoor maps.
  • Venues and convention space — halls, breakout rooms and stalls, with set-up time and, if needed, quotes and deposits. See the venue solution.
  • Shared equipment and vehicles — loan bookings with check-out and return, optionally with an RFID or barcode scan at hand-over.
  • Labs, classrooms and amenities — timetable-driven spaces with fixed slots and capacity limits.

Showing bookings on the floor plan

Spatial Map itself does not take or release bookings, and you cannot book from the map. The custom booking system stays the source of truth and writes one row per space to a table through the table write API: space ID, floor, status (free, booked, in use), current booking and next start time. A data link then colours each room on the 3D plan by status and shows the next booking in its tooltip.

  • Updates — every change is an upsert; the service batches rows because the API allows 60 requests a minute per key.
  • Presence — if you already have occupancy sensors or BLE gateways, their rows can be written to the same table, so the map can show “booked but empty”. A Spatial Map alert rule can flag that in the app; releasing the room is done by the booking system.
  • Finding the room — Spatial Map’s wayfinding can route between places across floors, with step-free options. There is no live blue dot for the visitor.
  • Sharing — a read-only share link or a built-in report shows utilisation without extra code.

Calendars, sign-in, notifications and payments

A booking system earns its keep by fitting into tools people already use. We connect, generically:

  • Calendars — two-way sync with calendar systems that offer an API or an iCalendar feed, so a booking appears in the organiser’s calendar and cancellations flow back.
  • Sign-in — your directory or identity provider through standard sign-in protocols, so people use their work account and roles map to booking rights.
  • Email and SMS — confirmations, reminders and release warnings sent by the custom service. Spatial Map’s own alerts stay in the app, so anything outside it is built as part of the project.
  • Charging for space — price rules, deposits through your payment provider, and invoice export to your ERP or accounting system, where venues are paid for.

How we build it

Booking rules look simple and turn out to be the hard part, so we spend time on them first:

  • Discovery — who books what today, the exceptions that cause arguments, the calendars and directories in use, and a floor plan if the map is part of it.
  • Design — the rule set and booking flows agreed in writing and in clickable mock-ups.
  • Build — booking engine, web app that works on phones and desktops, admin tools and room displays.
  • Integrate — calendars, sign-in, notifications, payments and, optionally, Spatial Map.
  • Hand-over — a pilot floor or building first, then roll-out, admin training and documentation.

Hosting and what you own

The booking service can run in your cloud account, in ours or on your own servers, depending on your IT policy; on-premises installs suit sites that cannot send data out. The map side can be the hosted Spatial Map app or the self-hosted open-source edition — see deployment.

Ownership is written into the proposal. The usual position is that you own the source code written for you, your booking data and the accounts the service runs in; third-party components keep their own licences.

How it connects

How the pieces fit together

  1. 01

    People

    Staff, visitors and organisers book in the web app or from their calendar.

  2. 02

    Booking system

    Rules, approvals, check-in, release, notifications and admin.

  3. 03

    Your tools

    Calendar, directory sign-in, payments and ERP or accounting.

  4. 04

    Sensors (optional)

    Occupancy or BLE presence rows for “booked but empty”.

  5. 05

    Spatial Map

    One row per space through the table write API → rooms coloured by status on the live plan.

Custom booking systems — frequently asked questions

No. Spatial Map is indoor mapping software with no booking module. A booking system is custom software built for one client; it can show its bookings on the Spatial Map floor plan through the table write API.

Not in Spatial Map itself. Bookings are made in the custom booking app, which can link to the facility. The map shows free, booked and in-use state; it does not write bookings back.

Calendar systems that offer an API or an iCalendar feed. We confirm the route in the proposal after reading the provider’s documentation, including how cancellations and changes sync.

Yes. Desks, vehicles, lab equipment and loan items use the same engine with their own rules, and equipment can be checked out and returned with a barcode or RFID scan.

Yes. A check-in step with a grace period releases unclaimed bookings. If you have occupancy or presence sensors, their data can drive the release as well.

Scoped and quoted per project, from a written proposal after we know your booking rules, integrations and number of sites.

Tell us what gets booked. We’ll build the rules around it.

Share the spaces and assets, how people book today, the calendars and sign-in you use, and a floor plan. We will reply with a scoped proposal — and show the result on a live map.