The Legal Landscape: What’s Required?

In the United States, federal and state laws impose strict requirements on records retention, particularly for public entities and regulated industries. The Federal Records Act mandates that government agencies preserve records that document the organization, functions, policies, decisions, and essential transactions of the agency. Similarly, the Freedom of Information Act (FOIA) and state-level open records laws require that certain communications be accessible to the public.

For private-sector organizations, regulations like the Sarbanes-Oxley Act, HIPAA, and SEC Rule 17a-4 impose retention requirements that can span years. These laws apply to all communication mediums (email, text, or encrypted messaging), requiring organizations to retain any qualifying business record.

Messaging Apps and Auto-Deletion: A Risky Combination

Apps like Signal and Telegram offer auto-delete features that can erase messages after a set period—sometimes in as little as 30 seconds. While these features enhance privacy, they can also undermine compliance if not properly managed. Without a clear Records Retention and Disposition Schedule (RRS), organizations risk losing critical data, legal penalties, and damaging public trust.

Case in Point: Denver’s “Strike Force”

In early 2025, Denver Mayor Mike Johnston and 14 senior staff members formed a group dubbed “Strike Force” to coordinate the city’s response to the migrant crisis. They used Signal, an encrypted messaging app, and enabled auto-deletion for their communications. This decision came just weeks after legal watchdogs filed open records requests related to the city’s handling of the crisis.

Critics, including the Colorado Freedom of Information Coalition, argued that this was a deliberate attempt to circumvent transparency laws. Although the mayor’s office later adjusted the auto-delete settings and eventually disabled them, the damage to public trust was already done.

Lessons for RIM Professionals

This incident underscores the importance of proactive records management policies. Here are key takeaways:

• Audit Messaging Tools: Know and regulate which platforms your employees use and know whether they support auto-deletion or encryption. Ensure disposition practices align with policies and procedures.
• Update Your RRS & PIM Policy: Ensure your retention schedule and records and information management policy account for records and non-records in all communication channels, including ephemeral messaging apps.
• Train Staff: Employees must understand that convenience should never override compliance.
• Implement Governance Tools: Use enterprise-grade solutions that integrate with messaging platforms to archive and manage records automatically.

Zasio Can Help

At Zasio, we specialize in helping organizations navigate the complexities of modern records management. Our solutions are designed to ensure compliance across all communication platforms, including those with auto-delete features. Whether you’re updating your RRS or conducting a compliance audit, Zasio provides the tools and expertise to keep your organization protected.

Disclaimer: The purpose of this post is to provide general education on information governance software. The statements are informational only and do not constitute legal advice. If you have specific questions regarding the application of the law to your business activities, you should seek the advice of your legal counsel.

The post Hidden Dangers of Poor Records Retention Policies in Messaging Apps appeared first on Zasio.

What is an event trigger?

Also known as “event-based retention,” event triggers start the disposition process by providing a specific occurrence that begins the specified period required before disposition. An event trigger often aligns with the natural lifecycle of a record. For example, a common event trigger for personnel records is “Duration of Employment.” This is in line with the lifecycle for a personnel record and its usefulness, spanning the creation beginning at the time of hiring through the end of employment. Once the employment ends, the fixed retention period begins. Duration of Employment + 7 Years is a common retention period for these records.

Beyond practical lifecycle considerations, event triggers may be mandated by legal regulatory requirements, as is the case for personnel records. Effective and compliant event triggers need to consider both lifecycle and regulatory factors.

Why are event triggers so triggering?

When the requisite event has either begun or concluded is often difficult to determine. In the case of “Duration of Employment,” your HR department can provide information about an employee’s “Duration of Employment.” To begin the period of retention, this trigger determination is contingent on getting additional information. Many event triggers require coordination and input from multiple individuals, adding a hurdle to the disposition process.

In contrast, a retention of “Creation” or “Calendar Year” can easily be automated within a system and is not contingent upon additional information. These simplified and straightforward “flat” retention periods are preferred and more easily actionable. Fewer hurdles equal a higher likelihood of adherence and effective disposition.

