Data retention is not merely technical housekeeping for an organization built on continuing education management in Moodle. For a professional association, it is a compliance mandate. Associations accredited by outside bodies face strict requirements for keeping member records. One such body is IACET, the International Accreditors for Continuing Education and Training. Another is ACCME, the Accreditation Council for Continuing Medical Education. Those periods run for years, so failing to meet them can jeopardize an association’s accredited status. This guide sets out what Moodle data retention for professional associations has to achieve. It also names the platform defaults that quietly work against it.
Engaged the team for a global retailer application development project. Schedules were consistently met with flexibility to changing scope. Was always impressed with Mindfield’s responsiveness and ability to quickly grasp the problem while offering creative solutions. Applications were of high quality and I wouldn’t hesitate to recommend Mindfield Consulting for any custom development.
Grant R
review Source: Google Reviews
Outline
- The 1000-Day Ceiling Against a Seven-Year Accreditation Window
- What an Accreditor Actually Audits: Participation, Contact Hours, and Grade Changes
- Why a Retired Course is a Retired Audit Trail
- Certificate Reissue Years Later, and the Records It Silently Depends On
- Archiving on the Accreditation Cycle Rather Than on the Storage Complaint
- Accelerate Compliance with Moodle Experts
- Frequently Asked Questions (FAQs)
The 1000-Day Ceiling Against a Seven-Year Accreditation Window
Accreditation standards dictate how long training records must be kept. However, those periods extend far beyond Moodle’s native long-term retention capabilities.
Accreditation Mandates for Record Keeping
Various accrediting bodies impose specific minimum retention periods for educational records. For example, IACET Standard 8.5 requires accredited providers to maintain training records for a minimum of seven years. They must also make those records available to learners. Similarly, ACCME mandates that providers record and verify participation for six years from the activity date.
Standards from NASBA, the National Association of State Boards of Accountancy, set a different bar. Its CPE rules with the AICPA require program documentation to be retained for a minimum of five years. Providers answering to a government regulator rather than an accreditor carry a comparable obligation. Similarly, Moodle compliance for BC private training institutions shows the same pattern.
Moodle’s Default Retention Limitations
Two Moodle settings hold the long-term evidence: the standard log store’s log lifetime (logstore_standard/loglifetime) and the grade history lifetime (gradehistorylifetime). Both present the same challenge. Both settings offer a longest non-zero retention period of 1000 days, which is just under three years. This 1000-day ceiling falls short of the five, six, or seven-year requirements imposed by most accreditors.
The Strategic Implication of “Never Delete”
Both the log lifetime and grade history lifetime settings ship as “never delete” (value 0). That is indefinite retention of individual member behavior, with no expiry. That introduces real data privacy liability. Consequently, associations hold sensitive personal data far longer than any operational need justifies.
Consequently, the retention schedule for accredited professional associations cannot solely reside within Moodle’s settings. It must be managed externally instead. That means durable copies of the essential records, held somewhere that outlives Moodle’s limits.
What an Accreditor Actually Audits: Participation, Contact Hours, and Grade Changes
Accreditation audits for professional associations do not merely review course content; they meticulously examine the evidence of individual member activity. Auditors focus on three core data points to verify compliance and the integrity of awarded credentials.
Participation Evidence Beyond Enrollment
Participation is not enrollment; it is evidence the member was actually engaged. In Moodle, that data resides primarily in the standard log store.
NASBA, for instance, expects attendance-monitoring mechanisms for group internet-based programs that account for late arrivals, early departures, and extended breaks. Furthermore, at least three instances of unpredictable interactivity must be completed per CPE credit.
Without these detailed log entries, an association cannot substantiate its claims of member engagement.
Reconstructing Contact Hours
The credit awarded for a course is fundamentally a claim about the time spent learning. Moodle does not natively compute or store a defensible measure of time on task. Instead, the claim for contact hours is reconstructed from the access records within the log store.
Those records show when a member opened materials, worked through activities and submitted work. Turning that raw trail into a defensible contact-hour figure is a deliberate extraction exercise. Moodle does not report the figure on its own.
The Importance of Grade Change History
Accreditors look closely at grade changes: who altered a mark, from what to what, and when. That is recorded in Moodle’s grade history, which is enabled by default (disablegradehistory defaults to 0). A passing grade edited after the fact without justification undermines the credential, turning an earned achievement into a favor.
The Critical Gap in Moodle Backups
Here is the strategic problem. Moodle’s default backup configurations exclude two of those three audit trails. Automated backups omit both, because backup/backup_auto_logs and backup/backup_auto_histories default to 0. Manual course backups omit them too, since backup/backup_general_logs and backup/backup_general_histories also default to 0. By contrast, users, role assignments and user completion records are included by default. backup_auto_users, backup_auto_role_assignments and backup_auto_userscompletion, plus their backup_general_ equivalents, all default to 1.
Consequently, an association’s standard Moodle archive holds the completion flag and the enrollment status. However, it does not hold the participation trail or the grade-change trail that substantiate them. A Moodle backup is not, by default, an audit archive. Including logs and grade histories has to be a deliberate decision. Specifically, it belongs to someone who knows what their accrediting body asks for.
Why a Retired Course is a Retired Audit Trail
Professional associations frequently retire and replace courses due to curriculum revisions, standard updates, or the natural progression of annual cycles. Retiring a course in Moodle is not a neutral act, though. It can erase the very records an accreditor will ask for years later.
The Destructive Nature of Course Deletion
Deleting a course removes several classes of data at once:
- Course completion information: All records indicating a member completed the course.
- Gradebook data: The complete gradebook and its associated items.
- Per-activity completion records: Individual records of activity views and completions.
- Enrolments: All member enrollments within that course.
- Course backup files: Every backup file held against that course in the course backup file area.
That last point matters most. Automated backups are stored by default within the course’s own backup file area (backup/backup_auto_storage). Therefore, when a course is deleted, its own backups are also automatically destroyed.
The Short Lifespan of the Recycle Bin
Moodle’s course recycle bin holds a deleted course for seven days by default (tool_recyclebin/coursebinexpiry). That is a window for catching an accidental deletion. It is not a window for a question that arrives five, six or seven years later. Furthermore, the recycle bin’s copy of a deleted course inherits the automated backup settings. It therefore excludes logs and grade histories too, and preserves no full audit trail.
Automated Backup Blind Spots
Other defaults deepen the risk. Automated backups are disabled out of the box (backup/backup_auto_active defaults to 0). Even when enabled, they keep only one automated backup per course, since backup/backup_auto_max_kept defaults to 1. Each new run therefore overwrites the previous one.
More critically, automated backups skip hidden courses, because backup/backup_auto_skip_hidden defaults to on. They also skip courses not modified in the last 30 days, since backup/backup_auto_skip_modif_days defaults to 30. That describes a completed cohort exactly: closed, hidden and left alone. As a result, the courses most relevant to an audit are the first to fall out of the backup rotation.
Separating Course Retirement from Record Retirement
Moodle treats “retire the course” and “retire the record” as one decision. For professional associations they are two. The working life of a course and the retention period of its records answer to different calendars. The same caution applies when a shell is reused rather than retired. Indeed, resetting a course for a new cohort or refresher training clears the learner data that proved the previous cohort completed. Either way, the archiving decision has to be settled before the course leaves the live environment.
Certificate Reissue Years Later, and the Records It Silently Depends On
Associations field this request often: reissue a member’s certificate, or verify a credential. It usually arrives long after the course itself was retired. Moreover, it depends silently on course data that may already be gone.
Certificates as Dynamic Documents
Moodle core does not natively issue completion certificates; associations typically rely on a certificate plugin for this functionality. The certificate document itself is not stored as a file. The plugin generates the document on demand. It draws on a template and the live course data every time the certificate is downloaded or verified.
The system records only the issue itself: the member, the certificate activity, a verification code and the issue date. The Moodle certificate plugin and customization strategy an association chooses decides what that record holds.
The Silent Failure of Verification
So a certificate is not a document the association possesses. Rather, it is a promise. A set of underlying records must still be there when someone tries to download or verify it. Those records are specific: the issue record, the verification code, the certificate activity and its template. They also include the course all of them belong to, and the grade or completion data the template prints.
If the course is retired and deleted, every one of these dependencies vanishes simultaneously. So reissue requests fail and verification codes stop resolving. There is no warning and no error message until a member or an external body tries.
Strategic Extraction for Durable Evidence
The evidence of what a member earned must not depend on the course they earned it in. That means extracting completion and issue evidence into a durable system that outlives the LMS. Verification has to work without handing the verifier a Moodle account.
Archiving on the Accreditation Cycle Rather Than on the Storage Complaint
The typical trigger for a Moodle clean-up is pragmatic. It is a looming hosting invoice, a slow backup window, or an administrator tidying a crowded course list. However, for professional associations, none of these operational concerns align with the critical accreditation calendar. Moodle data retention for professional associations has to answer to audit readiness instead.
Reframing the Retention Clock
That decision belongs to the accreditation term and the audit window. It does not belong to available disk space. Associations should establish a written retention schedule that specifies different periods for various classes of data.
For instance, credential and issue evidence should be kept for the full accreditor’s window. Participation and grade-change evidence should match it. Conversely, ordinary operational data, not directly tied to accreditation, can be kept for shorter periods. The same separation underpins any workable Moodle backup and migration strategy.
Integrating Archiving with the Accreditation Cycle
Archiving should run on the same cycle the association is already reviewed on. A course’s evidence is then extracted and secured before that course is ever retired. It also requires a deliberate process for existing courses, because Moodle’s own data-privacy retention defaults apply only to newly created instances.
Older, audited cohorts in the back catalogue need deliberate coverage. So does deleting Moodle accounts rather than suspending them, since that choice decides what course history survives.
Balancing Compliance with Privacy
“Never delete” is not a policy. Members are individuals with privacy interests. Keeping every log line forever, because Moodle offered no middle option, accumulates liability quietly. Associations already working within named privacy regimes will recognize the exercise from FIPPA, PIPEDA and HIPAA compliance in Moodle. That is, map each class of data to the period it actually needs.
The fix has three parts: one accountable owner for retention, and a written schedule mapped to the accreditor’s window. Finally, a review gate before any course is retired. That puts the decision with the people answerable for accreditation rather than with whoever administers the LMS.
Accelerate Compliance with Moodle Experts
Moodle data retention for professional associations sits across accreditation standards and Moodle’s own architecture. However, the two rarely line up on their own. Mindfield Consulting’s Moodle specialists design and maintain retention strategies built around an association’s accreditation obligations. We can help you set the policy and configure Moodle to match. We also build the external archive that keeps your evidence available long after a course is retired.
Frequently Asked Questions (FAQs)
This article may contain conceptual illustrations to help support the article content.
