2026

Records findability starts at the point of creation

Trustworthy information has four attributes. It must be accurate, reliable, timely, and findable. Last episode covered the first two. This week, Lee Karas and Maura Dunn take on the other two.

The rule does not change. Capture the record where the work happens. Capture it when it happens. Capture it from the people doing the work. As a result, timeliness and findability follow along.

Why your file dates cannot be trusted

Open a shared drive and sort by date. The dates look authoritative. However, they are not.

Sometimes opening a document changes the date. The created date gives way to the modified date. Meanwhile, that modified date may only mean someone glanced at the file.

Auto-save makes it worse. Word saves before you rename your copy. Your manual version scheme then breaks quietly. It never runs at all in Microsoft Project or Visio. Even in Excel, it can miss when OneDrive has not finished logging in.

Timeliness is proof, not a timestamp

An approval date proves timeliness. So capture it deliberately. A workflow engine already knows who drafted, who commented, who approved, and when. Record that context anyway, because property values alone will not carry it.

Maura describes a client who did this on paper. Every requirements document carried five or six signature blocks. Each reviewer initialed and dated in ink. Then the team scanned it. An e-signature process gets you the same result today, with less effort.

Traceability at every step

Business requirement one becomes functional requirements 1.3, 1.4, and 1.5. That trace increases accuracy. The sign-offs at each step add timeliness.

Universe search versus precision search

Library science calls keyword search a universe search. You give it three words. In return, it gives you everything near those words. For example, ask for “training” and you also get “learning.”

The result set grows. The usefulness does not. Instead of the whole company, you now face a couple thousand documents.

A precision search works differently. First you set the file type. Next you name the business process. Then you name the contract or the facility. Now the found set is small enough to use.

Metadata is what makes records findable

Four elements matter most: function, process, record category, and trigger date or event. Those are real data, not keywords. Because of that, you can filter on them and build a collection. In other words, you get a virtual folder without a physical file plan.

Maura and Lee revisit an old FileNet argument on exactly this point. An IT lead wanted no folders and no file plan. He trusted full-text search to sort out billions of documents. He was partly right, but for the wrong reason.

Search, access, and retrieval

Findability has three parts. Search identifies potentially responsive material. Retrieval pulls it back so you can use it. Access decides whether you may open it at all.

Sometimes users can see that a record exists but cannot read it. Sometimes they cannot see it at all. That choice is yours, so make it on purpose.

Episode chapters

00:00 Timeliness and findability: the two attributes we still owe you
00:58 Why the date on the file lies: created versus modified
02:12 Auto-save versus manual versioning, and when OneDrive has not logged in yet
04:35 A tangent worth an episode: password management as a mapping problem
05:34 Capture at the point of creation, then make capture into storage
06:39 What the workflow engine already knows, and what you must record by hand
08:09 Ink initials and signature blocks: traceability from business to functional requirements
09:44 The universe search: three keywords, a million results, ranked by confidence
11:51 The precision search: file type, process, and facility narrow it down
12:58 Process metadata tags every file behind the scenes
14:27 The FileNet argument: “we will just use search”
15:24 Function, process, record category, and trigger as real metadata, not keywords
17:19 Contract records split: construction and non-construction retention
18:47 Collections as virtual folders, and knowing your repository before you commit
19:46 Search, access, and retrieval: three parts of one problem
20:39 Should users know a record exists if they cannot open it?

Closing

What Counts is produced by TrailBlazer Consulting, LLC and hosted by Lee Karas and Maura Dunn. Learn more or reach out directly at info@trailblazer.us.com. Explore compliance-ready corporate training programs at the TrailBlazer Learning Academy. Read more from Maura at Maura’s Substack. Music by Jason Blake. Full disclaimer.

Provenance decides whether your data is AI-ready

Everyone wants to point AI at their content repositories. Maura Dunn’s position in Episode 139 is simpler than that. A model can only be as trustworthy as the data feeding it. Provenance settles that question long before anyone builds a pipeline.

Records capture points settle provenance. These are the moments in a business process where an input becomes a record. Seventeen (17) steps later, the process has changed that input into something new. That is another capture point. Every copy, every hand-off, every transformation makes chain of custody harder to establish.

Content versus context

Our back file characterization approach documents the method while we build it. We do not hand a client a disposition report with no reasoning attached.

Consider a recommendation to destroy sixty (60) of seventy-five (75) files. That report is content. The folder structures, file properties, creation and modification dates, and security group access rights behind it are context.

