A 2015 filing lapse delayed TRID, and the CFPB proposed October 3 partly because system updates were late
On June 17, 2015, the CFPB said it would propose delaying its mortgage disclosure rule after finding an administrative error. Its proposal chose Saturday, October 3, citing late system updates that cut testing time, and the final rule kept that date.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
On June 17, 2015, the CFPB said it would propose delaying its mortgage disclosure rule after finding an administrative error. Its proposal chose Saturday, October 3, citing late system updates that cut testing time, and the final rule kept that date.
- The week The statement gave a second reason for choosing a later date.
- The cause: a filing lapse inside the regulator The proposal published on June 26, 2015 explained the error.
- The dependency: software lenders bought from others The final delay rule, published on July 24, 2015, put a figure on how far lenders depended on vendors.
- The people: staff, brokers and settlement agents The final rule listed the costs that firms would incur from delaying past the statutory date.
- The cutover: how the switch actually happened The rule did not switch over on a single day for every loan.
- How the delay landed on different firms For depository institutions that relied on vendors, the delay was mainly a scheduling problem.
- Objections, and where the argument stops The strongest objection is that the delay helped industry.
- Checks for leaders running a regulatory change These are our own suggestions, not requirements of any rule.
- With hindsight The final rule was dated July 20, 2015 and published on July 24, 2015, at 80 FR 43911. [4] Effective July 24, it moved the effective date from August 1, 2015 to October 3, 2015. [4] The Bureau adopted October 3 as proposed and made technical corrections to two provisions. [4] It did not adopt a formal grace period or a dual compliance period.
The week
On June 17, 2015, the Consumer Financial Protection Bureau published a statement by its Director on the Know Before You Owe mortgage disclosure rule. [1] The statement said the Bureau would issue a proposed amendment to delay the rule’s effective date until October 1, 2015. [1] It gave a reason: an administrative error, just discovered, in meeting requirements under federal law. [1] The statement said that error would have delayed the rule’s effective date by two weeks. [1]
The statement gave a second reason for choosing a later date. It said the extra time would better accommodate consumers and providers whose families would be busy with the start of the school year. [1] It said the public would be able to comment on the proposal, and that a final decision was expected shortly after. [1]
The rule being delayed was large. In November 2013, under sections 1098 and 1100A of the Dodd-Frank Act, the Bureau had issued a rule combining certain disclosures consumers receive when applying for and closing on a mortgage. [2] The Dodd-Frank Act had transferred rulemaking authority under both the Truth in Lending Act and the Real Estate Settlement Procedures Act to the Bureau. [2] It also mandated a single disclosure scheme in place of the two laws’ separate requirements. [2]
Those separate requirements had their own clocks. Under the Truth in Lending Act, a creditor generally had to give a good faith estimate of credit costs within three business days of receiving an application. [2] It had to give it at least seven business days before consummation of certain transactions. [2] Under the Real Estate Settlement Procedures Act, the creditor or broker had to give a good faith estimate of settlement charges no later than three business days after receiving the application. [2] The new rule replaced these with integrated disclosures, including a Loan Estimate given after application. [2]
The Bureau had already amended the rule once that year. On February 19, 2015, it published amendments, effective August 1, 2015. [2] They applied to transactions for which the creditor or mortgage broker received an application on or after August 1, 2015. [2] They extended the time to give a revised Loan Estimate after a consumer locked a rate, to three business days. [2] They also placed the loan originator’s Nationwide Mortgage Licensing System and Registry identifier on the integrated disclosures. [2] The Bureau said it received 31 comments on that proposal, from creditors, trade associations, technology vendors and others. [2]
The Bureau had also built an implementation program. Its February rule listed a plain-language compliance guide, a guide to the forms, a readiness guide, a disclosure timeline and a series of webinars. [2] It listed roundtable meetings with creditors, settlement service providers and technology vendors. [2] It listed coordination with state and federal regulators on consistent examination procedures. [2]
So by mid-June 2015, lenders, settlement agents and their software providers had been working toward an August 1 start. [2] The June 17 statement told them the date would move, to a date still to be proposed. [1] It did not say what the error was. [1]
The CFPB’s 2015 delay of its integrated mortgage disclosure rule is easy to read as a clerical footnote. The Bureau had not filed a required report with Congress, and the rule could not take effect on schedule. [3] For an operations leader at a bank, credit union or mortgage company, the episode is more useful than that. It showed what a compliance date is: a milestone in a project shared by many firms. The Bureau believed only approximately 5 percent of creditors did not rely on third-party vendors. [4]
The Bureau’s own documents make the point. When it proposed the new date, it said it had learned that delays in delivering system updates had left creditors and others with limited time to test. [3] It proposed a Saturday, saying that may allow firms to launch new system configurations and test over a weekend. [3] Its final rule later listed the costs of the delay as including staff training, software programming and coordination with vendors, brokers and settlement agents. [4]
Our argument is that the 2015 delay turned a legal effective date into an operating plan, and showed where the plan could break. In our reading, the break points were not in the rule’s text. They were in the regulator’s own process, in vendors’ release schedules, in the people who had to be trained twice, and in the mechanics of the cutover itself.
We take the episode in four parts:
- The cause: the filing lapse inside the regulator.
- The dependency: software and systems that lenders bought from others.
- The people: staff, brokers and settlement agents who had to be ready on one day.
- The cutover: how the switch from old forms to new actually happened.
The parts do not overlap. The first is the regulator’s process, the second the technology supply chain, the third the workforce and the fourth the transition mechanics. After them we look at how the delay landed on different kinds of firms, take the objections, and end with checks an operations leader could run.
The cause: a filing lapse inside the regulator
What the Bureau said went wrong
The proposal published on June 26, 2015 explained the error. Section 801 of the Congressional Review Act bars a rule from taking effect until the agency submits a rule report to each House of Congress and to the Comptroller General. [3] A “major rule,” which included this one, cannot take effect until, in the proposal’s words, “60 days after (1) publication in the Federal Register or (2) receipt by Congress, whichever is later.” [3]
The rule had been published on December 31, 2013. [3] The Bureau said it had recently discovered that it “inadvertently had not submitted the rule report to Congress as required.” [3] It said it submitted the report to both Houses and to the Government Accountability Office on June 16, 2015, immediately on discovering the error. [3] Under the statute, the rule could then take effect on August 15, 2015 at the earliest. [3]
The choice the error forced
The error left the Bureau two options. It could let the rule take effect on the statutory date, August 15, or it could set a later one. [3] The proposal said a mid-month date could create additional challenges. [3] It said moving readiness from August 1 to August 15 was likely to pose implementation challenges for many organizations. [3]
The Bureau also weighed a longer delay. It said a longer delay would impose unnecessary costs on the parts of industry that had worked hardest to be ready on time, and on consumers. [3] It proposed October 3, 2015. [3] The June 17 statement had mentioned October 1. [1] The formal proposal moved it to the Saturday. [3]
A week of uncertainty
The sequence left firms to plan on partial information. The June 17 statement named October 1 and gave no detail on the error. [1] The formal proposal, issued on June 24 and published on June 26, named October 3 and explained the statute. [3] [4] Comments ran until July 7, and the final rule was published on July 24. [3] [4]
In our reading, each step forced a choice. A firm could replan on the statement, wait for the proposal, or wait for the final rule. Waiting cost time that vendors and testers needed. Acting early risked planning for a date that changed again, as October 1 became October 3. The final rule shows that firms acted on the proposal, and that the Bureau then kept the proposed date partly for that reason. [4]
What the cause part shows
The error was procedural and internal to the regulator. The rule’s content did not change. [3] Yet every firm preparing for August 1 had to replan. In our reading, this is the plainest lesson of the episode for operations leaders. A compliance date depends on steps outside the regulated firm’s control, including the regulator’s own filings.
That does not mean firms should expect regulators to miss filings. It means a project plan built around a single date should have a documented way to absorb a change in that date. The Bureau’s own description of the cost of “stopping and restarting” shows what happens without one. [4]
The Bureau’s implementation program
The regulator had invested in readiness. The final delay rule listed its efforts: compliance and form guides, a readiness guide, a disclosure timeline, webinars with an index of questions answered, and roundtables with creditors, settlement service providers and technology vendors. [4] It said there had been over 30,000 downloads of its small entity compliance guide and other implementation materials during June 2015 alone. [4] It listed close collaboration with state and federal regulators on consistent examination procedures. [4]
In our reading, the program shows that the Bureau treated implementation as a shared project. It held roundtables with technology vendors because it knew lenders depended on them. That made the internal filing lapse more costly, because it moved the date for a project that the regulator itself had helped schedule.
The cause part also shows how small the trigger was compared with its effect. A single report, not submitted until June 16, 2015, moved the start of a rule that the Bureau said required major operational changes across an industry. [3] In our reading, firms cannot prevent such triggers. They can decide in advance who in the organization owns the response when one occurs, and how quickly the plan is reset.
Readiness the Bureau assumed
The Bureau said it continued to believe that the nearly 21-month implementation period, with its support efforts, had given all participants a reasonable opportunity to comply by August 1. [3] It said it understood that many organizations were well prepared for August 1. [3] It also recognized that the rule posed “perhaps unique implementation challenges for industry,” requiring major operational changes and close coordination among many parties. [3]
In our reading, those two statements sit side by side for a reason. The regulator judged that firms had enough time. It also recognized that the work depended on coordination it could not see in full. The late system updates it described in the same proposal were evidence of that gap. [3]
The dependency: software lenders bought from others
The Bureau’s view of vendor reliance
The final delay rule, published on July 24, 2015, put a figure on how far lenders depended on vendors. It said the Bureau believed approximately 5 percent of creditors do not rely on third-party vendors, citing its 2013 analysis. [4] It said the costs of delay were likely higher for larger creditors and for creditors that rely primarily on proprietary systems. [4]
Read the other way, the Bureau’s estimate meant the rest of the market relied on vendors for at least part of the work. In our reading, a lender’s readiness for the rule was therefore a function of its vendors’ readiness. A bank could finish its own policies, training and testing and still not be ready if its loan origination or document system was not.
Late updates and short testing windows
The proposal said the Bureau had learned, in recent weeks, that delays in delivering system updates had left creditors and others with limited time to fully test their systems. [3] It said firms needed to test that each system worked with the others. [3] It said these delays posed risks to the smooth implementation of the new Loan Estimate and Closing Disclosure. [3]
The final rule recorded what commenters said. Many industry commenters, both individuals and institutions, cited delays in updating software and systems the industry relies on for compliance. [4] They also cited related delays in testing and training on those systems. [4] Several, including trade associations, a technology vendor and two banks, said that adjusting systems from August 1 to a later date posed extensive challenges. [4]
Integration, not a single system
The proposal’s phrasing is precise: firms needed time to test “all of their systems and system components to ensure that each system works with the others.” [3] A mortgage file moves through several systems: point of sale, loan origination, pricing, document preparation, closing and post-closing. The integrated disclosures had to be produced by these systems together, with consistent figures.
In our reading, the late updates mattered because they compressed integration testing, which comes last. A vendor can deliver its piece on time and still leave too little time to test how it works with every other piece. The rule’s new tolerances and timing requirements made those interactions high stakes.
Who owns a defect between vendors
Integration testing raises a question no single contract answers: who fixes a fee on which the pricing engine and the document system disagree. In our reading, the rule’s tolerances made the answer matter, because a changed fee could require a cure. The proposal itself adjusted the timing of an interpretation on the relationship between RESPA tolerance cures and Regulation Z points and fees cures. [3]
In our reading, a lender that had not assigned ownership of cross-vendor defects before testing began lost time when one appeared. The late updates the Bureau described made that time scarce. [3] An operations leader could assign a single internal owner for each handoff between systems, with authority to call in both vendors.
Contract terms that mattered
The episode also showed which vendor contract terms carried weight. A regulatory change clause that committed a vendor to deliver by a stated date was only as useful as the date. When the date moved, the clause had to say whether the vendor’s obligation moved with it, and who paid for the extra release work.
Test environments mattered too. A vendor that delivered a release to production but not to a stable test environment left the lender unable to test handoffs in advance. In our reading, the right questions in 2015 were about delivery to test as well as to production, and about support during the cutover weekend.
Small creditors and vendor schedules
A small creditor buying a standard product had little say over its vendor’s release schedule. It received the release when the vendor shipped it to all customers. In our reading, a date change hit such firms through their vendor’s plan as much as their own. Their main lever was testing promptly once the release arrived and reporting defects early.
Larger creditors with proprietary systems controlled their own schedules but carried their own costs, as the Bureau noted. [4] Neither model escaped the date change. Each felt it in a different part of the organization.
What the dependency part meant for a lender
For a lender, the dependency part turned vendor management into rule readiness. The facts an operations leader needed were concrete:
- the date each vendor would deliver its release;
- the date each release would be in the lender’s test environment;
- who would test the handoffs between systems;
- who would fix a defect that fell between two vendors’ products.
The Bureau could not answer those questions for firms. It could only move the date. In our reading, the two additional months it chose were sized to give the supply chain time to finish, while avoiding a longer delay that it said would cost consumers the rule’s benefits. [4]
The people: staff, brokers and settlement agents
The cost categories the Bureau named
The final rule listed the costs that firms would incur from delaying past the statutory date. They included “communication with and training of staff, software programming, vendor and outside supplier coordination, advertising and product development costs, and broker and settlement agent coordination.” [4] It said firms might incur additional costs, “including ongoing training, testing, and opportunity costs.” [4]
Several of these are people costs. Staff trained for an August launch had to stay ready for October. Brokers and settlement agents had to reset their own schedules to match each lender’s. In our reading, the delay extended a period in which people were trained on a process they could not yet use.
Settlement agents and the many parties
The Bureau said the rule required “close coordination among many different parties.” [3] The Closing Disclosure brought together figures from the lender and the settlement agent. A lender’s readiness did not guarantee its settlement agents’ readiness, and the reverse.
The final rule recorded concerns about this coordination in the comments on a “dual compliance” period. Some credit unions and their trade associations asked for an optional period in which creditors could test new disclosures in live transactions. [4] A technology vendor and a title underwriter opposed it. [4] They said it would increase the risk of errors, disadvantage some smaller firms, complicate information flows to secondary market investors and raise the risk of consumer confusion. [4]
In our reading, both sides were describing a workforce problem. One wanted staff to practice on live files before the date. The other worried that two processes at once would produce errors. The Bureau did not adopt a dual compliance period. [4]
Supervisory expectations
Commenters also asked for a grace period after the effective date. [4] Many suggested it could apply to creditors that showed good faith efforts to comply. [4] Consumer advocacy groups opposed a formal grace period and noted that regulators already had discretion not to sanction creditors. [4]
The Bureau pointed to an approach its Director had described in a June 3, 2015 letter to members of Congress. [4] That letter said oversight in the early period would be sensitive to the progress of firms that had focused on good-faith efforts to comply on time. [4] The Bureau said this approach remained appropriate. [4] In our reading, this was a supervisory posture, not a legal safe harbor, and firms needed evidence of their own good-faith efforts.
Families, schools and calendars
The June 17 statement gave a reason that had nothing to do with systems. It said the extra time would better accommodate consumers and providers whose families would be busy with the new school year. [1] In our reading, the regulator was recognizing that the people doing the work, and the borrowers, had calendars of their own. A launch in mid-August would have coincided with that period.
Training that holds
Training for the new forms was a large effort. The lenders surveyed for the Bureau’s 2020 assessment named training, with technology and policies, among their largest implementation costs. [6] A delay after training meant either repeating it or relying on staff to remember. In our reading, the cheaper path was a short refresher near the new date, built around the questions staff had raised in testing.
Questions to the regulator
Staff and compliance teams also turned to the Bureau. Its 2020 assessment said rule-related guidance inquiries increased sharply from early 2015, peaked around the effective date and then declined. [6] The Bureau said the pattern was similar to other rules and may indicate that firms’ uncertainty peaked around the effective date. [6] It added that the pattern may instead indicate that inquiries declined for other reasons. [6]
In our reading, that peak coincided with the period when people were being trained and systems tested. A firm’s own internal question log was worth keeping for the same reason. It showed where staff were unsure, and so where a refresher was needed.
What the people part meant for a lender
For an operations leader, the people part meant planning for readiness to be held as well as reached. Training had to be refreshed, not repeated from scratch. Partners had to be told the new date and asked to confirm their own plans. Evidence of effort, such as test results, training records and vendor communications, had value if supervisors asked how the firm had prepared.
The cutover: how the switch actually happened
Applications, not closings
The rule did not switch over on a single day for every loan. The final rule’s commentary said the revisions applied to covered loans for which the creditor or mortgage broker received an application on or after October 3, 2015. [4] A few provisions applied from October 3 without regard to when an application was received. [4]
In our reading, this made the cutover a period, not an event. Applications received before October 3 stayed on the old forms through closing. Applications received on or after it used the new ones. For weeks or months, depending on each lender’s pipeline, staff handled both.
The Saturday
The proposal explained the Saturday. It said a Saturday date may allow smoother implementation by giving industry time over the weekend “to launch new systems configurations and to test systems.” [3] It also said a Saturday launch was consistent with existing plans tied to the original Saturday, August 1. [3]
The final rule added what commenters said. Industry commenters did not express a uniform preference for Saturday, but many preferred a weekend day. [4] The Bureau noted that since November 2013 industry had prepared on the understanding that implementation would be on a Saturday at the beginning of a month. [4] It said it preferred to minimize disruption to settled expectations. [4]
Why the date had to stay put
The final rule also recorded a practical reason not to change the proposed date. Multiple commenters said firms had already relied on October 3 in adjusting their schedules and operations. [4] Industry had begun making system adjustments based on the proposed date, before the rule was final. [4] The Bureau said that, absent compelling evidence that another date was better, it was reluctant to impose further costs. [4]
In our reading, this shows how quickly a proposed date became an operating fact. Firms could not wait for the final rule to replan. They replanned on the proposal and relied on the Bureau to keep it.
Redisclosure clocks at the boundary
The new rules also changed the clocks inside each file. The February 2015 amendments extended the time to give a revised Loan Estimate after a rate lock to three business days. [2] The Bureau said this harmonized the requirement with other redisclosure timing in the 2013 rule. [2] It said it was consistent with existing practice for a revised Good Faith Estimate. [2]
In our reading, staff who handled both old and new files during the cutover had to apply two sets of documents, with clocks that partly matched and partly did not. Training on the boundary, as well as on the new rule, earned its cost there.
Notices after closing
Some commenters asked whether the new date applied to post-consummation notices. The final rule said the Dodd-Frank Act disclosures in sections 1026.20(e) and 1026.39(d)(5) became mandatory on the effective date, now October 3, 2015. [4] In our reading, this meant the cutover reached servicing and loan transfer processes as well as origination. Teams outside the origination workflow had their own date to meet.
Application bunching
The Bureau later looked at what happened around the date. Its 2020 assessment said application volume deviated slightly from trend in the week before the effective date, then roughly doubled on the day before it. [6] It said this bunching suggested lenders may have encouraged prospective clients to apply before the date. [6] It also said the deviation was small enough to suggest the rule did not cause significant disruption to application volumes. [6]
In our reading, the bunching is the cutover rule at work. Because the old forms applied to applications received before October 3, a surge of applications the day before extended the period during which staff ran both processes.
Defects after the switch
The Bureau’s 2020 assessment looked for signs of disruption in loan quality. It cited data from a mortgage quality control software provider on the share of mortgages with at least one critical defect. [6] That share was about 1.8 percent in the second quarter of 2015, 0.8 percent in the third, 1.2 percent in the fourth and 1.9 percent in the first quarter of 2016. [6]
The Bureau said the increase from the third to the fourth quarter of 2015 left the share roughly where it had been in the second quarter. [6] In our reading, the figures do not show a lasting break in quality at the cutover. They do show that defect rates moved around the switch, which is when a firm’s monitoring matters most.
How the delay landed on different firms
Banks and credit unions with vendor systems
For depository institutions that relied on vendors, the delay was mainly a scheduling problem. Their readiness depended on their vendors’ releases and on their own testing. The Bureau believed approximately 5 percent of creditors did not rely on third-party vendors. [4] In our reading, vendor-reliant firms were therefore the bulk of the market. For them, the delay gave time to complete testing that late releases had compressed. [3]
Credit unions were among the commenters asking for an optional dual compliance period. [4] In our reading, their request reflected a wish to practice with members’ live files before the date, with the ability to fall back.
Large creditors with proprietary systems
The Bureau said delay costs were likely higher for larger creditors and those relying primarily on proprietary systems. [4] Those firms carried their own development teams and release schedules. Keeping teams ready for a later date, or redirecting them, had a direct cost.
Nonbank lenders and brokers
The rule applied to creditors and mortgage brokers alike, as the effective date commentary shows. [4] Brokers coordinated with several lenders, each of which had its own implementation plan. In our reading, a date change multiplied their coordination work by the number of lenders they used.
Correspondent lenders
The Bureau named one group specifically when it declined a dual compliance period: institutions that act both as correspondent lenders and originators. [4] It said dual compliance could be complicated for them, as well as for vendors and the secondary market. [4] In our reading, a firm that both originated and bought loans faced two cutovers: its own, and each seller’s. Its operations had to recognize which forms each purchased loan should carry.
Housing finance agencies and nonprofits
The rule reached public and nonprofit lenders too. The Bureau’s 2017 amendments adjusted a partial exemption that it said mainly affected housing finance agencies and nonprofits. [5] In our reading, these organizations, with smaller operations teams, faced the same date change as large lenders and the same dependence on systems they did not build.
Settlement agents and title companies
Settlement agents prepared closings under the new forms with each lender. The Bureau named broker and settlement agent coordination among the costs of delay. [4] The 2020 assessment later found that settlement companies’ median reported one-time implementation cost was roughly $39 per closing conducted in 2015. [6]
Objections, and where the argument stops
“The delay was a gift, not a cost”
The strongest objection is that the delay helped industry. Commenters most often justified extending the date on the basis that industry needed more time to prepare, according to the final rule. [4] Some asked for an even longer delay, to the start of 2016. [4]
We accept that the delay gave firms more time, and that commenters asked for it. The argument here is about what the delay revealed. The Bureau tied its choice to late system updates and testing. [3] That means industry readiness was not a matter of each firm’s own effort alone. In our reading, a delay that helps also exposes a dependency.
“A filing error tells us nothing about operations”
A second objection is that the CRA lapse was a one-off. Perhaps. But the cost of the one-off fell on operations: replanning, retraining and retesting. [4] The Bureau said many of these costs were largely incurred with the initial delay to the statutory date, before the extra weeks it chose. [4] In our reading, the lapse shows that a firm’s plan needs a way to absorb a date change, whatever causes it.
“The Bureau should have let the rule start August 15”
A third objection is that the Bureau should have used the earliest legal date. It considered that option and sought comment on it. [3] It concluded that a mid-month start and the short time to readjust would create challenges, and that October 3 was the earliest practically feasible date. [4] We take no view on whether that balance was right. The argument does not depend on it.
“The vendors were at fault”
A fourth objection runs the other way: that the episode shows vendors failed lenders. We do not draw that conclusion. The Bureau described delays in delivering system updates without naming anyone or assigning fault. [3] Vendors faced the same changing date as their customers, and a technology vendor was among the commenters who told the Bureau that adjusting from August 1 posed extensive challenges. [4] The argument is about dependency, not blame.
“Consumers bore no cost”
A fifth objection is that the delay cost consumers nothing. The Bureau disagreed. It said consumer costs would consist mostly of delayed benefits, chiefly better understanding of mortgage transactions and a greater ability to shop. [4] It said the longer the delay, the greater that cost, though it could not quantify it. [4] In our reading, this is why the Bureau kept the delay short.
“The later amendments show the rule was not ready”
A sixth objection points to the 2017 amendments. The Bureau said they memorialized its informal guidance on various issues and made clarifications and technical amendments. [5] Some might read that as proof the rule was unfinished in 2015. We read it as the Bureau described it: guidance put into the rule after the fact. [5] The argument here does not depend on whether the rule text was perfect in 2015.
Where the argument stops
We do not know how many firms were ready for August 1. The Bureau said many were well prepared; it did not give a count. [3] We do not claim the late updates were the main reason for the length of the delay. The Bureau gave several reasons, including consumer costs and settled expectations. [4] Our claim is narrower: the Bureau’s documents tie the date to system and testing realities.
Checks for leaders running a regulatory change
These are our own suggestions, not requirements of any rule.
Before the date
- Map every system and vendor that touches the regulated process, and the date each must deliver.
- Ask each vendor whether its delivery commitment moves if the regulatory date moves, and who pays for extra releases.
- Plan integration testing as its own milestone, with time protected if a vendor slips.
- Keep a record of training, testing and vendor communications as evidence of good-faith effort.
If the date moves
- Decide quickly whether to replan on a proposed date, and record the decision.
- Tell brokers, settlement agents and other partners the new plan, and ask for theirs.
- Refresh training close to the new date, rather than repeating it in full.
For boards and executives
- Ask management which outside parties could move a compliance date, and what the plan is if one does.
- Ask which vendors the firm depends on for each regulated process, and how their readiness is checked.
At cutover
- Know which rule applies to each file in the pipeline, and by what trigger: application date, closing date or another.
- Staff for a period of running both processes, and watch for application surges before the date.
- Track defects found after launch by system and vendor, so fixes go to the right party.
- Check that servicing and transfer teams know their own date for any notices the rule changes.
With hindsight
The Bureau issued its formal proposal on June 24, 2015, and it appeared in the Federal Register on June 26. [3] [4] Comments were due on or before July 7, 2015. [3] The Bureau said it received more than 1,300 comments, from trade associations, creditors, technology vendors, consumer advocacy groups and others. [4]
The final rule was dated July 20, 2015 and published on July 24, 2015, at 80 FR 43911. [4] Effective July 24, it moved the effective date from August 1, 2015 to October 3, 2015. [4] The Bureau adopted October 3 as proposed and made technical corrections to two provisions. [4] It did not adopt a formal grace period or a dual compliance period. It pointed instead to the good-faith approach in its Director’s June 3 letter. [4]
The rule took effect on October 3, 2015, as the Bureau’s later assessment confirms. [6] The Bureau then returned to the rule. On August 11, 2017, it published amendments at 82 FR 37656. [5] It said they memorialized its informal guidance on various issues and made clarifications and technical amendments. [5] They also created tolerances for the total of payments and extended coverage to all cooperative units. [5] They took effect October 10, 2017, with a mandatory compliance date of October 1, 2018. [5]
In October 2020, the Bureau published its assessment of the rule, required by section 1022(d) of the Dodd-Frank Act. [6] It found the forms improved prospective borrowers’ ability to locate key information and to compare offers, based on data collected in a laboratory setting. [6] It said evidence on whether the rule increased shopping was mixed. [6] It said it did not obtain or generate the data needed for a full benefit-cost analysis. [6]
The assessment also looked at firms’ costs. In a lender survey, the median estimate of one-time implementation cost was roughly $146 per mortgage originated in 2015. [6] The Bureau said that was 2.0 percent of the average cost of originating a mortgage that year, against its earlier estimate of about $135. [6] Lenders reported their largest implementation costs as new information technology systems, policies and training. [6] The Bureau cautioned that the surveys were voluntary and relied on recall, so may not be representative. [6]
For settlement companies, the median one-time cost was roughly $39 per closing in 2015, and the median respondent reported added ongoing costs of $100 per closing. [6] The Bureau said its original analysis had predicted negligible ongoing costs. [6] It found that guidance inquiries rose sharply from early 2015, peaked around the effective date and then declined, while cautioning that the decline might have other causes. [6]
What held up from June 2015 is the Bureau’s description of the rule as an operational change requiring coordination among many parties. [3] The firms that later reported their costs named technology, policies and training first. [6] What the episode adds is a reminder that a date set by law can move for reasons inside the regulator. [3] As checked on November 16, 2026, the assessment remains posted on the Bureau’s site.
Spotted an error? Tell us and we will check it and correct the article where needed.