Skip to main content
All CollectionsHeadrush Fundamentals
Workflows: Tasks and Modules
Workflows: Tasks and Modules

Understanding the task and module level workflows in Headrush

James Carlson avatar
Written by James Carlson
Updated over a week ago

The concept of workflow is a part of all modern day work, and increasingly a part of modern and progressive learning. The idea behind workflow is that each item of work--be that a project, task, or other learning scenario--has an associated status that indicates what is happening right now, who is responsible and what happens next.

Headrush supports workflows on the Module, on Tasks that require Evidence, and on Tasks that do not require Evidence but still need to be tracked or assessed for completion.

Module workflows represent the entire lifecycle of a learning scenario, be that a personal learning plan or a weekly seminar, from draft state to active work and on to being assessed.

Task workflows represent the lifecycle of action on a specific task, from being in-progress, to submitted for Advisor review, needing additional work, and on to complete.

Module Workflows

Module workflows apply to the module as a whole, and typically include statuses such as:

  • Draft or Upcoming

  • In progress or Active

  • Complete

  • Assessed

The specific workflow used depends on the module's type, which is determined when it is created. Your organization may also have custom module workflows. Changing a module's status in Headrush is simple. Click on the module status and select a new status:

Headrush will ask for required information or confirmation when statuses are changed.

Please note: If the module is set to allow Learners to join (in the Overview) it will automatically be set to a To Review or Upcoming status. Therefore, we recommend making all the changes to the module first, and then making it available for learners to Join. Learn more about creating Joinable Experiences.

Task Workflows

When a Task requires Evidence, a workflow is automatically applied to that task. The Advisor can also require a workflow for tasks that don't need Evidence -- as a way of noting learner completion when assessments are not needed.

Each Learner moves each Task individually through the steps of this workflow, which are fixed. When the Learner sets the status of the Task to Submitted, the Advisor then reviews the evidence and either sets the status to Needs Review, which means the Learner has more work to do; or to Complete, which means the Task is complete.

Track and/or Assess Tasks without Evidence

Setup the Task to be assessed or tracked, but do not require evidence.

When Tasks are setup like this, the Advisor must change the status -- normally, directly to Completed -- as the Learner cannot submit evidence.

Learn More

Should you want to look at all Tasks within a particular Workflow status regardless of Module and across all students, the Advisor Task Inbox can help with that...

# # #

Did this answer your question?