Office management Workplace and reception Occupancy and usage

Custom office management software development

An office manager's work rarely fits into a single system. The rooms are in the calendar, the visitors in a notebook or on a tablet, the keys in a spreadsheet, the office orders in a mailbox and the report about the leaking tap in a group chat. Each part works on its own, but nobody sees the connection. Appfront builds custom software that brings booking, reception, access, stock, reports and occupancy in a work environment together.

What office management software is

Office management software is the working system of the people who keep the office running: the office manager, reception, the secretariat and the colleague who always ends up getting pulled in. It covers the day-to-day running of things inside the walls: which workspaces and rooms are occupied, who is coming in today, who holds which key or pass, what needs reordering and which report about the building is still open. That is a collection of small processes that are each unremarkable on their own and together determine whether an office day runs smoothly.

The category is often confused with two neighbours. Facility management is about the building and the contracts: maintenance plans, inspections, installations and suppliers. Building management or smart building is about the technology: climate, energy and faults from the installations themselves. Office management sits in between, at the level of people and things. If you are after the contract and maintenance side, facility management software is the better starting point, and for installations and sensor data, read on at smart building software.

Who uses the system determines what it should look like, and there are five different types of user. The office manager manages and sees everything. Reception wants a view of the day: who is coming in today, to which room and to see whom. Staff want to be able to do two things and nothing more: book a space and report an issue, ideally in a few taps on their phone. A team leader wants to get their team together on the same day. And whoever is responsible for the building or the contract only wants to see figures. A system that mainly gets the administrator view right falls apart in use, because without staff booking and reporting there is no data, and without data the reporting at the end is an empty promise.

Are you in the right place? This page is about the office and the building, not about HR administration. Absence, contracts and appraisals belong in the HR system and stay there. If your question is about exchanging employee data between that HR system and the office systems, you want HR and office integration. Here, the focus is the working day itself.

Five lists, one working day

Bookings, visitors, passes, orders and reports all touch the same day. For now, only the office manager sees the connection.

People and things, not installations

Climate, energy and technical faults belong to building management. Here, the focus is on who is in the building and what they need.

Every record is tied to a person

Passes, keys and bookings all refer to employees. That is why the integration with the staff register is so sensitive.

Where the separate lists meet

Each of those five parts is easy enough to solve on its own. The calendar can reserve rooms, a tablet at the front desk can let visitors sign in, a spreadsheet keeps track of keys and a mailbox collects orders. The bottleneck is not in the parts but in the hand-offs, and those hand-offs are exactly where an office day breaks down.

A visitor checks in at the front desk for a meeting. Reception sees the registration, but not that the room was moved to another floor an hour earlier, because that change was made in the calendar and not in the visitor system. A new colleague starts and gets a pass, but the change in the HR system has not been processed yet, so the access system does not recognise them and the pass does not work on the third floor. Someone leaves and their pass is blocked, but the key to the archive cabinet is still in a drawer at home; the overview says returned because nobody actually checked. A room is marked as occupied and stays empty, while four people stand in the corridor trying to find somewhere to talk. And the coffee order goes along with whoever happens to be heading to the shop, so nobody can see what the office really consumes.

These are not dramatic failures, and that is exactly why they persist. Each one costs a few minutes, mainly causes irritation for visitors and new colleagues, and leaves no trace that anyone could use to demonstrate the pattern. The office manager knows, because they deal with all five cases, but has no figure to start the conversation with. What a system adds here is not speed but consistency: the same appointment, the same person and the same room are the same thing everywhere, and whoever changes something only has to do so in one place.

Take the desk that is booked and stays empty. It is the most visible problem in any office with flexible workspaces, and it has two causes that call for different solutions. The first is today's forgotten booking: someone reserves a desk and works from home. The fix is a short check-in on arrival, after which the desk releases itself if no confirmation comes. Set too strictly, this annoys people stuck in traffic; set too loosely, it does nothing. The second cause is more persistent: the recurring booking that nobody cancels. A weekly meeting that stopped happening long ago keeps the best room occupied, and nobody is responsible for clearing it up. A system should spot that pattern itself and ask the owner whether the series is still needed.

