Executive Summary
For many financial institutions, deposit disclosure compliance does not break down at creation. It becomes most challenging during change.
Disclosures must be updated as products evolve, regulations shift, and business needs emerge, often on compressed timelines. Managing those changes accurately and consistently is where operational risk and internal friction tend to surface.
St. Mary’s participated in the CompliEditor beta program to evaluate a different approach to disclosure management. While the institution has not yet completed implementation, the beta experience provided a clear view into how CompliEditor is designed to support disclosure change once disclosures are live and in use.
This paper shares forward‑looking insights from that experience, using direct feedback from the St. Mary’s team to illustrate how early structure and clarity can position a financial institution for greater confidence and control in ongoing disclosure updates.
Rethinking the Disclosure Challenge
Deposit disclosures are living documents. They must remain aligned with regulatory requirements, institutional policy, and product strategy over time.
Many disclosure tools emphasize speed and simplicity at the point of creation. While that has value, it addresses only the starting line. The greater challenge begins after disclosures are approved and distributed, when institutions must respond to change without introducing unintended risk.
St. Mary’s entered the CompliEditor beta with the goal of understanding whether a more structured system could support that future state. The focus was not on eliminating all upfront effort, but on building a foundation that would make downstream change easier to manage.
Initial Setup as an Investment in Future Control
As with any structured compliance platform, the beta setup process required engagement and learning. For the St. Mary’s team, CompliEditor represented a new way of organizing and thinking about disclosure content.
“I think it was all new to us and every single thing we looked at, we really had to throw ourselves into it,” said Rhonda Lacombe, describing the beta experience.
Rather than viewing this as a barrier, the team recognized the setup phase as an investment. Once an initial disclosure was completed, the process became more clear and repeatable.
“Once we had one done that we could use as a guide, it was easier,” Lacombe said.
This early effort helped the team envision how future work would feel once disclosures were established and reused.
Understanding the Model Builds Confidence
CompliEditor separates disclosure content into organization information, policy content, and product outputs. While this structure required some orientation during the beta, the St. Mary’s team saw clear long‑term value in that clarity.
As the team worked through the beta, that distinction became more intuitive and more valuable. From a forward‑looking perspective, this structure gave the team confidence that future changes would be easier to manage because each type of update would have a clear home.
Looking Ahead: Managing Change Once Disclosures Are Live
While St. Mary’s has not yet completed implementation, the beta provided a strong preview of how CompliEditor is intended to support ongoing disclosure maintenance.
Once disclosures are built, the platform’s structure allows teams to work from an established baseline rather than starting over with each change.
“Once we had a baseline. It became much easier to understand how things connected,” said Rhonda Lacombe, describing how the system is expected to support future updates.
This forward‑looking benefit was central to the institution’s evaluation. Instead of treating each revision as a standalone project, CompliEditor is designed to support incremental, controlled change within an existing framework.
Anticipating Easier Review and Approval
One of the capabilities that stood out during the beta was CompliEditor’s proof output, which visually distinguishes standard language from institution‑entered content.
For the St. Mary’s team, this transparency is expected to play a meaningful role once disclosures are in active use.
“Being able to see what was entered versus what was standard made it easier to review,” said Rhonda Lacombe.
Looking ahead, this level of visibility is expected to support faster internal reviews and more confident approvals by making changes immediately clear to reviewers and stakeholders.
Designed for Real‑World Change
Change rarely arrives under ideal conditions. Product updates, regulatory guidance, and operational needs often overlap.
Based on the beta experience, the St. Mary’s team viewed CompliEditor as a system designed for those realities. Once users understand where different types of content belong, the platform is expected to support more controlled and predictable updates.
That sense of control is particularly important for teams preparing to manage disclosures over time, rather than simply creating them once.
Preparing for Long‑Term Disclosure Confidence
The St. Mary’s beta experience highlights an important consideration for financial institutions evaluating disclosure technology.
Ease of initial setup is only part of the equation. The more critical question is how well a system supports change once disclosures are live.
CompliEditor requires engagement at the beginning. In return, it is designed to provide clarity, structure, and confidence as disclosures evolve.
“Once we got through the initial learning, it made a lot more sense how we would manage changes going forward,” said Rhonda Lacombe.
For St. Mary’s, the beta offered a clear view into how CompliEditor could support a more sustainable and controlled approach to disclosure change in the future.