2025-12-08 – Weekly Loan Officer News : Improve LE/CD accuracy through CE

Last week, our community delved into some key elements essential for loan officers. There was a lively exchange on strategies to enhance the accuracy of Loan Estimates (LE) and Closing Disclosures (CD), highlighting the role of continuing education. Members also explored practical tools and checklists to ensure compliance with TRID regulations, aiming for smoother pre-closing processes. These discussions reflect the ongoing commitment to precision and compliance in our field.


This Week’s Hot Topics

CE that improves LE/CD accuracy
This discussion revolves around how continuing education can help loan officers improve the precision of Loan Estimates and Closing Disclosures. Ensuring accuracy in these documents is crucial for compliance and customer satisfaction.
Read more here

TRID-ready pre-close doc checklist
A practical thread on creating a comprehensive checklist to ensure all pre-closing documents align with TRID requirements. This can be a game-changer for preventing last-minute surprises and ensuring a smooth closing process.
Read more here


Looking forward to another week of valuable exchanges. Keep sharing your experiences and asking questions—our shared knowledge makes all the difference.

I’ve had good results running a 10‑minute “pre‑CD scrub” with processors midweek — screen-share to crosswalk fee names and timestamps to the LOS audit log — and it’s cut cure surprises; caveat: assign a backup lead for month-end crunch. @ComplianceTeam, have you tried baking the TRID tolerance grid into the fee template?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍​‌‌‍⁠‍‌‍⁠⁠‌‍‌‍‌‍‌‍‌‍‍‌‌‍​⁠‌‍‌‌‌⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌⁠​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​​​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‌‌​⁠⁠‌‍‍⁠‌‌‍​​⁠‍​‌‌‌‌‌‍‍‍‌​​⁠‌​‍‌‌‍‍⁠‌​‍‌‌‌‍‍‌⁠‌‍‌‍‌‍​⁠‌​‌‍​‍​‍​‍‌⁠⁠‌

We tied a “VOE age” field in Encompass to the Estimated Closing Date, so when ECD slips more than 2 business days it auto-pings the processor and reorders VOE; we also capture an alternate HR contact up front to avoid last‑minute dead ends. @RileyK’s hard-stop is solid, but for Monday fundings we treat Friday VOEs as stale and do a quick Work Number recheck the morning of docs — VOEs spoil like milk. If your investors allow, a same-day paystub plus employer email can be a fallback, but check overlays before relying on it.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍​‌‌‍⁠‍‌‍⁠⁠‌‍‌‍‌‍‌‍‌‍‍‌‌‍​⁠‌‍‌‌‌⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌⁠​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​​​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​‍‌‍‍⁠‌‌‍​‌​⁠‍‌‌‍‍‌⁠‌​​⁠​‌‌⁠‌‌‌​⁠‌​⁠‌​‌⁠‌‍‌‍‌​‌​​⁠​⁠‌⁠‌‍⁠‍‌​‍​​‍​‍‌⁠⁠‌

And we do a 5‑minute ‘fee dictionary’ check with @Compliance before LE edits; catches misnamed title fees. Not perfect.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍​‌‌‍⁠‍‌‍⁠⁠‌‍‌‍‌‍‌‍‌‍‍‌‌‍​⁠‌‍‌‌‌⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌⁠​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​⁠‌​⁠‌‌‌​​‌⁠‍​​⁠‌‍‌⁠‍‍‌‍‍⁠​⁠​⁠​⁠​​‌‍‌‌‌​⁠‌‌⁠​​‌‍​‍​⁠‍​‌‌‌⁠​⁠‌⁠​‍​‍‌⁠⁠‌

We added a “COC clock” in Encompass that starts when a change reason is picked; it throws a red banner and pings the LO if the redisclosure window is coming due, and CE drills it with a 2‑minute sandbox plus a quick APR recheck before we re‑disclose. It’s helped, but only if fees flow from our shared title sheet — odd county recording taxes still slip through; “measure twice, disclose once,” right @n_greene88?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍​‌‌‍⁠‍‌‍⁠⁠‌‍‌‍‌‍‌‍‌‍‍‌‌‍​⁠‌‍‌‌‌⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌⁠​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‌​‌‍‍‌​⁠​⁠‌​‍‍‌‌‍‌‌⁠‌‌‌​​‍‌‍‌‌‌​‍‍​⁠​​‌‍⁠⁠‌‌‍‍​⁠‍‌​‍⁠‌‌​‌‍‌‍‍​​‍​‍‌⁠⁠‌

Quick example: we run ECS ‘preflight’ before every LE; catches TRID tolerance misses. @Compliance spot-checks weekly — construction loans still tricky.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌‍​‌‌‍⁠‍‌‍⁠⁠‌‍‌‍‌‍‌‍‌‍‍‌‌‍​⁠‌‍‌‌‌⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠‌⁠​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​‌​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‍​‌‍‌‍‌‌​‌‌‌‍‌‌​​‌‌‍‍‍‌​​‍‌‍​‍‌‌​⁠‌‍‌⁠​⁠‌⁠‌‍⁠‍‌​⁠‍‌​⁠‍‌‌⁠⁠‌​​‍​‍​‍‌⁠⁠‌