A new colleague's first day is the second example where the separate checklists come together. On the office side, that day needs a workstation, a pass that works, possibly a key or a locker, sometimes a parking space, and someone to welcome the new starter. That is four or five tasks spread across as many people, usually organised via an email that not everyone reads. A checklist per arrival, with an owner and a status on each line, is the whole solution. On departure the same list works in reverse, and it matters even more then, because it determines what has to be handed back. The people side of that process stays in the HR system; this is about equipment, workspaces and access.

Office supplies seem the most harmless part and are the worst organised. Coffee, paper, cleaning products, batteries, keyboards, the box of cables: things get ordered the moment someone notices they are nearly gone, and that moment rarely coincides with a convenient time to order. The result is small one-off orders, rush deliveries, and consumption that nobody can attribute to a floor or a location. With minimum and maximum levels per item per location, the moment to reorder announces itself, and fixed ordering rounds bundle what would otherwise go out the door piecemeal. Just as important is who may order and up to what limit, and what happens when a request exceeds it. With multiple locations, a question arises that nobody can answer without tracking: does one site consistently use more than another, and can that be explained by the number of people present? It is the same occupancy question, now seen from the purchasing side.

Where reports about the building get stuck

Reports deserve separate attention, because almost everywhere they go wrong in the same way. A report comes in as a remark in the corridor, a message in a group chat or an email to the office manager. What is missing is not the report but the follow-up: an owner, a status and a moment when someone reports back. Without those three, a report is just a wish. The colleague who reported the broken chair never finds out whether anything happened with their message, and next time reports nothing.

The second mistake is that office reports end up in the IT service desk, simply because it is the only ticketing system around. A jammed door then sits in the same queue as a password reset, with categories that do not fit and handlers who are not responsible for it. A dedicated reporting flow with office categories, a location on a floor plan and a hand-off to the facilities provider works better. If you need the handling side, with queues, response-time agreements and reporting, look at a custom ticketing system, or at an integration with what is already in place, such as a TOPdesk integration.

The third mistake is that nobody keeps a record of reports. Only once they are logged does it become clear that it is the same meeting room that has been too warm for the third quarter running, or that the coffee machine on the second floor breaks down time and again. That is the difference between an incident and a pattern, and it is the only thing that gets you anywhere with a supplier or the landlord.

What an office management system needs to do

Six components, and the value lies in the combination. Booking without reception leaves the front desk in the dark, access without an issue register gives you a block list with no history, and measuring occupancy without bookings and check-ins produces figures nobody dares to use. Specialist software exists for each component, and where that is the better choice we point to it below.

Introducing everything at once is rarely wise. Start with the component that goes wrong most often for you, because that is the quickest way to deliver something your colleagues will notice. What you do need to get right from the start is the foundation: a person, a location and a room should be the same thing everywhere, with the same register behind them. Trying to slot a shared room register underneath three separately built components later costs more than thinking of it at the outset. That is also why separate tools side by side look cheaper on paper and are not in practice.

Workspace and room in one booking layer

Desks, meeting rooms, parking spaces and lockers with capacity, facilities, team days and release on a no-show. See also flexible desk booking.

Pre-registration and reception

Pre-registration, check-in at the desk, a notification to the host, badges and non-disclosure agreements where needed. See also visitor registration.

Keys, passes and access

Issue and return with confirmation, who holds what, a locking plan per cylinder and temporary rights for contractors. See also key management.

Office stock and orders

Minimum and maximum levels per location, a reorder prompt that triggers itself, approval from the budget holder and ticking off deliveries on receipt.

Reports with an owner and a status

Reporting with the location on the floor plan and a photo, an owner per category, feedback to the reporter and visibility of what keeps recurring.

Occupancy and actual use

Bookings, check-ins and counts side by side per zone and per day, so a peak can be told apart from an average.

Measuring occupancy to justify square metres

