What happens to hotel FF&E data after the designer leaves
The design firm hands over a document. Nobody updates it. The data degrades. Here's why this happens structurally — and what the alternative looks like.

The interior design firm finishes its work. The project is complete. The hotel opens. And on handover day, the design firm delivers the O&M manual — a document pack that can run to hundreds of pages, containing the specification for every piece of FF&E in the building.
Then the designer leaves. And that's roughly where the data starts dying.
What's in the handover document
A typical O&M pack contains per-room-type Control Books — documents that record the specification for each furniture piece in a given room category, including the manufacturer, model, finish, fabric, fire rating and supplier. Alongside these sit the FF&E Matrix (a room-by-room breakdown of what's in each space), the Type Schedule (a summary of room types and their contents), and a Drawing Register that maps everything to the project drawings.
It is, when it's well assembled, a comprehensive record of every asset in the building at the moment of opening. The problem is what happens to it from that moment onwards.
Why the data degrades immediately
Three forces start working against the handover document from day one.
It's static. The O&M manual records the building as it was at handover. The moment a lamp is replaced, a chair is reupholstered, a piece of bedding is swapped — the manual is already wrong. There's no mechanism to update it. The hotel that opened with a pristine specification record is running, within months, on a document that no longer accurately reflects reality.
It's not searchable. A 400-page PDF, or a shared folder of twenty PDFs, cannot answer the question "what is the bedside lamp in room 214 and who made it?" in the moment it needs to be answered. Finding a specific item means knowing roughly where it is in the document, scrolling to find it, and hoping it's not buried in a Control Book that's filed in a slightly unexpected place.
Nobody updates it because nobody owns it. This is the structural problem. The design firm's job ended at handover. The procurement company's job ended at delivery. The manufacturer's obligation ended at sale. The hotel brand, if there is one, doesn't own the individual property's assets. The GM received the document, but wasn't involved in creating it, may not know how it's structured, and will likely rotate on before the first major replacement cycle anyway. Hospitality experiences some of the highest staff turnover of any sector — around 70–80% annually by some measures. The person who received the manual is often gone by the time the first item fails.
Three actors who could own the data, and why none of them do
It's worth being specific about why each of the obvious candidates doesn't end up maintaining the record.
The design firm could maintain it, but their commercial relationship ends at project close. There's no contractual incentive to keep updating a document for a client who is no longer paying them. Some firms offer post-opening services, but it's not the norm and it's not free.
The procurement company handles the purchasing and coordinates delivery, but they're not involved in the operational life of the hotel. They don't know which items fail first, which suppliers have been replaced, or what alternatives the hotel has accepted over time.
The hotel's own team is the most natural owner, but they inherit a document they didn't create, in a format they can't easily update. Adding a note to a PDF every time a replacement is made is not a realistic operational expectation, especially across a team with high turnover.
The result is a coordination failure: everyone has a rational reason not to maintain the data, so nobody does.
What happens when the data degrades
For the first year or two, things are manageable. The original specification is still mostly accurate, items are mostly still available, and at least some of the original project team is still around to answer questions. The cracks appear gradually.
By year three or four, a meaningful proportion of the specified items have been discontinued. Several replacements have been made without updating the documentation. The team handling maintenance has changed at least once. The O&M manual now describes a hotel that no longer quite exists.
By year six or seven — the typical window for a soft-goods refresh cycle, as noted in hotel management literature on PIP planning — the specification is sufficiently outdated that any major refurbishment effectively has to start over from scratch, because nobody can be confident what's actually in the rooms at that point.
What the alternative looks like
A live asset record isn't a better version of the PDF. It's a different thing entirely.
Instead of a document that records the building at a point in time, a live record is a queryable database that follows the building over time. When a lamp is replaced, the record updates. When a fabric is discontinued, the record flags it. When a supplier changes, the record reflects the new contact. The specification reflects the building as it is, not as it was on opening day.
This requires that the data is captured correctly at source — which means the design firm needs to build the specification in a system, not in a Word document or spreadsheet — and that there's a workflow for updating the record when changes are made operationally.
That's the lifecycle loop: the design firm builds the specification on a platform, and the hotel inherits a live database rather than a dead PDF. The designer's output doesn't die at handover. It carries through into operations and keeps being updated as the building evolves.
If you're running a property with an O&M manual you haven't touched since opening, the guide on why O&M manuals fail is a good companion to this piece. And if you want to see what a live asset record looks like for your property, book a demo.
Frequently asked questions
Can we digitise an existing O&M manual after the fact?
Yes, though the effort involved depends on the format of the original documentation. Scanned or image-only PDFs require more work than those with programmatic text. And regardless of the format, digitisation captures the building as it was at the time of the original document — which means the first priority after digitisation is identifying what's changed since then. That reconciliation is real work, but it's the work that makes the resulting record useful.
What format should a hotel demand at handover?
In an ideal world, structured data rather than PDFs — a spreadsheet or database format that can be imported into a live system, rather than a document designed to be printed. In practice, most design firms and procurement companies don't yet work that way, so the more realistic ask is for well-structured PDFs with programmatic (not scanned) text, so that the data can be extracted programmatically. The complete guide to hotel FF&E procurement covers what to ask for at handover in more detail.
How do we keep the record current after it's been digitised?
The workflow needs to be embedded in the maintenance process. When a replacement is made, whoever approves the replacement should also update the asset record — this becomes a one-step action rather than a separate administrative task if the replacement workflow runs through the same platform. That's exactly how Controlbook approaches it: the replacement order and the specification update are the same action.