Automatic Presence Detection in the Office: What's Technically Possible and What to Sort Out First

Dock your laptop, and your desk is booked. Automatic check-ins sound like an easy fix for a familiar problem, and technically, a lot is possible. But whether it makes sense for your organization is rarely a question of technology.

Sooner or later, almost every company with desk sharing runs into the same question: Who's actually in the office? Desk bookings show who plans to come in and where, but they don't reflect what really happens. People book from home, forget to check in, and switch desks on the fly without it ever showing up in the numbers.

The market is increasingly answering with automatic presence detection. Software on the laptop, network signals or sensors are supposed to detect whether a desk is in use and take care of booking and check-in along the way.

Customers regularly ask us whether Gingco Share can do this too. The short answer: yes. The honest answer takes a bit longer. Whether automatic detection makes sense depends less on the technology than on its purpose, data protection, co-determination rights, and whether your employees are on board. This article puts the technical options in context and shows what you should clarify before rolling anything out.

Booked Doesn't Mean Present

Automatic presence detection refers to methods that determine whether a person is in the building or a desk is in use, without employees having to do anything. They rely on technical signals, such as a laptop connecting to the corporate network, a docking station or a monitor, data from the access control system, or presence sensors. An automatic check-in uses these signals to mark a booking as used without manual confirmation, or to create the booking in the first place.

This needs to be distinguished from three types of data that often get lumped together in practice:

• Booking data shows intent: who wants to use which desk, and when.
• Check-in data shows confirmation: the person is there and using the desk they booked.
• Occupancy data shows actual use: how much a desk or area is really being used, with or without being tied to individuals.

This distinction is more than semantics. For space planning and utilization analysis, anonymous occupancy data is usually all you need. The questions this article focuses on only come up once a system is supposed to know who is there.

The Technical Options

The methods differ mainly in two ways: how precisely they locate someone and how closely they're tied to individual people. Both determine how much alignment with your data protection team and works council will be needed.

In many cases, two methods already solve the original problem well enough: IP range mapping to tell whether someone is on site, and a standard check-in at the building or site entrance. If you need to know whether individual desks are occupied, you can do that without identifying anyone, for example with a button at the desk or with sensors.

What Automatic Detection Can Do

Used the right way, automatic methods solve real problems in day-to-day desk sharing.

More Reliable Utilization Data

Space decisions are often based on booking data. People who book and don't show up skew the numbers just as much as people who grab a free desk without booking. Occupancy data closes that gap and gives you a more solid picture of how floors and spaces are actually used.

Fewer Blocked Desks

When bookings without a check-in are released automatically, unused desks become available to others again. An automatic or very simple check-in reduces the number of bookings that lapse simply because someone forgot.

Less Effort for Employees

Every manual step is a hurdle. The less people have to actively confirm, the better the data quality tends to be, as long as employees accept the method.

A Foundation for Building Management

If you know which floors sit empty on which days, you can plan cleaning, heating and air conditioning accordingly. Anonymous occupancy data is all you need for that.

Where the Limits Are

Every method measures a signal and infers presence from it. That inference is never completely reliable.

• Network signals are imprecise. An IP address shows that a device is on the corporate network, not which desk it's at. VPN connections, hotspots or network segments that span several floors distort the picture.
• A device is not a person. A docked laptop shows that a device is connected. People who work on a tablet, leave their computer in a locker or only drop by for a meeting won't be detected.
• Software on every device. Client-based solutions have to be installed on all relevant devices, maintained and approved for every operating system. In large enterprises with strict software approval processes, that's a project in its own right.
• Hardware takes up space and needs upkeep. Sensors and buttons need to be mounted, require power or batteries, and have to be connected to the booking system.
• The data often already exists, just not for this purpose. Network, device management and access control systems can often detect presence already. Whether that data may be used for this is a different question, which we'll get to in the next section.

Data Protection, Works Council and Employee Buy-In

In our consulting experience, automatic presence solutions rarely fail because of the technology. They usually fail at approval by the works council and data protection team, or because employees don't accept them. Factoring this in from the start saves you from a project that ends up never being allowed to go live.

Works Council Co-Determination

Under Section 87(1) No. 6 of the German Works Constitution Act (BetrVG), the works council has a right of co-determination when technical systems designed to monitor employee behavior or performance are introduced or used. According to established case law of the Federal Labor Court, it is enough for a system to be objectively capable of monitoring. The employer's intent is irrelevant. As a rule, a system that automatically records when which person is in the office therefore requires co-determination. The usual approach is a works agreement that defines the purpose, the data collected, the analyses and the access rights.