Since hybrid working became normal, the question of how much office space an organisation needs has become a recurring conversation. That conversation is almost always held on gut feeling: one manager sees an empty floor, another has no meeting room on Tuesdays. Office management software is the one place where the data can come from to make that conversation factual, because bookings, registrations and attendance already come together there. That is also the argument that gets an office manager's system sold internally: it provides the evidence the board asks for.

There are three sources of occupancy data, and each one is misleading in its own way. Bookings show intention, including the spaces that are booked and not used. Check-ins show behaviour, but require an action people forget, so the figures come out too low. Counts and sensors show presence without knowing who is sitting there, which is often exactly enough for this question. If you want to build a serious case, put the three side by side and explain the differences, rather than elevating one of them to the truth.

The number that matters is the peak per zone per weekday, not the average across the whole week. An average makes every office look half empty, while the building has to cope with its busiest day. Also look at the difference between types of space: desks are often empty while meeting rooms are in short supply, and that leads to a refit rather than a smaller lease. Measure per zone rather than just per floor, too, because in practice teams claim corners of a floor.

The measurement period is a pitfall. Figures from a holiday period, from the weeks around a move, or from a time when a floor was under scaffolding are no basis for a decision about a lease. So record with every report which period was measured and what was unusual about it. Expect measuring to change behaviour as well: as soon as people know they are being counted, some will book spaces they would not otherwise book. So publish what you measure and why, and use the same figure internally and externally.

Measuring is not a goal in itself, so agree in advance what you will do with the outcome. There are three directions. You can rent fewer square metres, in which case the peak per zone is the figure you negotiate on. You can lay out the same space differently, for example swapping desks for meeting and focus space, in which case you need the difference between types of space. Or you can steer demand: spreading team days across the week is the cheapest intervention and often delivers the most, because Friday's empty desks do nothing for Tuesday's crowding. Also agree in advance what occupancy counts as full, because without a standard every number gets challenged again the moment the outcome does not suit someone.

There is a limit that goes with this. Occupancy per zone per part of the day is not about individual employees and is a useful metric. As soon as you record a name per desk, you are processing personal data and have a tool that can be used to track employee attendance. That is permitted, but it requires a documented purpose, a retention period and no more data than necessary. For arrangements that can monitor employees' attendance or behaviour, the works council has a right of consent. Take that step early, because defending a measurement system afterwards costs more than explaining it beforehand.

  • Peak occupancy per zone per weekday, not the weekly average
  • Bookings, check-ins and counts side by side, with the differences explained
  • Desks and meeting rooms separately, because they move in opposite directions
  • Measurement period and anomalies recorded with every report
  • Zone level for the square metres, names only where it serves a purpose
  • Retention period and purpose fixed in advance, works council involved in good time
  • The same figure for the board, the teams and the landlord
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Integrations, data and the boundary with HR

An office management system is rarely the first system in an organisation. It arrives in a landscape where the calendar, the personnel register, the access system, the service desk and the procurement administration are already in place. So the question is not which data the system will record, but which data it may read and what it is the source of. Without that agreement you end up with a second personnel file, and that is the most expensive mistake in this category.

Start with the personnel register. The office management system needs very little: name, team, location and whether someone is employed. That comes from the HR system and none of it should be entered again here. In practice, the first and last working days are when things go wrong, because that is when the pass, key, desk and access rights have to follow a change made elsewhere. We have a separate page on setting up that exchange, including provisioning user accounts via the standard provisioning protocols: HR and office integration. What does not belong there, and does not belong here either, are absence, contracts and appraisals.

The calendar is the second integration and usually the trickiest. A booking that exists only in the office system doesn't appear in the invitation attendees see; a room that is booked only in the calendar is invisible to reception. Syncing with Microsoft 365 or Google Workspace solves that, but forces a choice: which side may change the room, and what happens when there is a conflict. If you don't make that choice, you end up with two sources of truth. For the broader booking question, beyond the office, custom booking software is the wider starting point.

Access is the third and calls for restraint. The physical layer has its own suppliers, controllers and protocols; between card reader and controller, OSDP is the common successor to the old Wiegand signal, and mobile passes work via NFC or Bluetooth on the phone. An office system shouldn't control that door itself. What it does do is record and pass on the authorisation: this person or visitor may enter this zone, from this time until that time, with this pass. The issuing register around it remains the domain of this system, because that is administration rather than security engineering.

