What problem it solves
Requirement references can show possible relationships. GoldMap shows where prior learning actually counts inside the selected program.
← Back to GoldMap overview
Step 1. Gather
Step 2. Institution
Step 3. Program selection
Step 4. Report
Low Fit
Moderate Fit
Higher Fit
GoldMap Explore
This page explains the GoldMap segment in the same portal language as the other Explore surfaces. It is not a framed app, not a modal, and not a separate product shell.
GoldMap answers the advising question that static requirement references alone do not answer: how does this learner's prior learning apply to this specific target program before the learner commits?
What the learner gets
A course-by-course applicability report with dispositions, evidence, and requirement context before enrollment decisions are made.
What institutions get
A clearer picture of learner intent tied to institution, program, and prior learning history instead of vague interest signals.
What it does not claim
GoldMap is advisory. Official applicability decisions remain with the institution and its review rules.
What matters is what the learner has actually done, tried, completed, struggled through, and learned from. Measurement is often inaccurate because most systems never receive the fuller record of experience, failure, iteration, and nontraditional evidence.
Why traditional measurement falls short
- Most learners do not share everything they have done.
- Failure, persistence, and lived experience rarely show up in official records.
- Knowledge depth alone does not explain real-world readiness.
- Static transcripts leave out evidence that may change the guidance story.
Why GoldMap gathers more context
- Transcript, resume, certifications, badges, and other evidence can all matter.
- The fuller the evidence, the more grounded the applicability and next-step suggestions become.
- GoldMap is trying to understand what may count, not just what was officially labeled.
- This is why the reflection and direction layers belong before a narrow target choice.
Bloom: what someone knows
Bloom helps explain depth of knowledge through Remember, Understand, Apply, Analyze, Evaluate, and Create. It is useful for learning outcomes, but it does not fully describe workforce performance.
Dreyfus: how well someone can do it
Dreyfus helps explain real-world skill growth through Novice, Advanced Beginner, Competent, Proficient, and Expert. It adds judgment and execution, not just content exposure.
O*NET: what work requires
O*NET grounds the conversation in workforce competencies such as knowledge, skills, abilities, work activities, work context, and tasks.
Kolb and Miller: how experience becomes performance
Kolb explains how learning develops through experience, reflection, and experimentation. Miller helps show the movement from knowing, to knowing how, to showing how, to actually doing.
Where KSAWorks sits
GoldMap gathers evidence. Competency mapping aligns it to workforce needs. Gap analysis helps explain what is still missing. Pathways turn that into next-step action.
The anchor line
Bloom tells you what you know. Dreyfus tells you how well you can do it. O*NET tells you what the world needs. KSAWorks connects them.
GoldMap has one flow. Importer, upload, and manual entry are different intake paths into the same applicability segment.
Bring prior learning in through coursework import when available, or use upload and manual entry when it is not.
Select the receiving institution whose program requirements will be used for the applicability review.
Choose the target program so the learner record is checked against a real published requirement structure.
Generate a requirement-aware report that shows what satisfies, what partially satisfies, and what remains a gap.
Every prior course receives a disposition, and the report rolls those decisions up against the selected program's published requirement lines and groups.
Course Dispositions
- Satisfies when evidence strongly matches the target requirement.
- May satisfy when evidence is partial or needs review.
- Elective or Gen Ed when the course counts outside the named major requirement.
- Does not apply when the course does not satisfy the selected program requirement set.
Report Outcomes
- Requirement coverage for major, general education, and elective areas.
- Visible evidence and confidence for each course-level decision.
- A clearer planning conversation before time and money are committed.
- Institution-specific applicability instead of generic assumptions.
Jordan is not a separate product. Jordan is one learner shown three ways so the same person can demonstrate low, moderate, and higher applicability against a real target program.
Same learner, different readiness
- Jordan A shows low fit from a manufacturing-heavy DCCC record.
- Jordan B shows moderate fit from a business-aligned prior learning record.
- Jordan C shows stronger fit with a fuller DCCC applicability pattern.
Same GoldMap segment
- Same live GoldMap pages.
- Same institution and program selection flow.
- Same applicability report logic.
- No detached demo-only shell.
Jordan Reynolds A
Manufacturing and electronics coursework with limited direct alignment to WCU Business Management.
Launch Jordan AJordan Reynolds B
DCCC business courses that land meaningfully against WCU pre-business requirements.
Launch Jordan BJordan Reynolds C
A fuller DCCC course pattern that shows stronger overall applicability while still using the same learner storyline.
Launch Jordan C