Each of these event triggers can be calculated to occur within one year. So, by adding on a year and using a default creation date as the trigger, you create a simplified retention period as tracking creation is much easier and allows you to standardize. While you may add some time to the retention period by rounding up, the amount of time is small, and the benefit from increased adherence typically outweighs any drawbacks.

Calculable Retention Periods

Products

Some of the most difficult event triggers to implement are those tied to a specific event that has wide variation and may require input from multiple knowledgeable individuals to determine when an event has been triggered. Here are a couple of the biggest offenders:

These event triggers are used for a few reasons. Primarily, there are often regulations and standards that require certain records to be kept for the duration of the life of a product or following the shelf life or expiration of a lot, batch, or other type. This is to ensure records are made available in case of a quality issue or recall, for instance.

Additionally, these triggers speak to the records lifecycle as certain records that support design certifications or marketing authorizations need to be kept for as long as a product is on the market. Often, it’s possible to calculate the life or shelf life of a product. For instance, if the expected life of a drug is 1 year,  a shelf life of 1 year plus 5 years would equal a total retention period of Creation + 6 Years.

For each, you may gather additional information to get a sense of when and how frequently these events trigger. For example, many record types are periodically reviewed and superseded on an annual basis. When that happens, superseded (1 Year) plus 3 years would result in a simplified retention period of Creation + 4 Years. If the lifecycle of a project is typically no more than 2 years, then project completion (2 Years) plus 5 years equals 7 years. Depending on the complexity and diversity of your organization’s processes and their related records lifecycle, you can use a similar type of determination for the other event trigger categories listed above.

But Can I Get Rid of All Event Triggers?

Unfortunately, despite your best efforts, you’ll still find it difficult to get rid of some event triggers. “Duration of Employment” is a good example of a necessary event trigger. This is due to the variability in the amount of time of employment, regulatory recordkeeping requirements, and personal information risks for over-retention. A simplified calculated retention period for “Duration of Employment” runs the risks of either under or over-retention for specific employee records.

Conclusion

Retention schedule simplification is a growing trend, especially when it comes to implementing retention periods across systems with varying event trigger capabilities. With a little investigation, you can simplify many types of event triggers within your organization’s records retention schedule. It’s helpful to gather insight from stakeholders who can confirm essential information. Calculable retention periods depend on details surrounding records lifecycles and the nature of various products. But this effort on the front end will pay off through increased records retention schedule adherence, hopefully leaving you tickled instead of triggered.

Disclaimer: The purpose of this post is to provide general education on Information Governance solutions. The statements are informational only and do not constitute legal advice. If you have specific questions regarding the application of the law to your business activities, you should seek the advice of your legal counsel.

The post Tired of Getting Triggered by Retention Event Triggers? Try Simplifying. appeared first on Zasio.

The integration means it’s now possible to directly manage records retention in your electronic document repositories.

“Zasio is the first company in the market to offer such a powerful solution: The ability to apply our legal research capabilities directly to electronic documents, including third-party repositories such as SharePoint, One Drive, etc.,” said Kevin Zasio, founder and president.

The process also works seamlessly with shared network folders that can have retention policies applied directly to documents. You can watch a demonstration of the process below.

Zasio has helped thousands of organizations build, maintain, and revise records retention schedules—through both consulting services and software solutions. But having a schedule isn’t enough. In fact, having a retention schedule and not applying it to your records can actually be worse than not having one at all.

“Many companies have made great strides in developing and enhancing their records retention schedule, but very few have actually put it into practice on digital repositories–making it operational throughout their infrastructure,” said Warren Bean, senior sales engineer at Zasio.

Thanks to the new integration of the Versatile software, the process, and efficiency of applying retention to your repositories become easier for you and your organization.

Have questions? Feel free to reach out to sales@zasio.com or by calling 800-513-1000 option 1.

The post Zasio Software Allows Users to Directly Manage Records Retention in Electronic Document Repositories appeared first on Zasio.

