A data inventory template for forgotten archives

Why a data inventory matters for dormant archives

When a business acquires another company, shuts down a product line, or migrates away from legacy platforms, data often remains scattered across forgotten servers, cloud buckets, and offline tapes. That data can be valuable, but it can also expose risk. Without a clear inventory, you cannot answer three basic questions:

1. What exists?
2. Who may use it?
3. What must be protected or deleted?

A disciplined inventory turns a chaotic collection into a documented asset. It enables you to present a clean, reviewable package to potential partners, to meet regulatory obligations, and to reduce the cost of unnecessary storage. The template below is built from the work we do at Dormant Data Partners. It reflects the fields we ask for in every engagement, and it can be used as a stand‑alone tool.

Key components of a data inventory template

The template is organized into six logical sections. Each section maps to a service we offer, and each field is short enough to be filled in by a data steward or a technical lead.

1. Source identification

Field	Description
System name	Human‑readable name of the application or platform.
Owner / Business unit	Department that originally commissioned the data.
Physical location	Data center, cloud region, or tape vault identifier.
Date range	First and last record dates covered by the system.
Status	Active, decommissioned, archived, or unknown.

2. Dataset catalog

Field	Description
Dataset name	Unique name used in internal reporting.
Format	CSV, Parquet, SQL dump, etc.
Volume	Approximate size (GB) and record count.
Primary keys	Fields that uniquely identify a record.
Refresh cadence	Static, daily, real‑time, or ad‑hoc.

3. Rights and provenance register

Field	Description
Origin	Internal creation, third‑party purchase, public source.
License type	Proprietary, open‑source, restricted, unknown.
Expiration	Date the license ends or “perpetual”.
Restrictions	Commercial use, redistribution, geographic limits.
Provenance notes	Brief description of how the data moved between systems.

4. PII and privacy mapping

Field	Description
Contains PII?	Yes / No.
PII categories	Names, emails, IP addresses, biometric data, etc.
Legal basis	Consent, contract, legitimate interest, etc.
Retention rule	Retain, delete after X years, or archive with encryption.
Mitigation steps	Pseudonymisation, masking, aggregation.

5. Deduplication and quality flags

Field	Description
Duplicate indicator	Yes / No / Unknown.
Quality score	1‑5 rating based on completeness and consistency.
Known issues	Missing values, outdated codes, schema drift.
Suggested cleanup	De‑duplicate, re‑code, enrich, or discard.

6. Metadata recovery and sample manifest

Field	Description
Metadata source	Data dictionary, schema file, code comments.
Recovery status	Complete, partial, not started.
Sample size	Number of rows or files provided for review.
Access method	Secure FTP, encrypted S3 bucket, on‑prem copy.
Contact	Person responsible for granting access.

Each row in the template corresponds to a distinct dataset. The template can be captured in a spreadsheet, a database table, or a structured file such as JSON. The important point is that the fields are consistent across all datasets, making downstream analysis straightforward.

Step‑by‑step guide to completing the template

Below is a practical workflow that you can follow from the moment you learn that an archive is dormant to the point where you have a completed inventory ready for a readiness review.

Step 1 – Assemble a small project team

• Owner: Assign a senior data steward or product manager.
• Technical lead: Someone who knows the storage infrastructure.
• Legal liaison: A counsel or compliance officer who can answer rights questions.

Document the team in the “Contact” column of the template. This ensures accountability.

Step 2 – Capture the system landscape

Run inventory scripts, query asset management tools, or request a list from the IT operations group. Populate the Source identification table for every system that may still hold data. If a system is unknown, create a placeholder entry with “unknown” status and schedule a follow‑up.

Step 3 – Export high‑level dataset listings

Most databases provide a catalog of tables or collections. Export that catalog into a CSV and import it into the Dataset catalog section. For file‑based stores, list the top‑level folders and note the file types.

Step 4 – Map rights and provenance

Work with the legal liaison to answer each rights field. If a license is “unknown,” mark it as such and flag it for deeper review. Include any contractual clauses that limit commercial use or require attribution.

Step 5 – Identify personal data

