What is a rent-escalation clause?

A rent-escalation clause is the contractual rule that updates rent over the term. It takes one of three common shapes — CPI-indexed, fixed-percent, or stepped — and each shape has its own failure modes a landlord, broker, or property manager wants on file before the next adjustment date. Holdmark extracts the clause from the uploaded lease PDF and binds every figure to its page and section, so the audit trail reads as a verification step, not a guess.

The mechanical rule that adjusts rent — distinct from base rent, CAM, or percentage rent.

A rent-escalation clause is not the base rent figure, not the CAM reconciliation, and not the percentage-rent trigger. It is the mechanical rule that moves the headline rent number forward over the term — most often annually, sometimes at preset milestones. Its outputs feed the next month's invoice; its inputs (index prints, anniversary dates, step tables) belong on the operator's calendar before the adjustment, not after.

The clause is also one of the easier places for a draftsperson to embed ambiguity — an unnamed index, a missing cap, a compounding basis that the parties meant one way and read another. Where the language reads ambiguously, a structured abstract surfaces the field as ambiguous rather than resolving it silently; the audit trail is the deliverable.

CPI-indexed, fixed-percent, and stepped — each with its own failure mode.

CPI-indexed

Periodic adjustment tied to a published index — usually CPI-U or a local CPI variant.

A CPI escalation names a published index, a measurement month, and an effective date. Most pairs add a cap (the maximum annual change the tenant pays regardless of the index print) and a floor (a minimum increase, even when the print is negative). The clause spells out which index and which month the index is read from.

Flag: A cap at 3% with the index printing at 7% does NOT mean the tenant pays 7% — the tenant pays the capped figure. Flag ambiguous cap language and confirm the floor exists or doesn't.

Fixed-percent

A stated percent per annum — simple or compounded, anniversary or calendar.

The fixed-percent shape names a single number (often 3%) and applies it yearly. The clause specifies whether the increase is compounded on the prior year's adjusted rent or applied to the original base, and whether the anniversary tracks lease commencement or a calendar year.

Flag: Confirm compounding basis (simple vs. compounded), the exact anniversary date, and whether the schedule survives a renewal option. A clause that says "3% per annum" without specifying compounding is one worth flagging.

Stepped schedules

Pre-agreed dollar amounts at preset lease years — Years 1–5 listed in a table.

The stepped shape skips the index entirely. Years 1 through 5 (and often 10) carry fixed dollar figures written into the lease. The clause ties each step to a named lease year, not a calendar date, so a commencement-month shift moves every subsequent step by the same offset.

Flag: Tie each step to the lease year exactly. Watch for base-year resets at renewal reopeners, mid-term expansion rent bumps, and parent / sublease carve-outs that replay the schedule.

Three checks worth running before the next adjustment date.

Index, cap, and floor.

Confirm the index is named (CPI-U, CPI-W, a local CPI variant), whether a cap and floor exist, and what the index measurement month is. A clause that names the index without a measurement month is ambiguous on the first adjustment — flag, don't guess.

Anniversary and measurement dates.

Confirm the effective date of each annual adjustment — whether the date is fixed or computed from the prior print, and how a shortened first or last lease year is handled. A 14-month stub period at the end of the term is exactly the kind of edge case an operator wants surfaced before renewal.

Renewal reopeners.

Confirm whether a renewal option reopens the escalator to market or extends the same schedule. Some clauses hand the renewal back to the cap/floor pair; others reset the base and resume the prior step table. The two paths produce materially different numbers at the same term length.

Each value is bound to the page and section reference in the source lease — auditors verify it in one click. The per-lease schedule lives in alert preferences; plans and integrations live on the pricing page.