Context gives the client something to react to. We can say we hold this level of confidence that these records align with your sales and marketing category. That category carries an end of fiscal year trigger and a five (5) year retention period. The client then makes the risk judgment. Without context, one answer survives a year later: “because Maura said so.”

What the Superfund SITREP got away with

We built the same principle into our records process mapping work.

The contrast comes from the US EPA Superfund program. A SITREP moved from field samples and a gas chromatograph printout to a typed memo in a drawer. Eventually it went into a box at the Federal Records Center. That process produced no interim record steps. In a paper world, it did not need to.

Engineering records capture points into the workflow

Digital process manipulates information continuously. So the workflow itself has to carry the capture points. Mark the inputs and the interim decision support drafts. Mark the comment responses where public comment periods apply, and the finals.

Automated workflow and document management version control make those records capture points easier to build than ever. Growing volume makes the discipline harder. Records prove what happened. That proof now doubles as the audit trail for whatever your AI does next.

Universal search was designed to bring you the universe. So is your AI assistant. Lee and Maura take on the two questions they left hanging last episode: how do you know which version is the last one, and how do you know your data is reliable? AI-ready data turns out to be the same problem, it is not solved by searching harder, and in 2026 it carries a regulatory clock.

Corporate data capture risk is a critical vulnerability that can completely disrupt an enterprise during sudden regulatory compliance audits or high-stakes litigation holds. Welcome back to What Counts, the podcast that digs into the messy information governance problems organizations inherit, ignore, and discover too late. In this episode, hosts Lee Karas and Maura Dunn move past theoretical concepts to break down exactly how unstructured file systems multiply your operational liabilities. Manual filing structures inevitably fail under heavy daily workloads, placing the burden entirely on your technology infrastructure to secure critical corporate history.

Clean dashboards and reliable data don’t happen by accident. In this episode of What Counts, Lee Karas and Maura Dunn pick up from the shift from records management to information governance and move into the three action principles that actually get you there: stop making copies, focus on data creation points, and touch once, use many times. They trace how society lost its mindfulness about creating data from Sumerian clay tablets to the printing press to the Federal Records Act and walk through a painfully familiar example of how a single shared link quietly multiplies into four copies. Along the way, they unpack the reliability paradox at the heart of information governance: the more copies you make, the less you can trust your data. It’s a candid, practical conversation about why these simple-sounding principles are so hard to follow, and why the tools we use every day keep reinforcing our worst habits.

New here? Start with the previous episode: Records Management vs. Information Governance.

Key Takeaways

The more copies you make, the less reliable your data becomes. People hoard copies because they don’t trust they’ll find the original later, which only makes the underlying data less trustworthy. It’s a paradox, but it holds.

We’ve lost our mindfulness about creating data. When information was expensive and hard to produce, more thought went into it. Now anyone can create and disseminate data in seconds, so almost none goes into it.

Three principles work together: stop making copies, focus on data creation points, and touch once / use many times. They’re simple to say, clear to understand, and genuinely hard to do.

Data creation deserves rules. Who’s allowed to create a new contract, location, or counterparty record? Where does it live? Who can change it, and how? Answering these up front prevents downstream chaos.

Acquisitions are data creation events. When data comes in through an acquisition, you need a crosswalk from old identifiers to new ones or you end up asking, “Where’s all the data for Armadillo Ranch?”

Bad data has real costs: failed audits, unanswerable litigation and e-discovery requests, duplicate survey spend, and revenue you can’t collect because you can’t prove your rights.

Your tools may be the problem. Email and collaboration platforms often reinforce copy-making habits or force workarounds, because the value of doing it right isn’t obvious in the moment.

What’s the difference between records management and information governance — and why should anyone running a business care? In this episode of What Counts, Lee Karas and Maura Dunn step back from the weeds of counterparty data to answer a deceptively simple question: what is information governance, and why is it the natural next step? Maura traces the journey from a world where creating a record was hard and expensive — clay tablets, hand-copied scrolls, the Federal Records Act — to today, where producing information takes ten seconds and most of it is noise. Along the way they untangle the vocabulary (governance is strategy and the “why”; management is execution), revisit the records-management principles that still hold true, and show how information governance helps you surface the small slice of information that actually runs your business. They close with practical moves you can make now: stop making copies, send a link instead of an attachment, and standardize and automate your contracts so your best people spend their time where the value and the risk actually live.

This episode builds on Episode 134, where Lee and Maura broke down how to keep counterparty and vendor data from sprawling across teams and systems before contracts are even signed. Listen to the previous episode here.

“Governance is more strategic — it incorporates the why. Management is execution.”

