Executive Summary
Most hybrid policies are written in days: three days a week in the office, two anchor days per team, a minimum per month. Most office data is recorded in bookings. The gap between the two is where disputes start. An employee says they came in on Tuesday; the report shows a booking but no evidence; a manager draws a conclusion either way. This guide is for HR and people leaders who need office days to be counted the same way for everyone. It explains what a desk QR system has to record before a booking can be treated as an office day, how DeskHybrid turns check-ins into a verified day count, which thresholds you need to choose, and how to use the result fairly. The configuration side, covering check-in windows, release delays, and enforcement settings, is covered in our companion guide on desk QR systems for policy-driven hybrid offices.
Audience + Job To Be Done
Primary readers are HR business partners, people operations leads, and managers in hybrid organizations of roughly 25 to 250 employees. The job to be done is to answer one question consistently: did this person spend a working day in the office? The answer should be the same whoever asks it, and the employee should be able to see it too.
Specialist Positioning
DeskHybrid is a desk-sharing specialist. Verified office days come out of the desk booking and check-in workflow; DeskHybrid does not read badge systems, Wi-Fi logs, or calendars to infer attendance, and this guide does not recommend doing so.
Why a booking is not an office day
A desk booking records intent. It says someone planned to be in, on a given desk, for a given time. Intent is useful for planning, but it is a weak basis for an attendance policy, for three reasons.
First, plans change after the booking is made. People get ill, trains get cancelled, a client meeting moves. Some people cancel; many do not. Second, bookings can be made speculatively, especially when desks are scarce, and a speculative booking looks identical to a real one. Third, a booking says nothing about duration. Arriving at 4pm for a single call and spending a full day with the team produce the same booking record.
If an attendance policy is enforced on bookings alone, the honest employees who cancel when plans change look worse than the ones who never cancel. That is the opposite of what any HR team intends, and employees notice quickly.
What DeskHybrid counts as a verified office day
DeskHybrid only counts a day when a chain of events has completed, and each link is recorded by the system rather than reported by the employee:
- **A booking exists** for a desk at one of the company's locations.
- **The employee checked in** during the check-in window, by scanning the desk's QR code or, where the workspace allows it, by confirming in the app.
- **The booking was completed.** That happens automatically at the booking's end time, or earlier if the employee checks out, which also frees the desk for someone else.
- **Check-in and completion fall on the same local day**, measured in the company's timezone.
- **The checked-in time meets the workspace minimum.** The time from check-in to the end of the booking is added up per day and compared with a minimum duration set by the workspace admin.
Days that pass every step appear in the employee's own dashboard as "My Office Days" for the current week and month. Bookings that were released as no-shows never qualify, because they were never checked in, and cancelled bookings are excluded as well. Only completed bookings are counted.
The design choice that matters is that duration is measured from check-in, not from the booking start. Someone who books 9:00 to 17:00 but checks in at 14:00 has three hours of verified time, not eight.
Choosing the minimum duration that makes a day count
The minimum duration is the most consequential number in this setup, and it is a policy decision before it is a setting. Set it to zero and any check-in counts as a day, including a quick visit to collect a laptop. Set it to a full working day and people who leave early for a school run lose the day entirely.
A practical way to choose it:
- Start from the policy's purpose. If the goal is collaboration, a day probably means being present for the core hours when teammates overlap. If the goal is simply reconnecting with the office, a shorter threshold is defensible.
- Write the threshold in hours in the policy document, so employees can check their own days against it.
- Remember that time is summed per day. If someone checks out of one desk and books and checks in to another later the same day, both periods count toward the same day.
- Revisit it after a month of data. If a large share of days fall just below the threshold, either the threshold is out of step with how people actually work, or the booking durations people choose are too short.
A worked week
Take an illustrative employee on a three-days-a-week policy in a workspace that has set a four-hour minimum.
On Monday they book 9:00 to 17:00, scan the desk code at 9:10, and the booking completes at 17:00. That is close to eight hours of checked-in time and counts as a day. On Tuesday they book but a family matter keeps them home and they forget to cancel; the booking is released as a no-show and does not count. On Wednesday they book 9:00 to 17:00 but only arrive at 14:30, by which time the original booking has been released, so they book again from 14:30 and check in. Two and a half hours falls short of the minimum, so the day does not count. On Thursday they check in at 8:55 and check out at 13:30 to catch a flight; four and a half hours meets the threshold and the day counts.
Their dashboard shows two office days for the week. Every one of those outcomes can be explained from the policy page, which is the test any verification rule should pass.
Planned days versus verified days
Verified days answer "did it happen?". Planning answers "will it happen?", and hybrid teams need both. DeskHybrid's optional weekly plan lets employees mark the days they intend to be in the office, and the team page shows a Team Weekly Plan so colleagues can line up their days. Admins switch it on in the workspace settings; it is off by default.
Keep the two signals separate in your policy language. A planned day is a coordination tool and should never be used as evidence of attendance. A verified day is evidence and should not be used to pressure people about their plans. When a team's plans and verified days diverge week after week, the useful conversation is about why, whether that is unclear expectations, desk shortages on popular days, or anchor days that clash with travel, rather than about individual compliance.
Making the scan trustworthy enough to count
If verified days are going to matter in policy conversations, the check-in itself has to be hard to fake and easy to do.
By default, DeskHybrid accepts either a QR scan at the desk or the in-app check-in button during the check-in window. For a policy that counts days, that is usually too loose, because a button can be tapped from home. Admins can require QR check-in for desks, which makes the scan at the desk the only accepted route. Each desk code is cryptographically signed, so a code that has been edited, or that belongs to a different floor, is refused.
Where photographed codes are a real concern, admins can also require that the scan happens within a set radius of the floor's configured location. The phone's position is read once, at the moment of the scan, and compared with the floor. Nothing is tracked before or after. Say this plainly in the policy, because an accurate description of what is collected is what keeps verification from feeling like monitoring.
Ease matters as much as rigor. DeskHybrid is available on Web, Android, and iOS, so employees can check in with the device they already carry, and biometric sign-in on the mobile apps removes the password prompt at the desk. If someone books after the check-in window has opened, the mobile apps offer check-in immediately, which avoids a whole category of "I booked from my desk but forgot to check in" days.
Edge cases HR should decide in advance
Verification rules are tested by edge cases, so decide them before employees raise them.
**Late arrivals.** If an employee arrives after their booking has been released, the original booking cannot be checked in. They can book a desk again and check in, and the time from that check-in counts. Make sure people know this so a late train does not cost them the day.
**Forgotten scans.** An employee who worked in the office but never checked in has no verified day. Decide whether managers can accept other evidence for occasional misses, and make that route explicit rather than ad hoc. Treat repeated forgotten scans as a usability signal first: is the code placed where people actually sit down?
**Half days and split days.** Decide whether half days count toward the policy at all. If they do, the minimum duration needs to reflect that.
**Visiting another office.** A checked-in day at any of the company's locations counts in the same way as a day at the employee's usual office, so a policy written in days does not need a separate rule for travel between sites.
**Leave, travel, and sickness.** Verified days only record presence. Absences that the policy excuses need to be handled in your HR system, not by adjusting desk data.
Using verified days fairly
A verified office day is a fact about a desk and a time. It should be used to understand patterns and support conversations, not to rank people.
Each employee sees their own week and month count, which means the first person to notice a discrepancy is usually the employee, not their manager. Encourage people to check it. Workplace reports give admins aggregate booking, occupancy, and no-show views for planning. Occupancy figures count only active desks, so capacity is not overstated when desks are out of service.
Agree in writing who may look at what and for what purpose. A sound default is that managers discuss attendance patterns with the employee using the same numbers the employee can already see, and that verified days are never combined with other monitoring data. Policies that hold to this tend to get higher check-in rates, because employees see the system as a record they can rely on rather than a trap.
Communicating the policy to employees
Employees should be able to answer four questions from a single page: what counts as an office day, how to check in, what happens if they are late or forget, and where they can see their own count. Include the minimum duration in hours. Include a screenshot of the desk code and where it sits on the desk.
DeskHybrid's interface is available in English and Turkish, the language on a first visit follows the browser, and a language choice carries across the web and mobile apps. For mixed-language teams, publish the policy page in both languages as well, so the rules and the interface read the same way.
Where the company uses Microsoft Entra ID, single sign-on keeps identities tied to the directory. Accounts are created on first sign-in, there are no separate passwords, and display names come from the workspace. That matters for verified days, because the name on the record is the name HR knows.
Measuring whether verification is working
In the first quarter, watch a small set of indicators. The check-in rate shows whether verification is practical: low rates on one floor usually point to code placement. The share of checked-in days that miss the minimum duration shows whether the threshold fits how people work. The gap between planned days and verified days, by team, shows where coordination is breaking down. Disputes raised by employees about their own count should be rare and easy to resolve; if they are not, the rules are not clear enough yet.
Review these monthly with HR and workplace operations, change one rule at a time, and record why.