This template belongs to the loan document exception closure guide. Fill it in after a first conversation with the lending operations head, using only facts someone at the lender will stand behind.
The blank brief: nine fields
Copy the first two columns and answer each field in a line or two. "Unknown" is an acceptable answer and often the honest one.
| Field | What to write | Who usually knows |
|---|---|---|
| Lender | Type (bank, equipment finance, specialty lender), country, full-time headcount at peak | CEO or CFO |
| Loan types | Commercial, equipment, real estate, consumer; rough share of each | Lending operations head |
| Record classes | Closing checklists, exception log with fix notes, generated document versions, signing packets and completion certificates, final signed sets | Post-closing manager |
| Systems | Loan origination or documentation system, e-sign accounts (how many), document archive, any spreadsheet logs | Lending operations head with IT |
| Coverage | Years held in each system, and gaps from earlier migrations or acquisitions | IT or the post-closing manager |
| Volume | Closings a year and the share with documentation exceptions, as estimates with their source | Lending operations head |
| Deadline | A documented access end: e-sign contract end, archive hosting end, loan system conversion date | Procurement or the project lead |
| Open question | The one fact nobody yet knows about how well the records join | Post-closing manager |
| Contacts | Records owner, content expert, decision-maker, counsel | Lending operations head |
Filling each field without touching a loan file
Lender. Headcount matters because the program requires 50+ full-time employees at peak, contractors excluded. Write the number the CFO's office gives you.
Record classes. Name classes, not contents. "Exception log with fix notes since 2013" tells a reviewer that the lender has tracked documentation problems for years and written down how each was resolved. A sample entry is never needed.
Systems. Count e-sign accounts, including any inherited from an acquired lender, and say whether each signing packet is tagged with the loan number. Docusign, for example, lets account administrators set up custom fields as free text or a list, required or optional, and includes the values in the completion certificate; "loan number field required since 2019" tells a reviewer how well packets will join to loans.
Coverage and volume. Pair every number with its source. Ranges are better than false precision.
Deadline. Only a documented date. A rumored system change is not a deadline; mark it unconfirmed.
Open question. One question only. If there are five, the brief is premature.
Contacts. Roles, not personal details beyond a name and title. The decision-maker is the CEO, or the owner in an owner-run lender; the who can license decision tree explains why the convener alone is not enough.
Completed example: a forwardable note (Illustrative)
Invented for this page. A fictional 340-person equipment finance lender in the U.S. The lending operations head reviewed every line before it was sent.
| Field | Entry |
|---|---|
| Lender | Equipment finance company, United States, about 340 full-time employees at peak |
| Loan types | Mostly commercial equipment loans and leases; some small real estate loans |
| Record classes | Closing checklists, exception log with fix notes, generated document versions, signing packets with completion certificates, final signed sets |
| Systems | Loan origination system being replaced, two e-sign accounts (one from a 2019 acquisition), document archive |
| Coverage | Checklists and exception notes since 2015; document versions since 2018; archive since 2009 |
| Volume | About 3,000 closings a year, documentation exceptions on a meaningful minority, per the lending operations head; not verified |
| Deadline | The old loan system goes read-only at conversion, and the acquired e-sign account closes four months later; dates confirmed in the project plan |
| Open question | Before 2019, exception notes rarely cite a signing packet ID, so some fixes may only match by loan number and date |
| Contacts | Lending operations head (records), chief credit officer (content), CEO (decision), general counsel (customer agreements) |
The covering paragraph the lending operations head forwarded read, in full:
We are converting to a new loan origination system next spring, and the e-sign account we inherited in 2019 closes four months after that. Our closing records since 2015 include checklists, an exception log with fix notes, generated document versions and signing packets with completion certificates. Our CEO would decide on any licensing discussion, with general counsel reviewing customer agreements.
Nothing is attached: no exception entry, no signed document, no screenshot and no customer list. A worked closing exception of the kind this lender records is in the exception examples.
Before you send it
- Consent. Record the client's consent to the introduction, as described in how to document client consent for a referral.
- Covering message. The warm introduction brief has wording, including the line saying you may receive a referral reward.
- Agreement. Sign the Channel Partner Agreement before submitting.
- Eligibility. The lender needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.
- Attribution. The first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company.
Customer information stays with the lender throughout. Lenders covered by the FTC's Safeguards Rule must keep an information security program with administrative, technical and physical safeguards for customer information, and a brief that contains none of it never tests that program. Fund-level lenders are a different category with different records; what is a NAV loan explains the distinction.
What the brief leaves to SourceX
The brief tells SourceX what exists and who decides. It cannot settle whether buyers want closing exception histories, what rights review concludes about customer and guarantor information, which years and record classes would be selected, what must be de-identified, or whether an offer follows. SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
When every field of the brief has an answer or an honest "unknown" and the decision-maker is named, register as a partner, check the lender on who qualifies and read the program terms before you forward it.