Lease Administration interview questions

What a strong answer covers

• Start by assembling the full document set: the executed lease, every amendment, any letter agreement, commencement date certificate, and guaranty, because later documents override earlier ones.
• Capture the identifying facts first: legal parties, premises description and rentable area, commencement, rent commencement and expiration dates, and the measurement standard if one is named.
• Then the money: base rent schedule with each step, escalation mechanics, operating expense or CAM structure, base year or expense stop, percentage rent if retail, security deposit and any letter of credit.
• Then the rights and obligations: renewal, termination, expansion and right of first refusal options with their notice windows, assignment and sublet, maintenance and repair split, insurance requirements, and holdover terms.
• Record a clause reference against every field, flag anything ambiguous for legal rather than interpreting it, and have the abstract reviewed before it feeds billing.

Where people lose the point

• ×Abstracting from the original lease when amendments have changed the term, rent or premises.
• ×Recording conclusions without clause references, which makes the abstract unauditable.
• ×Interpreting ambiguous language yourself instead of routing it to counsel.

What a strong answer covers

• Every date-bearing right or obligation goes into the lease administration system at abstraction time, not later: options, notice windows, insurance certificate renewals, escalation effective dates and expiries.
• The tracked deadline is the notice window, calculated backwards from the option date, with internal reminders early enough that the business can actually decide.
• Reminders need a named owner rather than a distribution list, and an escalation path if the first reminder is not acknowledged.
• Reconcile the date register periodically against the documents themselves, because dates entered once and never verified drift as amendments arrive.
• A strong answer mentions closing the loop: once notice is served, record the delivery method, date and proof, and update the term in the system.

Where people lose the point

• ×Tracking the option expiry date and missing the notice period in front of it.
• ×Relying on one person's calendar rather than a system with an escalation path.
• ×Never auditing the date register against the source documents after initial load.

What a strong answer covers

• For a fixed escalation, build the full rent schedule for the term at abstraction and check whether the increase compounds on the prior year's rent or applies to the original base, because the lease language decides that and the two diverge over a long term.
• Confirm the anniversary the increase runs from: lease commencement, rent commencement, or a stated calendar date, since these are often different.
• For an index-linked escalation, identify the exact index and series named in the lease, the base period, the comparison period, the publication lag, and any floor or ceiling on the annual movement.
• Index revisions and rebasing need handling per the lease's own language, and where the lease is silent it is a question for legal rather than an assumption.
• A strong answer notes that both types should be recalculated independently rather than rolled forward from last year's billing, so an early error does not persist for the whole term.

Where people lose the point

• ×Assuming an escalation compounds when the lease applies it to the original base, or the reverse.
• ×Using a general inflation figure instead of the specific index and series the lease names.
• ×Carrying forward a prior year's calculation without re-deriving it from the lease.

What a strong answer covers

• Start from the lease, not the statement: pull the inclusion and exclusion language, the pro rata share definition, the cap and how it is measured, any base year or expense stop, gross-up provisions and the audit right with its deadline.
• Check the share calculation: the numerator is the premises area per the lease and the denominator is whatever the lease defines, which may or may not be total building area and may change if the property was expanded.
• Test the expense pool for items the lease excludes, common examples being capital improvements that should be amortised, landlord's own overhead, leasing commissions, and costs recoverable from insurance or other tenants.
• Verify the estimate to actual comparison arithmetic and confirm the billed estimates in the statement match what was actually invoiced and paid.
• Raise findings in writing with clause citations and figures, note the audit deadline so the tenant's rights are preserved, and document the landlord's response.

Where people lose the point

• ×Reviewing the statement on its own terms without reading the lease's definitions.
• ×Missing the audit or objection deadline, which can waive the tenant's right to challenge.
• ×Challenging totals without identifying the specific line items and the clause that excludes them.

What a strong answer covers

• Go back to source first and confirm what the document set actually says, including any amendment or commencement date certificate that may fix the dates, before changing anything.
• Do not silently edit the record. Identify what the wrong date has already caused downstream: billing, accounting treatment, critical date reminders, portfolio reporting, and any decision taken on the basis of the wrong expiry.
• Escalate with evidence attached, typically to the lease administration lead plus legal and finance, so the correction and any restatement is a decision made by the people accountable for it.
• Correct the record with a documented change note that says what changed, on the authority of which document and clause, who approved it, and when.
• A strong answer then asks why the error happened, whether other leases loaded in the same batch or by the same process carry it, and what check would catch it next time.

