Back to all templates
Hot-desking & hybrid office

Desk Reservation Form Template

Capture desk reservations for hot-desking and hybrid work — date, floor, desk preference, and duration. Built for hybrid programs with anchor days (engineering Tuesday-Thursday, sales Wednesday-Friday), team neighborhoods (the design team always sits together on Floor 3 east side), and the office-portfolio analytics that drive rightsizing decisions.

Free — included in every plan

Desk Reservation Form Template

Live preview — try the fields below.

No fields to preview.

Who this template is for

Desk reservation in the post-2020 hybrid office is fundamentally different from the pre-2020 assigned-seat model. The shift: employees no longer have permanent desks; they book a desk per visit; the office runs at 30-60 % occupancy on any given day instead of 100 % assigned; the office portfolio shrinks accordingly with companies subletting or terminating excess floor space; the team-coordination challenge becomes 'who is in the office today and where are they sitting?'. This template structures the reservation itself — employee identity (name + work email for the booking record and team-coordination integrations), date of reservation (with the calendar integration that respects team anchor days — engineering teams may have Tuesday-Thursday anchor days, sales teams Wednesday-Friday, design teams may have specific neighborhood days), office location (floor and zone — most modern offices have multiple neighborhoods on each floor, with team-affinity zones, quiet zones, collaborative zones, executive zones), desk preference (standing desk / sitting desk / quiet zone / collaborative area / window seat — the preferences that determine the desk match within the location), and duration (half-day AM for the morning shift, half-day PM for the afternoon shift, full day for the standard reservation, multiple days for the 2-5 day chunks common in hybrid policies). It is the structured intake your office ops and facilities team use for the hot-desking workflow — distinct from the room-booking workflow that handles meeting spaces. Used by hybrid offices running 2-4 days in-office per week, fully-flexible offices where employees come in as needed, coworking spaces (WeWork, Spaces, Industrious, Knotel, Convene, Mindspace, Talent Garden, Selina CoWork) with member desk booking, and any organization where hot-desking has replaced assigned seating. Pairs with the modern desk-booking platforms — Robin (the dominant US-built platform with strong desk + room + visitor management), Envoy (workplace experience platform), Skedda (booking-focused), Tactic (modern hybrid work platform), OfficeRnD (workplace and coworking management), Joan (room and desk booking with hardware integration), Condeco/Eptura (enterprise workplace management after the 2022 merger), Officely (Slack-native desk booking that runs entirely inside Slack channels), Yarooms (Eastern European with strong EU presence), Othership (UK-built modern alternative).

From desk request to confirmed reservation in one structured flow

