Know Where You Stand: Assessing Governance Maturity Before You Plan
LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD Week 2 of 12 The first article in this series made the case for funding governance proactively, during planning season, instead of reactively, after an incident forces the conversation. That case only works if it starts from an honest picture of where the organization stands. You cannot plan what you have not assessed, and you cannot fund what you cannot describe. Most organizations skip this step, or shortcut it. They plan from the policy manual, from what the last audit said two years ago, or from what leadership believes to be true based on how the program looked when it was built. None of those sources reflect current state. They reflect a version of the program that may no longer exist. Why Assessment Has to Come First A governance investment sized against the wrong starting point fails in predictable ways. It underfunds a gap nobody realized had grown that large. It overfunds a capability that was already further along than assumed. It sequences work in the wrong order, addressing a visible symptom before the structural issue underneath it. And when the investment is reviewed for renewal, the numbers do not hold up, because they were never built on an accurate baseline to begin with. Assessment is not a formality that precedes the real work. It is the foundation the rest of the plan stands on. Skipping it does not save time. It moves the cost of getting the baseline wrong to a later point in the process, where it is more expensive and more visible to fix. What a Maturity Lens Actually Looks At A useful governance maturity assessment does not ask whether policies exist. Most organizations already have retention schedules, classification frameworks, and disposition policies on paper. The more revealing question is whether those policies are executed consistently, across business units, systems, and data types, or whether execution depends on which team happens to be paying attention this quarter. That distinction points to the dimensions worth assessing directly: whether retention practice matches documented policy in the systems that actually hold the data; whether the organization has visibility into what data exists and where, particularly outside the systems that were built with governance in mind; whether ownership and accountability for governance outcomes are assigned to specific roles, or diffused across a committee that meets quarterly; and whether the technology in place enables consistent execution, or requires manual effort to compensate for what the systems cannot do on their own. Each of these can be scored honestly, on a simple scale from ad hoc to managed to consistently operational, without turning the exercise into a multi-month audit. The goal is a clear, defensible picture, not an exhaustive one. Consider a retention schedule that looks complete on paper but is enforced in only two of the twelve systems that hold the data it covers. A policy review alone would score that program well. A maturity assessment focused on execution would score it accurately: strong on documentation, weak on operational consistency, and exposed everywhere the schedule is not actually applied. That is the gap planning season needs to see. The Honesty Problem The hardest part of this exercise is rarely technical. It is organizational. Teams that have worked hard to manage around a gap tend to describe that gap as smaller than it is, not out of dishonesty, but because the workaround has become normal. A retention schedule enforced manually by one diligent records manager looks, from a distance, like a functioning program. It is not the same as a program that would keep functioning if that person left tomorrow. An accurate assessment must separate what the organization has documented from what would happen under audit, litigation, or a regulatory inquiry. That separation is uncomfortable to surface internally. It is far more comfortable to surface it now, during planning, than to have it surface itself later, during an incident. A Practical Way to Locate Gaps The most useful version of this assessment is one leadership can act on, not one that sits in a binder. That means keeping it focused on a small number of dimensions, scoring each one against current practice rather than stated policy, and pairing every gap identified with a plain description of what it costs the organization to leave unaddressed. A gap without a cost attached rarely survives the next round of budget prioritization. It also means resisting the instinct to assess everything at once. A maturity lens applied narrowly to the areas most exposed to risk or most central to the next planning cycle, produces a picture leadership can use immediately. A maturity lens applied everywhere produces a report that takes months to finish and arrives after the budget conversation has already happened without it. The assessment also works best as a shared exercise rather than a single function’s report. Legal sees exposure that IT does not. IT sees where data lives in ways records management assumptions often miss. Business units know where workarounds have quietly become standard practice. Bringing those perspectives together before the numbers go to leadership produces a picture that holds up when it is questioned, rather than one that unravels the first time someone outside the exercise looks closely at it. What This Sets Up An honest maturity picture does more than support a smarter plan. It becomes the evidence base for everything that follows in this series: the cost of the status quo, the business case that gets funded, and the roadmap leadership can approve with confidence. Every one of those depends on starting from where the organization really is, not where it was assumed to be. The Bottom Line Planning season rewards organizations that show up with an accurate picture of their own governance program, not the most polished one. An honest maturity assessment, focused on execution rather than policy language, gives leadership something they can act on and something the program can be held to later. That is a stronger position than a confident guess, and it is the only foundation a governance investment can be built on. Next in the series: The Real Cost of the Status Quo, a practical look at what unaddressed governance gaps are already costing
The Governance Conversation Nobody Schedules Until It’s Too Late
LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD Week 1 of 12 Most governance programs are not planned. They are triggered. An audit finding surfaces a retention gap that should have closed years ago. A breach investigation reveals that nobody can say with confidence what data exists, where it lives, or why it is still there. A litigation hold turns into a six-month search because the organization never built the infrastructure to answer basic questions about its own records. In each case, governance gets funded, eventually, after the cost has already been paid in a different form. This pattern is familiar to nearly everyone who has worked in information governance, records management, or compliance. It is also avoidable. Planning season, the annual window when budgets are built and priorities are set for the year ahead, offers a predictable chance to plan and fund governance before an incident drives the decision. A Timing Problem, Not an Awareness Problem The gap between knowing and funding shows up the same way in most organizations. Legal flags the retention exposure. IT flags the volume of unstructured data with no clear owner. Compliance flags the audit finding that never fully closed. Each function raises the issue on its own timeline and competes against other priorities that already have a budget line and a sponsor. Without a coordinated case, governance often loses that competition because it reaches the table without a clear, fundable plan. The gap is rarely about awareness. Most legal, compliance, and IT leaders already know their retention practices are inconsistent, that structured and unstructured data have grown faster than any plan to manage them, and that AI initiatives are advancing without the governance foundation to support them safely. The knowledge exists. What is usually missing is a process that turns that awareness into a funded plan before an incident forces the issue. Reactive funding carries a cost beyond the incident itself. It compresses a program that should be built deliberately into a response that has to move immediately. Governance becomes crisis management instead of infrastructure, and point solutions are often built to close a single gap quickly without creating a program that can hold up over time. Why This Series, and Why Now Publishing this series from late summer into fall is intentional. It lines up with the planning and budget cycles most organizations are already running. The goal is practical: to give readers language and frameworks they can use directly to build the internal case for governance. This series is a guide to that work: assess honestly, prioritize what matters most, build the case in terms leadership can act on, and sequence the work into a program leadership can approve and sustain beyond the first year. It then applies that same discipline to the newest pressure on the data environment: AI and the governance foundation it needs to scale responsibly. This builds directly on the previous series, which made the case for treating retention as infrastructure instead of a project with an end date. That foundation is the starting point here. This series picks up the next question: how do you plan and fund the program needed to put that foundation into practice? From there, we will look at extending it across the broader data environment and, ultimately, into AI. What Honest Assessment Requires None of this works without an honest look at where the organization stands. Not where the policy says it stands. Not where it stood at the last audit. Where it stands today, across retention practice, data visibility, and the operational discipline to execute consistently rather than in pockets. That assessment can be uncomfortable for organizations that have managed around gaps instead of closing them. It is worth doing anyway. A governance investment based on an inflated view of the current state will be sized and sequenced incorrectly, making it difficult to defend when renewal comes up. An accurate assessment gives the investment a far better chance of being funded, sustained, and credited when it works. The second article in this series focuses on that work. It provides a practical assessment leaders can use to identify gaps and gauge readiness before taking a plan or dollar figure to leadership. What This Means for Planning Season For organizations heading into budget cycles this fall, the opportunity is straightforward. Planning season already asks every function to make its case for the year ahead. Governance can enter that conversation with a clear picture of its current state, a cost-of-inaction baseline, and a sequenced roadmap. Waiting leaves the next incident to make the case and set the timeline. This is also the moment to bring retention, unstructured data, and AI readiness into a single conversation. A shared foundation and sequenced plan strengthen the case for investment and make the program easier to sustain once it is approved. The weeks ahead in this series will work through each part of that path: assessing the current state, quantifying the cost of the status quo, prioritizing where risk and value are highest, building the business case, sequencing the roadmap, budgeting for people, process, and technology, proving the investment works, and sustaining it beyond year one. The series closes by applying that same discipline across the broader data environment and into AI, where the strongest investment is often the governance foundation beneath it. The Bottom Line Governance does not have to wait for a crisis to get funded. Planning season is the window to make that case proactively, with a clear-eyed assessment, a defensible cost baseline, and a roadmap leadership can actually approve. The organizations that use this window well spend the rest of the year executing a plan. The ones that do not spend it responding to whatever surfaces next. Next in the series: Know Where You Stand: Assessing Governance Maturity Before You Plan. The information you obtain at this site, or this blog is not, nor is it intended to be, legal or consulting advice. You should consult with a professional regarding your individual situation. We invite you to contact us through the website, email, phone, or through LinkedIn.
Why Late Summer Is the Right Time to Plan for Governance
We recently closed a series with a simple idea. Retention, and operational governance more broadly, is becoming infrastructure. Foundational, continuous, and something the rest of the business depends on. Infrastructure has one defining characteristic that is easy to overlook. It is planned. It is budgeted. It is built on purpose, ahead of need, rather than assembled in a hurry after something breaks. Which raises a timely question. If governance is becoming infrastructure, when should you plan for it? For most organizations, the answer is now. Governance Rarely Makes the Budget on Time For a lot of organizations, late summer into early fall is when planning for the year ahead begins. Priorities are set. Budgets take shape. Cases are made for where next year’s investment should go. Governance often misses that window. Not because it does not matter, but because it competes with initiatives that feel more urgent and are easier to quantify. Governance tends to enter the budget conversation later, and usually for the wrong reason: an audit finding, a regulatory inquiry, a breach, or a piece of litigation that exposes a gap. By then, the conversation has changed. You are no longer planning an investment. You are justifying a scramble. Planning Ahead Changes the Conversation There is a meaningful difference between funding governance proactively and funding it reactively. Reactive funding happens under pressure. The scope is set by whatever went wrong. The timeline is compressed. The spending is defensive. Proactive funding happens on your terms. You get to frame governance as a strategic investment, tie it to business priorities, and sequence it sensibly. You can make the case with evidence rather than urgency. The difference is largely a matter of timing. And the timing is set by the planning calendar, which is why late summer matters. Why This Year in Particular Two forces make the case more pressing than usual. The first is data. Volumes keep growing, information keeps spreading across more systems, and regulatory expectations keep expanding. The cost of an unmanaged information environment compounds quietly, year over year. The second is AI. Responsible adoption depends on being able to answer basic questions about your information: what you have, how it is classified, and how long it should be kept. Organizations that want to move on AI next year will find that the governance foundation underneath it is not optional. It is a prerequisite. Both are planning problems before they are execution problems. They are far easier to address in a budget cycle than in a crisis. What Starting Now Looks Like Planning for governance does not mean committing to a large program overnight. It means using this window to get ready to make the case. A few practical starting points: None of these require a budget to begin. They require time, and time is exactly what the planning season provides. A Closing Thought: Build It Before You Need It Infrastructure is not something you improvise. You plan it, fund it, and build it before the moment you depend on it arrives. Governance is no different. The organizations that treat it as a deliberate investment, planned into the cycle rather than forced by an incident, are the ones that enter each year with a foundation they can build on. Late summer is when that planning starts. It is a good time to bring governance into the conversation, while there is still room in the plan to do it well. Over the coming weeks, we will explore how to do exactly that: how to assess, prioritize, fund, and sustain a governance program built for the year ahead. If governance is on your roadmap for next year, this is the moment to start shaping it. The information you obtain at this site, or this blog is not, nor is it intended to be, legal or consulting advice. You should consult with a professional regarding your individual situation. We invite you to contact us through the website, email, phone, or through LinkedIn.
Defensible Disposition: Proving Deletion Was Correct, Not Just That It Happened
Most governance programs are built around a single question: what should we keep, and for how long. That question matters, but it’s only half the job. The other half, the one that gets far less attention, is what happens when the retention period ends. Deleting the content isn’t the hard part. Being able to prove, later, that the deletion was correct, is. The current state Defensible disposition has quietly become a growing priority in information governance, and for good reason. Organizations have spent years investing in retention schedules, classification tools, and policies that describe what should happen to information over its lifecycle. Far fewer have built an equally rigorous process for the moment that lifecycle ends. Content becomes eligible for deletion, and then it either gets deleted through an ad hoc process nobody documented, or it doesn’t get deleted at all, because deleting the wrong thing feels riskier than keeping too much. That asymmetry shows up everywhere. Storage volumes keep growing well past the point the retention schedule says they should. Backlogs of expired, eligible-for-deletion content sit untouched for years. And when a deletion does happen, it’s rarely accompanied by a record showing what was destroyed, under what authority, and confirming that nothing under a legal hold was caught up in it. The observation There’s a meaningful difference between content that was deleted and content whose deletion can be proven correct. The first is an IT event. The second is a governance outcome, and it requires its own evidence trail, separate from the retention schedule that made the content eligible in the first place. A retention schedule tells you when something is allowed to be deleted. It doesn’t tell you that the deletion actually happened on schedule, that a legal hold wasn’t in effect at the time, that the right person approved it, or that the method of destruction was appropriate for the sensitivity of the content. Without that second layer of evidence, an organization can have a well-designed retention schedule and still be unable to answer the most basic question a court or regulator might ask: how do you know this was deleted correctly, and not simply deleted? Why this happens Disposition gets treated as the least interesting part of the governance lifecycle, which is exactly why it tends to be the least rigorous. Building a retention schedule is a project with a clear deliverable. Classifying content is increasingly automated and measurable. Actually executing deletion, consistently, on schedule, with the right approvals and hold checks, is an ongoing operational responsibility that doesn’t have the same natural momentum behind it. It’s easy to defer. There’s also a fear factor that works against disposition specifically. Deleting the wrong document, especially one connected to a matter nobody flagged in time, is a visible, attributable mistake. Keeping too much rarely feels like a mistake in the moment, even though it usually is one. That asymmetry pushes organizations toward over-retention by default, which quietly undermines the credibility of the entire program. A retention schedule that never actually triggers deletion isn’t a retention schedule. It’s a storage strategy with better documentation. Why this matters The risk runs in both directions, and both are expensive. Deleting content that turns out to be under a legal hold, even unintentionally, can lead to spoliation claims and sanctions, and courts may scrutinize processes that lack a documented hold check. On the other side, failing to delete content that should have been destroyed means it’s still sitting there when a discovery request or breach investigation arrives, expanding the scope, cost, and exposure of whatever comes next. Neither failure mode is really about the deletion itself. Both come down to the absence of a documented, repeatable process that confirms the deletion was appropriate at the moment it happened. Without that record, the organization is relying on memory and good faith to explain a decision that may get scrutinized years later, long after anyone involved can reliably reconstruct it. Common mistakes A few patterns show up consistently in organizations that struggle here: Treating disposition as a technical task, specifically a delete job, rather than a governed process that requires sign-off and documentation like any other compliance decision. Having no systematic check against active legal holds before content is destroyed and relying instead on someone remembering to look. Failing to keep a record of what was destroyed, when, and under what authority, leaving the organization unable to answer questions about specific content after the fact. Confusing “eligible for deletion” with “deleted,” which allows backlogs of expired content to accumulate because nothing forces the disposition step to occur. The recommendation Treat disposition as its own governed process, with its own documentation, rather than the final, unglamorous step of retention management. Create a disposition record for each governed destruction event, not just the large or sensitive ones. That record should show what was destroyed, the retention category it fell under, who approved the disposition, confirmation that no legal hold applied, the date, and the method of destruction. This is the artifact that turns “we believe this was deleted appropriately” into “here is the evidence that it was.” Automate the legal hold check so it’s a systematic gate every disposition event has to pass through, not a manual step someone might forget under time pressure. If the organization already has a hold tracking system and a retention or classification tool, connecting them so disposition can’t proceed without a hold clearance closes one of the most common gaps. Separate the person or system executing the deletion from the person approving it. That segregation of duties is standard practice in most other compliance functions, and disposition deserves the same discipline given what’s at stake on both sides of the decision. Run disposition on a defined operational cadence, with quarterly as a reasonable starting point for most organizations, rather than treating it as an occasional special project. Where classification tools already identify redundant, obsolete, and expired content, feed that output directly into the disposition queue so eligible content doesn’t just sit there waiting for someone to notice it. What this looks like when it works When someone asks about a specific piece of content months or years after it was deleted, a mature disposition process has an answer that doesn’t depend on anyone’s memory. There’s a record showing the retention category it fell under, the approval, the hold clearance, and the date and method of destruction. The organization isn’t reconstructing what probably happened. It’s producing evidence of what actually did. The business
You Do Not Have Governance, You Have Documentation
Ask most organizations with an IG program if they have governance over their information, and the answer is yes. There’s a policy. There’s a retention schedule. There’s a framework, usually well written, sometimes benchmarked against a recognized standard, occasionally reviewed by outside counsel. By any reasonable definition of “having governance in place,” the box gets checked. None of that is governance. It’s documentation. Governance is what happens after the document is written, when a person somewhere in the organization makes a decision about a piece of information and that decision matches what the document says should happen. Too often, it doesn’t, and most organizations don’t find out until something forces the question. The current state Gartner estimates that 80 percent of organizations trying to scale digital business will fail because they lack a modern, execution-led approach to data and analytics governance, not because they lack policies. Separately, surveys of data management professionals consistently find that even among organizations with a formal governance program already in place, data quality and governance issues remain among their biggest ongoing challenges. The pattern is consistent across the industry: the documentation exists almost everywhere. The execution not so much. That gap isn’t really about effort. Most governance teams work hard, and most policies are reasonably well constructed. The problem is that a policy describes an intention, and intentions don’t enforce themselves. A retention schedule says how long a category of content should be kept. It doesn’t move that content into the right folder, apply the right label, or delete it on schedule. A person, or a system acting on that person’s behalf, must do that, every time, across every system where the content lives. The observation This is the distinction that gets lost in most governance conversations: a document is a statement of what should happen. Governance is the process that executes what’s in the documents and preserves the evidence of what happened. Those are not the same thing and treating them as interchangeable is how organizations end up confident about their governance posture right up until an audit, a breach, or a discovery request asks them to prove it. The confidence is usually genuine, which is what makes the gap dangerous. Leadership reviews the policy, sees that it’s thorough, and reasonably concludes the organization is in good shape. Nobody in that review is lying or cutting corners. They’re evaluating the wrong artifact. A well-written policy tells you what good behavior looks like. It tells you nothing about whether that behavior is occurring across the thousands of daily decisions people make about where information goes, who has access to it, how long it stays, and when it gets deleted. Why this happens Documentation is easier to produce than execution, and it’s easier to measure. A policy has a clear finish line: it gets drafted, reviewed, approved, and published. Execution doesn’t have a finish line. It’s an ongoing operational discipline that must hold up across every system, every team, and every new employee who never read the policy in the first place. Organizations naturally gravitate toward the work that can be finished and signed off on, and governance documentation fits that description far better than governance operations do. There’s also an accountability problem underneath this. Writing the policy usually belongs to one team, records management, legal, or a governance committee. Following the policy belongs to everyone else, spread across every department, none of whom were involved in writing it and few of whom have any real incentive to prioritize it over their actual job. Nobody owns the gap between the document and the daily decision, so the gap persists. Why this matters The moment this gap becomes visible is rarely convenient. It shows up during litigation, when opposing counsel asks whether the retention schedule was actually followed and the honest answer is “inconsistently.” It shows up during a regulatory exam, when an examiner asks for evidence that a control was operating, not just that a policy described the control. It shows up during a breach investigation, when the organization discovers that sensitive data was sitting in a location the policy explicitly said it shouldn’t be. In each of these cases, the organization isn’t caught because it lacked governance intentions. It’s caught because the intentions and the reality had quietly diverged, sometimes for years, without anyone measuring the distance between them. The document held up fine under review. The operation underneath it didn’t. Common mistakes A few habits show up repeatedly in organizations that mistake documentation for governance. The most common is treating policy approval as the finish line for a governance initiative, rather than the starting point for an operational one. A close second is measuring governance maturity by the quality of the written policy rather than by evidence of how consistently it’s been followed. A third is assuming that training people on a policy is the same as building a system that makes the right behavior the easy behavior. And a fourth is reviewing the policy on a regular cycle while never actually testing whether real-world practice still matches it. The recommendation Closing this gap requires treating execution as its own workstream, with its own accountability, rather than as something that automatically follows once the policy is published. Assign explicit ownership for operational compliance, separate from ownership of the written policy. The person or team accountable for whether the retention schedule is being followed should not be the same as, or subordinate to, the team that simply drafted it. Build measurement directly into the program. Sample actual practice against the documented policy on a regular basis, the same way an internal audit function would, rather than assuming compliance because the policy exists and training was delivered. Where possible, move enforcement into the systems people already use, so following the policy is the default behavior rather than something an individual has to remember to do correctly every time. This is where classification, automated retention triggers, access reviews, and workflow-based controls do more good than another round of policy training. Report on execution, not just documentation, to leadership. A governance update that only covers policy status gives leadership a false sense of where the organization stands. A governance update that includes evidence of operational compliance gives them something they can rely on. What this looks like when it works A mature governance program doesn’t necessarily look different on paper. It looks different in what leadership can point to when someone asks a hard question. Instead of
Legacy Systems Don’t Just Store Data, They Accumulate Risk
Every organization has at least one system nobody wants to touch. A legacy repository built for a platform that’s no longer supported. An old file share that survived three reorganizations. An on-prem archive that outlived the department that created it. These systems don’t sit quietly in the background while the rest of the organization modernizes around them. They accumulate risk, year after year, whether anyone is paying attention to them or not. The current state Most legacy systems started out as reasonably well-organized repositories. Somewhere along the way, the original owners moved on, the folder structure stopped reflecting how the business worked, and new content got dropped in without much thought about where it belonged. A decade or two later, the system holds an enormous, unindexed mix of records, drafts, duplicates, and content nobody can identify without opening it. Migration projects get proposed and then postponed, usually because the scope feels too large to take on. Classification gets pushed off for the same reason. Manually reviewing years or decades of unstructured content isn’t a project most teams can staff, so the system stays exactly where it is, quietly getting larger and older. The observation The risk in a legacy system is invisible right up until something forces a look: a litigation hold, a breach investigation, a regulatory inquiry, an M&A due diligence request, or a migration mandate that can no longer be delayed. Until one of those events happens, an ungoverned legacy system looks like a storage cost line item. It isn’t. It’s a growing liability that nobody has measured. That growth compounds in two directions at once. The content itself keeps accumulating, and the institutional knowledge about what’s in the system keeps eroding as the people who understood it move on or leave the organization. Five years from now, the same system will hold more content and fewer people who can explain any of it. That’s the opposite of how risk is supposed to move over time. Why this happens The instinct to leave legacy systems alone is understandable. They’re usually stable, they’re not causing an active problem, and touching them raises the very question everyone wants to avoid: what’s in there? Answering that question with a manual review effort is exactly the kind of open-ended, resource-intensive project that keeps losing the prioritization fight against work with a clearer deadline. The result is a familiar pattern: organizations either leave the legacy system alone indefinitely, or they migrate it with a “lift and shift” approach that moves the content into a new platform without resolving any of the underlying governance questions. Lift and shift feels like progress because the system gets modernized. But if nothing was classified, deleted, or aligned to a retention schedule along the way, the organization has just moved the same risk into newer, more expensive infrastructure. Why this matters Legacy systems frequently hold sensitive data nobody remembers is there: personal information, financial records, health data, or intellectual property that was never flagged or protected because no one has looked at the content in years. That’s precisely the kind of exposure that turns a routine audit or a discovery request into a much bigger problem than it needed to be, because the organization is discovering its own risk at the same moment a regulator or opposing counsel is asking about it. The cost isn’t only measured in worst-case scenarios. Storage costs for legacy repositories rarely go down on their own. E-discovery costs scale with the volume of ungoverned content that must be reviewed. And every year the system goes unaddressed, the eventual cleanup gets more expensive, because there’s more content, less context, and fewer people left who remember what any of it was for. Common mistakes A few patterns show up repeatedly in organizations dealing with legacy content. The most common is treating classification as a prerequisite that must be finished before migration can start, which makes the project large enough that it never gets scheduled. A close second is assuming a lift-and-shift migration counts as modernization, when it typically just relocates the same unresolved risk. A third is deprioritizing legacy cleanup because the system isn’t causing a visible problem today, without accounting for how much more expensive the problem becomes with each additional year of neglect. And a fourth is trying to solve the entire legacy estate at once instead of triaging by risk, which stalls the effort before it produces any results. Where AI-enhanced auto-classification helps This is exactly the kind of problem AI-enhanced auto-classification is well suited to. Pattern recognition at scale can inventory and classify years of unstructured legacy content far faster than a manual review team ever could, identifying redundant, obsolete, and trivial content, flagging likely sensitive data, and aligning what remains to a retention schedule, even when the content arrived with little or no usable metadata. The practical shift is in when classification happens relative to migration. Rather than treating classification as a blocking prerequisite, a growing number of organizations are applying it during or after migration, once content has landed in a modern platform where classification tools and retention structures can operate on it. That keeps the scope of any single phase manageable and turns a stalled, all-or-nothing project into a series of achievable ones. None of this replaces human judgment. AI-enhanced classification performs best on a clearly scoped, well-defined problem, refined through iteration and human review, the same requirement that applies to any AI-assisted governance effort. What it changes is the starting point: instead of an unstaffed manual review that never gets prioritized, the organization gets a fast, structured first pass that a smaller team, ideally lead by an IG professional, can refine and act on. The recommendation Start with an inventory, not a decision. Before deciding whether to migrate, decommission, or retain a legacy system, run an AI-assisted inventory to understand what’s inside it. Too many of these decisions get made without that information, based on assumptions that are years out of date. Prioritize sensitive data identification first. Flagging personal information, financial records, and other high-risk content early gives the organization a clear picture of its exposure long before full classification is complete and lets legal and security teams start managing that risk immediately rather than waiting for the whole project to finish. Treat classification as a rolling, phased activity rather than a single completed gate. Run it in stages, refine the rules and categories as accuracy improves, and apply what’s learned from one phase to the next, rather than trying to solve the entire legacy estate in one
AI Governance Is Now Judged by Evidence, Not Principles
Many organizations already have the beginnings of an AI governance program. There’s an acceptable use policy, a responsible AI statement, maybe a committee that meets quarterly to talk about risk. For some time now, that’s been enough to say the organization “has AI governance.” That’s changing, and it’s changing faster than most governance programs have adjusted for. The shift isn’t about whether organizations have the right principles written down. Most do. It’s about whether they can prove, on demand, that those principles were followed for a specific system, on a specific date, by a specific person. The current state Regulators, auditors, and courts are no longer satisfied with a policy document. They want to see documented processes and evidence: risk assessments for specific systems, logs of human review, records showing who approved a given use of AI and when. The EU AI Act’s transparency requirements, state AI laws working through legislatures across the country, and the broader shift toward mandatory compliance frameworks all point the same direction. AI governance in 2026 is being judged by evidence of what really happened, not by the quality of the principles written down in advance. That’s a meaningful shift in what “good governance” requires. A well-written policy used to be most of the job. Now it’s the starting point. An organization can have a strong acceptable use policy, a responsible AI committee, and a public commitment to ethical AI, and still fail an audit, because none of those things produce a record that a specific system was reviewed, approved, and monitored the way the policy said it would be. The artifacts regulators are asking for are specific: model risk assessments, data protection impact analyses, logs showing a human reviewed a high-stakes output before it was used, and a record of who signed off on a system before it went into production. These aren’t new concepts. Most of them have existed in some form in financial services model risk management or in privacy impact assessments for years. What’s new is the expectation that this kind of documentation exists for AI systems specifically, at the pace those systems are being adopted. The observation This shift exposes a structural problem that most organizations haven’t addressed: no single function wholly owns the full evidence trail for AI governance. Legal typically owns risk interpretation and regulatory response. IT owns the tools themselves, along with access and usage logs. Privacy owns questions about what data an AI system touches. Records management and information governance own retention, classification, and the underlying question of what must be kept and for how long. Each of these functions holds a piece of what a regulator or a court would eventually ask for. None of them holds the whole thing. That fragmentation doesn’t show up as a problem day to day. Everyone is doing their job. It shows up the moment someone asks a specific question: show me that this AI system was reviewed before deployment, show me who approved it, show me that a person exercised oversight over its output. Answering that requires pulling evidence from four different functions that don’t currently coordinate around a shared record. Why the gap exists This isn’t a failure of any one team. It’s a byproduct of how these functions were built in the first place. Legal, IT, privacy, and information governance each grew up around a different mandate, at different points in time, usually well before AI was a factor. Legal’s processes were built around litigation and regulatory response. IT’s were built around uptime, security, and access control. Privacy’s were built around personal data handling, largely in response to GDPR and its successors. IG’s were built around retention schedules and regulatory obligations that predate AI by decades. When AI arrived, most organizations didn’t redesign ownership across these functions. They added AI-related tasks to each function’s existing workload instead: legal reviews new AI vendor contracts, IT manages access to AI tools, privacy assesses data flows into AI systems, IG and Records figure out what to keep. That’s a reasonable short-term response, but it means the evidence produced by each function was never designed to connect to the others. Nobody owns the seam between them, and the seam is exactly where regulators are now looking. Why this matters The organizations that struggle here aren’t the ones without governance. They’re the ones with governance spread across departments that each did their part correctly, without anyone responsible for assembling the whole picture. When a regulatory inquiry or a discovery request lands, what should be a straightforward production often becomes a multi-week scramble to reconstruct a history that was never centrally documented in the first place. This is the same pattern that shows up in other parts of information governance: policy defines the rules, but nobody has ownership of proving the rules were followed. The difference with AI is that the number of systems, the pace of adoption, and the specificity of what regulators are asking for all make that gap far more expensive to leave unaddressed. A single ungoverned shared drive is a cleanup project. A portfolio of AI systems without a documented evidence trail is a recurring exposure that grows every time a new tool gets adopted. Common mistakes A few patterns show up consistently in organizations that get caught flat-footed. The most common is assuming that committee minutes or a policy sign-off count as evidence of ongoing oversight, when what’s needed is a record tied to a specific system, not a general statement of intent. A close second is treating evidence collection as one department’s responsibility rather than a shared obligation with defined handoffs, which is exactly the fragmentation problem described above. A third is building the evidence trail reactively, after an incident or an inquiry, rather than as a standing part of how new AI tools get adopted. And a fourth is assuming that because a system was reviewed once at launch, that review still reflects how the system is being used a year later. The recommendation Closing this gap starts with ownership, not with more policy. Assign a single accountable role, not necessarily a new department, but one function responsible for assembling and maintaining the complete evidence trail for each AI system in use. This role doesn’t need to do the underlying work of every other function; it needs the authority and the mandate to pull the pieces together and know when something is missing. Map which function currently owns each type of evidence: risk assessments with legal, usage logs
Records Retention Hasn’t Caught Up to AI
Most organizations have spent years building retention schedules around a familiar set of record types: project documents, contracts, financial records, HR files, correspondence. These schedules reflect how work used to get created. They don’t reflect how work gets created now, and the gap between the two is wider than most governance programs have acknowledged. The current state AI tools are embedded in day-to-day work across most organizations, whether or not that use is formally sanctioned. Employees draft with them, summarize with them, analyze with them, and generate first-pass output with them. Every one of those interactions creates content: prompts, draft outputs, revised outputs, chat logs, and in some cases entire training or fine-tuning datasets. None of that maps cleanly onto a retention schedule built for a pre-AI world. Most schedules have no category for an AI prompt. Few define whether a model’s output is a business record, a transitory draft, or something in between. Almost none address what happens when the same piece of content exists in three or four states: the prompt, the raw output, the edited draft, and the final version that gets used. That ambiguity doesn’t resolve itself. It just gets pushed down to whoever happens to be using the tool that day. Why an AI-generated draft isn’t the same as a human draft Traditional records management has a clear, well-established answer for drafts: they’re transitory. Once the final contract is signed, the final policy is issued, or the final report is published, earlier drafts are considered to have no ongoing business, legal, or regulatory value, and most retention policies call for them to be deleted. That’s the right approach, and it has been for decades. A human draft is evidence of a person’s thinking in progress. Once the decision is made, preserving every prior iteration of that thinking adds volume without adding value. An AI-generated draft breaks that logic in a specific way. A human draft documents a person’s judgment as it evolves. An AI-generated draft documents what a system produced, independent of any person’s judgment. Once someone edits that output into a final record, the final record shows what was decided, but it doesn’t show what the AI actually generated, how far a person had to depart from it, or whether meaningful review happened at all. That distinction matters the moment the question stops being “what did we decide” and becomes “did the AI system behave appropriately, and did a person actually exercise oversight before relying on it.” That second question is coming up more often, not less. Regulators, courts, and increasingly customers want to know whether an AI system had a hand in producing a record and whether a person reviewed its output before it became final. If the original AI-generated draft has already been deleted on the same schedule as a human’s rough draft, the organization has no way to answer that question, regardless of how sound the final record turns out to be. None of this means every AI-touched draft becomes a permanent record. It means the retention decision must be made deliberately, based on how much weight the AI’s output carried and how consequential the final decision was, rather than defaulting to the disposal timeline built for a person’s private working notes. The observation This isn’t a failure of the retention schedule itself. Most schedules are reasonably well built for the record types they were designed to cover. The gap is that AI-generated and AI-assisted content was never in scope when those schedules were written, and very few organizations have gone back to close that gap. That creates a familiar pattern for anyone who has worked in information governance: policy defines the rules, and the underlying data has moved on without it. Why this matters The implication shows up first in litigation and regulatory response. Discovery requests and regulatory inquiries increasingly ask specific questions about AI use: what tool was used, what prompt was entered, what the output was, and whether that output was reviewed before it informed a decision. Governance programs that haven’t defined AI content as a record type struggle to answer those questions consistently, because the underlying content was never captured, classified, or retained with intent. The default response tends to fall into one of two failure modes. Some organizations retain everything, because no one has made a decision about what to delete, which increases the volume of discoverable material and the associated risk. Others delete inconsistently, department by department or tool by tool, which creates exactly the kind of defensibility gap that regulators and opposing counsel look for. What to do Closing this gap doesn’t require rebuilding the retention schedule from scratch. It requires extending it deliberately. Add AI-generated and AI-assisted content as an explicit category in the retention schedule, with clear definitions for prompts, outputs, and revised drafts rather than leaving that distinction to individual judgment. Establish a standing review, ideally quarterly, between records management and whoever owns AI tool governance, so classification keeps pace as new tools are adopted. Extend legal hold and e-discovery protocols to name AI interaction logs specifically, rather than assuming existing email and document holds will capture them. Assign clear ownership for this category the same way ownership exists for financial records or HR files, so the schedule doesn’t just describe good intentions. And set a deliberate rule for AI-generated drafts tied to how consequential the decision is, rather than applying the standard human-draft disposal timeline by default, particularly for content that informs legal, regulatory, HR, or financial decisions. The information you obtain at this site, or this blog is not, nor is it intended to be, legal or consulting advice. You should consult with a professional regarding your individual situation. We invite you to contact us through the website, email, phone, or through LinkedIn.
Order From Chaos: What AI Actually Changes About Classification
Organizations don’t struggle to manage their data because they lack policy. Most have a retention schedule somewhere, a records management program with a name and a budget line, and a set of rules that, on paper, tell every employee what to keep and what to delete. The problem is that policy defines intent, and data reflects reality. In most organizations, those two things were never connected in the first place. The scale of the problem The numbers explain why this gap keeps widening. Global data volume was projected to reach 181 zettabytes by 2025, and 90 percent of it was created in just the last two years. Organizations are generating roughly 400 million terabytes of data every day. No records team, however well-staffed, can keep pace with that growth using manual review. Traditional classification methods were built for a slower, smaller world. Manual tagging depends on people remembering to do it. User-driven classification depends on people agreeing on what a document is. Static retention schedules depend on categories that made sense five years ago still making sense today. Volume, unstructured content, and inconsistent application have broken all three. What AI-enhanced classification actually changes AI-enhanced classification is not magic, and it is not a replacement for governance. What it does well is pattern recognition across large volumes of content, classification at scale, and alignment of that content to policy-defined rules. It performs strongly on redundant, obsolete, and trivial data identification, and on building an inventory across repositories that would take a human team months to compile manually. It struggles with the same things people struggle with ambiguous content, poorly defined retention categories, and missing context. That is an important distinction. AI does not fail because the technology is immature. It underperforms when the problem it has been asked to solve was never clearly defined to begin with. This is why transparency matters as much as accuracy. A classification decision that cannot show its work is not defensible, no matter how confident the output looks. AI needs structure, and it needs people AI reflects the model you give it, for better or worse. More categories create more confusion, not more precision. Ambiguity in a retention schedule does not disappear when AI is introduced. It gets amplified, because the system will apply that ambiguity consistently across millions of documents instead of inconsistently across a handful of employees. This is why human-in-the-loop involvement is not optional. People define scope. They remove ambiguity from category definitions. They validate results and tune the model as patterns emerge. That iterative involvement is what turns an initial output into a defensible outcome. Scope, not sophistication, is the real driver of accuracy The clearest trend across organizations experimenting with AI-enhanced classification is this: the technology performs in direct proportion to how well the problem has been scoped. Ask AI to sort content against a handful of clearly defined categories, and accuracy is strong from the first run. Ask it to classify against hundreds of overlapping categories with vague definitions, and it behaves exactly like an overwhelmed human team would: inconsistent, uncertain, and prone to error. Reducing scope improves accuracy. Adding complexity does not. Out-of-the-box results should be treated as a starting point, not a finished product. The organizations seeing the strongest outcomes are the ones treating classification as an iterative process, refining rules, scope notes, and category definitions over multiple cycles rather than expecting a single pass to get it right. Where AI-enhanced classification fits, and where it doesn’t AI-enhanced classification is well suited to organizations with high volumes of unstructured data, a known redundant, obsolete, and trivial (ROT) data problem, or active regulatory pressure to demonstrate control over their information. It is not a fit for organizations without a retention schedule, without clear governance ownership, or with an expectation that a tool can be deployed once and left alone. The common mistakes are consistent across industries: over-scoping the initial effort, ignoring the need for explainability, treating AI as the solution rather than an enabler of a governance program that already needs to exist, and underestimating how much expertise is required at the intersection of information governance and AI. This is not a technology deployment. It is a governance discipline supported by technology. The bigger picture Policy defines the rules. Data reflects the risk. Control comes from aligning the two, and that alignment does not happen by accident. It happens through clear scope, disciplined iteration, and people who stay engaged in the process rather than stepping back and hoping the technology handles it alone. Organizations that treat AI-enhanced classification as a governance capability, not a shortcut around governance, are the ones turning chaos into order. The rest are just automating their existing confusion. Join Us: Summer Governance Series 2026 This topic is the focus of our upcoming webinar series, where we go deeper into the practical realities of applying AI to information governance. Session 2: Order From Chaos: Real World Lessons Using AI-Enhanced Auto-Classification August 4, 2026 | 1:00 PM EDT Register here: https://lexshift.com/summer-governance-series-2026/ We hope you’ll join us. The information you obtain at this site, or this blog is not, nor is it intended to be, legal or consulting advice. You should consult with a professional regarding your individual situation. We invite you to contact us through the website, email, phone, or through LinkedIn.
Retention as Infrastructure: Why Operational Governance Is Becoming a Foundational Enterprise Capability
This series began with a simple claim. If information governance exists only in policy, it is not really governance. From there, we followed a single thread: what it actually takes to move retention from documentation to practice. Across every topic, from structure and consistency to AI, defensibility, disposition, and visibility, the same conclusion kept surfacing. Governance only works when it becomes operational. This final piece is about where that leads. Because when retention becomes truly operational, it stops being a compliance artifact and starts becoming something more foundational. It becomes infrastructure. The Path From Document to System It is worth retracing the path briefly, because the destination only makes sense in light of the journey. We started by separating documentation from governance. A policy describes intent. On its own, it does not control information. We looked at why spreadsheets cannot carry that weight, and why retention has to move from a static document to a structured system. We examined execution: applying policy consistently across systems, maintaining it across jurisdictions, and governing information created and processed by AI. We explored what makes governance defensible: tracking decisions, managing change over time, and closing the loop through disposition. And we made the case that visibility is a form of control, that structure is the foundation, that a good platform supports governance as a capability, and that an operating model is what makes all of it stick. Each topic approached the problem from a different angle. Each arrived at the same place. Retention has to function as a system, not a document. What “Infrastructure” Really Means Calling retention infrastructure is not a figure of speech. Infrastructure is the set of foundational systems that everything else quietly depends on. Roads. Power. Networks. Inside an enterprise, it includes financial controls, security, and data architecture. Infrastructure shares a few defining traits. It is foundational, because other capabilities are built on top of it. It is continuous, because it operates all the time rather than in bursts. And it is largely invisible when it works, noticed mainly when it fails. Retention is beginning to fit that description. Done well, it runs quietly beneath the organization, supporting compliance, risk management, and increasingly the responsible use of information. Done poorly, the failure eventually becomes visible, often at the worst possible moment. Why Retention Is Becoming Foundational Now Retention has always mattered. What has changed is how much now depends on it. Data volumes continue to grow. Information is spread across more systems than ever. Regulatory expectations keep expanding. And AI has introduced both new kinds of information and new speed at which information is created and processed. In that environment, ad hoc retention does not just create inefficiency. It undermines the things built on top of it. Consider AI. Responsible adoption depends on understanding what information exists, how it is classified, and how long it should be kept. An organization that cannot govern its information consistently cannot confidently feed that information into AI systems, or explain the results afterward. Retention, in other words, has moved upstream. It is no longer only a downstream compliance task. It is becoming a precondition for doing other things well. Infrastructure Is Built, Not Declared There is an important implication in all of this. You do not get infrastructure by writing a better policy or buying a tool. Infrastructure is built deliberately, over time. That is what this series has really been describing. Structure gives retention a durable foundation. A platform gives it a place to operate. An operating model gives it ownership, decisions, and process. Visibility gives it accountability. Together, these elements turn retention from a document into a dependable system. None of it happens by declaration. It is the result of sustained, coordinated work across legal, compliance, records, IT, and the business. A Shift in How Organizations Think Perhaps the biggest change is one of mindset. For a long time, retention was treated as a periodic obligation. A schedule to be written, approved, and revisited occasionally. Something to satisfy an auditor. Treating retention as infrastructure reframes the question. It is no longer simply “Do we have a retention schedule?” It becomes “Does our retention function as a system the enterprise can rely on?” That is a higher standard. It is also the standard that modern data environments increasingly demand. A Closing Thought: Governance That Holds Up This series has made one argument in many forms. Governance becomes real when it becomes operational. Retention is where that idea becomes concrete. It is one of the most established elements of information governance, and one of the most difficult to operationalize at scale. That is exactly why it is such a clear test of whether governance is actually working. When retention is treated as infrastructure, built on structure, supported by the right platform, and sustained by a real operating model, it becomes something an organization can depend on. It supports compliance. It reduces risk. It enables responsible innovation. And it holds up under scrutiny. The organizations that recognize this are not just improving a compliance process. They are building a foundational capability that will shape how well they adapt to whatever comes next. At LexShift, this is the work we care about most: helping organizations turn governance intent into operational practice, so that retention becomes not just a document they maintain, but a foundation they can build on. The conversation does not end here. It moves to what organizations choose to build on top of that foundation. The information you obtain at this site, or this blog is not, nor is it intended to be, legal or consulting advice. You should consult with a professional regarding your individual situation. We invite you to contact us through the website, email, phone, or through LinkedIn.