Skip to main content
Promotional banner for a CUI buildout guide
Fixed Dates or Watch Lists: Where Should 2027 Effort Go?Regulatory Compliance
4 min readFor Risk Managers

Fixed Dates or Watch Lists: Where Should 2027 Effort Go?

Your 2027 regulatory calendar has two types of entries. Some have set dates you can plan for, like the GENIUS Act and the OCC's stablecoin rule on January 18, 2027, FDIC signage on April 1, 2027, and Section 1071 data collection on January 1, 2028. Others are pending, such as FinCEN's AML/CFT program rule, the CFPB's Section 1033 rewrite, Basel III endgame, and third-party risk management guidance. The practical question is how to allocate your Compliance Program budget between them.

Balancing Priorities

Risk managers often have plenty of information about regulatory changes but lack the capacity to address them all. Every Regulatory Obligation competes with exam remediation, audit follow-up, and daily operations for attention.

Two strategies have emerged. One suggests focusing on fixed dates first, giving pending rules minimal attention. The other advocates investing early in uncertain items, as their lead times may be too short once finalized. Both perspectives have merit and warrant consideration.

Why Focus on Fixed Dates First

This approach emphasizes accountability. A date set by statute or final rule is a commitment you can be examined against. For example, the OCC's final rule under the GENIUS Act takes effect on January 18, 2027, with no grace period. Missing it isn't a delay; it's a violation.

Proponents of this strategy highlight:

  • Avoiding wasted effort. Section 1033 is a cautionary tale. A federal court enjoined the CFPB's 2024 rule, and a revised proposal is under review. Teams that prepared for the original compliance dates wasted effort on now-irrelevant requirements.
  • Testable rules. You can assign ownership, set milestones, map affected policies and Compliance Controls, and test them before the effective date. This produces audit evidence, unlike speculative work.
  • Examiners value readiness. A documented applicability decision, a named owner, and a tested control set are easier to defend than assumptions about a rule not yet finalized.

Why Invest Early in Uncertain Rules

The opposing view focuses on lead time. FinCEN's revised AML/CFT program requirements would take effect 12 months after a final rule, and there's no set issuance date. Twelve months may seem ample until you consider the necessary program changes: revised risk assessments, updated policies, system changes, training, and model validation.

Supporters of early investment argue:

  • Regulators set the timeline. If a final rule publishes late in the year, your compliance period still starts immediately. Teams waiting for certainty may face pressure.
  • Rule-agnostic work pays off. Inventorying customer risk data, documenting your current AML program, and identifying system owners are beneficial regardless of the final text.
  • Late starts have costs. Section 1071's coverage depends on origination counts across look-back years, with 2027 as a key year. Lenders unaware of their coverage until late will have little time to build collection processes.

Practical Application

Most experienced teams avoid a binary approach. They tier the calendar.

Dated obligations with confirmed applicability receive full Compliance Program treatment: ownership, milestones, change mapping, testing, and status reporting. Dated obligations with unresolved applicability, like Section 1071 coverage, get a decision deadline. A rationale must be recorded to determine if the institution is in scope.

Pending rules go on a watch list with defined triggers, usually the publication of a final rule and its compliance period, and a pre-agreed first action. Technology aids this process. A GRC Platform with an Obligations Library links each Regulatory Obligation to the controls, policies, and systems it affects, allowing for quick impact analysis when a trigger fires. It also keeps the Regulatory Inventory current when a rule is enjoined or reproposed, as with Section 1033.

Set the lead time before each milestone in your policy, extending it for rules affecting core systems.

Our Recommendation

Prioritize fixed dates, but don't ignore the watch list.

Fixed dates deserve priority because the consequences are clear and the work is testable. However, pending rules carry a hidden cost: if you've done nothing before the trigger fires, you'll spend the first month scoping instead of building. The right investment for an unresolved rule is small and specific. Document applicability, name a provisional owner, map current-state controls, and define the trigger. Pause until the rule is final.

The tradeoff is real. This approach accepts that you'll sometimes do light preparatory work on a rule that gets withdrawn or rewritten. It also accepts that a compressed final-rule timeline will still hurt. What you gain is a defensible allocation of effort and a calendar your board can read as a plan rather than a list of worries.

Rank each calendar entry on two axes: how firm the date is and how long the build takes. Firm date, long build: start now. Soft date, long build: do the minimum preparatory work and set the trigger. Firm date, short build: schedule it and protect the milestone. This ordering, applied consistently, is the essence of regulatory change management.

Basel III

Promotional banner for the Penetration Report Template Kit

You Might Also Like