Data Protection Under the GDPR

Three principles are especially relevant for presence data:

• Purpose limitation: Data from access control, the network or device management was collected for security and IT operations. Using it to analyze presence requires a separate legal basis.
• Data minimization: If the goal is space planning, you should only collect the data you need for that, which is usually anonymous occupancy data.
• Anonymous is not the same as pseudonymous: If device or network identifiers are collected that can be linked to a person, the data isn't anonymous but pseudonymous, so it's still personal data. Whenever you hear claims like “completely anonymous,” ask who can make that link.

In addition, systematically tracking employees may require a data protection impact assessment (DPIA) under Art. 35 GDPR. That's why you should involve your data protection officer early on.

Employee Buy-In

Even a legally sound solution can fail in everyday use. A program that reports in the background when someone arrives and leaves quickly feels like surveillance, no matter what's actually being analyzed. The result: employees work around the system, book less often or reject desk sharing altogether, which undermines the very data quality the method was supposed to improve.

Buy-in comes from transparency: a clearly stated purpose, visible limits on what's analyzed and, wherever possible, methods that employees trigger themselves.

Note: This article provides an overview and does not constitute legal advice. The specific assessment depends on how your solution is set up.

A Real-World Example: When the Answer Is No

An enterprise customer recently asked us whether Gingco Share could detect employee presence via their computers' network connection. The reasoning made sense: desks can also be booked remotely, so a booking says nothing about who's actually on site.

Technically, this requirement can be met. We outlined two options – querying the existing access control system and mapping IP ranges at login – and pointed out at the same time that concepts like these often fail to get works council approval.

The outcome: The customer's data protection team rejected the project. What stood out was that their existing network and device management tools could have done the job as well, but that kind of tracking had already been prohibited there.

This example shows what really matters: The key question isn't which tool can detect presence. It's whether the organization wants to do it and whether there's a purpose that justifies collecting the data. That question belongs at the beginning of a project, not at the end.

Checklist Before Rollout

Before you decide on a method, make sure these points are clear:

1. Purpose: What problem are you trying to solve: space planning, releasing unused bookings, or verifying who's on site?
2. Data needs: Is anonymous occupancy data enough, or do you really need to know who it is?
3. Location accuracy: Does the system need to know the individual desk, or are building and floor enough?
4. Existing infrastructure: Do you already have access control, terminals or sensors you can use?
5. Works council: When will the works council be brought in, and what should a works agreement cover?
6. Data protection: Legal basis, retention period, deletion policy, access rights and, if required, a data protection impact assessment.
7. Reporting: Who is allowed to see which reports, and at what level of aggregation?
8. Communication: How will employees find out what is and isn't being recorded?
9. Alternatives: Is there a less intrusive method that would serve the same purpose?

How Gingco Share Handles These Requirements

Gingco Share can detect presence in a number of ways. We've already implemented similar concepts as custom solutions for customers. We work with you to figure out which approach fits before anything gets configured.

• Check-in at the building: Ideally by querying your existing access control system. Anyone who enters the site or office building is considered present.
• IP range mapping: The simplest solution. When a person logs in to the web interface or app, Gingco Share assigns them to a location based on the network range. No additional client is needed on their computers.
• Anonymous desk occupancy: For example, via a button on the desk that employees press when they arrive. The system knows the desk is occupied, but not by whom.
• Sensors: Presence sensors from any manufacturer can be connected via MQTT or HTTPS. This generates anonymous occupancy data for space planning.
• Check-in via app, browser or display: Employees confirm their booking themselves. Check-in and check-out can be configured for each resource.

We're deliberately cautious with our recommendations: We'll implement what's technically requested, but we won't recommend a method just because it's technically possible. In many cases, you can reach your goal with a solution that doesn't identify individuals or that employees trigger themselves. These methods are easier to get approved and are more likely to be accepted in everyday use.

Frequently Asked Questions

Bottom Line: Purpose First, Technology Second

Technically, automatic presence detection is no longer a major hurdle. Network, access control, sensors or a simple button at the desk – there's a way to meet almost any requirement. But whether a method makes sense is decided elsewhere: by its purpose, co-determination, data protection and whether your employees accept it.

In many cases, the best solution isn't the one that collects the most data, but the one that gets by with the least and still answers the right question.

Thinking about tracking presence or occupancy automatically? Talk to us before you decide on a method. We'll show you which options fit your infrastructure and tell you openly where we see risks.