When a Student Wants a Refund Halfway Through a Course: What Data Should You Check First?

A student approaches you in the fourth week of your eight-week online course and asks for a refund. The first thing that might pop into your mind is to find out whether there is any refund policy in effect or not. But that does not say everything; the date alone will not do the trick.

It is wise first to examine what the student bought, had access to, did on the course, and whether you offered them what the sales page said. Someone who has opened half the lessons on the course might have done very little work. On the other hand, another might have gone through all the lessons but had trouble because of some technical issue or had no feedback like promised.

What is important is to create a timeline of events.

Check the Student’s Reason, Purchase Record, and Refund Terms

Let’s start from the student’s message. Note the reason in his own words. The phrase “I expected personal feedback” requires a different review than “I can no longer attend.” If the request is unclear, you only need to ask one question: “Could you tell us what led you to request a refund?” Do not ask the student to justify his decision.

Now, let’s open the purchase and payment records of this student. They should contain:

• Purchase date, date of course beginning, and date of requesting refund

• Amount of payment, applied discounts, payments already made, and those yet to be paid

• Version of the course, access time, and live lessons

• Refund policy available on checkout, its deadlines and terms

• Confirmation emails or receipts that show a student's agreement with the terms

Stick to the terms of checkout. Your website may show you the newest version of the refund policy, but you need to know which version the student has seen.

Now classify the request for internal review. Students might have faced such problems as a technical failure, lack of promised materials, discrepancy between sales page and lessons, dissatisfaction with teaching, or personal circumstances. These problems require different evidence. Do not categorize the request until you read the explanation from the student.

Identify the consumer protection laws applicable to the transaction. Depending on the country where it was made and the method of delivery, the student might have certain rights that cannot be excluded from your refund policy, even by the terms. Consult your legal or compliance department in case of doubt. Do not tell the student that the deadline concludes the discussion until you check your obligations.

At this point, you should have dated the purchase record, applicable terms, and the student's complaint statement. 

Confirm That the Student Could Access What They Bought

Before assessing any progress made, ensure that the student actually had access to the course. This is because a successful transaction will not guarantee that lessons, downloads, or instructor sessions were available.

Examine the learning platform and support records for:

• Activation of the student’s account and the time of the first log-in

• Unsuccessful login attempts, password resets, and account restriction measures

• Problems with downloading lessons or errors in permissions

• Links to live sessions, recordings, and access to community sites promised to students

• Support tickets regarding unavailable content and faulty features

Construct a timeline. Take note of the time that each problem arose, when the student reported it, the actions taken by your team to fix it, and when access resumed. Examine whether the difficulty was related to just one lesson or a particular section of the course.

For instance, a student might log in during the third week, but be unable to access the assignment portal. Although log-ins are proof of activity, error logs and support correspondence will provide the reason for the student’s inability to submit their assignment.

There are gaps in the learning platform logs. The student might be using a shared computer, face an unlogged error, or just quit after several unsuccessful tries. In case there is confusion in the records, ask yourself: “Which lesson or feature was inaccessible to you and when did the difficulty arise?”

Gather all evidence before determining whether access issues influenced the refund request.

Read Engagement Data Without Making Assumptions

Here are some metrics for consideration:

 

Examine student interaction with the course prior to and after his first issue with it. A student who has been attending three live classes and then stops joining them without any feedback, as promised, has reasons to complain about the course.

Additionally, pay attention to the ways in which students learn on their own. They can download worksheet files, do homework on paper, and watch recorded classes together with their relatives. Your LMS will not track that.

Two false assumptions you should avoid:

• No engagement = no effort. It could be explained by some technical issues, complicated instructions, and even personal reasons.

• High level of engagement = high level of satisfaction. One can attend and complete all lessons but find that a course does not provide what was offered.

Use engagement statistics to define the questions that should be asked, but never base your decision on completion percentage only.

Review Learning Progress and Instructor Feedback

Engagement records illustrate how a student interacts with course content. To evaluate the learning process, analyze the student's performance and get information about any feedback received from the professor or teaching assistant. Four aspects are important in this case.

• Assignments: Find out the submission date, missing assignments, and the presence of instructions.

• Assessments: Look at quiz grades, re-attempts, and topics that have created difficulties for a student.

• Instructor feedback: Make sure that an instructor replied within the required time and gave useful tips.

• Learning goals: Analyze the skills gained by a student against the course outcomes indicated in the syllabus.

