Buying hybrid workplace software is a decision you make once. Running it is a set of decisions you make every week: whether to lengthen the release delay, whether a team still needs its reserved desks, what to say to someone who keeps missing check-in, and which figures go in front of leadership. Organizations that treat desk sharing as an operating model, with named owners, a steady review rhythm, and a short list of trusted measures, get the predictable office they were promised. Those that treat it as an installation usually find the rules drifting within a quarter.
This guide describes that operating model. It covers who owns what, how the workspace policy is set and changed, the weekly and monthly rhythm, how check-in becomes the basis of attendance data, how to handle no-shows fairly, what to measure, and how identity and multiple devices fit in. It is written for workplace, HR, and IT leads running a desk-sharing program in DeskHybrid, but the structure applies to any hybrid workplace software that enforces policy centrally.
Choosing and rolling out the software is covered in the companion guide on how to choose desk booking software. This page starts where launch ends.
Why the tool is not the operating model
Software enforces rules. It does not choose them, explain them, or notice when they stop fitting the way people work. Three jobs stay with people no matter which product you run: deciding what fair access to desks means for your workforce, noticing when the rules no longer match reality, and having the conversations that rules cannot.
The operating model assigns those jobs to named owners and gives them a rhythm. The software's part is everything that can be automated reliably. In DeskHybrid that means applying one policy consistently on every client, checking every minute for bookings that were never claimed and releasing them, and keeping a clean record of office days and no-shows. That is intelligent automation in a deliberately narrow sense: it removes the chasing and counting, so the people involved spend their time on judgment rather than data collection.
Roles and ownership
Name four owners before launch. In a smaller organization one person may hold more than one role, but each role should still be explicit.
- Policy owner, usually HR or People. Decides what the rules are for: how far ahead people can plan, how strict check-in should be, and what counts as an office day. Approves every policy change.
- Workspace administrator, usually workplace operations or facilities. Configures the policy, maintains floor plans, marks team-reserved desks, switches desks off when they are out of service, keeps QR codes in place, and reads the reports.
- Identity owner, usually IT. Runs single sign-on, decides which email domains may create accounts automatically, and owns the Slack, Microsoft Teams, and calendar connections.
- Team managers. DeskHybrid has a Team Manager role, and its My Team view shows which teammates have booked for a given day, so managers can coordinate anchor days without polling the team.
Access follows these roles. Per-person attendance and no-show reports are restricted to workspace owners and administrators, which keeps individual data with the people accountable for using it carefully. The governance model article sets out a fuller responsibility matrix.
Setting the workspace policy
DeskHybrid holds one policy record per workspace, so the policy owner answers each question once, for everyone. The decisions are:
- Booking horizon: how many days ahead people can book. Shorter horizons discourage speculative bookings; longer ones help people who plan travel.
- Booking length: the minimum and maximum duration of a single booking.
- Working hours: the day the office is designed around.
- Check-in window: how long before the start time people can check in.
- Release: whether unclaimed desks are released at all, and after how long.
- Office-day threshold: how long a booking must last to count as an office day in each person's figures.
- Recommendations and weekly planning: both are off by default and can be switched on when the program is stable.
Some rules are fixed and need explaining rather than deciding: no bookings in the past, one booking per person per day, no overlapping bookings, and team-reserved desks bookable only by that team. Each office still has its own timezone, which determines how days are counted for the people who work there.
Write the result as a single page employees can read in two minutes. A policy people understand generates fewer exceptions than a stricter one they do not. The policy templates article has starting points by organization type.
The weekly rhythm
During the first months, hold a short weekly review led by the workspace administrator, with the policy owner attending when a change is on the table. A useful agenda fits in thirty minutes:
- Read the week's per-person no-show counts and look for patterns, such as the same weekday, the same floor, or the same arrival time, rather than individuals to blame.
- Review questions and complaints from employees, and note which rule caused each one.
- Check the floor against reality: switch off desks that are out of service, and reprint missing QR codes, which can be printed for a whole floor at once.
- Compare team-reserved desks with how often those teams actually come in.
- Agree at most one change, with an owner and a date.
Limiting the review to one change a week is the most useful discipline in the whole model. When the release delay, check-in window, and booking horizon all move at once, nobody can tell which change helped.
The monthly and quarterly review
Once the program is stable, move the detailed review to monthly. Compare this month's per-person office days and no-show counts with last month's, and decide whether the release delay and check-in window still fit how people arrive. DeskHybrid's reports are period views rather than trend charts, so keep a simple running log of a few headline figures from each month if leadership wants to see direction over time.
Quarterly, step back to capacity and access. Compare active desks with peak in-office days to see whether the floor is over- or under-supplied. Check whether team-reserved areas are still justified. Review who holds administrator and Team Manager roles, and confirm with IT that sign-in and integration settings still match the organization. The capacity planning and SLA design articles cover how to turn these reviews into commitments.
Verification: making check-in the basis of attendance
The most consequential operating decision is how much a booking has to prove. With release switched on, a booking in DeskHybrid that has not been checked in by the end of the release delay becomes a no-show and the desk is freed. Check-in is therefore what separates attendance from intention in every figure you report.
Choose the strength of evidence deliberately. In-app check-in is low friction and works well where trust is high. Requiring QR check-in across the workspace produces stronger evidence, because the person has to scan the signed code on the desk itself, but it only works if every desk has a readable code. An optional location check adds a single confirmation, at the moment of the scan, that the phone is within a set radius of the floor. It is a one-time check, not tracking, and employees should hear that from you before they encounter it.
Then remove avoidable misses. Employees are notified when their check-in window opens, and on the mobile apps someone who books while the window is already open is offered check-in straight away. Most missed check-ins in a healthy program come from people who simply forgot, not from people gaming the rules. The location-verified check-in article covers the communication side in detail.
Handling no-shows without turning them into discipline
No-shows in DeskHybrid are final; nobody can mark a person present after the fact. That keeps the record consistent, and it means legitimate exceptions, such as a sudden illness or a cancelled train, have to be handled through conversation rather than by editing data.
Treat no-show counts as a signal for tuning and coaching. A cluster on one weekday may point to a transport problem or a check-in window that opens too late. A cluster around one person usually calls for a friendly reminder that cancelling a booking frees the desk sooner than waiting for release. Avoid publishing rankings; they shift behavior toward avoiding bookings, which damages the planning data you need.
Remember that released desks do not trigger a waitlist or alert anyone. People looking for a desk later in the morning should simply check the map again. The no-show automation and release best-practice articles go deeper on timing.
Measurement: reading the numbers correctly
Keep the measurement set small and well understood. DeskHybrid gives each employee their own office days by week and month, shows everyone the number of active desks and how many people are in today, and gives owners and administrators per-person office days and no-show counts by week or month. Occupancy counts only active desks, so desks switched off for maintenance do not distort it, and a booking shorter than the office-day threshold does not count as an office day.
Know what the data does not include: there are no team or department breakdowns, no trend charts, and no exports. If leadership asks a question the reports cannot answer, say so and agree on a manual figure rather than stretching the existing ones to fit.
Read early data with caution. The first two weeks after launch mostly measure novelty. Set targets after that, and compare people only against the policy you published, never against an unstated norm. The KPI model and occupancy baseline articles describe which questions each figure can and cannot answer.
Identity and the employee lifecycle
Joiners, movers, and leavers are where an operating model meets IT. With single sign-on through Microsoft Entra ID, SSO becomes the primary way in, SSO accounts have no separate password, and just-in-time provisioning can create an employee's account on first sign-in for approved email domains. New accounts start as standard employees and pick up the company's timezone, so nobody receives elevated access by accident. Without SSO, administrators can import users from a spreadsheet.
Promote people to administrator or Team Manager deliberately, and review those roles quarterly. Display names are managed by the workspace rather than edited by employees, which keeps the booking map and reports consistent. For leavers, access is governed in Entra; administrators can also block an account in DeskHybrid, which ends its active sessions.
On the mobile apps, Face ID or fingerprint sign-in keeps daily access quick, which matters more than it seems: friction at sign-in is a common reason people skip check-in.
Multiple offices and many devices
A multi-office program in DeskHybrid runs as one workspace with several locations, each with its own floors and timezone, under one shared policy. That keeps rules identical across sites, which helps people who travel between offices. If a site genuinely needs different rules, raise it early, because the policy does not vary by office, floor, or team.
Employees will meet the program on whichever device they have. DeskHybrid is available on web, Android, and iOS. Because rules are enforced on the server, a booking refused on a phone is refused on the web for the same reason, and the operating team does not have to maintain separate guidance per client. A few capabilities are web only, notably calendar sync and weekly planning, and the interface is offered in English and Turkish with each person's language choice kept in sync across devices. Before announcing any policy change, test it on each client so the support desk is not the first to find a surprise. The cross-platform consistency article describes a simple test script.
Change management and keeping the policy from drifting
Policy drift rarely comes from one big decision. It comes from informal exceptions, unannounced setting changes, and floor plans that slowly stop matching the room. Three habits prevent most of it.
First, route every policy change through the policy owner, and keep a short change log of what changed, when, and why. Second, announce each change with its effective date and its reason, and look at the effect two weeks later. Third, give each team a named contact who can answer basic questions, so small confusions do not become complaints.
At launch and after major changes, lead with purpose. Employees accept check-in and release far more readily when they understand these rules exist to return desks to colleagues. The policy drift prevention article and the policy audit checklist offer a structured way to run a quarterly health check.