Skip to content
Controlbook
All posts
Academy· 6 min read

Why hotels lose track of their FF&E — and what to do about it

Hotel operators know their rooms. But ask them exactly what's in those rooms, who supplied it, and what the fire rating is — and the answer becomes complicated. Here's why that happens.

Stuart Anderson
Cozy hotel room with plush armchairs representing the FF&E that hotels frequently lose track of over time

A hotel general manager can typically tell you how many rooms they have, what their current occupancy is running at, and which three TripAdvisor reviewers they'd most like to call back personally. What they are less likely to be able to tell you — quickly and accurately — is what the armchair in room 214 is, who made it, and what it would take to replace it.

That's not a failure of management. It's what happens when the system that's supposed to hold that information is a PDF that nobody has updated since the day it arrived.

The turnover problem

Hospitality has some of the highest staff turnover of any major sector — around 70–80% annually by some industry measures. General managers specifically tend to rotate every two to four years, often moving between properties within the same group or to competitors offering better roles.

Each rotation is a knowledge reset. The GM who received the O&M manual at the hotel's opening may have built up, over time, a practical working knowledge of the specification: which suppliers to call, which items were already replaced and with what, which categories were causing recurring problems. None of that knowledge is recorded anywhere. When they leave, it leaves with them.

Their successor inherits a building they haven't been involved in specifying, a document they didn't participate in creating, and a team whose own knowledge is partial and unevenly distributed. The FF&E specification — if it's recoverable at all — requires re-learning from a document that may no longer accurately reflect what's actually in the rooms.

Three layers of FF&E knowledge, and which ones survive

It helps to be specific about what kind of knowledge gets lost and what doesn't.

Layer 1: What's in the rooms. The original specification — manufacturer, model, finish, supplier — for every item in every room type. This is the hardest to recover once the original project team has dispersed, but it's also the most durable if it's recorded correctly. A well-assembled Control Book captures this layer. The problem is that most Control Books are out of date within two years of handover, as items are replaced and substitutions aren't recorded.

Layer 2: What's changed. Every replacement, every substitution, every item added or removed since opening. This is the layer that almost never gets recorded systematically. When a bedside lamp is replaced because the original broke and the model was discontinued, the replacement information lives in an email, or in nobody's records at all. The gap between the original specification and the current state of the rooms widens with each unrecorded change.

Layer 3: What works. The accumulated knowledge of which suppliers respond quickly, which alternatives have been tried and rejected, which categories generate the most problems, which room types have the most outstanding maintenance items. This is the most fragile layer — it exists only in people's heads and evaporates with every team change.

A hotel that has operated for ten years without maintaining its specification record has, in practice, reliable knowledge only of Layer 1 at the moment of opening — and that record is increasingly misleading because Layer 2 has never been captured.

Why the problem compounds

The three layers interact. When Layer 1 is out of date because Layer 2 was never recorded, Layer 3 knowledge — the practical wisdom about how to handle replacement — has to compensate. A facilities manager who doesn't know the original specification has to rely on experience and relationships to navigate each replacement: calling the supplier they remember from last time, describing the item as best they can, accepting the closest available alternative.

That works, roughly, as long as the experienced facilities manager is still in post. When they leave, even that compensating knowledge is gone. The next person starts from scratch: a current specification record that's significantly out of date, no record of what's been changed and why, and no inherited knowledge of which suppliers or alternatives have been tried.

Each team rotation leaves the hotel marginally worse off in its knowledge of its own assets. Over a decade and multiple turnover cycles, the degradation is significant.

What institutional memory looks like when it's working

The contrast is a hotel where the asset record is current, maintained, and accessible to everyone who needs it — not because any individual remembers it, but because the system records it.

When an item is replaced, the record updates: new manufacturer, new model, new certificate, new supplier contact. When a supplier changes, the record reflects the new contact. When an alternative is sourced and found to work well, that preference is recorded against the item category so the next person to face the same replacement has a head start.

The facilities manager who joins this hotel doesn't inherit a failing memory and a PDF. They inherit a live database that reflects the actual current state of the building, with a record of what's been changed, when, and why. That's the difference between institutional knowledge that survives turnover and knowledge that disappears with each departing team member.

Where to start

If your property's FF&E knowledge is concentrated in people rather than systems, the starting point is the same regardless of whether you have a good original O&M manual or a poor one: establish what's actually in the rooms now, not what the original document says was there.

This means a structured audit — going through each room type and confirming the current specification against what's recorded, noting every discrepancy. It's not glamorous work, and for a large property it takes time. But the resulting record — one that reflects the building as it actually is rather than as it was at handover — is the foundation for everything else.

The guide on why O&M manuals fail hotels goes deeper into the structural reasons the data degrades. And if you want to see how Controlbook approaches the ongoing problem of keeping a live specification current as a hotel evolves, book a demo or read more on the platform page.

Frequently asked questions

Is the knowledge loss worse in managed hotels or owner-operated properties?

Both face the same fundamental problem, but it manifests differently. Managed hotels often have higher GM and team turnover because managers rotate between portfolio properties. Owner-operators may have more stable teams but often have less formal systems — the owner-operator who knows everything about their own property creates a single-point-of-failure risk when they eventually transition.

What's the fastest way to audit an existing property's FF&E record?

Focus first on the highest-risk categories: upholstered seating (compliance risk), decorative lighting (high discontinuation risk), and bespoke casegoods (long lead times if replacement is needed). Getting those categories right gives you the most operationally important coverage early. Accessories and lower-specification items can follow.

How do we encourage the team to record updates when they make replacements?

The key is making the update part of the replacement workflow rather than an additional administrative step. If updating the specification record is a separate task that requires logging into a separate system, it gets skipped. If updating the record is the same action as confirming the replacement order is complete — part of closing the maintenance ticket — it becomes part of the natural workflow. That's the design principle Controlbook is built around: the replacement update and the specification update are the same action.

See it running on your own property's data.

Give us 30 minutes. We'll report a real fault, identify the item, check availability and draft the supplier email, live, on a sample of your own data.