Desk booking
The desk is booked
on the plan of the floor.
You upload the floor plan, place the desks, the parking spots and the meeting rooms on it, and people book by clicking the pin. The rules — how far ahead, how long, whether approval is needed — are yours, set per resource type.
You book by clicking the floor plan.
A pin on the plan says more than a row called MI-2-D14: where the desk actually is, what is around it, what is already taken. Free, yours, occupied and pending are told apart at a glance — and by their label, never by colour alone.
One floor, one glance: what is free today and where it is.
Every resource type carries its own rules.
Desks by the day, rooms by the hour, parking by the half day: granularity, booking horizon, minimum and maximum duration and the daily cap per person are set per type. Approval is a switch — where you want a gatekeeper there is one, where you do not the booking is immediate.
The rules on one resource type: granularity, horizon, caps, approval.
Whoever is not there cannot book a desk.
An approved absence blocks the booking for those days, where you switch that rule on, so the plan stops filling with desks nobody will sit at. Your own bookings are one list, cancellable while they are still in the future.
A booking refused on an absence day, and the person's own bookings beside it.
Approvals travel like every other approval.
A pending booking notifies the approver, the outcome notifies the person, and the queue sits with the platform's other queues. Favourites keep the desk you always take one tap away.
The booking queue, where the platform keeps every other approval.
Everything it does
- Interactive floor planUpload each floor plan, place pins by dragging and book with one click; switch map, timeline and list views.
- Bookable resource catalogCreate desks, parking and rooms with capacity and amenities; office hours define full and half days.
- Full-day, half-day or hourly bookingBook a full day, half day or an hourly window, also via a form with purpose and notes, and cancel anytime.
- No overlapping bookingsThe same resource is never double-booked, and an approved absence can block a booking.
- Booking approvalsResources can require approval: the queue is decided one by one or in bulk, scoped to the team lead.
Questions we actually get asked.
- Can somebody manage bookings for their team?
- Yes — a team-admin permission exists for exactly that: whoever holds it handles their team's bookings without owning the whole floor.
- Are there recurring bookings?
- Not today: each booking is made for its period. What exists is deliberately simple — the map, the rules, the approval — and this page does not claim more.
- Can approval be skipped?
- Yes. Approval is set per resource type: where it is off, a booking is immediate; where it is on, the request waits for its approver and the outcome notifies the person.
Works with
- Document controlCompany documents with a structured code, a revision history, and a named person on each approval step.
- Corporate documentsDURC, certifications, policies and filings, each with its expiry and a reminder that arrives before it.
- CredentialsCompany passwords in shared lists, encrypted in a dedicated vault, with every reveal on the security log.
Tell us how you work today.
There is nothing to prepare. Half an hour on how your company runs — who tracks the hours, how an invoice comes together, when you find out whether a commessa made money — and we tell you which modules would fix it and what a quote looks like.