People, domains, groups, and access
Learner, instructor, and vendor files; internal and external populations; privileged access; communities; permissions; and system logs.
BaseCamp feature map
BaseCamp organizes the capabilities needed to plan, deliver, evaluate, document, and improve organizational learning. The feature map helps learning teams select a coherent implementation scope instead of assembling disconnected tools for each stage.
Overview
A learning management system creates value when its functions work together. Learner eligibility should influence registration. Catalogues and tracks should guide selection. Calendars should connect with delivery, resources, instructors, rooms, and capacity. Assessments should update progress. Certificates should follow approved completion rules. Analytics should use the same governed history rather than reconstructed data. Program evaluation and feedback can then use participation, assessment, completion, provider, adoption, and cost evidence from the same governed learning record.
BaseCamp groups these needs into a practical feature architecture. Core administration establishes people, access, catalogues, tracks, calendars, and knowledge. Additional capabilities can extend delivery, examinations, assessments, deliberation, certification, communication, analytics, corporate hierarchy, costing, and customization.
The correct implementation scope depends on the organization. A training department focused on mandatory certification may prioritize eligibility, learning tracks, examinations, repeat rules, and expiry monitoring. A corporate academy may require extensive catalogues, instructor and vendor management, blended delivery, communities, knowledge resources, evaluation, and cost analysis. The feature map supports both without treating one model as universal.
Connected process
The sequence below helps avoid implementing advanced reporting or automation before the underlying records and rules are dependable.
Define learner populations, instructors, vendors, organizational structures, domains, groups, communities, access rights, and audit expectations.
Create catalogues, courses, examinations, learning tracks, prerequisites, target groups, competencies, and completion expectations.
Publish calendars and offerings with delivery mode, instructor, location, capacity, materials, timing, fees, and registration conditions.
Manage applications, approvals, registrations, attendance, content access, assignments, communication, examination activity, and support.
Apply grading, appraisal, practical evaluation, deliberation, repeat, remediation, completion, and certification rules.
Analyze participation, progress, outcomes, organizational coverage, engagement, provider quality, resource use, and approved cost measures.
Capabilities
Each group has a distinct responsibility while contributing to one consistent learner and activity history.
Learner, instructor, and vendor files; internal and external populations; privileged access; communities; permissions; and system logs.
Applications, eligibility, supervisor or administrator approval, priorities, capacity, waiting considerations, and enrollment.
Course and exam catalogues, prerequisites, target audiences, development paths, schedules, instructors, resources, venues, and fees.
Online, classroom, hybrid, self-paced, secure local, attendance, assignments, multimedia, examinations, rooms, seating, and supervision.
Appraisals, practicals, grading, feedback, completion status, deliberation, remediation, repeat rules, and certificates.
Controlled resources, communities, alerts, reporting, hierarchy-based insight, provider evaluation, fees, and cost analysis.
Combine learner feedback, assessment outcomes, participation, provider evidence, adoption measures, and cost context to review training effectiveness and improve future programs.
Governance
Features become dependable only when the organization knows who owns the rules, records, content, approvals, and outcomes.
Assign responsibility for eligibility, prerequisites, mandatory learning, pass criteria, repeats, certification, renewal, and exemptions.
Identify who creates, approves, publishes, reviews, retires, and versions courses, examinations, materials, and learning tracks.
Define authoritative sources for people and hierarchy data, privileged information, role assignment, retention, and audit review.
Agree who interprets participation, performance, feedback, provider quality, cost, and organizational coverage—and what action follows.
Implementation readiness
A phased plan should preserve end-to-end user journeys even when not every optional capability is introduced at once.
Choose the learner and administrator journeys that must work completely in the first release.
Identify the structures, rules, data, content, notifications, reports, and integrations required by those journeys.
Set up the selected feature groups and load only approved, cleansed, useful records and materials.
Test eligibility, application, registration, delivery, assessment, completion, communication, reporting, and exception handling.
Add later capabilities only when ownership, data quality, adoption, support, and measurable need are clear.
Operational value
The platform can support different organizational priorities without fragmenting learning records and governance.
Target mandatory programs, apply eligibility and repeat rules, track completion, and manage certification or renewal.
Build role-based tracks, blended offerings, communities, knowledge resources, appraisals, and progress reviews.
Manage applicants, external learners, registration, providers, fees, assessments, certificates, and historical records.
Frequently asked questions
No. The implementation should include the capabilities needed to complete the agreed learning journeys, with optional groups added through a controlled roadmap.
A catalogue organizes available courses or examinations. A learning track arranges selected learning into a development path with sequence, prerequisites, role relevance, or completion expectations.
Yes. Administrators, managers, learners, instructors, providers, and reviewers can receive different access based on responsibilities and approved data visibility.
Yes. Eligibility, targeting, prerequisites, approvals, priorities, and learning tracks can distinguish mandatory, role-based, recommended, and elective development.
Start with the most important complete learning journeys, confirm the governing rules and data they need, and avoid introducing features whose owners, content, or measures are not ready.
Yes. Approved labels, statuses, forms, messages, reports, roles, and workflows can reflect the organization’s learning vocabulary and operating model.
Plan the next step
Review your priority learning journeys, governance, data, delivery methods, assessment needs, and roadmap with WMT.