University desks are harder to plan than they used to be.
Faculty may teach on campus 2 days a week, hold office hours in different buildings, and split time between research, teaching and remote work. Administrative staff may follow hybrid schedules. Visiting researchers may need a temporary place to work. Departments may own rooms that other teams also need to use.
At OfficeRnD, we work with numerous universities, so we see the same pattern often: the issue is rarely just “not enough desks.” It is usually a mix of shared space, changing schedules, department rules, unclear availability, and limited visibility into how campus workspaces are used.
Desk booking gives universities a clearer way to manage shared workspaces across departments, buildings, and campuses. It lets faculty and staff reserve the right space before they arrive, gives facilities teams better usage data, and helps IT support hybrid work with fewer manual processes.
A fixed seating plan does not always match how higher education teams work today. Desk booking can make shared campus workspaces easier to find, easier to manage, and easier to report on.
Desk booking lets people reserve a desk, workstation or shared work area for a specific time.
In a university, that can include:
The goal is simple: people should know where they can work before they come to campus.
For facilities teams, desk booking also shows how shared workspaces are being used. Which buildings fill up on Tuesdays? Which desks are rarely booked? Which departments need more shared space? Which areas look busy in theory but sit empty most days?
That data can support better campus planning.
Desk booking and room booking solve different day-to-day problems.
Room booking is usually for meetings, classes, interviews, group work or events. Desk booking is for individual work. A faculty member may book a desk in the morning, reserve a small meeting room for student office hours, and check in a guest lecturer later that day.
Universities often need both.
Desk booking becomes especially useful when:
A basic shared calendar may handle a few rooms. It usually struggles when many people need to find desks by location, department, access rules and availability.
Here’s a guide on the best desk booking software for 2026, and another one on deciding on the right scheduling software for universities.
Faculty schedules vary by semester, department, and teaching load. Some faculty members need a quiet place for grading and research. Others need space near students, labs or department staff.
Desk booking can help faculty reserve space around their campus days instead of depending on informal arrangements.
Useful features include:
Adjunct faculty often move between campuses, classes, and institutions. They may need workspace for short blocks of time before or after teaching.
A desk booking system can give them access to shared faculty areas without assigning permanent offices that may sit unused. This can also reduce pressure on department coordinators who would otherwise manage requests manually.
University admin teams often need some shared in-person time for planning, student services, finance, HR, operations or IT support.
Desk booking can help teams coordinate office days around the work that benefits from being on campus.
For example, a student services team may reserve nearby desks on peak advising days. An IT team may book workstations near service areas when new staff or faculty onboarding is scheduled.
Visiting researchers may need desks for a week, a semester or a short research project.
Desk booking helps departments provide access without changing long-term seating plans.
For this use case, permissions matter. A visiting researcher may need access to one building, one floor or one department area, with a defined start and end date.
Some work happens near labs, studios, clinics or research facilities. The desk itself may be ordinary, but the location matters.
Desk booking can help users find spaces near the rooms and resources they need.
This is useful when workspaces are tied to:
For hybrid staff, desk booking removes guesswork from campus days.
People can see where they can sit, who else plans to be in and whether a department area has enough capacity before they travel in.
This matters for employee experience, but it also matters for space planning. Booking data can show whether a hybrid policy matches how people use campus workspaces.
Adoption depends on the booking flow.
Faculty and staff should be able to book a desk in a few steps without knowing room codes, building abbreviations or internal facilities language.
A strong booking experience usually includes:
Floor plans are especially useful on large campuses. A desk name alone may mean little to a visiting lecturer or new staff member. A visual floor plan helps people understand where the desk is, what is nearby, and whether the location suits their day. This where Excel desk booking templates typically fail, for example.
Desk booking for a small company can be simple. Desk booking for a university needs more control.
Different groups need different access. A shared admin area may be open to staff only. A faculty workspace may be available to one school or department. A visiting researcher may need temporary access. A student worker may need access during certain hours.
The system should support rules such as:
This is where universities should be careful. If permissions are too basic, the system may push teams back to spreadsheets, email approvals, and side agreements.
Desk booking gives facilities teams a clearer view of workspace demand.
Useful metrics include:
Facilities teams need more than a booking count. They need data that explains where demand is concentrated, which areas are underused and which rules may need to change.
EAB’s 2025 analysis of higher education space utilization reports found that colleges and universities often collect room-by-room usage data, building inventories, floor plans, staffing data, and enrollment data.
It also found common patterns such as offices being used less than half the time, classrooms peaking from 10 a.m. to 2 p.m., and labs being underused in some departments while constrained in others. That variation is why desk booking data should be reviewed by building, department, space type, and day of week.
Desk booking data can answer practical questions.
Do faculty desks fill up on the same 2 days every week? Are some buildings busy while others are underused? Do admin teams need more shared space near student-facing services? Are desks booked often but not checked into?
The answers can guide small changes, such as opening another shared area on peak days, changing access rules or converting low-use desks into rooms that match stronger demand.
They can also support larger planning conversations around renovations, consolidation, and campus workplace strategy.
IT should be involved early because desk booking touches identity, calendars, and access.
Key questions include:
If the tool doesn’t fit the university’s identity and calendar setup, adoption will be harder. IT may also end up managing exceptions manually.
Desk booking can help HR and workplace teams understand how hybrid work is playing out.
The useful questions are practical:
Flexible work is still a live issue in higher education. CUPA-HR’s 2025 Higher Education Employee Retention Survey found that 28% of higher ed employees currently work in a hybrid or remote arrangement, while 61% prefer hybrid or remote work.
For HR and workplace teams, desk booking can help make those policies easier to manage by showing whether people have enough workspace on the days they come to campus.
Desk booking data should be used with care. It is more useful for planning than monitoring individuals. The goal is to understand patterns, fix space problems, and make office days easier to plan.
Desk booking works better when the rules are clear before rollout.
Start with these decisions.
Define access by department, role, campus or user group.
A long booking window may help faculty plan the semester. A shorter booking window may reduce unused reservations.
Recurring bookings can help with office days, but they can also block shared space. Use them carefully.
Check-in rules can help facilities teams separate planned usage from real usage.
In a university setting, that’s important. Department coordinators may need this option for guest lecturers, visiting researchers or new staff.
Some desks may be near restricted spaces, shared equipment or department-specific resources.
A full campus rollout can get messy if every department has different expectations.
A focused rollout is easier to manage.
Start with one area where the need is clear. Good pilot areas include:
During the pilot, track:
After 30 to 60 days, adjust the rules before expanding.
Facilities may own the space, but IT, HR and departments all affect rollout. Bring them in early.
Universities rarely have one simple access model. Department rules should be part of setup.
A low-use area may be in the wrong location, restricted to the wrong group or poorly explained in the system. Data should start the conversation.
Recurring bookings can be useful for office days. They can also recreate assigned seating by accident.
Users need to know which spaces are bookable, who can book them, and what to do when plans change.
Use this checklist before rollout:
Desk booking works best when it is treated as part of a wider campus space plan.
A university may start with shared desks for faculty or staff, then expand into related use cases:
This helps teams avoid managing desks in one system, rooms in another, and visitors through a separate manual process.
Before choosing a desk booking tool, check how it would fit with the other scheduling workflows your university already manages.
The most useful setup is usually the one that gives people a simple way to find and book space while giving facilities, IT, and workplace teams enough control behind the scenes.
For a closer look at how this can work across campus spaces, explore OfficeRnD Workplace as an option for a university scheduling tool.