In the world of records and information management (RIM), legal research plays a critical role by providing the foundation for a solidly defensible records management program. Legal research ensures that statutory and regulatory recordkeeping obligations have been considered and accounted for, particularly within record retention schedules.

Although legal research can be simply defined—identifying and retrieving the laws applicable to a particular set of facts to inform legal decision-making—in practice, legal research can be a mammoth project to take on. In today’s world of remote work and multi-national corporations, your business can find itself with operations across many jurisdictions, subject to dozens of regulatory bodies, all with different sets of recordkeeping requirements. Locating relevant laws in even just one jurisdiction can be a lengthy process (here’s looking at you, California). Luckily, that’s where the research colleagues at Zasio can help. We specialize in legal research to find, capture, and curate thousands of recordkeeping requirements across many industries and countries, and keep those requirements updated as laws change.

Let’s take a peek at what this process looks like.

Who, What, Where?

As with any research, the project’s scope must be clearly defined to optimize the research process. To that end, the hunt for recordkeeping requirements begins with answering three basic questions:

Who are the regulated entities?

What business products, services, activities, and record types are at issue? And,

Where are the regulated parties, business activities, products, or services located?

The answers to these questions set the parameters of the legal research project, whether it’s narrow and highly specialized, or it covers a broad range of activities and parties.

Once a project’s scope is set, we need to find the sources which contain the applicable laws in each jurisdiction (such as the country or state).

Straight from the Source

The best way to find and capture current and complete recordkeeping requirements is to pull them right from the source. In legal research, “primary authority” means the law itself. Laws can be statutes, regulations, decrees, orders, and other rules issued by a legislative body or regulatory authority.

For Zasio researchers, that means using public-facing official government websites, as well as subscriptions to legal databases, to find laws relevant to a research project. While secondary sources (like university websites or law firm articles) can provide useful information and direction, we primarily review laws from their primary source (where possible). Where the legal text isn’t accessible through the primary source, we turn to trusted and reliable secondary sources that make the text available.

Because we’ve already conducted extensive research in over 140 countries, we have the most relevant primary sources already identified and readily accessible in Zasio’s proprietary research database. This database forms the backbone of Zasio’s Versatile Retention SaaS and on-premise software offerings. When we run into a new jurisdiction, we conduct a thorough and systematic search for authorities to use as sources. We look to the main legislative bodies of a country or state, as well as any regulatory authorities such as ministries, agencies, or government departments that may govern either the relevant activities or parties.

These authorities can be located through resources like the United States Library of Congress website (which has guides for many countries identifying the executive, judicial, and legislative authorities), or by running a native language query using everyone’s favorite search engine.

The Methodology

When examining a source for potential recordkeeping requirements, reading every law a country has implemented wouldn’t be a particularly efficient (or enjoyable) use of time. Instead, we leverage the search features and filters the source makes available to craft keyword and Boolean searches to find relevant laws with language consistent with recordkeeping requirements.

For sources that include the feature, Boolean search operators are used to tailoring queries for laws that contain at least one term that is: (i) related to the regulated activities or parties, (ii) synonymous with retention or preservation, and (iii) associated with records or information (as well as other limiting factors).

Zasio researchers have seen A LOT of recordkeeping requirements, and they all tend to use similar terminology, phrases, and patterns of language. We use this knowledge and experience to run searches covering a wide range of regulated activities and parties in a systematic fashion until we can be certain that we’ve located all relevant laws within a particular source.

Depending on the search filters and sorting capabilities of a source, we can also narrow our search results using date ranges or categories associated with responsible agencies.

For sources with less advanced search features, we turn to other options and find creative solutions. Some sources organize laws by topic or subject, or by the issuing ministry or department. Other sources may only arrange their laws alphabetically, although generally, these jurisdictions have very few laws in force.

Regardless of the source’s search features, the key is to approach each source in a logical and consistent fashion. As laws turn up that meet the parameters of the project’s scope, we review the legal text to identify possible recordkeeping requirements.

So, what types of requirements are Zasio researchers looking for exactly?

Recordkeeping Requirements by Type

