Extracting Rent Escalation Schedules From a Lease

A rent escalation clause is a program. It takes a base rent and a commencement date and produces a payment schedule, and the useful extraction is that schedule — not the sentence. Two lawful readings of the same clause can differ by thousands of dollars by year five.

Four escalation shapes in one clause

Commercial leases mix mechanisms, often within a single paragraph, and each has a different field set:

• Stepped flat amounts. A table of annual or monthly rents by lease year. No arithmetic needed, but the table is usually in an exhibit rather than the clause.
• Fixed percentage. “Base Rent shall increase by three percent (3%) on each anniversary of the Commencement Date.” Needs a compounding basis.
• Index-linked. Tied to a published price index, with a base period, a comparison period and usually a floor and a cap.
• Hybrid. “The greater of three percent (3%) or the increase in the Index, not to exceed six percent (6%)”. This is a formula with two operands and a bound, and it is the shape most likely to be flattened into “3%” by a careless extraction.

Store escalation_type from a closed set, plus a formula object whose shape depends on the type, plus the section reference. The schedule is derived and recomputed, never taken from the model — the same rule that applies to renewal deadlines applies here, because a model asked for both a rule and its consequences will sometimes give you inconsistent versions of each.

Compounding is a field, not an assumption

“Three percent per annum” does not say what the three percent applies to. Compounded, each year’s increase applies to the previous year’s rent; simple, it applies to the original base every year. Take 12,000 rentable square feet at $30.00 per square foot per year:

Base annual rent  12,000 x 30.00 = 360,000.00
Escalation        3% on each anniversary

Lease year   Compounded      Simple (3% of original base)
  1          360,000.00      360,000.00
  2          370,800.00      370,800.00
  3          381,924.00      381,600.00
  4          393,381.72      392,400.00
  5          405,183.17      403,200.00

Divergence by year 5:  405,183.17 - 403,200.00 = 1,983.17

Under two thousand dollars in year five on a single suite, which sounds small until it is a portfolio of two hundred leases and the difference compounds through a ten-year term and into a renewal option whose rent is expressed as a percentage of the then-current rent. The two readings also diverge at an accelerating rate, so a five-year table understates the exposure of a fifteen-year lease.

Where the clause is genuinely silent, store compounding: "unspecified" and compute both. Storing a default and forgetting is how a whole portfolio ends up modelled one way because that was what the prompt happened to say.

The anniversary is not 1 January

Escalations run on lease-year anniversaries, and lease years start on the Commencement Date. Accounting systems run on calendar years or fiscal years. So a lease commencing 1 March 2024 produces a calendar 2025 that contains two months at the year-one rate and ten at the year-two rate:

Commencement          2024-03-01
Monthly year 1        360,000 / 12 = 30,000.00
Monthly year 2        370,800 / 12 = 30,900.00

Calendar 2025 = (2 x 30,000.00) + (10 x 30,900.00)
              = 60,000.00 + 309,000.00
              = 369,000.00

$369,000 is neither the year-one figure nor the year-two figure, and reconciling it against either will look like an error. If the extraction output feeds a forecast, it must emit a monthly series rather than an annual one, because only the monthly series survives the change of calendar.

Two more things move the anniversary. A free-rent or abatement period — “months 1 through 3 shall be abated” — is a separate field and does not usually shift the escalation clock. But where the lease distinguishes the Commencement Date from the Rent Commencement Date and anchors escalations to the latter, every anniversary moves by the length of the abatement. Extract both dates and an explicit escalation_anchor naming which one governs.

A CPI clause needs five more fields

An index-linked escalation is not extractable as “CPI”. There are many index series, and a clause that does not pin one down is itself a finding. The fields that make the clause computable:

• The series. In the United States this is usually the Consumer Price Index for All Urban Consumers, published by the U.S. Bureau of Labor Statistics, which also publishes a separate index for urban wage earners and clerical workers. They are different numbers. BLS documents the series and their publication schedule.
• The geography. National, or a specific metropolitan area. Local series are published for some areas at lower frequency than the national one, which matters if the clause names a monthly comparison against an index published bimonthly.
• The base and comparison months. “The Index for the month three months prior to the adjustment date compared with the Index for the same month in the preceding year” is a rule, and the three-month offset exists because index values are published after the month they describe.
• Floor and cap. “Not less than two percent (2%) nor more than five percent (5%)” means a 6.2% index move produces a 5% rent increase and a flat index still produces 2%. The collar, not the index, determines the rent in most years.
• The base period of the series itself. Index levels are only comparable within a series with the same reference base, and a rebasing between the base month and the comparison month has to be handled by the party doing the arithmetic.

When the exhibit disagrees with the prose

Most leases with percentage escalations also contain a rent schedule exhibit, and the two are produced by different people. When they disagree — a rounding difference, a missing abatement, a step applied a year early — the extraction has found something real and should surface both.

A reconciliation check is easy to run and catches this without any reference data: compute the schedule from the prose clause, compare it cell by cell to the extracted exhibit table — getting that table out cleanly is its own problem, covered in extracting a table with merged cells — and report the first year where they differ by more than a rounding tolerance. Expressed as a cross-field amount validation rule, it runs on every lease rather than on the ones somebody opens. Common causes, in rough order of frequency: the exhibit rounds monthly rent to the nearest dollar while the prose compounds exactly; the exhibit reflects an abatement the prose does not mention; the exhibit is expressed monthly and the prose annually and one of them was misread by a factor of twelve; and the exhibit was carried over from an earlier draft with a different base rent.

The factor-of-twelve error is worth a dedicated assertion. Any extracted rent figure that is within a few percent of twelve times or one twelfth of another figure on the same lease is almost certainly a unit confusion, and it is the single most common numeric error on lease extraction. Storing an explicit period on every money field — monthly, annual, per square foot per year — makes the check trivial and makes the value unambiguous to whatever reads it next. That, plus the decimal-separator and parenthesised-negative questions every money field has, is a currency amount validation rule.