That leaves the reports and the orders. A report that needs an engineer or a contract goes on to the facilities or IT service desk, with a reference back so that the person who reported it can see the status in the office system and doesn't have to check two portals. An office order eventually becomes a purchase order and then an invoice; that process shouldn't be rebuilt in an office tool but should flow on to where commitments and invoices belong. If that becomes the core of your question, read on at custom procurement software.

Underneath all these integrations lies something that is rarely discussed: the floor plan. As soon as you book workspaces, log reports against a location and report occupancy per zone, the floor plan is the heart of the system. A drawing as an image is dead material; what you need is a floor plan in which every desk, room and zone is its own addressable object. That comes from a drawing by the architect or the interior designer, often as an export from CAD or from the building model. More important than the source is maintenance, because every reorganisation and every renovation changes the plan. Decide who maintains the floor plan and how a change gets into it, otherwise your reports and figures will point to places that no longer exist after a move.

You log in with the accounts that already exist, via the organisation's identity provider, so that no second user list emerges that someone has to clean up. At the front desk this needs extra attention. A reception computer is used by several people, so a shared account is tempting, but then the same name appears in the log every time a pass is issued and the audit trail is worthless. Fast user switching on the same device solves that. For visitors the opposite applies: they don't get an account, only a registration with a short validity.

Finally, the data itself, because this is a more sensitive register than it seems. Taken together, it shows who was in the building and when, who holds which key and who may enter which zone. That calls for roles that go beyond administrator and user: a receptionist sees today's visitors, a team leader sees their own team, and a historical overview of attendance is day-to-day work for almost no one. This comes with an audit trail on issuing and authorisation, and retention periods per type of data. A visitor registration serves an evacuation purpose for today; keeping years of visitor history is a choice you must be able to explain explicitly.

Workspace booking Pre-registration Badge issuing Key and pass register Access authorisation Minimum and maximum stock Reports with an owner Occupancy reporting Calendar synchronisation Audit log

When an off-the-shelf package is the better choice

Office management is not an untapped gap in the software market. Workspace booking and visitor registration are mature product categories with plenty of suppliers, there are broad packages that combine property, workplace and facilities management in one suite, and most organisations already have a ticketing system. For some readers of this page, an off-the-shelf package is the wiser route, and we would rather say so now than halfway through a quoting process.

So start by taking stock of what you already pay for. Your office environment can probably already book rooms and has functionality for workspaces and floors. The supplier of your access system often has a visitor module that can issue passes, and that is exactly where that belongs. Your facilities provider usually offers a reporting portal. In many cases the answer is not new software but switching on and configuring what you already have, and agreeing which system is the source for what.

If your office follows the usual pattern of booking desks, registering visitors and reporting issues, you buy that ready-made, including maintenance and updates for changing regulations. Your effort shifts from building to configuring, and with this category that is no small job: floor plans, zones, permissions and categories all have to be thought through by you either way.

Custom software pays off in fewer situations than suppliers suggest, but a few come up again and again. The first is a reception that is the front door for more than visitors: a contractor who may only enter with a valid safety certificate, a supplier who must first complete an induction, or a building where several organisations share a front desk and the reception process differs per tenant. A gate like that at the desk is usually not part of standard products, and it is exactly the point where things go wrong if it is not right.

The second is a building that does not resemble an office: a laboratory with zones where authorisation, not availability, determines who may enter, a care location with visitors who are not really visitors, or a school where pupils, parents and suppliers come through the same door. The third is an organisation where reception is itself the product, such as serviced office space, because then the way things work at the desk is not a side issue but the offering. The fourth is easy to recognise: when the number of integrations between five separate tools grows larger than the system you would build around them.

