Notion vs. Slite for a Specialty Asset-Based Lender

When the compliance lead started exam prep, she asked for the current underwriting policy and got three different documents from three different loan officers, each reflecting decisions made at different points without the others being updated. None of them were wrong exactly, they'd each been accurate at some point, but none was reliably current, and reconstructing which version actually reflected the credit committee's most recent decisions took real time.

The lender rebuilt a single underwriting policy document, with every credit committee-approved exception logged separately against it rather than silently folded into a loan officer's personal copy. This went into a locked, published structure so a loan officer could see the current policy plus any standing exceptions, without any individual being able to quietly modify the base policy itself, even with good intentions during a busy underwriting cycle.

Loan covenants and their monitoring schedules had lived in loan officers' individual tracking spreadsheets, which meant a compliance review required chasing down each officer's personal system. The lender centralized covenant terms and monitoring status by borrower, with the actual monitoring cadence documented, so a compliance lead could review covenant compliance across the portfolio without a scavenger hunt through several officers' personal files.

Collateral valuations and borrowing base calculations needed to be retrievable per loan, with the methodology used documented alongside the number itself, not just the final figure. The lender required the borrowing base worksheet and its underlying assumptions to be attached directly to the loan file, so an examiner or auditor reviewing a specific loan could see exactly how the number was actually derived, not just what it ended up being.

The examiner's first request was for the current underwriting policy and evidence of consistent application, and the lender produced it in minutes instead of days. The exam still surfaced findings, exams generally do, but none of them were about document control or an inability to produce current policy, which the compliance lead considered the real measure of the rebuild's success.

Midway through the rebuild, the team realized their collections escalation process, when a past-due loan moves from a loan officer's direct contact to formal collections to legal referral, had never been formally documented at all, existing only as informal practice. They added it as its own locked reference, since an inconsistent collections process carries both a fair lending exposure and a real business risk if escalation happens too late or too inconsistently across borrowers.

The compliance lead anticipated pushback from loan officers who'd been operating with real autonomy in how they interpreted underwriting policy, and addressed it directly: the goal wasn't removing their judgment, it was making sure that judgment, once exercised through a credit committee exception, was actually preserved and visible instead of living only in that officer's head and lost the moment they moved to another role. Framed that way, most loan officers saw the rebuild as protecting decisions they'd already fought for, not constraining new ones.

This framing mattered for adoption. A compliance rebuild that loan officers experience as distrust tends to get quietly worked around, while one they understand as protecting their own prior decisions tends to actually get used going forward, which is ultimately what determines whether the next exam goes as smoothly as this one did.

The lender operated across several states with different licensing and rate cap requirements, and the underwriting policy rebuild had to account for state-specific variations rather than a single national policy. They structured the policy as a common core with clearly labeled state-specific addenda, so a loan officer working a specific state's loans could see exactly which rules applied without wading through requirements from states they don't operate in at all.

To rebuild your own documentation the same way, work through these steps:

1. Consolidate the underwriting policy into one current document and place it in a locked, published structure.
2. Log every credit committee exception against the policy, with the specific loan and the committee's stated reasoning.
3. Centralize covenant terms and monitoring status by borrower so a compliance review does not require chasing each loan officer's spreadsheet.
4. Store collateral valuations and borrowing base worksheets per loan, with the methodology and assumptions kept alongside the number.
5. Document collections escalation, from loan officer contact to formal collections to legal referral.
6. Structure the policy as a common core with state-specific variations for licensing and rate cap requirements.