Recordkeeping requirements identified by Zasio researchers fall into four basic types:

• Regulation requirements can be summarized as the duration of retention requirements. In other words: regulated party + record + minimum or maximum retention duration.
• Handling requirements deal with how records and information must be handled. These include requirements relating to: format, media, location, movement, cross-border transfers, language, data protection and destruction measures, sanitization and anonymization of protected personal information, and sanctions or penalties for recordkeeping violations.
• Data privacy requirements include requirements relating to notice, privacy breach notification and response, data subject choice and consent for use or processing, purpose limitations, individual data subject rights with regard to their own personal information, retention limits, data transfers, system and security requirements, process type requirements, and fines, penalties, and claims.
• Statutes of limitation requirements are just what they sound like—limitations or prescriptions that define how much time litigants have to bring certain causes of action and legal claims. Duration of intellectual property rights are also included in this type of requirement.

Each requirement is captured as a citation, which is broken down into key information fields that allow for easy location, application, and readability in Zasio’s Versatile Retention software or SaaS offerings. The most crucial of these include:

• Jurisdiction;
• Title of the law;
• A concise record description;
• Regulated party or parties;
• Retention period, handling requirement, or limitation period combined with the triggering event; and
• Relevant portions of text.

Happy Hunting!

Hopefully, your own forays into legal research prove successful; however, we also know that mastering the nuances of RIM legal research is not everyone’s cup of tea. For those who do not consider themselves RIM legal research gurus, and would prefer to capitalize on the collective wisdom and accumulated research of dedicated legal professionals, check out Versatile Retention, Zasio’s retention schedule management and research solution.

Disclaimer: The purpose of this post is to provide general education on Information Governance topics. The statements are informational only and do not constitute legal advice. If you have specific questions regarding the application of the law to your business activities, you should seek the advice of your legal counsel.

The post Legal Research and RIM – A Primer on Methodology appeared first on Zasio.

Most RIM practitioners can build a strong case for a good records management and retention policy – it can help avoid litigation, save on discovery costs, and limit the impact of a data breach. But what about using RIM as a way to elevate your company in the eyes of customers? One way to achieve this is through obtaining advanced certifications developed by the Industry Standards Organization (ISO).

The ISO develops “families” of internationally recognized standards companies can use to develop and certify their business processes. Two ISO standards that rely heavily on RIM are the ISO 9000 family on quality management and the ISO/IEC 27000 family on information security management. Both have stringent document information requirements.

Let’s start with the ISO 9001 Certification
ISO 9001, one of the more well-known ISO standards, is the only standard in the ISO 9000 family to which a company can be certified. This certification is available to any organization, regardless of size or industry, and is based on quality management principles like having a strong customer focus, top-tier management, and a business plan showing an approach and process for continual improvement.[3] Currently, there are over one million companies in over 170 countries that have achieved the ISO 9001 certification. Certification can be one of the most effective ways to alert consumers that your quality management system is consistent and products and services are good-quality.[3] This in turn brings business. So, to the millions of companies not yet 9001 certified, you may be wondering how to achieve such certification and how RIM plays into this process.

Achieving ISO 9001 Certification
To earn ISO 9001 certification, you must implement an ISO 9001 quality management system. Once you feel ready, you may select an external registrar to audit the performance of your organization. Upon earning a passing review, the registrar will issue the ISO 9001 certificate, which is good for three years. [4] Now, here’s where having a strong RIM program is beneficial, if not essential.

A Strong RIM Program Is Key to ISO 9001 Certification
For the audit, your organization will need to create, maintain, and retain certain documents to show, on paper, how its quality management system follows the ISO 9001 standards. These records must adhere to the documented information requirements of ISO 9001 clause 7.5 which outlines the following document types you must maintain:

• The scope of the quality management system (clause 4.3).
• Documented information necessary to support the operation of processes (clause 4.4). Examples include organization charts, process maps, process flow charts and/or process descriptions, procedures, work and/or test instructions, specifications, documents containing internal communications, production schedules, approved supplier lists, test, and inspection plans, quality plans, quality manuals, strategic plans, and forms.
• The quality policy (clause 5). The quality objectives (clause 6.2).[5]

