The Contract Type Is a Risk Decision, Not a Paperwork Detail

Before a hotel developer signs anything, the contract structure has already made a decision about who absorbs risk when conditions change. Steel prices move. Labor availability tightens. A subcontractor underperforms. Someone pays for that gap between plan and reality, and the contract determines who. A GMP contract in hotel construction is one answer to that question. It is not a formality to get to closing faster. It is a risk allocation instrument, and for a developer whose return depends on a pro forma built months earlier, that allocation matters as much as the interest rate on the construction loan.

Too many capital stack conversations treat contract type as a legal detail to be finalized after the deal terms are set. In practice, the contract structure is part of the deal terms. It determines whether a cost overrun becomes a change order the lender questions or a number the general contractor has to absorb.

What a GMP Actually Is, and What It Is Not

A guaranteed maximum price contract sets a ceiling on what the developer will pay for the defined scope of work. The general contractor is paid for actual costs plus a fee, up to that ceiling. If costs run below the GMP, the savings are typically shared or returned to the owner depending on how the contract is written. If costs exceed the GMP, the contractor absorbs the difference, not the developer.

What a GMP is not is a guarantee against every possible cost. It caps the contractor’s exposure for the scope that has been defined and priced. It does not protect against:

  • Owner-directed scope changes made after the GMP is set
  • Design that was incomplete at the time of pricing, which resurfaces as a change order
  • Allowances that were estimated low and get trued up later
  • Unforeseen site conditions excluded from the contract’s scope definition

This is where the outline of a GMP gets confused with the substance. A GMP is only as reliable as the completeness of the drawings and specifications it was priced against. That is why budget overruns start in design, not on the job site. A GMP set against a 60 percent design set is a number with a lot of room to move once the remaining 40 percent gets resolved.

Where the Risk Actually Shifts

The value of a GMP is not that costs cannot rise. It is that the developer’s downside is capped at a known number, which is what a pro forma actually requires. An IRR model built on assumptions needs those assumptions to hold within a defined range. A GMP gives the capital stack a ceiling to underwrite against, rather than an open-ended cost-plus arrangement where the final number is unknown until the project is substantially complete.

The risk that shifts to the contractor under a GMP includes:

  • Cost escalation on materials and labor within the defined scope
  • Subcontractor performance and the cost of remediating deficient work
  • Productivity risk, meaning the contractor bears the cost if the work takes longer than estimated for reasons within their control

What does not shift is schedule risk tied to owner decisions, permitting delays, or design changes requested after the fact. Those still land on the developer’s timeline, and schedule drift has its own cost to IRR separate from the hard construction number. A GMP protects the budget line. It does not by itself protect the calendar, which is why early GC involvement matters for protecting the capital stack before the GMP is ever finalized. The earlier the contractor is engaged in constructability review and scope definition, the fewer gaps show up later as change orders that erode the ceiling’s usefulness.

GMP vs Cost-Plus vs Lump Sum

Developers weighing contract structure are usually choosing among three models, and each allocates risk differently.

  • Cost-plus puts nearly all cost risk on the developer. The contractor is paid for actual costs plus a fee with no ceiling. This can make sense on highly uncertain scope, but it leaves the pro forma exposed to an open-ended number, which is a difficult position for a lender or equity partner to underwrite.
  • Lump sum shifts the most risk to the contractor, who prices the entire job for a fixed number regardless of actual cost. The tradeoff is that contractors price in a larger contingency to cover that risk, and a low lump sum bid is often a sign the contractor is planning to recover margin through change orders later. This is the dynamic behind why the lowest bid is often a risk signal rather than a value signal.
  • GMP sits between the two. The developer gets a ceiling and visibility into actual costs through open book accounting, while the contractor retains an incentive to manage costs efficiently because savings below the GMP are typically shared.

For a mid-market hotel developer managing a capital stack with defined equity and debt tranches, the GMP structure tends to align incentives better than either extreme. It gives the lender a number to underwrite, gives the developer a downside cap, and gives the contractor a reason to control costs rather than pad them.

The Contract Is Part of the Underwriting

None of this works if the GMP is set against incomplete design or a scope that has not been stress tested for constructability. A guaranteed maximum price is only a meaningful protection when it reflects a defined, coordinated scope of work, not a placeholder number attached to conceptual drawings. Developers who treat the GMP negotiation as a late-stage exercise often find the ceiling erodes within the first few months of construction through legitimate change orders tied to design gaps.

The right time to evaluate contract structure, contingency assumptions, and scope completeness is before the capital stack is finalized, not after. A pro forma and feasibility review at this stage gives developers a clearer picture of what a GMP can actually guarantee for their specific project, and where the real exposure still sits.