Do not forget about the feedback from the instructor. Has a student received some recommendations for improvement? Has he asked questions and received no answers?

For instance, a student registered in a beginner programming course and completed four modules but has difficulties with assignments that presuppose knowledge gained before. Make sure that such information was contained in the course description and whether the instructor gave proper assistance.

Avoid making a conclusion based on the amount of work completed by a student. There may be cases when a student has submitted assignments without grasping any concept. Some students can master certain skills but do not complete extra assignments.

At the same time, you cannot demand more assignments from a student just because he wants to receive the money back. Use the data available in your possession and ask for clarifications only if it is necessary.

Compare the Sales Promises with Delivery and Support

The student may complete half of the course and yet be justified in their complaint if the team failed to provide what was purchased. Evaluate the marketing materials at the time the student signed up, which may include a landing page, emails, and course description. Check what was promised against the student's experience.

 

Identify particular promises in the marketing materials. For example, if the landing page advertised that students would receive weekly feedback from instructors, make sure that the student received it. If six live workshops were included in the course description, evaluate how many workshops were held before the student applied for a refund.

Lastly, analyze the support tickets in the case record. Look for:

• Repeated questions from the student

• Closed tickets without any resolution of the issue

• Expired deadlines or promised follow-ups

• Solutions attempted unsuccessfully by the student

For instance, a student may ask for a refund because they waited two weeks for the feedback on an assignment. The case record may show regular activity in lessons but inconsistent support history.

Find out if your team proposed an adequate solution and if the student used it successfully. Save the dates and answers in the case record.

In case there is a delivery gap, identify the consequences of this gap for the student. Then, you will evaluate the remedy needed for this particular situation.

Choose a Response That Fits the Evidence

Having examined the records, determine how you should react to the situation. First, take into consideration the student's legal rights and the conditions of the refund at the time of purchase. Second, evaluate whether your team honored its responsibilities. Apply the facts found to pick a proper response.

 

Partial refunds might be appropriate in certain cases. However, you should not calculate it based on lesson completion. Think of the services the student bought, the services you provided, and the legal requirements concerning the refund amount.

Should you provide the student with a chance to pause/transfer the course or add some extra materials, allow the student to choose. Do not pressure the student to accept any alternative to the refund.

Explanation of your decision-making process

Your reply needs to be concise. Address the complaint, tell what you have checked, and tell what comes next. Here’s an example:

"Thank you for the information on the problems you had. We checked your enrollment, feedback on your assignments, and your requests for help. We found out that two feedback sessions that were supposed to take place did not happen. Under the terms and conditions, we can offer you a refund. Please give us your contact email."

If it is outside the terms of a refund, then give an explanation why it is the case and the email for further inquiry.

Have the cases where you are not sure about the legal obligations of the service or where there is some confusion about the promise or record examined by your manager or compliance specialist.

Who approved the decision? When was the decision given to the student?

Record the Decision and Check for Repeated Problems

Once the response is complete, file a record of the case that another team member can easily understand without reading all of the correspondence. The file should include:

• Reason provided by the student and the date of their request

• The terms of the transaction and the information analyzed during the process

• Response decision and the rationale behind it, as well as the approval signature

• The response that was sent, refund if there is one, and the processing date promised.

Save only the information required for the review. Limit the access rights to only those employees working on the case. Do not include any confidential information in course reviews.

Review the cases of refunds collectively at certain intervals. Categorize cases by reason for a refund, course version, and the period of enrollment. Five complaints regarding lack of feedback from one cohort might indicate a problem with the workload of instructors. Access problems following the upgrade of the platform require a separate analysis.

Find out the number of enrollments when analyzing the number of refund requests. Two requests from twenty students differ greatly from two requests from two thousand.

Assign an owner of the issue and have them conduct the investigation and make notes about the changes.

Closing Checklist: The Review Before You Reply

Before you respond to a student’s refund request, make sure that you’ve verified:

1. The rationale behind the refund request and the date when they reached out to you

2. The purchase information, terms of checkout, and consumer rights

3. Access and technical problems

4. The engagement history and its limitations

5. The status of the assignment and feedback promised by the instructor

6. The sales promise and support chats

7. The solution available and its approval

In case of discrepancy in records, seek clarification or escalate the matter further. But do not hesitate to issue the refund due to the student.

Communicate the decision, inform about further steps, and mention the timeline. Make sure to document the result for follow-up by your team.