Servicing fee disclosures fail when they read like legal filings. Borrowers skim, miss what matters, then feel ambushed when the fee posts later. The result is a compliance document that technically works and a retention outcome that doesn’t.
The disclosure paradox
Every consumer lender in the country produces fee disclosures that meet regulatory standards. Very few produce fee disclosures their borrowers actually understand. That’s the paradox. Compliance and comprehension aren’t the same thing, and regulators have been signaling for years that comprehension is the direction of travel.
The CFPB’s 2025 guidance on plain-language servicing communications moved the goalposts. It’s no longer enough to show you disclosed a fee. You increasingly need to show you disclosed it in a way the borrower could reasonably understand. That’s a different bar, and most disclosure packets don’t clear it.
What a plain-language disclosure looks like
A good servicing fee disclosure answers four questions on a single screen: what is this fee called, when does it get charged, how much is it, and what’s the borrower’s option to avoid it. Anything that gets in the way of those four answers is noise.
Compare two disclosure styles. The legacy version reads: ‘A returned item charge in the amount of $29.00 may be assessed in the event that any payment instrument is returned unpaid by the originating depository institution for any reason, including but not limited to insufficient funds.’ The plain-language version reads: ‘If your payment bounces, we charge a $29 returned-payment fee. To avoid it, make sure your bank account has enough money on your due date.’
Both disclose the same fee. Only one is readable.
Where to deliver the disclosure
Origination disclosures alone don’t cut it anymore. The borrower who signed your fee schedule nine months ago isn’t going to remember it. That doesn’t excuse them, but it also doesn’t help you keep them.
Modern servicing fee disclosures appear at three touchpoints: at origination in the full fee schedule, inside the borrower portal as contextual tooltips next to every fee-triggering event, and as real-time notifications when a fee becomes likely. That third touchpoint is where retention gets decided.
Is this more work for my servicing team?
Counterintuitively, no. Well-designed servicing fee disclosures reduce call volume because the borrower doesn’t need to call to understand what happened. Every plain-language disclosure you add to your portal is a call your call center doesn’t have to take.
Servicers that have moved to plain-language disclosures across the full fee stack report 15 to 25 percent reductions in fee-related inbound call volume and comparable drops in first-escalation rates. The disclosure work pays for itself inside two quarters.
The four-question rewrite exercise
Take your current fee disclosure document and run every fee through the four-question filter. What’s it called. When does it hit. How much is it. How does the borrower avoid it. If any answer takes more than one sentence, rewrite it.
If any fee doesn’t have a clear avoidance path, that’s a different problem. Some fees exist as pure penalties with no consumer-friendly avoidance option. Those fees are the ones most likely to drive disputes and churn. They deserve a second look at the product level, not just the disclosure level.
Plain language as a competitive moat
Most lenders aren’t going to do this. They’ll keep running the legacy disclosure language their lawyers approved in 2011, and they’ll keep absorbing the retention cost. The lenders that invest in plain-language servicing fee disclosures build a small but compounding advantage, one that shows up in retention numbers, NPS, and ultimately origination cost per funded loan.
Transparency doesn’t feel like a growth lever. It operates like one.
A 90-day rollout plan for plain-language disclosures
Most lenders treat this as a six-month compliance project. It isn’t. A focused 90-day rollout covers the ground and produces measurable retention lift in the second quarter after launch. The sequence matters.
Days 1 through 30, audit. Pull every servicing fee currently assessed. For each one, document the trigger, the amount, the avoidance path, and the current disclosure language. Run every disclosure through the four-question filter. Flag the failures. Most portfolios have between 20 and 40 distinct fees when you count them honestly, and somewhere between half and two-thirds of the disclosures will fail the readability test on the first pass.
Days 31 through 60, rewrite and validate. Rewrite every failed disclosure in plain language. Test the rewrites on non-finance readers inside the company (marketing, design, HR). If they can’t explain the fee after reading the disclosure once, rewrite again. Then route through legal and compliance for sign-off. Budget a week for that review and protect it.
Days 61 through 90, deploy. Push the new disclosure language to the borrower portal, update origination packets, and add contextual tooltips and pre-fee notifications where the infrastructure supports it. Deploy in waves to catch issues early, track fee-related call volume week over week, and publish the metric to the executive team.
The rollout will probably miss two or three fees that surface only through live borrower behavior. That’s fine. Fix them in the next sprint. What matters is that the borrower experience starts compounding in the right direction, and that your team internalizes plain language as a product standard instead of a compliance task.
Two language traps catch most teams on their first rewrite pass. The first is the ‘technically accurate, practically useless’ sentence, the kind that reads correctly to a compliance attorney and opaquely to a borrower. Watch for it. If the sentence needs a footnote to make sense, it’s still a legal artifact pretending to be a disclosure. The second is the ‘over-softened’ rewrite that strips out the fee amount or the trigger condition in an attempt to be friendly. Plain language isn’t soft language. It’s direct language. A borrower should always know exactly what the fee is, when it hits, and what to do about it.
Calibrate the rewrites with two audiences in mind. A new borrower who’s never seen your product and a long-tenured borrower who’s been on autopay for three years. If both would understand the disclosure without a follow-up question, the rewrite is working. That’s the bar.
Once the rollout is live, treat the disclosure library as versioned content. Every change gets dated, reviewed, and archived. That practice pays back twice. It creates the audit trail regulators increasingly expect, and it gives the marketing and product teams a ready record of how borrower-facing language has evolved, which is useful when communicating changes to borrowers without catching them off guard.
The disclosure you write today is the retention conversation you don’t have to have in six months. Are you ready to learn more? Connect with us today.