02 — What to build
Resources, rules and roles for a resource booking system
Resources by type: rooms, desks, parking, vehicles, equipment, with location, capacity and features
Reservations with requester, time slot, purpose and status: requested, confirmed, checked in, released
Booking rules per type: maximum duration, booking window, who may book, what needs approval
Check-in and auto-release so unclaimed rooms and desks return to the pool
Floor views for desk booking, filtered by team or neighborhood
Usage overview of no-shows and peak days for space planning
Roles
employee, approver, facilities admin
This page covers internal resources booked by employees. If customers book appointments with your staff, see the booking system guide.
03 — How to build it
Building the reservation app in Henosia, from floor plan to first booking
Create a private project
Nothing goes live until you publish.
Add mock data
rooms, desks, vehicles and equipment with their attributes, plus a month of calendar exports as CSV.
Connect a database for resources, rules and reservations.
Describe your rules in Plan mode
The agent asks about approvals, windows and exceptions, then proposes a plan before anything is built.
Build a first version and make test bookings.
Test and iterate
overlapping requests, no-shows, a vehicle in repair.
Publish to your company domain.
Build an internal reservation system for our two office locations.
Employees book desks up to 14 days ahead and meeting rooms up to 30 days ahead.
Release desks and rooms not checked in within 15 minutes.
Pool vehicles need manager approval and are capped at 3 days per booking.
Show availability by floor and a weekly no-show report for facilities.Paste it into a private Henosia project in Plan mode. The agent asks questions and proposes a plan first.
04 — Before you go live
Opening the reservation system to every employee
Before rollout, decide:
- Who owns each resource type: facilities for rooms and desks, fleet for vehicles, IT for equipment
- Who can book and approve. Henosia Authentication ties access to your company email domain, with app-level roles and optional IP restriction
- Calendar integrations, scoped per system, data direction and access level; start read-only. More point-and-click connector interfaces are on Henosia's roadmap
- Who approves publishing and changes to booking rules
For equipment you also track over its whole life, pair this with an asset management app.
Start a private project in Henosia, load your room and desk list as mock data and plan your booking rules.
Start a private project05 — FAQ
Frequently asked questions
What is an internal reservation system?
An internal reservation system is a booking tool for shared company resources. Employees reserve meeting rooms, desks, parking, pool vehicles or equipment, while rules control booking windows, approvals and check-in. It works as a room booking system and desk booking system in one, with a single view for facilities.
What is the difference between a reservation system and a booking system?
In our guides, a reservation system is for internal resources that employees book, such as rooms, desks, vehicles and equipment. A booking system is for customer appointments, where clients book time with your staff. The rules, users and access needs differ, so they are usually built as separate apps.
Do I need developers to build a meeting room booking system?
Not for a first version. A facilities or workplace lead can describe resources, rules and approvals in Plan mode and build without writing code themselves. Involve IT when you connect calendars or HR data, decide on access for contractors, or set who approves publishing.
Who can see and make reservations?
You decide. Henosia Authentication limits access to your company email domain and supports more granular app-level access, optional IP restriction and access for selected external parties such as contractors. Facilities admins can see every booking while employees see availability. Confirm specific security requirements with Henosia.