Hot Desk & Hoteling Reservations: Book a Desk, Check In, Auto-Release No-Shows
Let your hybrid team reserve a specific desk by floor and neighborhood for the days they're in, check in on arrival, and auto-release unclaimed desks at a cutoff — with a manager approving standing reservations and over-capacity exceptions before they lock in.
An internal web tool where staff pick a day and a desk or neighborhood, the tool conflict-checks and confirms one-off bookings instantly, a workplace manager approves standing reservations and over-capacity exceptions, people check in on arrival, no-shows auto-release at your cutoff, and you get a live occupancy report plus a clean CSV export.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free) for booking and check-in emails
- A desk list with floor, zone/neighborhood, and any fixed/assigned flags (CSV or Google Sheet)
- A staff list and your team-to-zone mapping
- Claude Code or any AI coding agent
The problem this kills
Your office went hybrid, so you took out the assigned seats and added "flexible desks." Now nobody actually knows where they'll sit on Tuesday. The marketing team wants to sit together but keeps getting scattered. Two people show up to the same corner desk and one of them ends up perched at the kitchen counter. Half the desks people "reserved" sit empty all day because someone worked from home and never told anyone — so the people who did come in couldn't find a seat that was supposedly free.
Meanwhile your facilities manager is trying to right-size the lease and can't get a straight answer to the one question that matters: how full is this office, really, on a given day? The booking spreadsheet says one thing, the badge data says another, and the standing "this is Jane's desk" arrangements that quietly crept back in aren't written down anywhere.
You don't need a five-figure workplace platform with a year-long rollout to fix this. You can build a desk-booking tool that fits your floors, your neighborhoods, and your rules — this weekend.
What you'll build
An internal web tool your team logs into. They pick a day (or a few days), choose a floor and a neighborhood, and grab a specific desk. The tool checks for conflicts on the spot — one desk per person per day, and a desk can't be double-booked — and confirms the booking instantly. When someone arrives, they check in with a tap. If a booked desk isn't checked in by your cutoff (say 10am), the tool auto-releases it so a walk-in can grab it.
Standing arrangements and crunch days get a grown-up: a workplace manager reviews and approves recurring/standing desk reservations and any over-capacity exceptions before they lock in, while ordinary one-off daily bookings auto-confirm. Neighborhood rules are enforced (the design team's zone really does keep the design team together), and at the end of every week you get a live occupancy report — booked vs. checked-in vs. no-show, by floor and neighborhood — plus a clean CSV export you can hand to whoever owns the lease.
What's inside the Implementation Plan
The downloadable plan is a single markdown file you paste into an AI coding agent. It opens by interviewing you about your own office — your floors and neighborhoods, how you name desks, which seats are fixed or assigned, your team-to-zone rules, your check-in cutoff, and your messy exceptions — and then it reads a short spec back for your thumbs-up before it builds anything. That's the difference between a tool shaped to your building and a generic template you have to bend to fit.
From there it walks the agent through the data model (desks, zones, staff, bookings, check-ins), the desk and staff importers, the conflict-check and one-desk-per-person-per-day rules, the neighborhood enforcement, the standing-reservation approval gate, the check-in flow, the auto-release job, and the occupancy report and export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path: load desks from a Google Sheet or CSV and export bookings and occupancy as CSV — so it's fully buildable today, with no integration to any badge or HR system required.
The governance it includes (this is the point)
Space is shared, so the controls are the product. The plan builds them in: a login so only your team can book; row-level security so each organization only ever sees its own floors and bookings; a complete audit trail of who booked, approved, checked in, released, and exported, and when; a hard human-approval gate so no standing reservation or over-capacity exception goes live until a workplace manager signs off; and duplicate guards (on desk + date) so the same seat can't be booked twice for the same day. The auto-release of no-shows is logged too — so when someone asks "who released my desk?", there's a clean answer.
Who it's for
Workplace and facilities managers, office managers, and people-ops leads running a hybrid office who are tired of seating chaos and guesswork about occupancy. If you can explain to a new hire how someone grabs a desk for the day and what makes a standing reservation worth a manager's nod, you can build this — no developer required.
You've got this — open the plan, paste the first prompt, answer a few questions about how your office actually works, and you'll watch your first desk get booked, checked in, and reported on.