Where people lose the point

• ×Fixing the field quietly and moving on, leaving no audit trail and no downstream correction.
• ×Assuming the system is right because it has been used for years.
• ×Treating it as an isolated typo without checking for a systemic cause.

What a strong answer covers

• An estoppel certificate is a tenant's written confirmation of the current facts of its tenancy: that the lease is in effect, the rent and dates, deposits held, any amendments, and whether either party is in default. It is usually requested when the property is being sold or financed.
• Its effect is that the tenant is generally prevented from later asserting facts contrary to what it certified, which is why every statement is checked against the lease file before signing rather than confirmed from memory.
• An SNDA is a three party agreement between tenant, landlord and lender covering subordination (the lease sits behind the lender's security), non-disturbance (the tenant keeps possession if the lender forecloses, provided it is not in default), and attornment (the tenant recognises the successor as landlord).
• The practical distinction is that an estoppel confirms today's facts, while an SNDA governs what happens to the lease in a future foreclosure or transfer.
• A strong answer notes that lease administration's role is to assemble accurate facts and flag anything inconsistent with the lease file, with legal reviewing the language and signing authority sitting where the company's policy places it.

Where people lose the point

• ×Describing an estoppel as a legal opinion rather than a factual confirmation.
• ×Signing an estoppel from memory or from the abstract instead of verifying against the executed documents.
• ×Confusing subordination with non-disturbance, when the second is the protection the tenant actually wants.

What a strong answer covers

• Establish from the lease what counts as gross sales, what is excluded (common examples include returns, some taxes and certain inter-store transfers), and the reporting period and deadline for tenant sales reports.
• Identify the structure: whether there is a natural or stated breakpoint, whether percentage rent is calculated monthly or annually with a true-up, and whether base rent offsets against it.
• Reconcile reported sales against what was billed, chase missing or late reports because the obligation to report is itself a lease term, and apply the calculation exactly as the clause specifies.
• Where the lease gives an audit right over tenant sales records, know the notice requirements and the deadline attached to it.
• A strong answer notes that definitions of gross sales vary considerably between leases and markets, so the calculation is only as good as reading that specific clause.

Where people lose the point

• ×Applying a standard breakpoint formula when the lease states a fixed breakpoint instead.
• ×Using the tenant's own reported net sales figure without checking the lease's definition.
• ×Letting late sales reports slide, which erodes the ability to bill and to audit.

What a strong answer covers

• Acknowledge quickly, get the dispute in writing with the specific line items and amounts, and confirm what is being withheld versus what is being paid.
• Re-derive the charge from the lease independently rather than defending the invoice, including the clause, the calculation and the supporting expense detail.
• If the charge is wrong, say so plainly, issue the correction or credit, and check whether the same error affected other periods or other tenants under similar leases.
• If the charge is right, respond with the clause language and the workings rather than an assertion, and offer the supporting documentation the lease entitles them to.
• Escalate to asset management and legal where the amount or the relationship warrants it, keep every exchange documented, and note any lease deadline that the dispute interacts with.

Where people lose the point

• ×Defending the bill before verifying it.
• ×Handling the dispute by phone with nothing written down.
• ×Fixing one tenant's charge without checking whether the error is systemic.

What a strong answer covers

• Confirm document completeness first: which leases have the full executed set with all amendments on file, because a record cannot be verified against a document you do not have.
• Prioritise by exposure rather than working alphabetically: highest rent, nearest critical dates, options with notice windows approaching, and anything feeding external reporting.
• Re-abstract the priority set from source, comparing field by field to what the system holds, and log every variance with its cause rather than just correcting it.
• Fix the intake process at the same time, so newly signed documents arrive with a defined handoff, an abstraction standard and a second-pair-of-eyes review before they go live.
• A strong answer sets a periodic re-verification cadence and reports data quality as a tracked measure rather than declaring the cleanup finished.

Where people lose the point

• ×Starting a full portfolio re-abstraction with no prioritisation and stalling part way.
• ×Correcting records without fixing the process that produced the errors.
• ×Treating data cleanup as a one-off project rather than an ongoing control.