How does the class review process work?

Dabble sends review surveys to students following events. Students are asked to provide both public and private feedback. Public feedback will be featured on your event page, and private feedback will only be shared with you. Our intent is to make sure that there is open communication between teachers and students, and a teacher can continue to hone his/her event listing. We display all of a teacher's public review comments on every course page they teach. On each event page, we also display the percent of positive reviews for a teacher overall, as well as the percentage for an individual event if a teacher teaches multiple events.

Teachers are given the opportunity to respond to any neutral or negative reviews and if a review is completely unrelated to the course or teacher (got lost, tried to cancel in conflict with policy or just didn't show up...) we will remove at our sole discretion. We aren't Yelp and we don't allow users that didn't attend your event to ruin your reputation and good rating.

Positive review percentages are calculated by awarding 5 point for positive reviews, 3 points for neutral reviews, and 1 point for negative reviews. We sum the points from all possible reviews, and take the average of the points. Note that we only display reviews with public comments on an event page, but reviews without comments also factor into the positive percent calculation.

Teacher payment is held 24 hours to allow users time to review or bring any issues to our attention. Dabble processes payment one to three days after an event occurs. In this time, if your students send us negative reviews, we will place the event under internal review.

If we deem it necessary to refund the event for due cause (at our sole discretion), we will refund the students and withhold teacher payment for the event. In case this scares you, we should note that this has occurred in less than 0.03% of classes thus far. At times, we may opt to refund the user and still pay the teacher if the fault was in any way tied to a Dabble error.