Clause 7.5 also identifies the following document types that you must retain:

• Documented information to the extent necessary to have confidence that the processes are being carried out as planned (clause 4.4).
• Evidence of fitness for purpose of monitoring and measuring resources (clause 7.1.5.1).
• Evidence of the basis used for calibration of the monitoring and measurement resources (when no international or national standards exist) (clause 7.1.5.2).
• Evidence of competence of person(s) doing work under the control of the organization that affects the performance and effectiveness of the QMS (clause 7.2).
• Results of the review and new requirements for the products and services (clause 8.2.3).
• Records needed to demonstrate that design and development requirements have been met (clause 8.3.2).
• Records on design and development inputs (clause 8.3.3).
• Records of the activities of design and development controls (clause 8.3.4).
• Records of design and development outputs (clause 8.3.5).
• Design and development changes, including the results of the review and the authorization of the changes and necessary actions (clause 8.3.6).
• Records of the evaluation, selection, monitoring of performance, and re‐evaluation of external providers and any and actions arising from these activities (clause 8.4.1).[5]

That is a lot of information!

So, What is the Best Way to Manage and Retain All of These Records and Documented Information?
The first step is to figure out what you have, where it’s all located, and how it should be organized. Then, catalog it in a retention schedule so you can be sure you’re retaining the necessary records for your future ISO audits. You also must track the location and retention of the documents required by Clause 7.5 in a records management system and dispose of unnecessary information (since we know too much information can be a liability). Sounds simple enough, right?

Alternatively, you can reach out to Zasio. Our team of in-house consultants can review your records to identify what you have, develop a retention schedule for you, and deliver it in Versatile Retention, our leading retention management solution. Once you have your retention schedule, you can easily apply it to your physical and electronic records using one of Zasio’s Versatile records management solutions. Then, when it’s time for your ISO 9001 audit, your information will be at your fingertips, helping ensure your company aces the documented information requirement.

Now Let’s Jump to the ISO/IEC 27001 Certification
While ISO 9001 concerns quality management systems, ISO 27001 is all about information security management systems (ISMS). But similar to ISO 9001, companies must build a system and show how the system was established, implemented, and the processes for maintaining and continually improving it.[6]

The ISO 27001 standard not only ensures an organization has an ISMS, but through its requirements, it also certifies that companies are compliant with applicable laws and regulations.[8] Information security concerns every organization, so keeping up with ISO 27001 requirements is a great way to help stay compliant with current regulations. Further, should you ever face an information security incident, ISO 27001 certification can help demonstrate due diligence regarding regulatory compliance.

What Kind of Information Security Requirements are in the ISO 27001 Standard?
Information security requirements may vary depending on your industry but in general, the information security requirements you can expect to see include:

• A.18.1.1. – Identification of Applicable Legislation and Contractual Requirements.
• A.18.1.2 – Intellectual Property Rights.
• A.18.1.3 – Protection of Records.
• A.18.1.4 – Privacy and Protection of Personally Identifiable Information (PII).
• A.18.1.5 – Regulation of Cryptographic Controls.[8]

The ISO 27001 Audit Process
So how do you prove ISO 27001 compliance during a certification audit? ISO/IEC 27001:2013 (the most recent revision) has a documented information clause that is very similar to ISO 9001’s clause 7.5. Accordingly, clause 7.5’s process for document retention applies here as well.

Conclusion
Becoming ISO 9000 certified for quality management or ISO 27001 certified for information security is a great way to ensure your company is performing to the highest level of standards and regulatory compliance. It also shows customers your company is a trusted business partner. Plus, it’s a perfect excuse to review your company’s information and strengthen your RIM program which provides more benefits than just ISO certification. Just about all cybersecurity frameworks—such as NIST, CSA-CCM, SOC 2 Type II, and COBIT—require records retention, so a strong RIM program will help your organization achieve maturity in those standards, as well.