Key takeaways

Governance ≠ management. Governance sets strategy and the “why”; management executes, audits, and proves it.

Records management isn’t dead — its core test still applies: does this provide evidence of a policy, process, decision, action, or transaction?

Cheap creation is the modern problem. When anyone can publish in ten seconds, the hard part isn’t making information — it’s finding the small slice that matters.

Information governance is how you fight the noise so you can surface what runs the business and demonstrates compliance.

Stop making copies. Replace emailed attachments with links to a single, easy-to-reach, always-current source.

Unmanaged data is a risk, not just clutter — especially when it contains sensitive or critical-infrastructure information.

Contracts are where governance pays off: standardize, automate the routine, and reserve human attention for the high-value, high-risk exceptions.

Overall Episode Length: 0018:28

Episode chapters

00:00 — Sponsor: TrailBlazer Insight. Scan your shared drives locally for PII, HIPAA, PCI, and other compliance risks — no cloud, no IT ticket.

00:20 — Welcome to What Counts. Every organization hides a story in its data; meet your hosts, Lee and Maura.

00:47 — Recap & the segue. From Episode 134’s counterparty-data cleanup (persistent IDs, central systems, choke points) to a bigger question: what is information governance?

01:33 — Why this, why now. Making your contracts work for you starts with understanding your counterparties — and that leads straight to governance.

02:00 — The vocabulary problem. The words around this work keep changing (including TrailBlazer’s short-lived attempt to coin “information design”).

03:21 — Governance vs. management. Governance is strategic and carries the “why”; management is execution — following, auditing, and proving the process.

04:07 — Records management roots. Library school, law firms, and federal records centers — and the definition that still anchors the field.

04:51 — What is a “record”? Information that’s recorded (or can be) and provides evidence of decisions, actions, and transactions.

06:13 — When records were scarce. Cuneiform, scrolls, ink, and recyclable paper that fell apart — and the Federal Records Act, the first time the U.S. allowed records to be destroyed.

07:44 — Today’s flood. Creating information is now the cheapest thing you can do — so the value of any single piece is hard to find, and most has none.

08:37 — Enter information governance. From information management to data governance to information governance: a philosophy built on records principles, executed in a completely new way, to fight through the noise.

09:54 — The inbox problem. Open, click, delete — so how do you catch the one email that’s actually a record you need to keep?

10:40 — A real-world miss. Donation receipts lost in a personal inbox overrun with ads — why noise costs you.

11:39 — Automating the noise away. The weekly report’s evolution from paper to email blasts to set-and-forget rules nobody reads.

12:47 — When unread data becomes a risk. An energy-sector example: construction reports holding critical infrastructure information, piling up and waiting to be breached.

13:24 — Principle #1: Stop making copies. Don’t email attachments — point people to a source. But make it genuinely easy.

14:00 — Make it easy and more valuable. A weekly link to a live dashboard beats a stale Friday report you read on Monday.

15:39 — Governance applied to contracts. Standardize terms and exceptions, automate the routine, and free the high-value, high-risk contracts from the noise so senior legal and business minds focus where it counts.

17:01 — The big shift. From “create the document, then apply retention” to “information that reflects and serves the goals of the business.”

17:33 — Wrap-up & what’s next. Where information governance goes from here.

17:53 — Credits & how to support the show.

“In our age, creating information is the cheapest thing you can do.”

Frequently asked questions

What is information governance?

A strategic approach to creating, organizing, and using information so an organization can cut through the noise and focus on the small share of information that runs the business and demonstrates compliance. It’s built on records-management principles but executed very differently.

What’s the difference between records management and information governance?

Records management focuses on the lifecycle of records — creation, protection, use, and disposition. Information governance is broader and more strategic: it asks why you hold information and how it can serve business goals, not just how to retain and dispose of it.

What’s the difference between management and governance?

Governance is strategic — it sets direction and incorporates the “why.” Management is execution — following the rules, auditing the process, and proving it was followed.

Who should listen

General counsel and legal ops, records and information-governance managers, compliance officers, COOs, and contract/CLM owners — especially in mid-market and enterprise energy, healthcare, professional and engineering services, construction, and manufacturing.

Listen & subscribe

New episodes of What Counts drop regularly. Subscribe on your favorite podcast app, and if this one was useful, share it with a colleague whose shared drives are full of contracts nobody reads, policies nobody follows, and files nobody can find.

