How to Run a Data Audit in a Weekend

Most businesses cannot answer a simple question: what data do you actually have? Not what you think you have. What is actually sitting in your spreadsheets, databases, and SaaS tools right now?

A data audit gives you that answer. It is a structured inventory of the data your organization collects, stores, and uses. It does not require a six-month consulting engagement. You can run a meaningful one in a single weekend. Here is the framework we use with our clients.

Before You Start: What You Need

• A spreadsheet with four tabs: Sources, Usage Map, Issues, and Action Plan.
• Access to your tools. Log into every system your team uses. If you do not have admin access to something, note it and move on.
• Two or three key people from different departments available for 15 to 20 minutes on Sunday morning. Send them a heads-up on Friday.

Saturday Morning: Inventory Your Data Sources

In the Sources tab, create columns for: Source Name, Type (database, spreadsheet, SaaS tool, manual report), Owner, Approximate Size, Update Frequency, and Notes. Then walk through each category:

• SaaS tools: CRM, accounting, project management, marketing analytics, HR, and support platforms
• Spreadsheets: Check shared drives, Google Drive, OneDrive, and Dropbox. This is where you find the most surprises. That spreadsheet your operations manager updates every Monday might be the most important dataset in the company.
• Databases: SQL Server, PostgreSQL, MySQL, or any data warehouse (Snowflake, BigQuery, Redshift)
• Manual reports and third-party data: PDFs, emailed reports, vendor data, industry benchmarks. Easy to overlook, but they often contain data that lives nowhere else.

If your company relies heavily on Excel, pay extra attention here. Spreadsheet sprawl is one of the most common data problems we see. Our comparison of Excel dashboards vs BI tools covers the signs that you have outgrown spreadsheets.

By Saturday lunch, you should have 15 to 40 sources listed. Fewer than 10 means you are probably missing things. More than 50 is itself a finding worth noting.

Saturday Afternoon: Map Who Uses What

In the Usage Map tab, answer four questions for each source: Who accesses it? How often? What decisions does it inform? How do they get to it (direct login, export, or someone emails it)?

You will likely discover single points of failure (one person maintains a source everyone depends on), abandoned data sources from old projects, critical numbers that get manually copied between systems, and multiple departments maintaining their own conflicting version of the same metric. Do not fix anything yet. Just document it.

Sunday Morning: Identify Gaps, Duplicates, and Trust Issues

Switch to the Issues tab and work through three categories:

Gaps:Ask your key people: "What questions come up in your work that you cannot answer with the data you have today?" Common answers include customer lifetime value, true cost per acquisition, and project profitability.

Duplicates: Where does the same data live in multiple places? If revenue shows up in your CRM, your accounting software, and a spreadsheet, which one is the source of truth? Conflicting numbers erode trust in all of them.

Trust issues:Ask your team: "What data do you not trust?" Everyone has an answer. Data people do not trust is data people do not use, and that is wasted investment.

Sunday Afternoon: Build Your Action Plan

Organize findings into three buckets:

Quick wins (this week): Delete unused sources, fix broken reports, assign ownership to orphaned datasets, consolidate obvious duplicates.

Short-term projects (30 to 90 days): Build a central dashboard for high-traffic metrics, automate manual copy-paste workflows, clean up the system with the worst trust issues, establish a single source of truth for key numbers.

Strategic investments (next quarter+): Implement a data warehouse, build self-service reporting, fill your biggest data gaps, and invest in data engineering services to make it all sustainable.

For each item, note who owns it, a rough timeline, and what success looks like. Keep the plan to one page.

What to Do with the Results

• Share it with leadership. A clear inventory with identified issues makes the case for investment better than any vendor pitch deck.
• Use it to scope projects. If you plan to build dashboards, the usage map tells you exactly who needs what. Our 6-step dashboard system starts with stakeholder interviews, and a completed audit gives you a massive head start.
• Revisit it quarterly. New tools get adopted, people leave, processes change. A quarterly check keeps your data landscape from drifting back into chaos.

When to Bring in Outside Help

You can run this audit yourself. But consider outside help when your data lives in complex technical systems that require engineering knowledge, when internal politics make honest answers difficult, or when your action plan includes projects your team cannot execute. This is exactly the kind of work a fractional data team is built for.

Start This Friday

Set aside this weekend. Create the spreadsheet. Send the calendar invites. By Sunday evening, you will have a clearer picture of your data than 90% of companies your size.

If you want help turning your findings into a concrete plan, book a free consultation with our team. We will review your audit, help you prioritize, and give you an honest assessment of what to tackle first.