Capability · Gap Analysis

Validate first. Improve second.

Most organizations already own more training content than they can defend. Gap Analysis interprets what your standards, policies, and frameworks actually require, then measures your existing library against it. At meaning, rather than at keyword.

Dark charcoal precision grid with visible gaps cut into it, molten orange light beaming up from below. Gap analysis illustration.
Why this matters

The content exists. That does not mean it covers what it should.

Procedures change. Standards update. Regulatory expectations shift. Subject matter expands. Priorities move. Over time, gaps emerge, not because anyone intended to create them, but because maintaining alignment across hundreds of documents and courses becomes structurally impossible by hand.

The result is a familiar and dangerous confidence: the content exists, therefore it must be correct. Knowledge Foundry treats that assumption as the risk it is, and replaces it with coverage that can be demonstrated at the resolution of each requirement.

Coverage, at five resolutions

Structured analysis across five dimensions, not keyword matching.

Traditional audits look for the phrase. Knowledge Foundry looks for the requirement, and the evidence that satisfies it, even when the language does not match.

Explicit coverage

Direct references to a requirement, concept, control, outcome, or standard clause are located and cited.

Semantic coverage

Conceptual alignment where the meaning is present but the exact language differs. Keywords do not decide fitness.

Hierarchical coverage

Parent and child relationships and dependency chains across frameworks, evaluated as a graph rather than a flat checklist.

Evidence mapping

Verification claims, outcomes, and assessments are located and matched against the requirements that demand them.

Structural coverage

Content is evaluated for whether it sits in the right place in a learning pathway, not just whether it exists somewhere.

Gaps ranked by risk

Gaps are ranked by regulatory exposure, criticality, and downstream dependency, so remediation starts where it matters.

How it runs

From library to defensible baseline.

Gap analysis is read only. Evidence comes first. Each finding is traceable and cited back to source. Nothing in your library is altered.

STEP 01

Ingest the library

Existing courses, policies, procedures, manuals, and supporting documentation are read in place. No manual reauthoring.

STEP 02

Interpret requirements

Selected standards, frameworks, competencies, or accreditation criteria are decomposed into measurable, testable criteria.

STEP 03

Map evidence

The system identifies where each requirement is addressed and records the supporting evidence at the level of a sentence.

STEP 04

Score coverage

Explicit, semantic, hierarchical, and evidential matches are evaluated together to determine true alignment.

STEP 05

Report gaps

Requirements with insufficient support, weak evidence, or drift are flagged with source citations and remediation prompts.

What you get out

A defensible baseline you can act on, not a spreadsheet you cannot.

The output is not an executive summary written in generalities. It is a structured object. Each framework requirement, the evidence located for it, the strength of the match, and any gap. Each row traces back to source document and paragraph.

Explicit matches are cited. Semantic matches are scored with confidence. Missing coverage is enumerated and ranked by regulatory weight. Weak evidence is separated from absent evidence. Each finding is exportable, and each export carries the analysis version that produced it.

Common questions

How Gap Analysis works, in detail.

Keyword search finds the phrase. It does not confirm the requirement is met. Gap Analysis interprets each requirement into what would count as evidence, then locates that evidence, regardless of the exact wording. A course can pass a keyword audit while failing the underlying obligation, and often does.
No. If a framework exists, whether internal, ISO, regulatory, or accreditation, we compare against it. If one does not, the platform can extract an implied framework from the source documents themselves, then compare that to your training. Both paths are supported.
Each finding carries a criticality weighting drawn from the source requirement. Mandatory controls and obligations sensitive to risk surface first. Cosmetic and stylistic drift is separated from coverage drift and can be suppressed. The default report is triaged, not raw.
Yes. Gap analysis can run against one course, one policy family, one ISO clause, or a whole learning portfolio. The engine and reporting are the same. The scope is a parameter.
A structured report, readable by both machines and humans, that lists each requirement, the evidence located for it, the confidence of the match, and any gap. Each line links back to the source document and paragraph. Exportable as PDF, HTML, or JSON.
No. Gap analysis is read only. Nothing in your library is altered. Remediation is a separate, deliberate step you commission after the report is reviewed.
Bring us a library

See your coverage without guesswork.

Send us a course, a policy family, or an accreditation you must align to. We spend 45 minutes with the Foundry on your material, and you leave with a coverage report. Yours to keep.

We reply within one business day.