[1] https://techjury.net/blog/how-much-data-is-created-every-day/#gref
[2] https://www.ibm.com/security/data-breach
[3] https://www.iso.org/iso-9001-quality-management.html 
[4] https://the9000store.com/what-are-iso-9000-standards/what-is-iso-9001/
[5] https://www.iso.org/files/live/sites/isoorg/files/archive/pdf/en/documented_information.pdf
[6] https://www.iso.org/standard/54534.html
[7] https://www.standardfusion.com/blog/iso-27001-18-1-1-satisfy-legal-regulatory-contractual-requirements/
[8] https://www.isms.online/iso-27001/annex-a-18-compliance/
[9] https://www.isms.online/iso-27001/determining-the-scope-for-your-isms/

Disclaimer: The purpose of this post is to provide general education on Information Governance topics. The statements are informational only and do not constitute legal advice. If you have specific questions regarding the application of the law to your business activities, you should seek the advice of your legal counsel.

The post ISO Compliance and Cybersecurity Reporting – Yet Another Way to Strengthen Your Records and Information Management Program appeared first on Zasio.

Consolidated Natural Gas, which later merged into Dominion Energy, has been using Versatile™, Zasio’s enterprise-level records management software, for over 25 years. They started out with Versatile for Windows™ and upgraded to Versatile Enterprise ™ in 2000. When the records team at Consolidated Natural Gas initially began looking for a records management solution, they needed something to help them streamline their existing records management process, which was very manual. Not long after their search had begun, Consolidated Natural Gas decided to bring the record center data from their entire system under one management system, which meant merging the data from five different sub-companies’ records centers into one. These two factors were what initially pushed Don Campbell, Supervisor of Administrative Services at Dominion Energy, to implement Versatile, but over the years, it has been the scalability and flexibility that Versatile Enterprise provides, along with Zasio’s top-tier customer service, that has retained them as a customer for over two decades.

Why Versatile Enterprise?

Don originally saw Versatile Enterprise demonstrated at an ARMA International event. At the time, its speed was what stood out. “It was instantaneous. The data went right into the system. There was no waiting for processing to happen or needing to verify—it was just working,” Don said. Since then, the team has been through several versions of Versatile Enterprise, each update offering new and improved features.

Implementing Versatile Enterprise

When Consolidated Natural Gas originally implemented Versatile Enterprise in 2000, they said it was a straightforward transition. The majority of their records data was stored in Excel™ spreadsheets, so it simply needed to be imported into the Versatile Enterprise database. Zasio Support made the implementation painless. “It was great, we more or less just verified things and our Support Technician handled everything with our IT team,” Don recalls. “She would guide them along, they would ask her questions, she would provide more guidance; it was fantastic.” Of the whole implementation, Don and Dwayne agree the hardest part was barcoding all of their boxes. “It was very challenging to get all of the barcodes on all of the boxes and all of the shelves,” said Dwayne, “but the barcoding system and scanners from Zasio were really helpful. It was a big project. We had 35,000 to 40,000 boxes at our largest records center, and the scanners made it doable for just the two of us.”

Time-Saving Features

While the whole system is lined with unique features and functionality, two of the features that the Dominion Energy Team use most frequently are Destruction and Space Management.

Destruction

Don handles all of the destruction reviews. “The destruction reports I can build out of the system are fabulous,” he says, “it makes life so much easier for the customers (employees in other departments at Dominion) to be able to follow along, see what they have, read the record descriptions, and know when they’re up for review.” It has also been a timesaver. Don used to send out destruction reports monthly, but now he only needs to send them annually. “I can send a whole year’s worth of reports and get approvals and then just destroy records when the dates come up,” Don said. The actual destruction process is easy too. Dwayne Kieger, Sr. Records Analyst, manages this part. “We simply feed in spreadsheets and the system determines what should be destroyed.” We’re able to easily destroy an average of 5,000 to 6,000 boxes per year,” he says.

Space Management 