What Counts is produced by TrailBlazer Consulting, LLC and hosted by Lee Karas and Maura Dunn. Learn more at trailblazer.us.com or email us at info@trailblazer.us.com. Explore compliance-ready training at the TrailBlazer Learning Academy. Read more from Maura at mauradunn.substack.com. Music by Jason Blake. Full disclaimer.

Welcome back to “What Count,” the podcast where information governance meets contract lifecycle management. In this episode, Lee and Maura explore the critical next step after solving your counterparty data chaos: maintaining control of vendor information across multiple systems and teams. Discover how to build a centralized counterparty database that enables operations teams, procurement, and legal to work in parallel—and why enforcing a unique persistent ID is the million-dollar strategy that keeps everything aligned, even before contracts are executed.

Building on our previous discussion of counterparty data complications and contract management challenges, this episode reveals the operational playbook for managing your newly consolidated vendor list. Click the link to listen to our last episode. https://trailblazer.us.com/podcast/counterparty-data-reconciliation-case-study/

Episode length: 00:13:09

0:27 – Introducing today’s topic: preventing counterparty data proliferation

0:46 – Recap: the contract data and counterparty challenges discussed previously

1:05 – The core problem: multiple data sources across teams

9:10 – Pre-contract data collection workflows

10:14 – The “prospect-to-vendor” workflow: collecting data before execution

11:40 – The million-dollar insight: why unique persistent IDs are critical

12:00 – Closing remarks and contact information

What Counts is produced by TrailBlazer Consulting, LLC and hosted by Lee Karas and Maura Dunn. Learn more at trailblazer.us.com or email us at info@trailblazer.us.com. Explore compliance-ready training at the TrailBlazer Learning Academy. Read more from Maura at mauradunn.substack.com. Music by Jason Blake. Full disclaimer.

Most counterparty data reconciliation projects fail at the same assumption: that one identifier — usually a tax ID — can resolve who you’re actually doing business with. In Episode 133 of What Counts, Maura Dunn walks through a real two-year project to reconcile 350,000 counterparty records across eight systems at a company built through acquisition: four contract management platforms, one ERP carrying both customer and supplier masters, and three trading systems, each with its own naming conventions, character limits, and overflow fields. She unpacks the 18 months of unproductive matching that came first, the rule-precedence approach that finally worked once Snowflake and Elasticsearch replaced the spreadsheet attempts, and the 10-to-1 collapse from 350K records down to 35K true entities. She also makes the case for where AI fits this kind of work today — and the one thing it still can’t do unless you put deep institutional knowledge into the prompt. If you want to see what’s hiding in your own shared drives right now, search TrailBlazer Insight in the Microsoft Store — it scans locally for PII, HIPAA, PCI, and other compliance risks with no cloud upload and no IT ticket required.

This episode picks up where Episode 132: Data Reconciliation Before AI left off — Maura delivers the full case study we teased last time.

Topics covered in this episode include post-acquisition contract data cleanup, duplicate counterparty detection across multiple CLM platforms, rule-based data matching at scale using Snowflake and Elasticsearch, and the role of AI in contract data reconciliation when source systems lack consistent identifiers.

Episode length: 00:21:01

0:00 – Pre-roll: TrailBlazer Insight — local compliance scanning for PII, HIPAA, and PCI

0:20 – Show intro

0:47 – Setting up the case study: 350,000 records across 8 systems

1:52 – How growth through acquisition created 7 (then 8) active counterparty sources

3:55 – Why the same legal entity can appear differently in every system

6:22 – The small business analogy: 4 addresses in 13 years

8:09 – The first 18 months: why tax ID matching failed at scale

10:48 – Name matching, character limits, overflow fields, and legacy system formatting

12:41 – Spreadsheet-by-spreadsheet spinning wheels

13:25 – The breakthrough: contract type bucketing + multi-variable matching

15:08 – Moving to Snowflake and Elasticsearch for rule-precedence matching

16:14 – Where AI could accelerate this today — and what it still needs from you

17:41 – The result: 350K records collapsed to 35K true entities

18:13 – What came out of all that work

19:49 – Teaser: next episode covers how to prevent this from happening again

What Counts is produced by TrailBlazer Consulting, LLC and hosted by Lee Karas and Maura Dunn. Learn more at trailblazer.us.com or email us at info@trailblazer.us.com. Explore compliance-ready training at the TrailBlazer Learning Academy. Read more from Maura at mauradunn.substack.com. Music by Jason Blake. Full disclaimer.

