For private training institutions in British Columbia, adopting an LMS is no longer just about improving the learning experience, it is a regulatory requirement tied directly to your ability to operate and maintain certification. Once a program delivers more than 20% of its instructional hours online, excluding work experience, regulators expect institutions to demonstrate that their LMS can support structured delivery, student accountability, and data protection. This means your system must go beyond hosting files, it must actively track, verify, and document the entire learning process.
Many institutions assume that simply having Moodle in place is enough. In reality, compliance depends on how the system is configured and used, not just whether it exists. In this article, we break down each requirement, explain the real compliance risks, and show how Moodle can be configured to meet expectations confidently.
Working with Mindfield is a life changing experience. From Product knowledge to technical expertise the team has gone above and beyond the call of duty more times then I can count.
Greg Shorland
Funeral Learning Hub
Outline
Core LMS Compliance Requirements
For programs that include distance or combined delivery, PTIRU sets specific requirements for how online learning must be managed. The most important requirements are outlined below, along with practical ways Moodle can be configured to help institutions demonstrate compliance.
1. An LMS Is Required When More Than 20% of Instruction Is Online
Any approved program with more than 20% of its instructional hours delivered through distance education, excluding work experience, must use a Learning Management System (LMS). PTIRU defines an LMS as software used for the administration, documentation, tracking, reporting, automation, and delivery of education and specifically notes that MS Teams is not an LMS. (Private Training Act Policy Manual, s. 3.2.8 and footnote 8, p. 49)
Moodle recommendation:
- Use Moodle as the central location for course content, activities, assessments, progress records, and reporting.
- Treat Zoom, Teams, and similar platforms as supporting or integrated tools rather than replacements for the LMS.
2. The LMS Must Be Available 24/7
PTIRU requires the LMS to be available 24/7, subject to maintenance requirements. (Policy Manual, s. 3.2.8(i), p. 49)
Moodle recommendation:
- Use reliable hosting and monitoring.
- Schedule maintenance in advance where possible.
- Keep records of major outages and planned maintenance so system availability can be demonstrated if required.
3. Students Must Have Reasonable Access to Technical Support
Students must have reasonable access to technical support for the LMS throughout the program. (Policy Manual, s. 3.2.8(ii), p. 49)
Moodle recommendation:
- Provide a clearly visible helpdesk email, ticket system, or support page.
- Include support information in the Moodle dashboard or navigation.
- Document how students can request assistance.
The regulation focuses on reasonable access to support rather than prescribing a specific response time.
4. The LMS Must Protect Personal Information
The LMS must include security features that protect students’ personal information. (Policy Manual, s. 3.2.8(iii), p. 49)
Moodle recommendation:
- Use HTTPS and secure authentication.
- Configure roles and permissions carefully.
- Restrict access to student records based on staff responsibilities.
- Regularly review administrator and elevated-access accounts.
The goal is not simply to have security settings available, but to be able to demonstrate that access to student information is appropriately controlled.
5. The LMS Must Have a Method of Verifying Student Identity
PTIRU requires institutions using an LMS under the distance-delivery standard to have a system to verify student identity. The policy does not prescribe one specific technology that every institution must use. (Policy Manual, s. 3.2.8(iv), p. 49)
Moodle recommendation:
Depending on the program and assessment risk, institutions may consider stronger authentication, controlled assessment procedures, proctoring solutions, or other documented identity-verification processes.
The important point is that the institution should be able to explain and demonstrate how it verifies that the registered student is completing the required learning and assessment activities.
6. Asynchronous Student Progress Must Be Trackable
For asynchronous delivery, the institution must have a system that enables it to track and confirm a student’s progress. (Policy Manual, s. 3.2.8, p. 49)
Moodle recommendation:
- Configure activity completion.
- Configure course completion where appropriate.
- Use logs and reports to review participation.
- Ensure required activities and assessments have measurable completion criteria.
A course containing PDFs and videos without meaningful tracking may make it much harder to demonstrate student progress during a compliance review.
7. Assessment Integrity Must Be Protected
PTIRU requires institutions to ensure the integrity of all assessments used in their programs. (Policy Manual, s. 3.2.8, p. 49)
Moodle recommendation:
Depending on the type and importance of the assessment, institutions can use Moodle controls such as question banks, randomized questions, time limits, attempt restrictions, question behaviours, and appropriate supervision procedures.
These Moodle features are implementation options—the regulatory requirement itself is that the institution can demonstrate the integrity of its assessments.
8. Required Equipment, Software, and Materials Must Be Available
For distance and combined delivery programs, required equipment, software, and materials must be in good working order and available to students before the start of the course where they are required. PTIRU’s broader program-delivery standards also require course materials to be provided before or at the time they are needed. (Policy Manual, s. 3.2.8, p. 49)
Moodle recommendation:
- Build course content before learner enrolment or course launch.
- Test links, files, videos, SCORM packages, and required software.
- Verify that release restrictions do not accidentally prevent students from accessing materials when they are required.
9. Attendance Records Must Be Maintained
Attendance is a broader institutional compliance requirement rather than one of the specific LMS requirements listed under the 20% rule. Institutions must maintain a written Student Attendance Policy, and student records must include attendance information. (Policy Manual, s. 3.2.1, p. 36; Appendix 13(d), p. 131)
Moodle recommendation:
Where Moodle is used to support attendance or participation records, ensure those records can be clearly connected to the institution’s official attendance process and retained as required.
10. Keep Evidence, Not Just Settings
Compliance depends on more than enabling Moodle features. Institutions should be able to produce records showing how the LMS is actually being used—for example, completion reports, assessment records, activity logs, support processes, access controls, and attendance information.
This is particularly important because PTIRU may conduct compliance inspections, and the registrar has authority to issue compliance orders where an institution has contravened the Act or regulations.
Risk and Penalty Likelihood
LMS compliance issues should not be viewed as simple technical problems. Under the Private Training Act, the registrar can issue compliance orders and, depending on the contravention, impose administrative penalties or suspend or cancel an institution’s certificate. (Policy Manual, s. 4.3.3, p. 58 and s. 4.4, p. 59) (Policy Manual, s. 4.4, p. 59; Private Training Act, ss. 32, 33, 36, 37)
What Can the Penalties Look Like?
PTIRU’s current administrative penalty schedule includes penalties ranging from $250 to $1,000 per contravention, depending on the specific provision that has been violated. Not every LMS requirement has its own standalone dollar penalty, so institutions should avoid assuming that every issue carries the same fine. (Policy Manual, Appendix 14, pp. 133-136)
Examples relevant to online delivery and student records include:
- $1,000 per contravention for failing to comply with a compliance order.
- $1,000 per contravention for enrolling an international student with a study permit in an approved program where 50% or more of instructional hours, excluding work experience, are delivered through distance education.
- $500 per contravention for failing to keep a current student record for each student enrolled in an approved program.
- $250 per contravention for failing to comply with student attendance standards.
Source: Private Training Act Policy Manual, Appendix 14, pp. 134-136.
The penalty can also become more significant when a problem continues. If a contravention continues for two or more consecutive days, PTIRU may impose a separate administrative penalty for each day the contravention continues. (Policy Manual, Appendix 14, “Continuing Contraventions”, p. 136)
One Penalty Can Have Effects Beyond the Fine
Administrative penalties are published in PTIRU’s Online Directory for at least two years and are considered when determining an institution’s regulatory category. (Policy Manual, s. 4.4, p. 59)
The number of administrative penalties is itself one of PTIRU’s category-assessment criteria: (Policy Manual, s. 6.2.1, p. 68)
- 0 administrative penalties: Category 1 rating for this criterion
- 1 administrative penalty: Category 2 rating for this criterion
- More than 1 administrative penalty: Category 3 rating for this criterion
This does not mean that one penalty automatically changes the institution’s overall category—the final category is based on multiple assessment criteria—but it shows why repeated compliance issues can have consequences beyond the original fine.
A certificate suspension can also prevent an institution from advertising, contracting with, or enrolling new students at the affected location while the suspension remains in effect. Certificate cancellation can require the institution to stop providing applicable programs and prevent it from applying for another certificate for at least one year. (Policy Manual, s. 4.4, p. 59)
The practical takeaway is simple: small compliance gaps become much more serious when they are repeated, undocumented, or left unresolved.
Common Compliance Gaps We See
Across institutions, the same patterns appear repeatedly.
Many organizations:
- Use Moodle as a content library instead of a structured LMS
- Skip completion tracking because it requires setup
- Rely on external tools without proper integration
- Have no clear identity verification process
- Lack centralized reporting
These gaps are often not intentional; they usually result from partial implementations, inconsistent processes, or a lack of configuration knowledge.
However, during audits, intent doesn’t matter, only evidence of compliance does.
Best Practices for BC Institutions
To stay compliant, institutions should treat Moodle as a regulated system, not just a learning tool.
Best practices include:
- Configuring completion tracking across all courses
- Using Moodle as the single source of truth
- Ensuring all learning activities are trackable and reportable
- Standardizing course structures
- Regularly reviewing system performance and logs
A strong compliance setup is one where: You can demonstrate compliance without needing to explain it manually
From Setup to Sign-Off: Why a Moodle Expert Makes the Difference
Configuring Moodle for BC compliance is not just about turning on features, it’s about aligning your LMS with regulatory expectations in a way that is consistent, traceable, and audit ready. A Moodle expert understands how requirements like progress tracking, identity verification, and assessment integrity translate into real configurations within the system. Instead of relying on trial and error, you get a structured setup where every feature serves a compliance purpose, reducing the risk of gaps that may only surface during an audit.
Beyond initial setup, a Moodle expert helps ensure your platform remains stable, secure, and scalable as your programs evolve. They can identify hidden risks, optimize performance for 24/7 availability, and implement best practices that make compliance easier to maintain long term. Ultimately, this means less time troubleshooting and more confidence that your LMS can stand up to regulatory scrutiny, without last minute fixes or uncertainty.
Sources
- Private Training Act Policy Manual, Private Training Institutions Regulatory Unit, published November 3, 2025 — s. 3.2.1 (p. 36), s. 3.2.8 (pp. 49–50), s. 4.3.3 (p. 58), s. 4.4 (p. 59), s. 6.2.1 (p. 68), Appendix 13 (p. 131), Appendix 14 (pp. 133–136).
- Private Training Act, SBC 2015, c. 5 — s. 32 (compliance orders), s. 33 (determination of administrative penalties), ss. 36–37 (suspension and cancellation of certificate).
- Private Training Regulation, BC Reg 153/2016.
Regulatory requirements change. Figures in this article reflect the November 3, 2025 edition of the Private Training Act Policy Manual and are current as of publication. Confirm current requirements with PTIRU before acting on them.
