The short answer
A shift needs four basics: a participant, a date, start and end times, and either an assigned worker or a decision to leave it open. Most support workers never build this record, but knowing what goes into it helps if you step into scheduling.
A shift record needs four things to exist: a participant, a date, a start and end time, and either an assigned worker or a decision to leave it unassigned for now. That is true whether someone is filling in a paper roster, a spreadsheet, or rostering software. For most support workers, someone else handles this step. But if you have been handed scheduling access, or you organise your own client work, it helps to know what should go into a shift before you build one.
Why most support workers never touch this screen
If you are employed by a provider, creating the shift itself usually sits with an owner, coordinator or admin. They set the participant, date and times, decide who is working, and approve hours once the shift is done. Your part is different: you see the shifts assigned to you, record your availability, add notes after a visit, and submit your hours for approval. You do not need to build the shift record for this to work, and nothing about your role requires you to buy separate scheduling software.
What a shift actually needs, step by step
- A participant linked to that booking
- A date, plus a start time and an end time
- A worker assigned, or the shift left open until someone is rostered
- For a 2:1 support or group session, an extra participant or staff member added
- An optional repeat setting if it is a regular weekly booking, not a one-off
- An optional adjustment to the usual task list, just for that booking
- Billing and pay details drawn from the business's price list
A fictional example: handed the Saturday roster
Picture a fictional, anonymous support worker we will call Priya. She has worked with the same small team for a year and is recently trusted to build the Saturday shifts while her coordinator is on leave. Priya starts with the participant, sets the date and times, and checks whether the booking needs two workers before assigning anyone. For a regular client she sets it to repeat weekly. For one participant whose plan has changed recently, she removes a task that no longer applies to that single booking rather than changing the standing list. Before confirming, she reads a clash warning that flags an overlap with another booking and fixes the time before saving. None of this is a real business or participant, it is a fictional walkthrough of the decisions involved.
If you run your own client work instead of being employed
Independent support workers managing their own clients are in a different position from an employee. You are not being rostered by someone else, so you need your own way to track bookings, write shift notes and invoice. Sparks Provider is built for running a provider team, so it is not the right fit here. Sparks Scribe, made by the same Sparks team, is for independent support workers managing their own client work, with shift notes and invoicing including typed or spoken note capture. Worth knowing about if that describes your situation, not something every reader needs.
Questions worth asking if scheduling becomes part of your role
- Is the right participant linked, especially if two clients have similar names
- Do the start and end times account for travel or handover, not just the visit itself
- Does this booking need a second worker, and has that been added
- Does the task list for this booking still match the participant's current plan
- Have you read any clash warning properly before confirming the shift
Related reading
If you want the other side of this process, see What Actually Happens When You're Offered a Shift (And How to Reply Fast) and Shift Changed at the Last Minute? Here Is What to Check Before You Go, both on this site.
Frequently asked questions
Do I need to create my own shifts as an employee?
No. Assigned shift creation sits with your employer or scheduler. As an employee you accept, work and record notes on shifts rather than build the shift itself.
What does it mean if a shift shows as unassigned?
It means the booking exists but no worker has been chosen for it yet. If you were expecting to be on it, check with your coordinator.
I run my own client work. Do I need the same software as a provider business?
Not necessarily. Sparks Provider is for running a provider team. Sparks Scribe, from the same Sparks team, is for independent support workers managing their own client work, with shift notes and invoicing.
What should I do if I see a clash warning while building a shift?
Read it before confirming. It flags an overlap with another booking so you can check and adjust the time before the shift is saved.