A building with glass windows

Broker Resources

How Do You Authorize Broker Sharing Under an Acquisition NDA?

Match acquisition documents and financing recipients to actual NDA permission. Resolve approvals before distribution and keep secure handling separate.

By Peyton Williams · · 8 min read

Key takeaway: An acquisition NDA and a brokerage appointment answer different questions. Confirm the permitted recipients, materials and purpose before sharing protected records, including any approval or undertaking required by the actual agreement. A secure channel does not create consent, and a lender’s interest does not eliminate the seller’s disclosure restrictions.

The quick read: Before a broker shares acquisition documents, confirm who the seller's confidentiality agreement permits to receive them and which conditions apply. A borrower instruction to seek financing does not override a separate NDA. Match each recipient and document to the actual permission, resolve missing approvals and keep confidential financing work separate from public marketing.

Which agreement controls the seller's information?

The agreement controlling the seller's information must be identified before the buyer instructs a broker to distribute a financing package because an appointment to seek debt does not change obligations accepted when accessing a data room or signing a purchase agreement. Read the confidentiality documents together and ask counsel which provision governs each category of material.

The buyer may have signed an initial NDA, a later purchase agreement and additional consultant-access terms. Keep all of them in the evidence set. A new transaction document might preserve, modify or incorporate another obligation, but that conclusion needs the actual wording rather than the assumption that the latest file replaces every earlier one.

Identify whose information is being handled. A seller's operating statement can have a different permission basis from the buyer's own financial statement. A combined financing summary may contain both. Creating a new spreadsheet does not necessarily remove confidentiality from the underlying facts or analysis derived from protected material.

Ask the broker what documents are needed for the proposed financing discussion. That lets the buyer request the necessary permission rather than granting unrestricted access to the entire acquisition archive. The decision concerns contractual disclosure authority, not simply whether the information would help a lender.

What can a real property contract permit for financing?

A real property contract can permit disclosure to specified lenders or advisers subject to stated confidentiality conditions, so the borrower should verify the actual exception before assuming every prospective funding source may receive every document. Preserve the permitted purpose and any instruction or separate-agreement requirement with the recipient record instead of reducing the provision to lenders allowed.

A historical 2006 San Diego purchase-and-sale agreement filed with the SEC provides a concrete example. Its confidentiality provision permits specified financing and professional recipients for the transaction and includes duties concerning confidentiality and certain consultant agreements. This is that negotiated property transaction, not a nationwide permission rule or the terms of your acquisition. Filed property confidentiality provision.

For the actual file, identify whether the permission includes prospective lenders, equity sources, brokers, consultants or only named recipients. Ask whether sharing requires notice, a signed undertaking or another approval. A familiar financial institution does not remove the requirement if the contract imposes one.

If the proposed recipient is not clearly included, record that gap and obtain the required resolution before sending protected material. An owner's urgency to get a quote is not evidence that the other party consented. Counsel should interpret an unclear clause; the broker can organize the requested recipient and purpose without deciding the legal exception itself.

Why can the definition of representative matter?

The definition of representative matters because an NDA can include advisers while excluding financing sources until a particular approval occurs, so permission to use a broker does not necessarily establish permission for the broker's intended lender recipients. Read the definition and its exceptions before relying on a broad label, and retain any accepted addition to the approved group.

A separate 2013 SEC-filed business-acquisition confidentiality agreement expressly excludes prospective financing sources from its initial representative definition unless approved, while identifying an approved debt-financing group in separate correspondence. This is a corporate acquisition specimen, not a property NDA or a legal rule for all CRE financing. It demonstrates a different negotiated structure. Filed representative and financing-source definition.

Comparing the two specimens is useful because the same practical objective—obtaining financing—can sit under different document permissions. Do not borrow the broader exception from one agreement to fill a narrower provision in another. The buyer's actual documents and approved amendments establish the operating boundary.

Distinguish a lender's employees and necessary service providers from a separate funding institution. The NDA may describe downstream recipients or impose obligations on them. Ask how those conditions are documented rather than treating an approved institutional name as permission to circulate the material without further control.

How should recipients and materials be matched?

Recipients and materials should be matched in a permission register that identifies the source document, confidentiality basis, permitted purpose and required undertaking so the broker can work from a specific authorization rather than a general instruction to shop the deal. Keep unresolved rows open, and separate permission confirmation from proof that the proposed lender will consider the loan.

Illustrative acquisition-document permission register — not an actual consent:

Material Source or controlling record Proposed recipient Confirmation before release
Material Seller operating statement Source or controlling record NDA and purchase confidentiality terms Proposed recipient Financing source A Confirmation before release Included recipient and permitted transaction purpose
Material Tenant lease copies Source or controlling record Seller documents and relevant restrictions Proposed recipient Source A's authorized reviewer Confirmation before release Required confidentiality conditions and scope
Material Buyer-created analysis using seller facts Source or controlling record NDA treatment of derived material Proposed recipient Financing source B Confirmation before release Whether approval or undertaking is still needed
Material Buyer financial statement Source or controlling record Buyer authority and applicable handling requirements Proposed recipient Proposed lender Confirmation before release Approved channel and appropriate access
Material Consultant report Source or controlling record Report engagement and confidentiality conditions Proposed recipient Named lender reviewer Confirmation before release Permitted recipient/use and any separate consent

