Home / Guides / Course Site Documents

Guides

Course Site Documents

Before you launch an online course site, your policies need to match how you enrol learners, take payment, deliver content and handle personal information. A clear document set helps you set terms from day one and reduces avoidable disputes later on.

Course Site Documents

What a course site needs before the first enrolment

If you sell short courses, coaching programmes, certificates or membership-based learning, your site should explain the rules before a learner clicks pay. The aim is simple: make the process fair, lawful and easy to follow. For South African providers, that usually means looking at your privacy notice, terms of use, refund position, cookie notice, and any learner specific terms around access, completion and assessments.

Many course sites also need wording for digital delivery, since learners may access material from Cape Town, Gqeberha, Durban or a farm in the Karoo on patchy mobile data. If your platform sends links through our contact form, stores progress or uses automated reminders, those details should be covered in plain language. It is better to spell this out than try to fix a complaint after a student misses a deadline or loses access.

Before launch, check whether your enrolment flow matches what your documents say. If your checkout says instant access, your terms should not promise manual approval within 48 hours. If a course includes live sessions, test the timing, rescheduling rules and recording consent too.

The core documents every online learning provider should review

Not every business needs the same pack, but most course sites benefit from a core set of documents that work together. Here is a practical starting point:

  • Website terms of use for browsing, account use and acceptable behaviour.
  • Privacy policy covering personal details, payment data and learner records.
  • Course terms for enrolment, access periods, assessments and certification.
  • Refund and cancellation terms explaining cooling-off rights where applicable and your own refund position.
  • PAIA and POPIA aligned notices where you collect, store or share learner information.
  • Ecommerce wording if you sell through a checkout, subscription or recurring billing model.

If you run a school-style platform with multiple instructors, you may also need content ownership wording and rules for user-generated material. That matters when a lecturer uploads slides, a learner submits assignments or a coach shares templates with the group.

We often see course sites with a good homepage but weak backend wording. That creates gaps around access, disputes and data use, especially when students ask for copies of recordings or want to transfer to another intake.

Set the enrolment rules clearly from the start

Your enrolment process should leave no doubt about what the learner is buying. State the course name, format, start date or access window, duration, price in Rand, and whether support is included. If there are prerequisites, say so before payment is taken. If there are limited seats, say how reservations work and what happens if a class is full.

For fixed-date programmes, include your rescheduling and deferral rules. If a learner can move to a later intake once, say how much notice is needed and whether a fee applies. If access is granted to a content library for 3 months, 12 months or lifetime access, define that period clearly and make the renewal position easy to understand.

Where assessments or certificates are involved, explain what counts as completion. Some providers issue a certificate after all modules are viewed while others require a pass mark or live attendance. If the learner does not meet the requirement, the site should say what happens next. Small details matter here because misunderstandings usually start with timing, not the course itself.

  • Describe the exact course being sold.
  • State access periods and expiry dates.
  • Explain support hours and response times.
  • Set out transfer, cancellation and refund rules.
  • Confirm what qualifies a learner for a certificate.

Cover privacy, payment data and learner records properly

Online learning providers handle names, ID numbers, contact details, payment information and often sensitive progress data. Under POPIA, you need to tell people what you collect, why you collect it, who can access it and how long you keep it. That applies whether you run a small writing course from Gardens or a nationwide academy with intake dates every month.

Be specific about third parties. If a payment processor, learning platform, video host or messaging tool handles learner data, mention that in your privacy policy. If your team uses backups for load-shedding protection or remote work, say how records are secured during those interruptions. Coastal humidity and device failures can affect storage equipment, so your internal access controls should be practical as well as compliant.

Also check what you collect on forms. Do you really need a learner's date of birth, ID number or company registration details? If not, leave it out. Less data means lower risk. Where you do need it, explain the purpose and keep only what is necessary for the course and any statutory recordkeeping.

Build a refund and cancellation position that matches the product

Course refunds are one of the most common sources of frustration, especially when a learner has already accessed lessons or downloaded material. Your terms should explain whether a refund is available before access starts, after login, or not at all once content has been consumed. If your programme includes live sessions, webinars or one-to-one calls, deal with missed attendance separately.

South African consumer rules can apply differently depending on how the course is sold, the price point and the sales channel. That is why a one-line refund promise is risky. You need wording that fits your actual delivery model, whether you sell subscriptions, once-off courses or corporate training packages.

It also helps to address technical problems. If a learner cannot access a module because of a platform fault, say what support you will provide and how quickly. Clear steps reduce arguments and make the site easier to manage when registrations pick up before quarter-end.

  • Decide when a refund can be requested.
  • Specify what counts as course access.
  • State the treatment of live sessions already delivered.
  • Explain how technical faults are handled.
  • Record any cooling-off rights that may apply.

Use a launch checklist before the first ad goes live

Before you spend on ads or send the first WhatsApp invite, do a launch readiness check. Read every policy against the actual user journey from landing page to payment confirmation. If the process says one thing and the documents say another, fix the mismatch first.

A useful final checklist includes the following:

  • Do the privacy policy and terms match the real checkout flow?
  • Are course names, prices and access periods consistent across pages?
  • Do the refund rules match your admin process?
  • Are consent boxes, cookie notices and form fields working properly?
  • Can your team answer support queries with the same wording used on the site?
  • Are updates scheduled for future intakes, changed dates or new modules?

If you run a course business with multiple offerings, review your documents each time a new programme launches. A bookkeeping course, for example, may need different wording from a leadership workshop or a subscription library. One extra page now can save a long back-and-forth later on.

Why ongoing updates matter after launch

Compliance for course sites is not a once-off task. As you add new payment methods, new instructors, new software or new types of learner data, your documents need to keep pace. Even a simple change like adding a payment plan or recording a live session can alter what must be disclosed.

TsAndCs supports businesses across South Africa with policy pack customisation, compliance review, POPIA alignment, PAIA support, ecommerce policy setup, subscription policy support and ongoing compliance updates. If your training business is based in Gardens, Cape Town CBD, Sea Point, Claremont, Bellville, Stellenbosch, Paarl or anywhere else in South Africa, the same principle applies: the documents should reflect how the business actually runs.

For online learning providers, good compliance is practical. It helps with trust, cuts admin friction and gives your team a firmer basis when questions come in after hours. That matters when you are juggling enrolments, content delivery and support on a busy week.

Questions we get asked

Do I need separate terms for each online course?

Not always, but different course types often need different wording. A subscription library, a live cohort and a corporate training package usually have different access, refund and completion rules.

What should be covered in a course privacy policy?

Your policy should explain what learner data you collect, why you collect it, who receives it, how long you keep it and what rights the learner has under POPIA.

Can I use one refund rule for all courses?

You can set a general approach, but it should still fit the product. Fixed-date programmes, recorded modules and membership platforms may need different refund treatment.

Planning something? Send the team a message.

Contact form