#DataGovernance

Records Management vs. Information Governance: Cutting Through the Data Noise – E135

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.

Stop Counterparty Data Sprawl: Centralize & Control Vendor Information Before Contracts Begin – E134

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.

Counterparty Data Reconciliation at Scale: A 350,000-Record Case Study – E133

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.

Your Data Is Lying To You: Why Reconciliation Has To Come Before AI – E132

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.