Skip to main content

GUIDE / 4 MIN READ

Tenant estoppel certificates: compare every response with the lease file

By Alex Cinovoj, Founder & CTO, TechTide AI · CTO & Co-Founder, CPG Playbook

Published · September 2026 editorial collection

When a commercial property is sold or refinanced, the buyer or lender usually wants to hear from the tenants directly. Each tenant is asked to sign an estoppel certificate confirming the key terms of its lease: rent, term, deposits, options and whether any defaults or claims exist. For a property with many tenants, preparing those requests and checking the signed responses is a large document review under a deadline.

The checking step is where careful automation can help. Comparing each returned certificate with the lease file and the rent ledger is repetitive and detail-heavy. Deciding what a discrepancy means, and whether to accept, dispute or correct a certificate, is work for the property team and counsel.

This is a proposed workflow, not legal advice. The effect of an estoppel certificate depends on the lease, the jurisdiction and the transaction documents, and counsel should define how discrepancies are handled.

Know why the details matter

The House of Representatives' leasing guidance describes an estoppel certificate as establishing the current status of the lease terms for a third party, typically used when a landlord is selling the building or refinancing, and generally asking the tenant to confirm that rent is current or whether it has claims against the landlord.

Courts can hold parties to what they certify. In Plaza Freeway Ltd. Partnership v. First Mountain Bank, a California appellate court held that a tenant who signed and delivered an estoppel certificate required by its lease was bound by the termination date it had certified, and that its later attempt to exercise a renewal option was therefore untimely. That case turned on California law and its facts, but it illustrates why a certificate that differs from the lease file should not pass unnoticed.

Build the comparison baseline first

Before certificates go out, the workflow should assemble a baseline for each tenant from the lease, every amendment, the current rent roll and the ledger. Commencement and expiration dates, current base rent, security deposit, renewal and termination options, and any recorded defaults or disputes are typical fields.

Each baseline value should link to its source document and clause. Where the lease file is incomplete or the documents conflict, the baseline should show that conflict rather than pick one value. A missing amendment discovered now is much better than one discovered after closing.

Prepare requests from the baseline

If the property team sends certificates on its own form or the lender's form, the workflow can pre-fill the form from the confirmed baseline for a person to review. Pre-filled values that a person has not checked should not go to tenants, because the landlord is effectively asking the tenant to confirm them.

Track each request: when it was sent, to whom, the response deadline in the lease or transaction documents, and reminders sent. The lease may specify how notices must be delivered, and the request process should follow it.

Compare returned certificates field by field

When a signed certificate comes back, the workflow can extract the certified values and compare each one with the baseline. Matches are shown as matches. Differences are listed with both values and their sources: what the tenant certified, and what the lease file says.

Some differences are clerical, such as a rent figure that does not reflect a scheduled increase. Others matter a great deal, such as a tenant certifying an option the landlord does not believe exists, or noting a claim against the landlord. The workflow should not rank these by legal significance. It should present them clearly so the people who understand the deal can.

Watch for added or deleted language. Tenants sometimes edit the form, strike sentences or add qualifications. The comparison should check the returned text against the form that was sent, not only the blanks.

Route discrepancies to the right people

Each discrepancy goes to the property manager or asset manager responsible for that tenant, with counsel involved according to the transaction team's rules. They decide whether to accept the certificate, ask the tenant to correct it, correct the landlord's records, or disclose the issue to the buyer or lender.

Record each decision and its reason. The record of what was found and how it was resolved may matter later, and it should not live only in an email thread.

Keep the files contained

Leases, ledgers and certificates contain commercially sensitive terms. The workflow should run inside the property team's approved document environment, with access limited to people working on the transaction. If a model service extracts values from certificates, confirm the data terms before sending tenant documents to it.

Measure against a manual review

On a pilot transaction or a past one, run the comparison alongside the team's manual review. Track discrepancies the workflow found that the team also found, ones it missed, and false differences the team dismissed. A comparison that floods reviewers with false differences will be ignored.

The acceptance condition I would agree: every baseline value links to its source, every returned certificate is compared field by field and against the sent form, and no certificate is marked accepted without a named person's decision.

Bring a redacted lease, a blank certificate form and a sample returned certificate.

About the author

Alex Cinovoj

AI & Infra Engineer. Building AI that survives outside the demo.

Founder & CTO, TechTide AI · CTO & Co-Founder, CPG Playbook

I spent 13 years in US enterprise IT, the last 2 focused entirely on AI implementation. I run TechTide AI, an implementation studio that takes stalled AI pilots into production. I write about the work in progress at alexcinovoj.com and on Substack.

Logs over vibes. Production over theater.

Related field notes

All field notes

Have a stalled build that needs to work?