Employee submits the reservation with their identity (name + work email — cross-validated against the active-employee directory; the directory integration also surfaces the employee's team and historical desk preferences so the workflow can suggest the team-neighborhood by default), date of reservation (the date picker validates against the team's anchor-day policy — if the engineering team anchor days are Tuesday-Thursday and the employee picks a Monday, the form may show a 'note: this is not your team's anchor day, are you sure?' nudge without blocking the booking; for fully-flexible policies, any date is allowed), office location (floor + zone with the floor plan visualization showing available desks in real time — most modern desk-booking platforms have a graphical floor plan with green/yellow/red desk-status indicators), desk preference (standing / sitting / quiet / collaborative / window — the standing-vs-sitting choice matters because not all desks are sit-stand convertible; the quiet-zone choice matters because not all offices have dedicated quiet zones; the collaborative-area choice signals the employee wants the bench-seating area near the team rather than the focus-area; the window-seat choice is the most-requested premium feature that drives the desk-allocation politics), and duration (half-day AM is typically 8 AM-12 PM, half-day PM is typically 1 PM-6 PM, full day is the standard 8-hour reservation, multiple days for the 2-5 day block bookings). On submission, the workflow validates against capacity (the floor/zone capacity and the team-neighborhood capacity), checks the team-coordination signals (is this employee booking alongside their team for coordinated in-office days?), checks the equipment availability (if the employee needs a standing desk and only sitting desks are available in the preferred zone, the workflow surfaces the alternative), and creates the booking with the appropriate confirmation. The booking integrates with the calendar (the desk reservation generates a calendar entry on the employee's calendar with the desk number for wayfinding), the badge/access system (some offices link the badge access for that day to the booked desk), the printer/IT-equipment system (some offices configure the printer routing to the booked desk's nearest printer), and the team-coordination dashboard (the manager or HR business partner can see who from the team is in the office on which days). Cancellations and no-shows are tracked — most desk-booking platforms have a no-show penalty (typically after 10:30 AM, the system marks the desk as no-show and releases it for re-booking; repeat no-shows may trigger booking restrictions). The office-portfolio analytics flow from the booking data — utilization by floor, by zone, by team, by day-of-week, by month — which is the data finance uses for the rightsizing decisions (do we need this much floor space? Should we sublet Floor 3? Should we consolidate the team to fewer floors? Should we expand a satellite office near a team cluster?).

What's included

Every field exists because some office ops team has been burned by its absence — usually at the in-office Wednesday when the design team showed up to find their preferred neighborhood booked by sales, or at the quarterly office-portfolio review when the utilization data was missing the team-anchor-day breakdown that finance needed to justify keeping the floor.

Offices using desk reservation forms

  • Hybrid offices with anchor-day policies (engineering Tue-Thu, sales Wed-Fri)

    Hybrid offices where teams have anchor-day policies — designated days when the team is expected in the office together for collaboration. The dominant pattern: engineering teams have Tuesday-Thursday anchor days (the 'core' days when in-person collaboration is highest-value); sales teams have Wednesday-Friday anchor days (the days when client calls and team prep is most aligned); product and design teams may have specific cross-functional anchor days (e.g., Wednesday for the product-engineering-design alignment). The form's date field respects the anchor-day policy with the nudge for non-anchor-day bookings. Pairs with Robin (the dominant US-built hybrid work platform with strong anchor-day support and team neighborhoods), Envoy (workplace experience), Tactic (modern hybrid work), OfficeRnD (workplace + coworking management), Joan (booking with hardware integration), Officely (Slack-native, very popular for smaller teams). The anchor-day pattern emerged in 2022-2024 as the dominant hybrid model after the experimentation phase of 2020-2021.

  • Team neighborhoods and zone-based seating

    Offices with team-neighborhood policies — designated zones for specific teams (the design team neighborhood on Floor 3 east, the engineering pod on Floor 2 north, the sales floor on Floor 1, the executive zone on Floor 4). The neighborhood model gives teams a stable spatial identity while preserving the flexibility of hot-desking (employees don't have assigned desks but always sit in the same neighborhood). The form's location field captures both the floor and the zone, with the team-affinity suggestion based on the employee's team in HRIS. Pairs with Robin Neighborhoods, Envoy Maps, Tactic Neighborhoods, OfficeRnD Neighborhood Maps — the modern platforms have first-class neighborhood concepts. For larger offices (500+ employees), the neighborhood approach scales better than fully-flexible hot-desking because it preserves the team identity and the operational efficiency (people know where their team is).

  • Fully-flexible offices with on-demand desk booking

    Fully-flexible offices where employees come in as needed without anchor-day requirements — common in mature remote-first companies that have offices for occasional in-person collaboration but don't require attendance. The form captures the on-demand reservation with maximum flexibility (any date, any zone, any duration) without the policy-enforcement layer. Pairs with all the major desk-booking platforms — Robin, Envoy, Skedda, Tactic, OfficeRnD, Joan, Officely, Yarooms, Othership — with the appropriate configuration for fully-flexible policies. The challenge: fully-flexible offices tend to have low utilization (often 15-30 % on any given day) which drives the office-portfolio analytics toward consolidation; some companies have downsized from full-floor to suite-within-coworking arrangements to match the actual utilization.

  • Coworking spaces with member desk booking

    Coworking spaces (WeWork, Spaces, Industrious, Knotel, Convene, Mindspace, Talent Garden, Selina CoWork) where members book desks within the coworking facility's flexible-membership model. The booking has different downstream implications than enterprise hot-desking — the coworking provider tracks usage for billing, provides the desk amenities (monitor, dock, coffee, printing), and may have specific membership tiers with desk-booking limits (e.g., 'hot desk' members have day-pass desk booking, 'dedicated desk' members have a permanent desk, 'private office' members have a private space). Pairs with coworking-specific platforms — OfficeRnD (the dominant coworking platform), Cobot (German-built, popular in EU), Nexudus (UK-built), Optix, Yardi Kube, WUN Systems, Plug Spaces (Brazilian-built strong in Latin America), Cloudworks (Spanish-built integrated with Aticco), Coworkin Brasil. The form's location field captures the specific coworking location for multi-site coworking operators.

  • Brazilian hybrid offices with Onfly + local desk-booking integration

    Brazilian hybrid offices typically combine corporate-real-estate strategies with the cultural preference for in-person collaboration that is still stronger than US/EU markets in many sectors. The form pairs with Brazilian-built desk-booking platforms — SeuPosto (Brazilian-built), Hosti (Brazilian coworking and hybrid platform), Plug Spaces (Brazilian coworking originally, now expanding to enterprise) — and with the global platforms (Robin, Envoy, Skedda) used by larger Brazilian enterprises and multinational subsidiaries. The integration with Brazilian HRIS (Convenia, Sólides, Senior Sistemas, TOTVS RH) provides the team-affinity data for the neighborhood suggestion. For Brazilian companies subject to CLT Art. 75-A et seq. teletrabalho (post-Lei 14.442/2022), the desk booking has implications for the teletrabalho-vs-presencial classification — employees with formal teletrabalho contracts who occasionally book a desk for in-person work need different documentation than employees with hybrid contracts who alternate between remote and in-office.

  • Spanish offices with TravelPerk Desk integration and PRL compliance

    Spanish offices running hybrid programs with the post-Ley 10/2021 trabajo a distancia framework that has shaped Spanish remote and hybrid practices. The form pairs with TravelPerk Desk (an extension of TravelPerk's hybrid work product for Spanish offices), Cobee Workspace (integrated with the Cobee retribución flexible platform), Holded Workspace (integrated with Holded HRIS), Factorial Workspace (integrated with Factorial HR), plus the global platforms (Robin, Envoy, Skedda, Tactic, OfficeRnD) used by larger Spanish enterprises. For PRL (Prevención de Riesgos Laborales) compliance under Ley 31/1995 and Real Decreto 486/1997 (workplace conditions), the desk booking has implications for the ergonomic risk assessment — when employees book desks at multiple locations across the office, the PRL assessment must cover each location with the appropriate ergonomic setup (sit-stand desks, ergonomic chairs, monitor heights, lighting). For LOPDGDD Art. 88 (right to digital disconnection), the desk booking provides the documentation of the employee's in-office presence which interacts with the digital-disconnection policy for the boundaries of the working day.

Tailor it to your hybrid program

Every hybrid office program has its own design decisions. Configure the anchor-day policy — most modern hybrid programs use team-specific anchor days (engineering Tue-Thu, sales Wed-Fri, etc.) that the form validates against; some programs use company-wide anchor days (everyone in Mon-Wed-Fri); some have no anchor days for fully-flexible policies. Configure the team-neighborhood mapping — for offices with team-affinity zones, the form's location field shows the team's neighborhood as the default with the option for employees to book outside the neighborhood. Configure the desk-preference options — most offices use Standing Desk / Sitting Desk / Quiet Zone / Collaborative Area / Window Seat as the standard five; some add Phone-Booth (for video calls), Focus-Room, Library-Style, Outdoor-Patio for offices with outdoor workspace. Configure the duration options — Half Day (AM) / Half Day (PM) / Full Day / Multiple Days is the standard; some offices add Hourly (for very short visits), Weekly (for visiting employees from satellite offices), Monthly (for employees in temporary assignment). Configure the no-show policy — most platforms have a 10:30 AM no-show threshold that auto-releases the desk for re-booking; some have stricter or more lenient thresholds. Configure the booking-restriction policy — some offices have booking-window limits (employees can only book 2 weeks in advance) to prevent the 'I always book Tuesday in the same desk' pattern that recreates assigned seating; some offices have weekly limits (e.g., max 3 days per week to encourage hybrid flexibility). Configure the equipment matching — sit-stand desks may be limited in number; the form validates against availability. Configure the accessibility features — wheelchair-accessible desks, lower-height desks, accessible parking-to-desk path, ADA-compliant restrooms nearby. Integrate with the desk-booking platform — Robin (the dominant US-built platform), Envoy (workplace experience), Skedda (booking-focused), Tactic (modern hybrid), OfficeRnD (workplace + coworking management), Joan (booking with hardware integration), Condeco/Eptura (enterprise workplace management), Officely (Slack-native), Yarooms (EU-strong), Othership (UK-built); SeuPosto, Hosti, Plug Spaces for Brazilian; Cobee Workspace, TravelPerk Desk, Holded Workspace, Factorial Workspace for Spanish. Integrate with the calendar — Google Calendar, Microsoft 365 Calendar, Outlook — for the desk reservation calendar entry. Integrate with the badge/access system for the day-specific access — Kisi, Brivo, Genetec, Salto, HID. Integrate with the HRIS — Workday, BambooHR, Personio, Factorial, Holded, Convenia, Sólides — for the team-affinity data and the in-office attendance signal. For office-portfolio analytics, the booking data feeds the utilization dashboards that finance and CFO use for the rightsizing decisions.

Desk reservation FAQs

Desk reservation and room booking are fundamentally different workflows that serve different needs. Desk reservation is the individual workspace booking — the employee needs a place to sit for their workday with the equipment they need (laptop dock, monitor, ergonomic chair); the booking is typically half-day to multi-day; the booking pattern is high-volume (each employee may book 80-150 times per year in a 2-3 days per week hybrid program); the no-show consequence is the desk goes unused but the employee can book again the next day; the analytics drive the office-portfolio rightsizing. Room booking is the shared meeting space — multiple people need to coordinate around a specific time and capacity; the booking is typically 30 minutes to 2 hours; the booking pattern is lower-volume but higher-conflict (popular rooms get over-booked); the no-show consequence is wasted meeting time for the group; the analytics drive room-mix decisions (do we need more conference rooms or more huddle rooms?). The two workflows have different policy considerations — desks have anchor-day and team-neighborhood policies; rooms have capacity-vs-attendees and recurring-meeting policies. The two workflows have different downstream integrations — desks integrate with badge access and equipment provisioning; rooms integrate with calendar invites and visitor management. Most companies running both have separate forms or separate UI flows within the same platform, but the platforms handle both — Robin, Envoy, Skedda, Tactic, OfficeRnD, Joan all have desk-and-room booking in the same product.
Anchor days are the designated days when a team is expected in the office together for collaboration. The post-2020 hybrid model has converged on the anchor-day pattern as the dominant approach (vs. the fully-flexible model which had lower adoption because it produced too much variability in who is in the office on any given day). The patterns that work: (1) team-specific anchor days (engineering Tue-Thu, sales Wed-Fri, design Mon-Wed, etc.) — this allows each team to optimize for their own collaboration patterns; the trade-off is that cross-functional collaboration suffers because the design team's Mon-Wed doesn't overlap with engineering's Tue-Thu fully; (2) company-wide anchor days (everyone in Mon-Wed-Fri, or Tue-Wed-Thu) — this maximizes cross-functional in-office overlap but may not optimize for any specific team's needs; (3) cluster anchor days (engineering + product + design all together on Tue-Thu for the 'build cluster'; sales + marketing + customer success on Wed-Fri for the 'go-to-market cluster') — a hybrid approach that respects both team identity and cross-functional needs. The right anchor-day policy depends on your company's collaboration patterns. Most companies test for 6-12 months with one model and then iterate based on the office utilization data, the employee satisfaction surveys, and the manager feedback. The form's date field validates against the anchor-day policy with the appropriate nudges for non-anchor-day bookings.
The desk-booking data is the most valuable office-portfolio data a company collects post-2020. The analytics produced: (1) overall utilization — what percentage of available desks are booked on average across the week, month, quarter (the post-2020 reality is that most offices run at 30-60 % utilization on the busiest day, 15-30 % on the slowest day); (2) per-floor and per-zone utilization — which floors and zones get the highest usage (the floor with the best views and the team kitchens usually wins; the floor near the executive offices may have low utilization despite the premium location); (3) per-team utilization — which teams come in most often (engineering often has high utilization due to anchor days; some teams may have 80 %+ utilization while others have 20 %); (4) day-of-week utilization — Tuesday-Wednesday-Thursday are typically the peak days; Monday and Friday are typically the lowest; (5) seasonal patterns — pre-summer and pre-Christmas typically dip; back-to-school and Q4 push typically peak. These analytics drive the CFO conversations about office portfolio rightsizing — do we need this much floor space (often the answer is no, leading to subletting or non-renewal of leases), should we consolidate to fewer floors (often yes, freeing capital and reducing the lease commitment), should we open a satellite office in a specific city where a team cluster is forming (a growing pattern for distributed teams), should we shift to coworking-with-private-suite for the smaller offices where dedicated commercial real estate is over-investment? Most post-2020 office reductions have been 30-50 % of pre-2020 footprint, driven by the desk-booking data showing the actual utilization.
Team coordination in a hot-desking office is one of the unsolved problems of the post-2020 hybrid model. The challenge: an employee comes to the office expecting to collaborate with their team and finds the team isn't there; the cross-functional partner is in remote-only mode and the in-person collaboration is half-functional; the manager wants to schedule a team in-office day but can't tell who's already booked which day. The solutions that work: (1) team-coordination dashboards — the manager or HR business partner has a view of who from the team is in the office on which days, integrated with the desk-booking platform (Robin, Envoy, Tactic all have team-coordination views); (2) anchor days that the team commits to publicly — the team agrees that Tue-Wed-Thu is the 'team in-office' time and members commit to that; (3) Slack integration showing the day's office attendance — Officely's killer feature is the daily Slack message 'today in the SF office: Alex, Sarah, Jamie' which removes the surprise of arriving and finding no one; (4) calendar integration — the desk reservation creates a calendar entry that team members can see in the shared team calendar; (5) office-presence flags — some platforms allow the employee to set 'I'm in the office today' status that shows in Slack, Microsoft Teams, Google Workspace status indicators. The form's structured intake feeds these coordination tools so the team-knowledge problem is reduced even if not entirely solved.
On submission, the workflow creates the desk booking in the hybrid work platform with the structured data attached. For Robin (the dominant US-built platform with strong desk + room + visitor management + neighborhoods), the booking creates a desk reservation in the Robin platform with the floor plan visualization and the team-affinity matching. For Envoy (workplace experience platform), similar booking with the workplace-experience features. For Skedda (booking-focused), Tactic (modern hybrid), OfficeRnD (workplace + coworking management), Joan (booking with hardware integration), Condeco/Eptura (enterprise workplace management), Officely (Slack-native — entirely integrated into Slack channels), Yarooms (EU-strong), Othership (UK-built modern alternative) — equivalent integrations. For Brazilian companies, integration with SeuPosto, Hosti, Plug Spaces, or the global platforms used in larger Brazilian enterprises. For Spanish companies, integration with Cobee Workspace (integrated with Cobee retribución flexible), TravelPerk Desk, Holded Workspace, Factorial Workspace. For the calendar, integration with Google Calendar, Microsoft 365 Calendar, Outlook — the desk reservation generates a calendar entry with the desk number and floor for wayfinding. For the badge/access system, integration with Kisi, Brivo, Genetec, Salto, HID Mercury — the desk reservation can link the badge access for that day to the booked desk's nearest entry point. For the HRIS, integration with Workday HCM, BambooHR, Personio Spain, Factorial HR, Holded, Convenia, Sólides, Senior Sistemas, TOTVS RH — the team-affinity data drives the neighborhood suggestion and the in-office attendance signal feeds the engagement and culture analytics. For office-portfolio analytics, the booking data feeds the utilization dashboards that finance and CFO use for the rightsizing decisions — typically reported quarterly with the trend data over multiple quarters to inform the lease renewal and subletting decisions. The audit trail captures the full desk-booking history for the office-portfolio analysis and the team-coordination decisions.

Related templates

Client Onboarding Questionnaire Template

Replace scattered intake calls and email threads with a structured client onboarding questionnaire — captures business details (W-9/EIN, CNPJ, CIF)

View template

Expense Report Form Template

Capture business expenses with line-item detail, receipt uploads, project allocation, and manager approval — built for IRS Publication 463 accountable-plan

View template

Project Proposal Form Template

Capture project proposals with the PMBOK Project Charter skeleton — business case, scope, milestones, capex vs opex breakdown, stakeholder RACI, risk register

View template

Ready to build forms that work for you?

Create your first form in minutes. Your submissions will thank you.

Be first in lineLimited early accessSet up in 2 minutes