Workflows turn a student process your team repeats again and again into an ordered set of steps. Each step is assigned to a role, lands on that person's to-do list, and is tracked so you can always see who is waiting, which step they're on, and whether the work finished on time.
Why use Workflows?
Nothing falls through the cracks: every step has an owner, a due date, and a place on someone's to-do list.
Hand-offs happen on their own: finishing one step automatically assigns the next one to the right role.
Overdue work gets noticed: escalation alerts a second role when a step slips past its due date, while the original owner keeps it.
You can see process fidelity at a glance: on-time rates and step-by-step counts show where students are and where things tend to stall.
Where Workflows appear
Sidebar
Under Student support, open Workflows.
Item | What it is |
Workflows page on the Navigation Bar | Your tasks. Click a row to open that student's run. |
Workflows tab on the Student Card | Shows the workflows that a student is a part of. |
Workflows Configuration (gear icon on the workflows tab) | Where managers build workflows. If your role can configure workflows but can't see tasks, the sidebar shows Workflow configuration on its own instead. |
Board
If you can work tasks, you'll see a Your workflow tasks card on the board. It lists up to five open tasks, soonest due date first, with the same Start, Complete, and Open buttons you'll find on the task list. Click See all to open the full list. When you're all caught up, the card says Nothing waiting on you.
Student card
Open a student and choose the Workflows tab.
Start workflow lists every active workflow that can start for this student, along with how many steps each one has.
Open runs are expanded, so you can see each step, who it's assigned to, and the buttons for the current step.
Finished and cancelled runs stay in the list, collapsed, with the date they started.
On related records
Encounters, plans, and Attendance Assistant cases show a banner when they're tied to a workflow:
Started {workflow} for {student} means this record's event kicked off the run.
Part of {workflow} for {student} (step: {step name}) means a step created or linked this record.
Click the workflow name to open the run, or click Show steps to expand the step list right there. The banner also shows whether the run is in progress, completed, or cancelled.
Part 1: Configure a workflow
Open Workflows, then click the configure gear.
The list on the left shows each of your workflows with its name, whether it's Active or Paused, what starts it, how many steps it has, and how many students are in progress. Select one to edit it on the right.
Create a workflow
Click New workflow.
August creates a paused workflow named Untitled workflow and opens it for you.
It starts with one step, First step, assigned to the Counselor role (or the first role in the list if your school doesn't have a Counselor role). The action is No action, due in 5 days.
Nothing will start the workflow until you choose a trigger (or start it by hand) and turn it on.
Name it and turn it on
Click the title and type a name your staff will recognize, like Intensive attendance support.
The switch on the right says Active or Paused:
Active allows new runs, whether they come from a trigger, from Start workflow on a student, from Run now, or from another workflow's Start workflow step.
Paused stops new runs. Students already in the workflow keep moving through the remaining steps.
Choose what starts it
Starts when is the event that opens a run. The default is Only when started manually, which means the workflow starts from a student's Workflows tab, from Run now, or from a Start workflow step in another workflow.
These events can start a workflow. A few only appear when a related feature is on for your school.
Starts when | When the run opens |
Student: Attendance threshold met | A student meets an attendance threshold. |
Encounter: Assignees changed | The assignees on an encounter change. |
Encounter: Closed or locked | An encounter is closed or locked for the first time. Closing and then locking it won't start a second run, and neither will reopening and closing it again. |
Form request packet: Needs review | A form packet needs review. |
Form request packet: Accepted | A form packet is accepted. |
Internal referral: Waiting | A referral is waiting. |
Internal referral: Encountered | A referral was seen. |
Internal referral: Missed | A referral was marked missed. |
Attendance case: Launched | An Attendance Assistant case is launched, which is when the family conversation goes live. |
The event has to belong to a single student, so keep these in mind:
An encounter with several students, or with no student, won't start a workflow.
A form packet starts a workflow for the student on that packet.
A workflow task's own assignment, escalation, or completion won't start another workflow. When you want one workflow to open another, use a Start workflow step.
Choose who it applies to
Applies to limits which students can enter the workflow. Search and add students, sections, or both. A student qualifies when they're one of the students you picked, or an active student in one of the sections you picked.
Students outside that set are skipped whenever a trigger fires, someone uses Start workflow, or someone uses Run now. Leave the field empty (it shows All students) when every student should be eligible.
Add the steps
Each card under STEPS is one step, in the order students will reach them. Add step adds a new step at the end (named Step 2, Step 3, and so on) and copies the role from the step above it. A workflow needs at least one step, so the remove button stays off while only one remains.
On each step:
Field | What to enter |
Step | The name staff see on their task (e.g., "Message the family" or "Review the support plan"). |
Assigned to | The role that receives the task. August figures out the specific people when the step starts. See How assignment works below. |
Due within | Calendar days from the moment the task is created. The default is 5, and 0 means it's due the same day. |
Action | What Start does (see the next section). No action means the assignee just marks the step done. |
Template | Shown when the action needs one. The label matches the action: Encounter template, Plan template, File template, Form template, or Workflow. |
If overdue, escalate to (Optional) | A role to notify after the due date, in addition to the assignees. No escalation leaves this blank. |
Use the up and down arrows to reorder steps. Removing a step keeps the history of any tasks already created from it.
Under each step, you'll see No data yet until someone completes it. After that, it shows the share of tasks finished on time and the average number of days from when the task was created to when it was completed.
What each action does
Action | What you choose | What Start does |
No action | Nothing | There's nothing to create. The assignee clicks Complete or Skip. |
Create encounter | An encounter template | Opens an encounter for the student from that template, with the template's default notes, and assigns it to the person who clicked Start. |
Create plan | A plan template | Drafts a plan for the student from that template, with the person who clicked Start as case owner. When AI plan generation is on, Start opens Generate with AI, with a link to Create the plan without AI instead. While generation runs, the button reads Generating…. |
Create file | A file template | Fills the template for the student and files it on their record. Only fields that come from the student are filled, and the template has to have finished reading its form fields. Open file goes to the student's record. |
Review plan | A plan template | Opens the student's current plan from that template (the latest one that hasn't been archived). If the student has no plan from that template, Start stops and explains why. Publishing the plan doesn't finish this step; the reviewer clicks Complete when the review is done. |
Message family | Nothing | Opens a message thread on the student's Messages tab between the person who clicked Start and the student's family contacts with portal access. If there are no family contacts with portal access, Start stops and explains why. |
Send form request | A form template | Sends that form to the student's family contacts with portal access, along with the new-request message. The message batch is named after the workflow and step. If nobody has portal access, Start stops and explains why. |
Start workflow | Another workflow | Starts that workflow for the same student. If it's already in progress for them, the step links to the open run instead. A step can't start the workflow it belongs to. |
Clicking Start moves the task to In progress as soon as the record exists. After that, Open encounter, Open plan, Open file, Open thread, Open form request, or Open workflow takes you back to it. Clicking Start again won't create a second record.
When a step finishes on its own
Two actions complete the task without another click, and then the run moves forward:
Create encounter completes when the encounter is closed or locked.
Create plan completes when the plan is published.
Every other action, including Review plan, waits for someone to click Complete or Skip. Accepting the form, closing the message thread, filing the document, or finishing a workflow the step started all leave the task open until someone marks it done.
How assignment works
Each step names a role. When a student reaches that step, August assigns the task to every active user who holds that role and whose role scope includes the student.
If nobody with that role can see the student, August assigns the task to every active user with the role so it never goes invisible. In that case, the task list shows no visibility under the assignee, and someone who can configure workflows should Reassign it to the right people.
Escalation doesn't take the task away from anyone. It adds the escalation role's users and notifies them, and the original assignees keep the task.
Due dates, overdue tasks, and escalation
The due date is set when the task is created: that moment plus the Due within days. If you change Due within later, only tasks created after the edit pick up the new timing. Tasks already on someone's list keep the due date they were given.
On the task list, upcoming tasks show the due date and how soon it is. A task past its due date is tagged Overdue in red until it's completed, skipped, or cancelled, and you can filter the list to Overdue.
Once a task is overdue, August notifies the If overdue, escalate to role, if you set one. Each task is escalated once. The original assignees still see it, and now the escalated people see it too.
On time means the task was completed on or before its due date. The workflow summary only counts completed tasks, so skipped tasks are left out of the percentage. The summary reads something like 12 students in progress · 40 completed · 86% of steps finished on time, and the in-progress and completed counts link to Students, already filtered to this workflow.
Above the steps, a strip shows each step, its role, how many students are on it right now, and that step's on-time share. Click any count above zero to open Students filtered to that step.
Run it for a group
Run now sits on the workflow header next to the Active switch. It stays off while the workflow is paused (the tooltip says Turn the workflow on to start it).
Turn the workflow Active.
Click Run now.
Search for students, sections, or both. A section includes its active students.
Click Start.
August starts the workflow in the background and lets you know when it's finished. You'll see the process listed as Start workflows.
Students who already have this workflow in progress, students outside Applies to, and students the person who clicked Start can't see are all skipped.
Pause, edit, or delete while students are in it
Edits apply to the live workflow, and open runs follow the steps as they stand when each task finishes.
Renaming a step, or changing its action or template, updates the open task. Any record already created by Start stays as it is.
Changing Assigned to updates the role shown on open tasks, but the people already assigned stay assigned until you reassign that task. The new role is used the next time the step starts for a student.
Reordering, inserting, or removing a step changes what comes next. When the current task is completed or skipped, the student moves to whatever step now follows it. Students who have already passed the spot where you insert a step won't go back to it, and a removed step stays in the history of runs that already reached it.
Pausing stops new runs and leaves current runs moving.
Deleting asks you to confirm first and tells you how many in-progress runs will stop. Open runs and their open tasks are cancelled, completed history is kept, and the workflow leaves the configure list.
Part 2: Work a task
Open Workflows in the sidebar, or click See all on the board or All tasks in Early warning. This opens Workflow tasks: the steps assigned to your role. Start the action, finish it, and the workflow hands the next step to the right person.
If you can configure workflows, you'll see a switch between My tasks and Everyone's. Everyone else sees their own tasks, including any escalated to them.
Read the list
The list opens on Open tasks, soonest due date first. Use these shortcuts to switch views:
Shortcut | Which tasks |
Open | Waiting to be started, or started and not finished yet. |
Overdue | Open tasks past their due date. |
Finished | Completed, skipped, or cancelled. |
The filter drawer lets you narrow by Student and by Status (Open, In progress, Completed, Skipped, Cancelled).
Each row shows:
The student
The role and the people assigned (hover to see every name, plus who it was escalated to)
The due date and status
The task, including the workflow name, where it sits (e.g., Step 2 of 4), and the action when it's something other than No action
Click a row to open the run, or use the buttons right on the row to do the same work without leaving the list.
On the run
The run card names the workflow, the student, and the run status:
Status | What it means |
In progress | A step is still open. |
Completed | Every step was completed or skipped. |
Cancelled | Someone stopped the run before it finished. |
Under the title, you can see when the run started, whether it started from a record or by hand, and when it finished or was cancelled. If a workflow that normally runs from a trigger was started by hand, the card says so and names the usual trigger.
Steps are listed in order. Steps the student hasn't reached yet show the role and how many days they'll have. The current step shows Start, Complete, Skip, and, for people who can configure workflows, Reassign.
Button | What it does |
Start | Creates or opens the record for this step, marks the task In progress, and takes you to that record. |
Open … | Takes you back to the encounter, plan, file, thread, form request, or workflow this step already started. |
Complete | Marks the step done and moves the run forward. On the last step, the run becomes Completed. |
Skip | Asks you to confirm, then moves on to the next step. The history keeps the skip, who skipped it, and the date. On the task list, Skip appears on the row once there's a record to open, and always appears for a No action step. |
Reassign | Replaces the current assignees with the people you pick (at least one) and notifies them as a new assignment. |
Cancel workflow | Stops this run and cancels the open task. Steps already finished stay finished. |
When a step is completed, August records who completed it and whether it was late. The next step's task is created at that moment with its own due date, and those people are notified.
Open views refresh as runs move, including the banner on an encounter or plan and the counts on Students.
Part 3: See who is in a workflow
Open Workflows → Students to see Students in workflows.
Use the switch at the top right to choose who's listed:
Choice | Who is listed |
In progress (Default) | Students with an open run. |
Completed | Students with a finished run. |
All | Every run, including cancelled runs. |
The pills across the top are your workflows, each with a count. Click one or more to combine them, or click All to clear the filter. Counts stay visible even at zero, so you can always turn a pill back off.
The table lists each student's name, grade, and student ID, followed by one line per run with the workflow name and where they stand. An open run reads something like Step 2 of 4: Message the family · due Oct 28, and a past-due step shows in red. Completed and cancelled runs show the date they ended.
The filter drawer includes Student, Grade, Section, and, while you're on In progress, Current step (grouped by workflow).
Click a student row to expand it. You'll see the same Workflows tab from the student card, so you can review every run and start another workflow right from there.
Notifications
Workflows come with two alert rules. You can review them under Alerts (the configure gear, or Alerts → Configure).
Alert | Who is notified | Default message |
Notify users when they are assigned a workflow task | Assigned users | New workflow task: {step name}. The body names the workflow, the student, and the due date. |
Notify escalation users when a workflow task is overdue | Escalated-to users | Overdue workflow task: {step name}. The body names the workflow, the student, and the due date. |
You can turn either rule on or off, change the recipients, and edit the wording just like any other alert. Messages can include the student name, workflow name, step name, and due date.
Reassigning a task sends the assignment alert again to the people you chose.
Completing a task is recorded on the run. The built-in alerts cover assignment and escalation only.
If you enable reminders on the assignment alert, they stop once the task is completed, skipped, or cancelled.
Best practices & tips
Start small. A workflow with three or four clear steps is easier to adopt than one that tries to capture every edge case on day one.
Name steps the way your team talks. The step name is what shows up on someone's to-do list, so make it obvious what needs to happen.
Set escalation on time-sensitive steps. It's a gentle safety net that keeps the original owner in charge while making sure someone else knows when things slip.
Test with Run now. Turn the workflow on, run it for a single student, and walk through each step before rolling it out to a whole section or trigger.
Questions?
We're always happy to help. Reach August Support through the Help icon in the app, or email us at [email protected].
