The day's workPart 1 of 3
My work
Each person starts with one list of what is due, ranked by urgency and the money at stake, with the reasons shown.
Workstride is being built for accreditation by DEWR as a Third Party Employment System. It is not yet accredited.
- Budget
- 25 items shown a day, best first; the rest are counted
- Escalation
- Site manager at 24 hours past due, tenant administrator at 168
- Snooze
- Up to 14 days, never past a hard limit
Shares its record with Placements and money
What it does
For a consultant, site manager, claims officer or approver: one ranked list of everything open, in your site access, instead of separate reminders in separate places.
Every deadline in Workstride is a clock (see Deadlines and service levels). My work turns the open clocks in your site access into a single ordered list. A score from 0 to 100 is built from the clock's state (breached 50, due today 35, warning 20, running 5), the money at stake on a log scale capped at 40, 10 points for each escalation step and 2 points for each day overdue, capped at 10. The inputs are shown next to every item, not hidden behind the number. In the build
Each item says what clears it, in the product's own words, and it clears itself the moment that work is recorded elsewhere on the record, such as a support contact or an attendance result. In the build
Caution
The score ranks work; it does not decide what the Department will pay or accept. Recording the underlying work (a contact, a result, a document) is still what matters, and Workstride's own defaults for support contacts, document requests and complaint times are provider policy, not Guideline deadlines.
On sample data
A Thursday morning for Sunita Pillai, Wollongong
Move Demo time forward to watch items warn, come due and breach; acknowledge or snooze one with a reason; mark Sunita away and see her work follow her; switch to Team work to see what her manager sees.
My work
What needs doing, in order of score: overdue and money at stake first. Items clear themselves when the evidence lands.
Overdue
2
Due today
3
Coming up
3
FIFITA, Mele 1 item
-
Breached Support contact due Record the support contact on the placement.
Acknowledge or snooze
KARIMI, Zahra 1 item
-
Breached Attendance result entered in ESS Web Record the attendance result and confirm it is entered in ESS Web.
Acknowledge or snooze
NGUYEN, Linh 2 items
-
Due today Support contact due Record the support contact on the placement.
Acknowledge or snooze
-
Warning Document received from the participant Chase the participant for the document, or record it when it arrives.
Acknowledge or snooze
BROWN, Tyler 1 item
-
Warning Wage subsidy agreement in place within 28 days of the start Have the employer approve the agreement and record the Department's agreement identifier on the request.
Acknowledge or snooze
PAPADOPOULOS, Maria 2 items
-
Due today Attendance result entered in ESS Web Record the attendance result and confirm it is entered in ESS Web.
Acknowledge or snooze
-
Running Support contact due Record the support contact on the placement.
Acknowledge or snooze
Participant lead #57 1 item
-
Due today Participant enquiry contacted Contact the person and move the lead past enquiry.
Acknowledge or snooze
ABDI, Hodan 1 item
-
Warning Employer follow-up after reverse marketing Contact the employer again and record the activity.
Acknowledge or snooze
OSEI, Kofi 1 item
-
Running Exit or transfer completed on its effective date Work through the checklist and complete the exit or transfer.
Acknowledge or snooze
Snoozed
- Employer follow-up after reverse marketing for KARIMI, Zahra, until 21/09/2026 07:00: Employer on leave until Monday.
- 08:30 PAPADOPOULOS, Maria, contact
- 10:30 ABDI, Hodan, job searchScheduled
- 13:00 NGUYEN, Linh, contactScheduled
- 15:00 WARD, Riley, reviewScheduled
While you are away your items route to your delegate, or to your site manager. Automatic replies in your mailbox set this for you; you can also set it here.
Team work
Each person's open items inside your site access, who is away and who is covering, and the overdue items you can move to someone else.
| Person | Open | Overdue | Due today | Covering | Score | Away |
|---|---|---|---|---|---|---|
| Bree Whitehead | 17 | 2 | 2 | 6 | 402 | |
| Dimitra Kallis | 9 | 3 | 318 | |||
| Helen Achterberg | 1 | 5 | ||||
| Jess Kavanagh | 12 | 1 | 1 | 241 | ||
| Joanne Fairweather | 3 | 1 | 1 | 128 | ||
| Marcus Byrne | 0 | 0 | Away until 21/09/2026 | |||
| Noor Hassan | 14 | 2 | 2 | 377 | ||
| Peter Galanis | 0 | 0 | ||||
| Quan Vo | 7 | 1 | 2 | 243 | ||
| Rafael Mendes | 0 | 0 | ||||
| Sunita Pillai | 10 | 2 | 3 | 361 |
- Score 86 Support contact due due 11/09/2026 17:00, with Bree Whitehead, escalated to Joanne Fairweather, $3,792.68 at stake
- Score 78 Support contact due due 15/09/2026 17:00, with Sunita Pillai, escalated to Joanne Fairweather, $4,340.27 at stake
- Score 64 Attendance result entered in ESS Web due 14/09/2026 17:00, with Sunita Pillai, escalated to Joanne Fairweather
- Score 62 Query answered by its due date due 15/09/2026 17:00, with Quan Vo, escalated to Joanne Fairweather
- Score 62 Participant told of the exit within 14 days due 15/09/2026 17:00, with Jess Kavanagh, escalated to Joanne Fairweather
- Score 50 Query answered by its due date due 16/09/2026 17:00, with Joanne Fairweather
- Score 50 Document received from the participant due 16/09/2026 17:00, with Noor Hassan
- Score 50 Attendance result entered in ESS Web due 16/09/2026 17:00, with Noor Hassan
- Score 50 Employer follow-up after reverse marketing due 16/09/2026 17:00, with Bree Whitehead
Sample data. Invented names. Illustrative figures.
-
The order
Breached items lead, then due today, then warnings, then running work; money, escalation and days overdue add on top. Not AI, not a prediction: the same rule every time (L64).
-
Attendance results are due in ESS Web by close of business, or within three Business Days where that is not possible; My work carries this deadline as a clock.
“The Provider must record an attendance result in the Department's IT Systems by close of business on the day of the Contact Appointment or Activity.”
-
Cover while away
When someone's out-of-office is on, their deadlines go to their delegate or to a manager covering the site.
How it works
One card per participant or employer
My work shows up to 25 items a day, best score first, with the rest counted on the page; a morning summary from your own mailbox covers the whole list, scheduled at 07:30 Sydney time for every provider, whatever your own time zone.
Acknowledge or snooze, never past a hard limit
Acknowledge an item with a reason and it stays on the list, marked seen. Snooze it with a reason and a date and it moves to a Snoozed list until that date, up to 14 days ahead and never past a clock's own hard limit, such as the three Business Day limit on an attendance result.
Overdue work climbs, on timings you set
Overdue work reaches the site manager 24 hours past due and the provider's administrator 168 hours past due, by default. A team chat notice posts when the deadline is missed and again at each climb, waiting for evenings and weekends to end before it posts. The held notice is not folded into the morning summary; it stays a separate chat notice.
Work follows people, not just their calendar
Automatic replies read hourly from Microsoft 365 or Gmail, or a delegate set by hand, route each open item to a delegate while its owner is away, then to a manager covering the site if the delegate is away too, with the reason written on the item.
Team work, for the person covering the site
A manager sees open, overdue, due today, covering and away for everyone in their site access, and can move any overdue item to someone else, with a reason.
“The Provider must record an attendance result in the Department's IT Systems by close of business on the day of the Contact Appointment or Activity.”
Note
Six kinds of obligation also appear as calendar entries in the responsible person's own calendar, and disappear when the work is recorded: support contacts, Ongoing Support Assessments, wage subsidy agreements, Employment Assistance Fund declarations, exit notifications and reverse marketing follow-ups. My work never creates a calendar entry for a claim hand-off or a lead's first contact.
What My work is not
Not AI, and not a prediction: the ranking is the same published rule applied to every item, every time. Not a staff monitoring tool: the counts and scores describe the work, not the person doing it. The same ranked list is also available through the API (see Developers).
Status, part by part
| Capability | Status | Rule, gate or note |
|---|---|---|
| Scoring and ranking | In the build | Provider policy for defaults; Part B 6.6 for attendance results |
| Daily budget and grouping | In the build | 25 items a day, by default |
| Acknowledge and snooze | In the build | Up to 14 days, never past a hard limit |
| Escalation and team chat notices | In the build | 24 and 168 hours past due, by default |
| Cover while away (Microsoft 365 and Gmail) | In the build | Verified on live directories before launch |
| Morning summary | In the build | 07:30 Sydney time for every provider |
| Team work and service level reporting | In the build | See Deadlines and service levels |
| API access to the ranked list | In the build | See Developers |
| Personal reminders and an in-app calendar of system events | Planned | Not built yet |
| Prediction beyond the published rules | Planned | Over participant data, also Waiting on approval |
- 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
- Personal reminders a person sets for themselves Planned
- An in-app calendar of the system's own dated events Planned
- Prediction or scoring built from participant data Waiting on approval
Related pages, guides and tools
-
Deadlines and service levels
How a clock's state, warning and hard limit are set, and how attainment is reported.
In the build
-
Lists and alerts
The same score and clock ideas, as a list you can filter, save and act on in bulk.
In the build
-
Claims and outcome tracking
Where a claim's own deadlines and money at stake come from.
In the build
Questions about My work
Does My work use AI to prioritise the day?
No. The score is a published, rules based formula applied the same way to every item every time: state, money at stake, escalation and days overdue. There is no AI or prediction in it (L64).
Is this a staff monitoring tool?
No. My work ranks open work, not the people doing it. It does not track time on task, keystrokes or activity; it shows what is due and what has already been recorded against it.
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 B, version 1.1
- 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.