Last week, the forum buzzed with discussions on process improvements and operational challenges. Members delved into optimizing pre-close document checklists to ensure compliance with TRID requirements. There was also considerable focus on data management, with conversations about the impact of nightly ETL processes on report accuracy. Additionally, strategies for improving post-closing handoffs generated valuable insights, highlighting the importance of seamless transitions in maintaining client satisfaction.
This Week’s Hot Topics
TRID-ready pre-close doc checklist
Members shared strategies on creating comprehensive checklists to meet TRID requirements, aiming to streamline the pre-close process and ensure compliance. Read more here
Nightly ETL window and report accuracy
A discussion emerged around the challenges of maintaining report accuracy due to nightly ETL processes, with members exchanging tips on optimizing data integrity. Read more here
Smoother handoffs after closing
This thread focused on improving the transition phase after closing, with practical advice on ensuring clients receive consistent service and communication. Read more here
Looking forward to another week of engaging discussions. Feel free to jump in and share your experiences or ask questions. Have a productive week ahead!
We baked our TRID pre-close checklist into Encompass with a hard stop — if CD fees don’t match the latest fee sheet, you can’t draw docs. @DataOps helped us offset the ‘nightly ETL’ lag by adding a noon manual refresh plus a visible timestamp — stale data was killing report accuracy, . If your LOS is locked down, a quick live-fee check in Power BI works too; CFPB TRID ref: https://www.consumerfinance.gov/policy-compliance/guidance/tila-respa-disclosure-rule/.
Quick example: we added a “CD fee snapshot timestamp” to the TRID pre-close checklist and compare it to the last fee change in Encompass; if it’s older, we trigger a re-tolerance check instead of waiting on the nightly ETL. Cuts the “, the report is stale” problem, but it does create a few false alarms on tiny fee edits. @Guide this pairs well with hard stops — ours stays soft unless the mismatch repeats within 24 hours.
We wired a small “fee delta” check into Encompass that compares CD lines against our vendor fee catalog and the latest title upload via API; if variance is over $5, it halts doc draw and opens a task to refresh. Only caveat: after-hours title updates created noise, so we added a 15‑minute buffer and an override with an audit note — thanks @Guide for the timestamp tip.
, our after-hours loads kept biting us, so we added a 45-minute ‘freeze window’ before doc draw: if a fee or provider changes inside that window, Encompass throws a soft stop and pings Slack for a quick review. Moving that check to the change event instead of waiting on the batch also tightened next-morning report accuracy. Small caveat: if your title partner posts partial updates, pair it with a ‘quote ID’ lock rather than just dollar amounts, @kelli_roberts86.
We added a small guardrail: any fee change after CD generation requires picking a “Changed Circumstance” code and attaching evidence, and Encompass stamps the audit note with user/time plus the doc ID; the checklist won’t clear without it. @Nina we kept it light — three codes tied to the CFPB guide (https://www.consumerfinance.gov/policy-compliance/guidance/tila-respa-disclosure-rule/) — adds a click, but it cut most oops moments; measure twice, redisclose once.
One tweak that helped us: our TRID checklist auto-compares the written provider list date to the service order and the selected vendor; if the list was late or off-list, it flips the tolerance bucket and triggers a reprice before the CD. To dodge “nightly ETL” lag, we read those fields directly in Encompass and show the capture timestamp on the checklist. Small caveat: you need clean list-sent times, so we added a quick intake prompt to confirm it.
Quick example: we stopped relying on nightly ETL and moved the TRID checklist into Encompass with a save-trigger that validates fees, LE dates, and APR in real time before the CD goes out. We also write a small “source of truth” snapshot to the loan log so reporting matches what was checked, and @DataOps throttles it to once per loan every 15 minutes to keep noise down. Small caveat: the APR recheck can lag if third‑party tax fees haven’t returned yet, so we surface a pending status instead of failing it outright.