The Space Management feature allows the team to consolidate and organize their warehouse space on a regular basis, but it has also saved the team in two unique situations: when they moved their records offsite for a short time, and when they merged to become Dominion Energy. When the records were stored offsite, Don and Dwayne were still able to manage and control them within their system. “We could track them and know what was going on with them, which was wonderful because the offsite company made a lot of mistakes,” said Don. It also made it easy to bring them back in-house, once the time came. A few years later when Consolidated Natural Gas merged with Dominion Energy, the team was able to use the Space Management feature to reorganize the Dominion Energy record centers. “Dominion would use a location but put it under a temporary ID, so if ten boxes were on a shelf, all ten would have the same number, which made things really hard to find,” said Don. “They needed help and Space Management made this easier.”

Versatile Web Enterprise™

Versatile Web Enterprise, an add-on module for Versatile Enterprise, allows users in an organization to access and edit specific records, without needing access to the full Versatile Enterprise application. For Don and Dwayne, Versatile Web really helped during the initial merger with Dominion, which brought thousands of new customers into the system, and it continues to allow them to manage the entire organization’s customer base of over 20,000, with a small records team of only six or seven. “The customer base has grown exponentially over the years and because we use Versatile Web, it’s easy to manage,” said Don. Dwayne agreed, “the web add-on is very straightforward, our customers never seem to have any issues with it once we introduce it to them.” They’ve also noticed the quality of the information entered into the system has improved. “With Versatile Web, we get much better descriptions than we used to, and it’s not just because of our training, it’s because it’s easy to understand,” said Don.

The Customer Support

While impressed with Versatile Enterprise, Don and Dwayne can both say the biggest selling point for them in keeping their business with Zasio is the customer support. “It’s just wonderful, said Don. “It’s definitely worth the annual fee, and if I’m ever challenged on it, I can just show them. Look we’re managing all of these records and all of these people, and we never have issues, because we have support. When we need help, it’s right there.” With Dominion’s recent upgrade to Versatile Cloud™, Zasio’s new cloud hosting platform for Versatile Enterprise, Zasio Support plays an even larger role. “Now that we’re on the cloud, we can deal with Zasio Support directly and get answers,” said Dwayne. “Before we were tied to our IT group. It’s so much better working directly with people who know the system and let me tell you, they definitely know their stuff!” he said.

Results

Since 2000, Versatile Enterprise has saved the Dominion Energy team time in their daily tasks, helped them consolidate warehouse space, bridge mergers between companies, combine multiple data sets, and manage exponential customer growth. While their system looks completely different than it did when it was first implemented, the basis of their original decision to purchase Versatile Enterprise remains the same – it’s a scalable, versatile solution, that comes with great customer service. Today, it just has a modern look, with their data servers and applications now hosted off- premise in Versatile Cloud, and their move away from their old barcode scanners to the Versatile Mobile Package™, which allows all of their barcoding work to take place on their mobile iOS devices via the Versatile Records On-The-Go™ app. Both of these upgrades are still new, but the Dominion Team couldn’t be more excited to test them out and continue the relationship with Zasio.

The post Versatile Enterprise™ Case Study: Dominion Energy appeared first on Zasio.

Author: Jennifer Chadband, IGP, CRM, ECMp

Senior Analyst / Licensed Attorney

The post Wait, Is That a COVID-19 Record? appeared first on Zasio.

The post ARMA ‘Virtual’ InfoCon 2020 – October 26-30, 2020 appeared first on Zasio.

During the webinar you’ll learn:

• Questions records managers should ask their business units to get a starting point for their research.
• Resources and tips for records managers conducting legal research.
• Strategies for mapping legal requirements to your records retention schedule.

The post Researching and Analyzing Legal Records Retention Requirements appeared first on Zasio.

• What is a records retention schedule, and how do they function within an organization?
• Why do organizations need to create one, and what benefits do they provide?
• How do I go about designing one from the ground up?
• How can I apply legal research to set retention periods
• How can I keep my schedule up to date as recordkeeping regulations change in the future?

The post Retention Schedules 101 appeared first on Zasio.