LMS Content Inventory: L&D’s Spreadsheet Checklist Before Migration
An LMS content inventory is a structured, exportable catalog of every learning asset your LMS holds, and it must capture core fields like title, type, owner, objectives, last update date, review cadence, and performance metrics to make migration, compliance, and governance possible. Without that catalog, teams migrate blind, miss expired certifications, and duplicate effort. With it, you can prioritize updates, retire dead content, and prove what learners actually received.
TL;DR:
- For libraries under a few hundred items, export everything; larger libraries can start with a stratified sample, then expand if verification finds gaps.
- Record SCORM package and SCO IDs, version, and referenced assets, plus LTI resource link IDs; test imports, launches, and gradebook score transfer in staging.
- Migrate aligned, recently used assets as is, rebuild moderately aligned items with outdated manifests, archive duplicates, and retire anything failing compliance or accessibility checks.
- Schedule recurring scans to flag policy or product changes, but require subject matter experts to review automated tags and draft updates before publication.
- Name a lead and unit owners first; data collection and enrichment take two to four weeks, followed by one to two weeks of quality checks.
Table of Contents
- Content Inventory Checklist and Spreadsheet Schema
- How to Run the Audit: Steps, Roles, and Timeline
- Technical Considerations: SCORM, Common Cartridge, and LTI Identifiers
- Decision Rubric for Keep, Retire, Archive, or Migrate
- Tools and Automation to Accelerate Inventory Work
- Continuous Audit and AI-Assisted Updates: An Enterprise Approach
- Author Perspective: Three Priorities for L&D Leaders
- How Continuity Intelligence Supports Continuous Inventory Health
- FAQ
- Sources
Content Inventory Checklist and Spreadsheet Schema
A content inventory works best as a living workbook, not a one-time export. The format matters less than the discipline of keeping every asset in one place, with consistent columns your whole team understands.
Start with a flat spreadsheet or a connected database. Each row is one learning asset: a course, a module, a video, a document, or a linked external tool. The goal is a single source of truth that supports three different jobs at once: migration planning, compliance verification, and performance analysis.
Core columns to include:
- Unique ID: a stable identifier that survives exports and re-imports.
- Title and content type: course, microlearning, video, PDF, assessment, or external LTI tool.
- File or package name and LMS path: where the asset lives today.
- Owner and target audience: who maintains it and who it’s built for.
- Learning objectives and tags or competencies: what the content teaches and how it maps to skills.
- Modality and duration: self-paced, instructor-led, blended, and estimated completion time.
- Publish date, last updated date, and next review date: the content life cycle at a glance.
- Accessibility status and compliance flags: WCAG conformance notes and regulatory tags.
- Performance metrics: completion rate, learner ratings, assessment scores.
- Dependencies and manifest or SCORM/LTI IDs: technical links that keep the asset functional.
Not every project needs all of these filled in immediately. A migration-focused inventory leans hardest on manifest IDs, LMS path, and dependencies. A compliance audit leans on review dates, compliance flags, and owner assignments. An analytics push prioritizes performance metrics and tags. Content inventories used by public sector teams typically include author, status, audience, dependencies, and review frequency as a baseline, which maps closely to what enterprise L&D teams need.
A sample row for a SCORM-based compliance course might read: ID COMP-0412, title “Workplace Harassment Prevention,” type SCORM 1.2, owner Compliance Team, last updated January 2025, next review January 2026, compliance flag “Annual Mandatory.” A linked external tool row would instead carry an LTI resource link ID and a domain reference rather than a package name.
How to Run the Audit: Steps, Roles, and Timeline
An audit without defined ownership stalls halfway through. Before pulling a single export, assign a project lead, identify content owners for each business unit, and loop in subject matter experts who can confirm whether objectives are still accurate.
- Define scope and success metrics: decide whether you’re inventorying one LMS instance, multiple systems, or a subset tied to a specific compliance program.
- Extract data: pull LMS reports, export SCORM and Common Cartridge packages, or use API calls to harvest metadata in bulk.
- Choose sampling or full export: a library under a few hundred items usually supports a full export; larger libraries often start with a stratified sample by content type or business unit, then verify accuracy before scaling up.
- Enrich records: add objectives, tags, and compliance flags that the raw export won’t include.
- Run QA checks: scan for broken links, test launch behavior, and run accessibility smoke tests on a representative subset.
- Sign off: have content owners confirm their portion of the inventory before it becomes the system of record.
A typical timeline for a mid-size library runs two to four weeks for extraction and enrichment, with QA and sign-off adding another one to two weeks. Larger enterprise libraries with multiple LMS instances often extend this to six to eight weeks, particularly when sampling needs to be expanded after early verification reveals gaps.
Pro Tip: Run your accessibility and broken-link scans in parallel with enrichment, not after it, so content owners can fix issues while the context is still fresh in their notes.
Verification matters as much as collection.
Technical Considerations: SCORM, Common Cartridge, and LTI Identifiers
Content migration fails most often at the technical layer, not the metadata layer. A SCORM package is a ZIP file built around an imsmanifest.xml file, and that manifest defines the organization structure, resources, and SCO definitions your LMS needs to preserve launch behavior and runtime tracking.
Capture these items for every SCORM-based asset:
- Package ID and SCO IDs from the manifest, so launch behavior maps correctly after import.
- SCORM version (1.2 or 2004), since testing requirements for import and launch compliance differ by version.
- Key assets referenced in the manifest, including any external media files.
- Common Cartridge metadata, which may bundle LTI links and, depending on version, accessibility metadata worth recording in a migration registry.
- LTI resource link IDs, since LTI Advantage guidance notes that resource links carry grade and line item information that must transfer correctly or gradebook sync breaks.
For any externally linked tool, record it as an LTI link with its domain, configuration notes, and whether it uses deep linking. Treat it as a dependency, not a standalone asset.
Before calling an item migration-ready, run three checks: an import test into a staging environment, a launch test to confirm the content opens and tracks correctly, and a grade round-trip check to verify scores pass back to the gradebook. Our free SCORM validator can confirm manifest integrity before you move a package anywhere.
Decision Rubric for Keep, Retire, Archive, or Migrate
Not every asset deserves a seat in the new system. A scoring rubric turns a subjective debate into a repeatable decision, and it keeps the inventory honest about what actually earns its place.
Score each item across these dimensions:
- Business alignment: does it still map to a current role, product, or policy?
- Usage: completion counts and recency of learner activity.
- Last update and review status: how long since content or objectives were verified.
- Compliance risk: whether outdated instructions could mislead employees or expose the organization to risk.
- Accessibility: whether it meets current conformance standards.
- Duplication: whether another asset already covers the same objective.
- Technical portability: whether the package format imports cleanly into the target system.
A simple threshold model works well: high alignment and recent usage means migrate as-is; moderate alignment with an outdated manifest means migrate with a technical rebuild; low alignment or heavy duplication means archive; failed compliance or accessibility checks mean retire immediately regardless of usage.
Record every decision in a keep/kill column with a short note, the reviewer’s name, and the date. Recurring compliance and certification content deserves its own flag, since it needs scheduled renewal rather than a one-time keep decision, and neglected inventories tend to raise compliance risk precisely because that renewal gets missed.
Tools and Automation to Accelerate Inventory Work
Manual inventory building does not scale past a few hundred assets. LMS export and reporting features handle bulk metadata pulls, and API access lets you automate extraction on a schedule rather than re-running it by hand every quarter.
Useful tool categories include:
- Manifest parsers that read SCORM and Common Cartridge packages and populate ID fields automatically.
- SCORM validators that confirm package integrity before import or after export.
- Broken-link scanners that flag dead URLs across course content.
- Accessibility checkers that run WCAG smoke tests across a batch of courses rather than one at a time.
Our free tools for L&D and instructional design cover several of these categories if you’re building a workflow from scratch. Automation also extends to metadata enrichment and scheduled drift scans that flag when content has likely gone stale based on last-update dates and related content changes elsewhere in the organization.
Pro Tip: Treat automated tags and flags as a first draft, not a final answer. Automation catches patterns at scale, but it still misses pedagogical nuance that only a subject matter expert can judge.
Automation creates noise when it flags every minor formatting change as drift or when metadata enrichment guesses at objectives from course titles alone. Human-in-the-loop review stays essential for exactly this reason: automation narrows the list of what needs attention, and people decide what the attention should look like.
Continuous Audit and AI-Assisted Updates: An Enterprise Approach
A one-time inventory goes stale the moment organizational knowledge changes. Treating the inventory as a living record, refreshed continuously rather than rebuilt annually, is what keeps compliance and performance data trustworthy over time.
In practice, continuous auditing maps directly onto the inventory spreadsheet you already built. Each scheduled scan compares current content against policy changes, product updates, or prior versions, and flags discrepancies as prioritized work items rather than burying them in a static report. That turns the inventory from a snapshot into a queue.
What this looks like operationally:
- Automated discrepancy detection flags when content no longer matches current policy, product details, or procedure.
- Prioritized alerts rank those discrepancies by compliance risk and audience size rather than treating every flag equally.
- AI-assisted draft updates give content owners a starting revision instead of a blank page, with human review before anything publishes.
- Audit trails log who reviewed each flag and what they decided, which supports the same keep/kill documentation discussed earlier.
Automation handles detection and first-draft generation well. It does not replace a subject matter expert’s judgment on tone, nuance, or whether a regulatory change actually applies to a given course. Integration matters here too: continuous audit workflows need to connect to the tools you already run, including your LMS, SSO, and content repositories, rather than asking teams to adopt a parallel system. Our guide to AI content governance walks through how that connective layer typically gets built.
Author Perspective: Three Priorities for L&D Leaders
If I had to narrow an inventory project to three priorities, they would be scope, ownership, and measurement. Keep the first pass manageable, even if that means sampling a large library instead of attempting a full export in week one. Name a single owner for the spreadsheet itself, separate from the content owners, so the inventory doesn’t drift the moment the project ends. Instrument performance metrics from day one rather than retrofitting them later.
Document every keep or retire decision with a note and a date, and set a review cadence you can actually sustain. Resist the instinct to migrate everything. The rubric exists so you don’t have to.
— Sally
How Continuity Intelligence Supports Continuous Inventory Health
A completed inventory is a starting point, not a finish line. We built our platform to keep that spreadsheet accurate after the project wraps, running continuous audits against your live LMS and content repositories, surfacing prioritized drift alerts, and generating AI-assisted draft updates for human review rather than silent auto-publishing.
Enterprise L&D teams, compliance managers, and certification program owners tend to see the most value, since they carry the largest libraries and the highest cost when outdated content slips through; sales leaders especially benefit from tools that help them use buyer mapping and AI to make reps use content. Our Self-Serve plan starts at $2,500 per month, and our Enterprise Managed plan starts at $95,000 per year for organizations that need a fully managed engagement. If your library is large enough that in-LMS exports miss content living outside the platform, our deep internet scan service extends discovery beyond your LMS walls.
FAQ
What does LMS content mean?
LMS content refers to any learning asset stored or delivered through a learning management system, including courses, videos, assessments, documents, and linked external tools. It covers both self-contained packages like SCORM courses and externally hosted resources connected through LTI.
What are LMS tools examples?
LMS tools typically include authoring tools for building courses, reporting dashboards for tracking completions, and integration tools like APIs or LTI connectors for linking external resources. Supporting tools such as SCORM validators and accessibility checkers also fall into this category, since they verify content before and after it reaches the LMS.
What does LMS stand for?
LMS stands for learning management system, the software platform organizations use to host, deliver, and track training content. It manages everything from course enrollment to completion records and, in many cases, compliance reporting.
What are the top 5 LMS systems?
The LMS market includes many established platforms, and the right choice depends heavily on organization size, compliance needs, and existing tool integrations rather than a single universal ranking. Evaluating platforms against your specific content formats, such as SCORM and LTI compatibility, matters more than following a generic top-five list.
How often should a content inventory be reviewed?
Review cadence depends on content type: regulatory and compliance training often needs an annual or more frequent review, while evergreen skills content can go longer between checks. Recording a next review date for every asset during the initial inventory makes this cadence enforceable rather than aspirational.
Sources
- Content inventory | Digital Service Standard
- SCORM Users Guide for Programmers (ADL)
- SCORM 2004 4th Ed. Testing Requirements (ADL)
- Best Practices for LTI Assessment Tools (1EdTech)
- Content inventory and audit - Province of British Columbia