The day's workPart 3 of 3
Lists and alerts
Every record type in Workstride opens into the same list, with plain-word filters, saved searches, bulk actions and alerts that are saved searches too.
Workstride is being built for accreditation by DEWR as a Third Party Employment System. It is not yet accredited.
- Filters
- 15 operators, in plain words
- Alerts
- 30 ship by default (counted 17/09/2026)
- Export
- Any list, to CSV
Shares its record with Participants and employers
One list behind every record type
For consultants scanning their own caseload, and for site managers and administrators scanning across a whole site or organisation.
Participants, appointments, placements, claims, queries, complaints and every other record type in Workstride open into the same kind of list. Filters read as plain sentences, not query syntax: "Status is any of Commenced, In Progress", "Last note before 30 days ago". Relative dates keep working as time passes, and derived fields, such as an age worked out from a date of birth or the distance to a due date, sit alongside the fields actually stored on the record. In the build
Fifteen operators cover what a filter needs to say: equals, is any of, contains, is empty, is before, is after, more than a number of days ago and so on. A column chooser picks which fields show, and any list exports to CSV with the columns you have chosen, limited to the records your own site access covers. In the build
Caution
A bulk action runs against every record you have selected, across every site your access covers, the moment you press Apply. Check the count above the button, not just the rows on screen, before you send an assignment, a status change or a message to a whole list.
On sample data
The "No note in 30 days" alert, opened as a list
Alerts for a site manager first, then the "No note in 30 days" row opened as the filtered, columned, bulk-actionable list behind it.
Alerts
What needs attention across the records your access covers. Each alert is a saved search; open one to see the records behind it.
Critical
24
Priority
39
Business as usual
15
Pinned
| Alert | Records | Priority | Applies to |
|---|---|---|---|
| Appointment result not recordedAppointments that have happened with no attendance result yet (Part B 6.6). | 4 | Critical | Appointments |
| Claims needing information from the consultantThe claims team has asked for more. | 0 | Critical | Claims |
| Complaints not yet acknowledgedComplaints received and not acknowledged to the person who made them. | 1 | Critical | Complaints |
| ESS entry overdueResults not confirmed as entered in ESS Web by close of business on the day. | 3 | Critical | Appointments |
| No note in 30 daysCommenced participants with no file note recorded in the last 30 days. | 9 | Critical | Participants |
| Queries past their due dateOpen queries whose due date has passed. | 2 | Critical | Queries |
| Support contact overdueActive placements whose next post placement support contact is past due. | 2 | Critical | Placements |
| Claim due within 7 daysClaims still tracking with a due date inside a week. | 3 | Priority | Claims |
| Expenses awaiting approvalRequests waiting on an approver. | 4 | Priority | Expenses |
| Lead waiting over 7 daysOpen participant leads not touched in a week. | 2 | Priority | Participant leads |
| No case managerCommenced participants nobody is managing. | 1 | Priority | Participants |
| Notification of Employment awaiting acceptancePlacements notified but not yet validated and anchored. | 2 | Priority | Placements |
| Queries nobody has picked upOpen queries with no assignee. | 2 | Priority | Queries |
| Registration windows ending with no Progress FeeFifty-two week registration windows ending within eight weeks with no Progress Fee claimed (two are available in each, Part B 11.4.1). | 7 | Priority | Progress periods |
| Wage subsidies awaiting approvalRequests waiting on a first or second approver. | 1 | Priority | Wage subsidy requests |
Sample people and organisations are invented. See "No note in 30 days" opened as a list.
"No note in 30 days" opened as a list
Website controls, not the product: reset this list to how it opened. Everything else in the frame below is the product itself.
No note in 30 days
9 participants matching your filters.
2 selected
| Name | Job Seeker ID | Status | Site | Managed by | Last note | Funding level | |
|---|---|---|---|---|---|---|---|
| BRENNAN, Chloe | ****8845 | Commenced | Orange (ORNG) | Bree Whitehead | 04/08/2026 11:20 | Level 3 | |
| ELLIS, Mitchell | ****3385 | Commenced | Dubbo (DUBB) | Marcus Byrne | 10/08/2026 14:30 | Level 2 | |
| HOANG, Ben | ****1946 | Commenced | Shellharbour (SHEL) | Jess Kavanagh | 29/07/2026 09:05 | Level 3 | |
| KAUR, Olivia | ****7420 | Commenced | Shellharbour (SHEL) | Jess Kavanagh | 12/08/2026 15:45 | Level 2 | |
| O'CONNOR, Declan | ****2218 | Commenced | Dubbo (DUBB) | Marcus Byrne | 06/08/2026 10:15 | Level 3 | |
| PRYOR, Lachlan | ****4409 | Commenced | Orange (ORNG) | Bree Whitehead | 21/07/2026 13:50 | Level 2 | |
| SANTOS, Gabriela | ****2754 | Commenced | Liverpool (LVPL) | Noor Hassan | 14/08/2026 11:40 | Level 2 | |
| WARD, Riley | ****6671 | Commenced | Wollongong (WOLL) | Sunita Pillai | 13/08/2026 09:30 | Level 3 | |
| YUSUF, Fatima | ****5126 | Commenced | Liverpool (LVPL) | Noor Hassan | 15/07/2026 16:10 | Level 4 |
Sample people and organisations are invented. Removing a filter, choosing columns, saving a search and applying a bulk action all work with a keyboard, and nothing you do here is sent anywhere.
-
Plain-word filters
Each filter reads as a sentence. Remove one and the list, and the count above it, updates at once.
-
Your site access
Only records inside your own site access ever appear here, and a CSV export carries the same limit.
-
Recorded record by record
A bulk action writes one line per record it touches, not one line for the whole batch, in the history below the list.
How it works
Saved searches, shared or pinned
Any filtered, columned list can be saved by name and shared with your organisation, or pinned to the top of your own list of searches. An alert is exactly this mechanism with three things added: a priority, a pinned position, and the roles it is visible to. Behind every alert is a saved search, and the count shown against it is scoped to the site access of whoever is looking. In the build
Bulk actions, recorded record by record
Select rows from a list and assign them a site or an owner, set a status, add or remove a tag, or send an email or an SMS (skipping anyone who has opted out). Workstride writes one history line for every record the action touches, not one line for the whole batch, so what happened to a particular person or employer is never lost inside a batch summary. In the build
Alerts clear themselves
An alert has no separate "resolved" state to set. Because it is a saved search, a record drops out the moment it stops matching: once a file note is recorded, "No note in 30 days" no longer lists that person. Where a record is not wrong, just not actionable yet, it can be set aside with a reason and a date instead, and those reasons feed the definition health report on deadlines and service levels. In the build
Product alerts and your own
Workstride ships with 30 alerts by default (counted 17/09/2026). Any provider can turn one off or narrow its filters today. A screen for building a new alert from scratch, rather than adjusting one of the 30, is planned. In the build Planned
“Where Providers manage File Notes through an approved IT System, the system must ensure File Notes have a date, time and user stamp on the entry, and these details are included in extracts or printouts uploaded to the Department's IT Systems as Documentary Evidence.”
Status, part by part
| Capability | Status | Rule, gate or note |
|---|---|---|
| The same list for every record type | In the build | Filters in plain words, relative dates, derived fields |
| Saved searches, shared or pinned | In the build | Shared across your organisation, or pinned to one person |
| Bulk actions, recorded record by record | In the build | Site, owner, status, tags, email, SMS with opt-outs skipped |
| Alerts as saved searches, with a priority and pinning | In the build | 30 ship by default (counted 17/09/2026) |
| Turning an alert off or narrowing its filters | In the build | Per provider |
| Set aside with a reason and a date | In the build | Feeds the definition health report |
| CSV export | In the build | Every list, scoped to your site access |
| An alert authoring screen | Planned | Building a new alert from scratch, not adjusting one of the 30 |
| Delivering alerts to calendars and chat | Planned | Today only deadlines reach calendars, chat and the morning summary |
- In the buildA first version exists and runs on sample data. No provider uses it yet.
- PlannedOn our roadmap, not built yet.
- Waiting on approvalNeeds a decision from the Department or DEWR, a supplier agreement, or legal sign-off.
What it does not do yet
- Quick filter chips for common views Planned
- Overdue row shading inside a list Planned
- Kanban views of a list Planned
- An alert authoring screen Planned
- Filtering alerts by program Planned
- Delivering alerts to calendars and chat Planned
Related pages, guides and tools
-
My work
The ranked list one alert can open into, explained item by item.
In the build
-
Deadlines and service levels
Where the reasons behind a set-aside record show up as definition health.
In the build
-
Caseload and records
The participant record behind every row in a list like this one.
In the build
Questions about lists and alerts
Can we build our own alert from scratch?
Not yet. You can turn off any of the 30 alerts Workstride ships with, or narrow its filters, today. A screen for authoring a new alert from nothing is planned.
Does an alert only ever show what I am allowed to see?
Yes. Every count and every row is scoped to the site access recorded against your staff record, the same access that governs everything else you can see in Workstride.
Can we use this with participants now?
No. Using Workstride with participant data first needs DEWR to accredit the Workstride system and us to hold a Third Party IT Vendor Deed, then your organisation's written approval from the Department (Part A 7.2.2).
Sources
- Inclusive Employment Australia Guidelines Part A, version 1.1
Sources checked on 17/09/2026. Checked against the build on 17/09/2026.
See it on sample data, with the people building it.
A walkthrough covers the parts of Workstride your teams would use, the status of each one, and the approval steps your organisation takes.
Using Workstride with participant data first needs DEWR to accredit the Workstride system and us to hold a Third Party IT Vendor Deed, then your organisation's written approval from the Department (IEA Guidelines Part A 7.2.2).
Workstride is new, and we are inviting Inclusive Employment Australia providers to help shape it before launch. Help shape Workstride.
Tell us who is coming
Send the form with the roles you want to bring and the parts you want to see.
We reply to set a time
We suggest times that suit your team and confirm what the session will cover.
The walkthrough
Sample data only, with the status of every part said out loud. Nothing about your participants is asked or needed.