Replace the fictional sources with actual recipients and evidence. The table does not establish that a particular document can be shared, that redaction resolves every restriction or that a provider must accept reliance. Those are questions for the relevant source owner and advisers.

A public property description can be separated from protected operating records if the facts and actual documents support that distinction. Do not label information public merely because the borrower already knows it or because a similar number appears on a listing. Preserve the basis for any public-information exception being relied on.

How can a permission delay affect the financing calendar?

A permission delay can affect the financing calendar when protected information is necessary for a lender's review and the actual required approval has not been obtained, so the borrower should model that dependency rather than assume the lender can price a complete file immediately. Separate the permission step from credit review, and avoid inventing a standard NDA turnaround time.

Use a labeled hypothetical schedule. A transaction has ten business days until its financing evidence is needed. Obtaining the required recipient approval is assumed to take three business days, assembling the authorized package takes two afterward, and the lender's review takes four after receipt. The dependent sequence totals nine business days, leaving one day under those invented assumptions.

If the permission step takes five instead of three days, the same sequence totals eleven business days and exceeds the target by one. A parallel internal task completed earlier does not automatically shorten the dependent chain. Nor does this scenario prove that the parties have a contractual right to extend the target date.

For a separate cash sensitivity, suppose an actual permitted transaction extension would create an assumed $2,000 of daily carry over five calendar days. The modeled added cost is $10,000. Those cost and date assumptions are invented, not lender terms or a prediction that the seller will grant an extension.

The useful decision is to clarify recipient approval early, identify the minimum necessary information and obtain the actual review estimates. Do not solve the calendar by sending material before permission is established or by claiming that a partial public summary is the complete confidential file.

How does contractual permission differ from secure handling?

Contractual permission differs from secure handling because the right to provide information and the method used to protect it are separate questions, and satisfying one does not automatically satisfy the other. Confirm both with the responsible parties. A secure folder does not create NDA consent, while consent does not justify exposing sensitive records to unnecessary recipients.

The FTC's Safeguards Rule guidance addresses customer information and covered financial institutions, with mortgage brokers among its examples. Its scope must be evaluated from the actual activities and information; this article does not conclude that every seller's CRE operating document falls under the same consumer-information rule. FTC information-safeguards guidance.

For practical coordination, identify who can access each file, what they need and whether an accepted secure channel is required. Keep personally sensitive buyer records out of an unrestricted marketing summary. Ask the lender and broker to confirm their process rather than claiming any particular platform is compliant from its appearance.

When the transaction ends or a recipient is removed, review the actual return, destruction and retention provisions. Some agreements permit defined retained records under conditions; others use different terms. This guide does not direct indiscriminate deletion of transaction evidence or assume all confidentiality obligations end with the lender search.

How should the borrower instruct the broker before disclosure?

The borrower should instruct the broker using the confirmed recipient list, permitted materials and required conditions so that an otherwise valid financing search does not begin with an unsupported disclosure assumption. Identify which approvals remain outstanding and who will obtain them. Keep the instruction record connected to the actual NDA and any accepted change.

YieldStack is a commercial mortgage brokerage. Lenders make their own credit decisions, and permission to share a file does not guarantee that a lender will accept the financing request.

YieldStack's editorial recommendation is to establish disclosure authority before providing protected acquisition records. This is attributable process guidance, not interpretation of the seller's NDA. For commercial financing, present the property decision and the material that can properly be supplied, with unresolved permissions identified.

Use the term-sheet context to keep information access separate from a lender commitment. You can submit the acquisition confidentiality question without claiming that a seller's consent or an approved recipient group already exists. For general intermediary roles, see brokerage versus direct lending.

Bottom line

Give the broker an authorization that identifies recipients, materials and the conditions supported by the actual agreement. Resolve missing approval before distributing protected records, then use an appropriate handling channel. Keep the permission calendar separate from credit review: a lender's interest in the acquisition does not override the seller's confidentiality terms.

Frequently Asked Questions

Does appointing a broker override the seller’s NDA?

No automatic change is established. Read the controlling agreements and confirm actual recipient and material permissions.

Is every prospective lender automatically a representative?

Not necessarily. The actual definition and accepted approvals control; the cited specimens use different negotiated structures.

Does a secure data room establish permission to disclose?

No. Disclosure authority and secure handling are separate questions, both requiring the appropriate confirmation.

Are the example approval dates a standard NDA turnaround?

No. They are hypothetical dependencies chosen to illustrate timing, not a promised approval or lender calendar.

Sources

  1. Historical 2006 San Diego property purchase agreement, confidentiality provisions.

    SEC EDGAR
  2. Historical 2013 business-acquisition NDA, representative and approved-financing-source definitions.

    SEC EDGAR
  3. FTC covered-institution and customer-information safeguards scope.

    Federal Trade Commission

Your deal

Scored against 20,000+ loan programs. Sent only to the 5–8 that fit.

Median first offer in under an hour. Zero upfront; 0.50–1.00% at closing.

Get Financing Now

Try the lender match tool · Request access