# Lender information requests and version control

Canonical: https://commercialdebtadvisory.com/execution/lender-information-requests-and-version-control/
Status: Published
Publisher: Jaken Finance Group

A lender asks for an updated rent roll. The property manager supplies it, the broker forwards it, and a credit analyst continues working from last month’s version. No one intentionally concealed anything, yet the financing package now contains two different descriptions of the same property. Version control is a financial control because changed facts can alter loan proceeds, conditions and closing cash.

Create a request register that connects each question to the document used to answer it and to the model affected by the answer. The goal is a small, reliable record of decisions. It is not an enormous folder whose newest filename happens to contain the word “final.”

## Distinguish facts, interpretations and conditions

A rent roll is a dated representation of leases and occupancy. A lease abstract is an interpretation of documents. A lender’s approval condition is a requirement for this transaction. Keep these categories separate even when they relate to the same tenant.

For example, “tenant has renewed” could mean that a renewal option exists, a notice has been sent, negotiations are advanced, or a fully executed renewal has been received. Those states have different underwriting consequences. Record the actual state and the supporting document; do not use a convenient shorthand that changes its meaning as it travels through the team.

In a [publicly filed Block 40 loan agreement, section 3.1.10](https://www.sec.gov/Archives/edgar/data/1795851/000166357726000199/ex10_30.htm), the borrower makes specific representations concerning delivered financial information. That historical contract illustrates why precision matters. The representations in an investor’s own executed documents must be reviewed separately; this article does not import those clauses into other loans.

## Give every request an owner and a closure standard

Use an identifier such as R-014 and record the requesting lender, date, exact question, responsible owner, due date, supporting file, file version and response. Add a separate field for lender acceptance. “Sent” should never automatically become “cleared.”

| Request | Evidence supplied | Status | What closes the item |
|---|---|---|---|
| R-014: explain tax increase | Tax estimate v2 and current bill | Sent; lender review pending | Lender accepts expense or identifies its own adjustment |
| R-015: document renewal | Unsigned draft amendment | Open | Executed document and lender review of material terms |
| R-016: reconcile collections | September ledger and deposit bridge v1 | Accepted for September | Reopen if the lender requests a later period |

These are hypothetical workflow examples. A document can satisfy one request and still create another. The tax estimate may answer the question about future expense while producing a new equity shortfall that the sponsor must address.

## Worked change: a tax correction reduces proceeds

Assume the initial model used $84,000 of annual property tax and $420,000 of accepted annual cash flow. A supported revised estimate is $108,000, increasing expense by $24,000 and reducing modeled cash flow to $396,000. Hold all other assumptions constant.

At a 1.25× DSCR requirement, 7% interest and 25-year monthly amortization, the annual debt constant is approximately 8.48135%. The difference in the DSCR loan ceiling is:

**$24,000 ÷ 1.25 ÷ 8.48135% = approximately $226,379.**

That is the change in this particular ceiling. The final loan amount changes only if coverage is binding; a lower LTV limit might already govern both versions. The request register should therefore link to the complete sizing model and record its new binding constraint.

The change also affects interest expense, lender fees if charged on principal, equity required and possibly an existing seller financing agreement. A team that changes only the tax cell can leave its lender comparison and closing statement inconsistent.

## Keep a record of what each lender actually received

Create a dated package manifest listing the filenames and versions shared with each recipient. When a material fact changes, issue a short change notice identifying the old fact, new fact, source and affected exhibits. Retain the previous package for traceability; clearly label it superseded so it is not reused.

Do not silently replace a file behind a link and assume every lender reopened it. Equally, avoid flooding all recipients with every internal draft. Identify which package is current for underwriting and which documents remain provisional.

A practical naming convention includes property identifier, document type, period and revision: `Asset-A_T12_2026-09_v02`. Do not put Social Security numbers, bank account numbers or other sensitive identifiers in filenames. Access permissions should follow the document’s sensitivity and each recipient’s role.

## Use AI to organize evidence, then verify the result

An AI extraction can save time by locating dates or comparing versions. It can also omit an amendment, misread a negative amount or confidently invent a relationship between fields. [NIST’s discussion of confabulation](https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf) provides a reason to retain source-level checks, particularly where a summary drives a consequential financing decision.

Require extracted values to carry a document name, page or section, measurement period and review status. Ask the system to leave missing values blank and identify conflicts. A polished narrative with no traceable source is not a completed diligence task.

If a lender provides a requirement only by telephone, send a written summary through the authorized communication channel and seek confirmation. The request register should preserve whether the interpretation is confirmed, rather than treating a meeting note as a negotiated amendment.

## Close the register into the servicing file

At closing, preserve the accepted final package, resolved exceptions and any obligations continuing after funding. Transfer reporting dates, deferred documents, reserve-release conditions and responsible contacts to the operating team. Keep unresolved post-closing obligations visible.

The useful completion test is simple: another person should be able to identify which fact the lender relied on, which source supported it, when it changed, and whether the lender accepted that change. That is the foundation for a financing process that remains explainable after the people who assembled it have moved on.


## Source references
- [SEC-filed Block 40 loan agreement dated June 1, 2022](https://www.sec.gov/Archives/edgar/data/1795851/000166357726000199/ex10_30.htm) — 3.1.10 Financial Information · Checked 2026-10-21 · Source date / context 2022-06-01 agreement · Historical negotiated contract example; not a universal representation or current offer.
- [NIST — Generative AI Profile](https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf) — 2.2 Confabulation · Checked 2026-10-21 · Voluntary AI risk guidance; relevant to checking extraction and summaries.