Hotel Architect Contracts: What to Lock Down on Scope and Budget Before You Sign
A hotel architecture contract needs two things nailed down before work starts: an explicit scope of service (who specifies what, down to the line item) and a budget allocation that matches it. Without both, the architect ends up accountable for gaps nobody agreed they owned — most often in OS&E coverage and back-of-house design, the two areas contracts leave vaguest most often.
Where the holes in the racket actually are
Most hotel architecture contracts are precise about the guest-facing scope — lobby, guestrooms, restaurant — and vague about everything behind the swing door. Two gaps recur on almost every project: which OS&E items the architect's fee actually covers (as opposed to what the operator assumes is "included"), and who is responsible for designing back-of-house — the kitchen, laundry, staff areas, storage — a scope that gets forgotten until it's nearly too late.
That's exactly why Figurz builds scope of service limits into its FF&E and OS&E estimator — a responsibility matrix that closes these gaps before the contract is signed, not after. Start by testing the free version.
OS&E: know exactly what your fee covers
FF&E is almost always explicit in an architecture contract — furniture, fixtures, and the major design elements are the architect's core deliverable. OS&E is where the ambiguity lives. A contract that says "architect to specify FF&E" without addressing OS&E leaves open questions that surface months later: does the architect's scope include selecting tableware style guidelines? Linens? The aesthetic direction of housekeeping carts visible in guest corridors?
None of these are unreasonable to include — but if they're not written down, the operator will assume they're covered, and the architect will assume they're not. That gap becomes a change order, a delay, or an unpaid scope expansion, depending on who has the weaker negotiating position at the time.
Back-of-house: the gap almost nobody catches in time
Back-of-house is the classic hole in the racket. Guest-facing design gets the attention, the budget, and the contractual clarity — back-of-house gets whatever's left of everyone's time. The result: kitchens designed by the culinary consultant with no input from the architect on flow and adjacency, staff areas treated as leftover space rather than designed space, and storage that turns out to be undersized once the FF&E and OS&E inventory is actually counted.
The contract should specify, explicitly, who owns back-of-house design — the architect, a specialist kitchen consultant, the operator's own technical services team, or some split between them — and where the handoff points are. Leaving this to "we'll figure it out during design development" is how back-of-house becomes the area with the least design attention and the most operational complaints after opening.
What to secure before signing
A line-by-line scope of service, not a general description — which FF&E and OS&E categories the architect specifies, which the operator selects independently, and which are shared.
An explicit back-of-house assignment — who designs it, who reviews it against operational requirements, and at what stage of the project.
A budget allocation that matches the scope, agreed before design starts — not derived from what's left after guest-facing spaces are finalized.
A change-order trigger defined in advance for anything outside the agreed scope, so scope creep has a cost attached from day one rather than becoming a dispute later.
Why this protects the architect as much as the project
An architect without a clear scope of service isn't just exposed to unpaid work — they're exposed to blame for gaps that were never contractually theirs to close. A precise, budgeted scope is what turns "the architect should have caught that" into "that was explicitly outside scope, as agreed."
An architect working from a clear FF&E/OS&E envelope from the outset avoids most of these disputes before they start.
Run a free FF&E and OS&E estimate at figurz.eu — in under a minute, before your scope of service gets tested by a gap nobody assigned.