The order in which you make that assessment determines the outcome more than the list of features does. First write down, per component, which system is the source: where the room is recorded, where the person is recorded, where the report is recorded. Then take stock of what you already have and what of it is switched on. Only then ask whether the gap that remains calls for a package or custom software. If you reverse that order, you start with demonstrations and then choose a system that introduces a second source of people or rooms. Also test the result on a real office day at a real location, with real bookings and real visitors, because a front desk on a busy morning exposes weak spots faster than any feature list.

The flip side comes with the territory. If you build it yourself, keeping the integrations up to date is your own organisation's job, and it is precisely calendar APIs and access systems that change without you having a say. Often the middle way is the best answer: an off-the-shelf package for bookings, custom development for the layer that ties the front desk, issuing and notifications together. If your notification flow mainly needs planned maintenance with work orders and history per asset, you are better served by custom maintenance software than by an office tool.

  • Off-the-shelf if booking and registration follow the standard pattern
  • Off-the-shelf if part of it already lives in your office environment or access system
  • Custom if the front desk is a gateway, with certificates or instructions
  • Custom if several organisations or tenants sit behind one front desk
  • Custom if reception is itself what your organisation offers
  • The middle way: off-the-shelf for bookings, custom for the connecting layer

Frequently asked questions about office management software

Facility management looks at the building and the contracts: maintenance plans, installations, suppliers, inspections and the property itself. Office management software is about the working day in the office: who sits where, who comes in, who has which key or pass, what needs to be ordered and which request is still open. The two meet at notifications and at space usage, because a request that needs an engineer or a contract should pass on to the facilities side, and the occupancy figures from the office are the evidence for decisions about square metres.

Yes, and that is usually exactly the benefit. A visitor comes for a meeting, so the visitor's registration and the room booking belong to the same appointment. If they sit in two systems, reception can't see which room the visitor needs to go to, and the host can't see that the room has since been moved. It is still wise to record for each component which system is the source, so there is one place where the appointment is changed and the rest follows.

By leaving the HR system as the source and letting the office management system only read what it really needs: name, team, location and whether someone is employed. The office management system does not store employment contracts, leave or appraisals itself. The two moments that most often go wrong are the first and the last working day, because that is when the pass, key and workspace must follow a change entered elsewhere. How such an integration is built in practice is covered on our page about HR and office integration.

Measuring is allowed, provided you set out in advance what you are doing it for and don't collect more than that requires. For a question about square metres, occupancy per zone per part of the day is enough, and at that level it isn't about individual employees. As soon as you record a name per workspace, you are processing personal data and you also have a means of tracking attendance. For arrangements of that kind the works council has a right of consent, so involve it early and be open about what you measure and what you do with it.

That is the moment when a loose spreadsheet usually lets you down. An issuing register records per person which pass, key, locker or safe key has been issued, with a date and confirmation on issue and on return. On departure, that register produces a checklist, and anything not returned stays open instead of quietly disappearing. For a missing key it should be immediately visible which cylinders it can open, because that determines whether you replace one cylinder or an entire keying group.

Often you do, and then that's the wiser route. Desk booking and visitor registration are mature product categories, and some of the functionality may already be in your office software or with the supplier of your access system. So start by taking stock of what you already have. Custom software becomes interesting when reception is also the front door for other flows, such as contractors with a valid certificate or visitors to several organisations in the same building, or when the number of integrations between separate tools outgrows the system itself.

Related services

Flexible workspace booking system

If booking is the core of your question, with desks, meeting rooms, parking spaces, team days and release on a no-show, then a custom flexible workspace booking system goes into that in detail.

Visitor registration software

If it is mainly about the front desk, with pre-registration, check-in via kiosk or QR code, badges, notifying the host and an evacuation list, read on at visitor registration software.

Key management software

For issuing and returning keys, lock plans per cylinder, the procedure for a missing key and an audit trail of everything that has been handed out: custom key management software.

Facility management and building data

For contracts, maintenance plans and suppliers, facility management software is the right place, and for installations, comfort and energy, see smart building software.

Your office day under the microscope

Tell us where a visitor is registered today, where you look up who has which key, and what happens to a building report after it has been passed on. Those three answers usually show whether you should switch on something you already have, choose a package, or need a custom connecting layer.

Edit content