Portfolio Intelligence
The course still works. Until you need to change it.
It launches. It tracks. The LMS reports completion. Then someone asks for an update, and you discover nobody can edit it anymore.
Source files disappear. Authoring tools change. Developers leave. Plug-ins die. A small update turns into a rebuild, and you end up paying again for a course you already own.
Portfolio Intelligence shows you what you still have, what you can edit or recover, and what may become a problem before your next update or migration.
73 packages across seven public-sector publishers. 46.6% shipped with no editable source.
The evidence
We measured 73 real course packages.
46.6%
had no editable source
15.1%
already had a dead runtime
70/73
still on SCORM 1.2
All 73 still tracked correctly.
The LMS still saw healthy courses. But tracking correctly is not the same as being maintainable. An LMS tells you the first. It does not tell you the second.
Seven publishers, four regions. We published our predictions, and what result would prove us wrong, before we opened a single package. By the time we went looking, one publisher’s index had been deleted; we recovered the packages through the Internet Archive.
Read the full study: method, sample frame, per-publisher results and limits →
How it runs
Know what you have. Know what it teaches. Know what’s worth keeping.
Stage one is cheaper, faster and sometimes decisive. There is no point mapping the capability coverage of a course nobody can open. If your library is in good shape, stage one is short and we say so.
01
Library Audit
What can we still use?
Inventory → source → runtime → portability → recovery. What exists, what opens, what can still be edited, and what is already broken.
02
Capability Intelligence
What does the library actually teach?
Objectives → KSATs → capability coverage → duplication → gaps. What the surviving library collectively teaches, where it repeats itself, and what it never covers.
03
Portfolio Decisions
What should we keep, recover, rebuild or retire?
Recover, rebuild or retire. Each costed, so the decision is made against evidence rather than whoever complains loudest.
Saving the library is only stage one.
Once we know which courses are still usable, we map what they actually teach. That shows where the library duplicates itself, where important capabilities are missing, and which courses are worth keeping.
Every course ends up in one of four buckets
Every course lands in one of the four, with the evidence behind it.
What you get
A decision map, not a spreadsheet of course titles.
The three stages produce one artifact: every course in your library, placed in a bucket, with the evidence and the cost behind the placement. Inventory and migration risk come out of stage one; capability coverage, duplication and gaps out of stage two; the economics of recover versus rebuild versus retire out of stage three.
How this connects to the rest
Portfolio Intelligence tells you what you have, what is worth keeping, and what is missing. Learning Preflight™ tells you whether the courses you are keeping are instructionally ready. Course Factory™ rebuilds or creates what isn’t. Most libraries need them in that order. You cannot test what you cannot open.
Pricing
Scoped to your library.
A 200-course library in good shape isn’t the same engagement as 3,000 courses built across fifteen years and six authoring systems. Pricing depends mainly on:
- Library size. How many packages, and whether you can export them or we work from the LMS. It scales far better than linearly. The checks are automated.
- Stage one only, or stage one plus capability mapping. Reading the packaging is faster than reading the instruction.
- How much content needs recovering. Triage and a ledger is one price; getting content back out of courses whose source is gone is another.
- Security and reporting requirements. Content that cannot go to a commercial API is scoped separately, as is checking what each package reports to your LMS or LRS. See data handling.
Want a number before a conversation? The published study applied these rules to 73 packages from seven public-sector publishers, and reports how much of that sample could still be opened and edited at all.
How much of your library can you still open?
If you are planning a migration, refresh or consolidation, we can show you what is actually maintainable before you decide what to move, recover, rebuild or retire.
Scoped per engagement · hello@actyra.com · +1 (407) 222-5432