Commercial lease abstraction and review, amendment reconciliation, purchase and sale agreement review, title and survey objections, diligence and closing checklists, estoppel and SNDA review, and zoning issue-spotting.
9 skills in this practice area. Every skill produces draft legal work product for review by a licensed attorney.
Use when building a closing checklist of deliverables for a real estate transaction, tracking responsible party, status, and dependencies.
When to use
A user asks to "build a closing checklist," "track closing deliverables," or "set up a closing tracker" for a real estate deal.
A transaction team needs a structured reference for managing the documents and items required to close a purchase, sale, or financing.
A closing is approaching and the parties need to see who owes what, in what status, and what depends on what.
A deliverables tracker is needed as an input to closing coordination after a purchase and sale agreement or loan agreement has been negotiated.
Required inputs
The transaction type — for example a purchase, a sale, a refinancing, an acquisition financing, or a combined purchase and loan closing.
The party role the tracker is prepared for — buyer, seller, lender, borrower, escrow, or title company.
The parties involved — buyer, seller, lender, escrow agent, and title company, with names where known.
The transaction agreement — the purchase and sale agreement or loan agreement — uploaded or pasted, if available. If it is not provided, the tracker can still be built as a general scaffold, but it will not be derived from the actual agreement.
If the transaction type, the party role, and the parties are not provided, stop and request them. Do not build a tracker without knowing the deal it covers.
Use when reviewing a commercial lease from a specified party's perspective to spot business and legal issues and produce a risk matrix for attorney review.
When to use
A user asks to "review this lease," "flag the issues in this lease," "what should we push back on," or "what are the risks in this lease for us."
A landlord, tenant, guarantor, lender, buyer, seller, or asset manager needs a first-pass issue-spotting review before negotiation, execution, or reliance.
A lease is being negotiated and the user wants a structured starting point for redlining or a counterparty discussion.
A lease must be assessed as part of acquisition, financing, or asset-management diligence and the user needs a perspective-specific risk view.
An in-house team or business owner needs a risk summary before escalating to outside counsel.
Required inputs
The full lease, and any amendments — uploaded or pasted. Do not review from a description, a partial excerpt, or a prior summary.
The party perspective the review is performed for — landlord, tenant, guarantor, lender, buyer, seller, or asset manager. The whole review is from this party's point of view.
The property type — for example office, retail, industrial, warehouse, ground lease, or mixed-use.
The transaction posture — for example a new lease being negotiated, a renewal, an amendment, a lease being assumed in an acquisition, or a lease being reviewed for a loan.
The jurisdiction governing the lease, or an explicit statement that it is unknown.
The document set — any amendments, side letters, exhibits, guaranties, or related agreements. If the lease references documents that were not provided, note them as missing.
If the full lease text or the party perspective is not provided, stop and request it. Do not begin issue-spotting by guessing at facts.
Use when reviewing tenant or landlord estoppel certificates, SNDAs, and recognition agreements, and comparing them against the lease where provided.
When to use
A user asks to "review this estoppel," "check this tenant estoppel against the lease," "review this SNDA," or "is this estoppel safe to sign."
A lender or its counsel needs an estoppel and SNDA reviewed as part of acquisition or refinancing diligence.
A tenant has received an estoppel certificate or an SNDA to sign and needs a first-pass review before responding.
A landlord needs to confirm that an estoppel a tenant has returned, or one the landlord must deliver, is accurate.
An estoppel or SNDA must be reconciled against the lease before it is certified or recorded.
Required inputs
The estoppel certificate, SNDA, or recognition agreement — uploaded or pasted in full. Do not review from a description, a partial excerpt, or a prior summary.
The review perspective — lender, tenant, or landlord. The issues that matter differ by perspective, so this must be stated.
The underlying lease and its amendments — optional but strongly preferred. The lease-versus-estoppel comparison can only be performed if the lease is provided. If the estoppel or SNDA references amendments, side letters, or other documents, note which were and were not provided.
If the document text or the review perspective is not provided, stop and request it. Do not begin the review by guessing at the perspective or the document.
Use when reconciling a base lease against its amendments, side letters, assignments, and related documents to determine the current controlling terms.
When to use
A user asks to "reconcile this lease and its amendments," "figure out the current terms," or "tell me what the lease says now after all the changes."
A lease has one or more amendments, side letters, or assignments and a team needs the controlling terms identified as part of diligence.
A reconciliation is needed before drafting or reviewing an estoppel, an SNDA, a renewal, or a further amendment.
An asset-management or transaction team needs a current-terms reference for a lease with a long amendment history.
Required inputs
The base lease — uploaded or pasted. Do not reconcile from a description, a partial excerpt, or a prior summary.
All amendments, side letters, assignments, guaranties, and estoppels — the full document set, uploaded or pasted. If any document is referenced but not provided, it must be noted as missing.
The party role the reconciliation is prepared for — landlord, tenant, guarantor, lender, buyer, or asset manager.
The complete document inventory — confirm with the user the full list of documents that exist, so that referenced-but-not-provided documents can be distinguished from documents that do not exist.
If the base lease or any provided amendment text is missing, stop and request it. Do not reconcile a document set you have not been given.
Use when reviewing a real estate purchase and sale agreement from a specified party's perspective to spot issues and produce a risk matrix for attorney review.
When to use
A user asks to "review this PSA," "review this purchase agreement," "flag the risks in this real estate contract," or "what should I push back on" in a property purchase or sale.
A buyer, seller, or lender needs a first-pass issue-spotting review of a PSA before negotiation, signing, or closing.
The user is preparing to redline a PSA and needs a structured, prioritized starting point.
A PSA is being amended or assigned and the user wants to understand baseline risk exposure from one party's perspective.
Required inputs
The full purchase and sale agreement — uploaded or pasted. Do not review from a description, a partial excerpt, or a prior summary.
The review perspective — which party the review is for: buyer, seller, or lender. The same agreement reads differently from each, so the perspective must be stated before substantive work begins.
The property type — for example raw land, single-tenant retail, office, industrial, multifamily, condominium, or a portfolio.
The transaction posture — for example an arm's-length sale, a distressed or short sale, a 1031 exchange leg, an entity or membership-interest deal, a sale-leaseback, or an assignment of contract — and the stage the deal is at.
The jurisdiction — the state (and, where relevant, the county or municipality) where the property sits. Record it; do not assume a default.
The document set — every amendment, addendum, exhibit, side letter, escrow instruction, and title commitment that exists. If the PSA references documents that were not provided, note them as missing.
If the full PSA text or the review perspective is not provided, stop and request it. Do not begin the review by guessing at facts.
Use when generating a tailored real estate due-diligence checklist based on the transaction type, property type, jurisdiction, party role, and document set.
When to use
A user asks to "build a diligence checklist," "put together a due-diligence list," or "tell me what to review for this deal."
A transaction team is opening the diligence period on an acquisition, disposition, financing, or leasing transaction and needs an organized scope.
A checklist is needed to track what has been received and what is still outstanding from a counterparty.
A diligence scope must be tailored to a specific property type and party role before substantive review begins.
Required inputs
The transaction type — for example acquisition, disposition, refinancing, ground lease, joint venture, or development.
The property type — for example office, retail, industrial, multifamily, hospitality, raw land, or mixed-use.
The jurisdiction — the state and locality where the property is located, because diligence categories that depend on local requirements are flagged for local-counsel confirmation rather than guessed.
The party role the checklist is prepared for — buyer, seller, borrower, lender, landlord, tenant, or investor.
The document set so far — the documents already provided, and what the user knows is still outstanding.
If the transaction type, the property type, the jurisdiction, or the party role is missing, stop and request it. Do not build a diligence checklist from an incomplete set of these gating inputs.
Use when organizing title commitment exceptions and survey matters into a tracked, source-cited objection list for attorney review.
When to use
A user asks to "track the title objections," "organize the Schedule B exceptions," or "build an objection list from this title commitment and survey."
A transaction team needs a structured reference for the exceptions and survey matters on a parcel under contract or under review.
Title and survey items must be organized as part of acquisition, financing, or development diligence.
An objection tracker is needed as an input to a purchase and sale agreement review or a closing deliverables checklist.
Required inputs
The title commitment or title report — uploaded or pasted, including Schedule A, Schedule B-I (requirements), and Schedule B-II (exceptions). Do not work from a description, a partial excerpt, or a prior summary.
The underlying exception documents — recorded easements, covenants, liens, plats, and similar — if available. Note which were and were not provided.
The survey — if available — including the surveyor's notes and table of matters.
The party role the tracker is prepared for — buyer, seller, borrower, lender, or developer.
The parcel(s) at issue — the legal description, tax parcel number, or street address each item relates to.
If the title commitment or report is not provided, stop and request it. Do not build a tracker from a document you have not been given.
Use when issue-spotting zoning, permitted-use, recorded-restriction, and use-clause concerns from provided materials and producing questions for local counsel.
When to use
A user asks to "spot the zoning issues," "flag use-restriction concerns," or "tell me what to ask local counsel about" for a property.
A transaction or leasing team needs an early read on whether an intended use raises zoning, covenant, or use-clause questions.
Provided diligence materials — zoning reports, CC&Rs, recorded restrictions, a lease use clause, permits, or certificates — need to be screened for concerns before counsel is engaged.
An issue-spotting list is needed as an input to a broader diligence review.
Required inputs
The intended use and operations — what the property will be used for, in enough detail to issue-spot (for example use category, hours, parking demand, signage, outdoor activity, occupancy).
The jurisdiction — the municipality or county whose zoning would govern. Do not assume one.
The property type — for example office, retail, industrial, warehouse, multifamily, or mixed-use.
The provided materials — the zoning materials, recorded restrictions, CC&Rs, lease use clause, permits, and certificates the user has. If a material is referenced but not provided, note it as missing.
If the intended use, the jurisdiction, the property type, or the materials to review are not provided, stop and request them. Do not issue-spot from a description alone, and do not proceed without knowing the jurisdiction.