Run automated scans for common PII patterns (email regex, SSN formats) and supplement with manual review. Record the result in the PII and privacy mapping section. This step is essential before any external party can view the data.

Step 6 – Assess duplication and quality

Use deduplication tools or simple SQL GROUP BY queries to spot obvious duplicates. Assign a quality score based on completeness, schema consistency, and known issues. Note any remediation actions you plan to take.

Step 7 – Recover missing metadata

If data dictionaries are stored in Confluence, SharePoint, or old wiki pages, retrieve them now. Populate the Metadata recovery fields. If metadata cannot be recovered, add a note describing why and how you will mitigate the gap (e.g., by creating a new dictionary).

Step 8 – Create a sample manifest

Select a representative subset of each dataset—as an Illustrative example, 100‑500 rows or a few megabytes. Store the sample in a secure location and record the access method in the template. This sample will be the first thing a potential buyer or partner reviews.

Step 9 – Review and sign off

Schedule a short meeting with the project team. Walk through every row of the template. Confirm that all fields are filled, that rights are accurately captured, and that any “unknown” items have an action plan. Once the team agrees, mark the row as “Reviewed” in a separate column.

Step 10 – Submit for a readiness review

When the inventory is complete, submit a brief through our confidential seller brief page. Include the inventory file, the sample manifest, and a short description of the archive’s business context. Our team will evaluate the package and advise on next steps, such as deeper rights clearance or additional data preparation.

Checklist for a ready‑to‑review archive

• All systems that may contain data are listed in Source identification.
• Every dataset has a row in Dataset catalog with format and volume.
• Rights and provenance fields are completed for 100 % of datasets.
• PII flags are set, and legal basis is documented where applicable.
• Duplicate indicators and quality scores are assigned.
• Metadata recovery status is “Complete” or “Partial” with notes.
• A sample manifest exists for each dataset and is stored securely.
• A project owner, technical lead, and legal liaison are recorded.
• The entire template has been reviewed and signed off by the team.
• The package is held securely and a high-level inquiry submitted via /accession/.

If any item remains unchecked, the inventory is not yet ready for external review. Address the gaps before moving forward.

Common pitfalls and how to avoid them

Pitfall	Why it hurts	Mitigation
Skipping systems that are “offline”.	Data may be locked on tapes or de‑provisioned VMs.	Ask the infrastructure team for a full list of decommissioned assets. Include “offline” as a status.
Assuming rights without documentation.	A license may restrict commercial use, causing a breach later.	Treat every unknown license as “restricted” until proven otherwise. Involve counsel early.
Ignoring small personal data fields.	Even a single email address can trigger privacy obligations.	Run automated scans on every file, not just the main tables.
Leaving duplicate data unmarked.	Buyers will see inflated volumes and may discount the asset.	Run deduplication scripts and record the outcome in the template.
Providing samples without security controls.	Unsecured samples can leak sensitive information.	Store samples in an encrypted bucket, grant access only to vetted reviewers, and log all downloads.

By anticipating these issues, you keep the inventory clean and the review process smooth.

How we help

Dormant Data Partners specializes in turning dormant archives into documented, reviewable data assets. Our services align directly with the sections of the template:

• Data inventory – We build the Source identification and Dataset catalog tables for you. Learn more at /collections/data-inventory/.
• Rights and provenance register – Our legal experts verify licenses and annotate restrictions. Details at /collections/rights-and-provenance/.
• Dataset preparation – We handle deduplication, PII masking, and metadata recovery. See /preparation/dataset-preparation/.

Our recovery planner (/preparation/recovery-planner/) generates a first-pass inventory checklist from storage formats, documentation and access problems. No upload is required. It identifies questions to resolve without determining rights or giving a score. Use it before you submit an accession inquiry.

The full process is described in our how it works page. It walks you through discovery, inventory, preparation, and optional licensing. The process is designed for senior decision‑makers who need a clear, actionable path.

If your organization is facing an acquisition, a product shutdown, or a legacy system migration, start with a confidential seller brief at /accession/. Share the scope, timeline, and authority structure. We will return a concise assessment of what can be packaged, what needs further work, and an estimate of the effort required.

---