The Facilitate page is where you’ll review student work, which students submit via tasks. Experts assess tasks using both formative and summative feedback to assess progress towards earning units and abilities tagged to a particular experience.

When you access the Facilitate page, you'll see something that looks like this:

This includes:

Tasks that are pending review indicate tasks that students have submitted but haven't been assessed yet, once the due date has passed.

This is the average response time an expert takes to assess a task. This is just something to keep an eye on, and it doesn't count Saturday/Sunday.

Learn more about different types of tasks:

When reviewing the Facilitate page, you'll see that each experience has a task table. Each student is on their own row and each task has its own column.

As tasks are assigned, due dates approach, and students submit tasks, you'll see the following status updates in your experience table:

Tasks that are pending submission indicate that a studen't hasn't submitted this task yet. You'll only see a task with this status before a task's due date.

A task is unassessed once a student submits a task, but the expert hasn't reviewed it yet.

A task is assessed whenever an expert has reviewed a task submitted by a student. Students are notified when tasks are assessed.

A task is missed when:

Students can use future tasks to submit work for previous tasks they've missed.

Here's the flow you can keep in mind when assessing tasks:

To begin assessing a task, click on the unassessed button in your experience's tasks table:

You'll be taken to that task's page, where you'll see...

On the left-hand sidebar:

In the middle of the page:

On the right-hand sidebar:

You can leave feedback a few different ways.

You can add comments that will appear as messages in the student's task submission window. To add a comment, enter your feedback in the text editor, below the student's task submission:

Next, click the send arrow in the bottom-right corner of the page:

You'll see a preview of your message and be prompted to mark the task as reviewed. Once you mark as reviewed, the student will be notified.

You'll see this status update in the task chat, and can mark undo to undo any feedback you've left. Note that this will revert the task status back to unassessed for you and your students.

You can also hover over the chat message to edit or delete it.

Adding preset comments are a great way to save time if you often use similar language for different kinds of tasks. You can create a bank of preset comments to use in any tasks you assess.

To create a preset comment, click +preset comment below the task comment editor:

Click create preset comment:

You'll see a pip-up appear, where you can create a preset comment.

You'll see your saved comment appear in your preset comment library on the right-hand side of the page:

You can create a new comment by clicking create new comment:

You can access all your saved comments in the future by clicking +Preset Comment and tapping the arrow to open up your preset content library:

You can add feedback about units and abilities by clicking +Add Feedback.

You'll see the units and abilities feedback window open in the right-hand side. By default, you'll see units and abilities already tagged to the experience.

To give formative feedback on a task, find the unit/ability you're assessing. You'll see a dropdown menu next to the unit or ability name.

The dropdown menu indicates:

Once you've made a selection, a text box will appear, where you can choose to add a comment about that specific unit/ability progress.

You can click the + button below the text editor to bring up preset comments:

Repeat this process for any other units/abilities you'd like to provide formative feedback on.Once you're finished, click Submit Feedback.

Once you've submitted feedback, the task will automatically be marked as reviewed.

Final deliverable tasks are the only tasks that students can submit for mastery levels (unit/ability credit).

When assessing feedback for final deliverables, you'll see a very similar page to when you assess regular tasks.

The main differences are the Schol Director/Dean's ability to grant a deadline extension and the ability to grant mastery levels with unit/ability feedback.

Students can request extensions of due dates for final deliverables only.

Students can request 48-hour extensions that are automatically approved by Sora Home.

School Directors and Deans also able to grand a deadline extension on final deliverables using the Deadline Extension button:

A pop-up window will appear to fill out the updated due date and reason for the extension:

You can leave a comment for the student's final deliverable, which can also include overall feedback on their progress throughout this experience.

This comment will appear on the student's end-cycle report alongside their mastery levels and self-reflection.

On the right-hand side of the page, you'll see the experience's tagged units and abilities along with the student's self-reflection and current mastery level.

You can search for and add extra units/abilities to assess as well by clicking the Select extra units and abilities dropdown.

You'll see that selected unit/ability appear in your assessment list. You'll see the student self-reflection level as well as the student's current mastery level.

When you're ready, click Submit Feedback.

You'll see your assessments and comments appear and the student will be able to view this within their task:

Final deliverable comments and assessments are compiled, along with student self-reflections and cycle statistics, into the end-cycle progress report.

Learn more:

Click the sticky note in the top-corner of the task assessment screen to view expedition progress.

You'll see a snapshot of the student's progress so far, including tasks submitted on time, attendance, and formative unit/ability feedback.

From time to time, you'll see a task submission that'd invalid in some way. A student submitted a link to an empty Google Doc, or broken link, or just typed 'submit' or gibberish - anything that you are unable to even review would be considered invalid in this scenario.

When this happens, here's what we recommend:

Send a comment to the student letting them know of the invalid submission and give them a chance to resolve the issue.

If the student has not resolved the issue with their submission before the due date, then we recommend marking the task as missed instead of marking the task as reviewed.