Episode 132 – Most organizations are being pushed to adopt AI-powered workflows before their data is anywhere close to ready. In this episode of What Counts, Maura and Lee pick up where they left off — diving deep into the concept of data reconciliation and why it must happen before AI ever touches your records. Using a real-world example built across multiple systems — a customer database, a work order system, and a contract management platform — they break down what it means to have duplicate, overlapping, and contradictory counterparty data, and why humans, not algorithms, are the ones who can resolve it. Maura introduces the concept of the golden record, explains the role of metadata mapping and fuzzy matching, and walks through the governance framework — policy, process, and system-of-record designation — that prevents the mess from coming back. If your organization is facing an AI initiative, a system migration, or growing pressure around data privacy and right-to-be-forgotten compliance, this episode gives you the foundational framework you need to start doing it right.

Episode length: 00:26:36

Learn more by visiting our website, or by sending TrailBlazer an email at info@TrailBlazer.us.com.

Episode 131 – Data governance and AI readiness go hand in hand — and most organizations aren’t as ready as they think. In this episode, Maura and Lee take a hard look at what an AI-powered customer support escalation workflow actually requires to function. Spoiler: it’s not just a smart model. It’s clean, connected, versioned data — customer records, contract terms, and executed agreement instances all properly linked. Using a real-world cable company scenario, they unpack how disconnected systems, outdated identifiers, and missing metadata cause AI to hallucinate answers instead of finding them. The episode closes with an introduction to data objects and metadata mapping — and a preview of the counterparty reconciliation work that has to happen before AI can deliver on its promises.

Episode length: 00:19:21

Learn more by visiting our website, or by sending TrailBlazer an email at info@TrailBlazer.us.com.

Episode 130 – When a company acquires another business, it inherits a tangled web of contracts — each with its own payment terms, clauses, and conditions. Contract one says 30 days, contract two says 45, and contract three says you never have to pay. So what happens when you point AI at this mess? In this episode of What Counts, we explore why contract data governance must come before AI deployment. AI is a powerful governance accelerator, but only when organizations harmonize their terms, configure their systems, and maintain human oversight every step of the way.

Episode length: 00:17:12

Learn more by visiting our website, or by sending TrailBlazer an email at info@TrailBlazer.us.com.

In this episode of What Counts, Lee and Maura move beyond diagnosing the tension between growth and governance and dive into what real solutions look like. From the “records police” stereotype to the engineering metaphor of an ungoverned engine ready to blow, they unpack why organizations struggle to balance speed with safety—and how cross‑functional coalitions can change everything. Through stories about generators, pencils, rogue sales promises, and the realities of legal, IT, compliance, and business teams working in silos, they reveal how governance becomes a true accelerator when everyone solves the problem together instead of alone.

Episode length: 00:13:12

To find out more about TrailBlazer Consulting, LLC, please visit our website at www.TrailBlazer.us.com.

Episode 128 – In this episode of What Counts, Lee and Maura dive into one of the most universal challenges leaders face: balancing the urgency of growth with the discipline of governance. From chasing new markets to managing real‑world information chaos—yes, even inside an information governance firm—they unpack why governance always feels like something you’ll “get to later,” and why “later” is exactly when the problems show up. Through candid stories and practical examples, they reveal how founders, operators, and executives can build sustainable growth without sacrificing control.

Episode length: 00:14:26

Learn more by visiting our website, or by sending TrailBlazer an email at info@TrailBlazer.us.com.

Episode 127 – This episode of What Counts unpacks a problem every organization faces but few diagnose correctly: workflows fail when they don’t reflect the reality of how work actually gets done. Through real‑world examples—from delegated invoice approvals to storage and construction contracts—we explore how policy changes, unclear roles, and poorly analyzed workflows create bottlenecks, late payments, workarounds, and operational risk. The conversation highlights why modern workflow design must be grounded in process analysis, role clarity, and meaningful controls that support—not obstruct—the accomplishment of work.

Episode length: 00:18:39

Learn more by visiting our website, or by sending TrailBlazer an email at info@TrailBlazer.us.com.

Episode 125 – Contract Lifecycle Management touches every corner of an organization—finance, legal, procurement, operations, compliance, and the business itself. But despite the promise of modern CLM platforms, most implementations fail for one simple reason: the organization wasn’t ready for the software. In this episode of What Counts, Lee and Maura revisit a conversation recorded in early 2024, long before TrailBlazer Learning Academy and its governance accelerator templates were publicly available. With the Academy now live and widely adopted, the discussion is more relevant than ever. They explore why readiness, alignment, and governance‑ready templates are the true drivers of CLM success, and how TrailBlazer’s tools help organizations build clarity and confidence long before implementation begins.

Episode Length: 00:25:32