Starting next Monday, October 15th, we will be putting an updated policy overview into effect: Yup Tutor Expectations. These guidelines aim to shift focus away from negative behaviors tutors should avoid and towards ideal, positive tutor behaviors. We will still be assessing your performance in the areas mentioned, however with less rigidity, instead focusing on a tutor’s overall ability to meet Yup expectations.
We hope this change will convey the good faith we have in tutors to use their best judgement when making professional decisions. However, it is important to note that an inability to meet the expectations set forth in this document may place your contract at risk.
Please let us know what questions you have about this update and have a wonderful weekend!
As the Engineering team works towards making the newest version of the Tutor Dashboard bug-free, we want to extend a huge thank you for your patience and understanding during this process. A special thank you to everyone who has been following the Bug Reporting instructions to take screenshots of bugs with the Dev. Console and sending them our way!
Here are some tips for avoiding some common Whiteboard bugs:
Problem 1: The “Send” button is missing
Solution: The send button will appear as soon as you start using the whiteboard. To send an image without editing it, make an inconspicuous marking to activate the send button.
Problem 2: Whiteboard error message: “Error loading the image. Reason Failed to fetch”
Solution: The following instructions will allow you to use the whiteboard when you see the above message until we issue a fix:
Problem 3: The line tool is behaving erratically
Solution: After using the line tool to draw a line, right-click to commit the line to the board OR continue to draw connected lines.
NEW FEATURE TIP: Click on the triangle tool and enter a number “n” in the provided box to drag out a polygon with “n” sides. (Try it now in the Whiteboard Practice Link!)
ENCOURAGING LANGUAGE REMINDER
Quick reminder for Standard 3.3: Please ensure you are always using encouraging language when interacting with students! We realize this may be a challenge when the student isn’t succeeding, but this is the most important time to praise the student’s efforts in order to keep them motivated.
Here are some phrases that are better than a simple “Not quite.”:
When the student gets something completely wrong:
“Good effort, Mike, but not quite! Let’s take a look at this step together.”
“Nice try, but not quite! Don’t worry, we will get there in no time 🙂 ”
When the student is wrong, but not far off:
“I see where you are going with this! Let’s talk about this step a bit more.”
As some of you may be aware, in July we made the decision to stop offering assistance with Chemistry and Physics subjects. This change will allow us to focus all our energy on offering top-notch math homework help, which the overwhelming majority of users are coming to us for. We hope to bring back these subjects in future, however we do not currently have a concrete plan to do so.
Starting this month, we will be enforcing changes to the Session Dispute policy that will hopefully help the Ops Team manage what is a large volume of incoming dispute requests received on a weekly basis.
While we do understand the importance of the Dispute channel, we want to make sure it is only being used when absolutely necessary:
AS OF JULY 2018
Tutors can submit a maximum of 3 disputes per month
For disputes related to rubric standards:
Sessions that earned a score of 8 or higher cannot be disputed
Tag disputes are limited to key tags(Gave Answer, Wrong Answer, Content Knowledge)
It is our hope that these changes will help curtail the number of disputes being regularly filed. That being said, if you ever have concerns about a session, the dispute process, or about any other Tutor Operations matter, please don’t hesitate to get in touch with us at firstname.lastname@example.org. Your feedback is always welcome and much appreciated!
American Forth of July Holiday
If anyone (American or otherwise!) is hoping to take time off on Wednesday, July 4th please email email@example.com or use the Scheduling form so we can adjust your schedule accordingly (48-hour notice not necessary.)
As part of our efforts to incorporate more tutor feedback into our evolution as a company, we will be conducting a test with the Gave Answer tag. Next week, we’ll begin a two-week experiment that will help us understand how this tag affects teaching and student experience.
For sessions created between Monday, 7/2 @ 12AM PDT through Monday, 7/16 @ 12AM PDT, earning the Gave Answer tag will not result in any QA penalties.
During this two-week period, even though Tutor Quality Managers will still apply the Gave Answer tag as usual, instances of this tag will not count toward any weekly Tutor Fault Tag limits, nor will the tag result in a Rubric Score of 0.
We encourage you to use this time period to experiment with your teaching habits, free from the worry of receiving a Gave Answer tag when you push information to struggling students.
That being said, although there are no Gave Answer Tag penalties during this period, we trust that you will continue to exercise good judgement in providing students with support and continue to teach with our rubric and values in mind.
If you have any questions about this change or the timeline for it, feel free to email firstname.lastname@example.org.