The site register
Every location your organisation runs, in one list.
- Search by site name or address
- Filter by site type
- Show or hide inactive sites
- Open any site straight into its record
Sites
Every house, program and service area, set up once and used everywhere.
In most organisations, how a site really runs lives in someone's head: who works there, who can be called in, what a worker has to hold before they set foot in the house, and which rules apply when someone wants to swap or hand a shift back. That knowledge does not survive a resignation or a bad weekend.
In BondiByte a site is a real record. It holds the participants, the team, the requirements and the operating rules for that location, and rostering, the staff app, documents and audit evidence all read from it.
- Create the site
- Link the participants it serves
- Build the staff team
- Set what a worker must hold
- Set the site's operating rules
- Roster the site
A register you can search, and a record that holds the detail.
The site record
One record, with every part of the site's operation on its own tab.
- Overview, with the site's people and roster context
- Clients and Staff
- Capabilities and Documents
- Roster, Reports and Shift Swaps
- History of what changed and who changed it
- Site settings
Participants and staff teams
Who the site supports, and who is allowed to work there.
- Link participants with the relationship that applies
- Build primary, secondary and relief teams
- Name a site lead or a coordinator with oversight
- Every assignment carries its own start and end date
Requirements for working there
What a worker must hold before this site will roster them.
- Add a requirement per site
- Choose a hard blocker or a preference
- Leave a note for managers and roster reviewers
- Deactivate a requirement without losing the record
Sites come in more than one shape.
A site type is set when you create the site and can be changed later. It groups the register, and it tells everyone reading the record what kind of place they are looking at.
Site type
Typically used for
SIL Home
A supported independent living home with its own team, roster pattern and requirements.
Respite
Short stay and respite placements, where the participants at the site change often.
Community Access
Community based supports that are not tied to a residence.
Office
Head office and administrative locations that still need staff, documents and rosters attached.
Other
Anything that does not fit the four above, including a logical service area for a single participant.
People
Known staff first, relief when you need it.
Participants are linked to the site with the relationship that actually applies, including SIL, current residence, short stay or respite, day program, community access, a service location, or a temporary placement. The link carries dates, so a record of who the site supported and when survives the change.
Staff are linked the same way. A worker joins the primary team, the secondary team or the relief team, or is named as the site lead or a coordinator with oversight. Rostering reads those relationships rather than guessing from availability alone.
Each site then decides how far down the list rostering is allowed to go: whether the secondary team can be used, whether relief staff can be used, whether the primary team is preferred, and whether secondary staff should be tried before relief.
Familiar faces first. Cover without guesswork. The record outlives the roster.
- Primary team
- Secondary team
- Relief team
Say what a worker must hold to work at this site.
Some sites need training, checks or skills that others do not. Add those requirements to the site, and rostering applies them every time it looks for someone to fill a shift there.
Hard blocker
The requirement decides who can be rostered.
- A worker who does not hold it is excluded from the site
- Use it for the checks and training you will not make an exception on
- Rostering explains why someone was not eligible
Preferred
The requirement guides the choice without blocking it.
- A worker who holds it scores better for the site's shifts
- A worker who does not is still available to roster
- Use it for the skills you want first, not the ones you insist on
Some requirements are enforced once for the whole organisation instead of site by site. Those appear on the site's list as read-only, so you can always see what applies here even when it was not set here. See how compliance enforcement works.
Rules that belong to the site, not to the whole organisation.
A quiet office does not need the same rules as a SIL home with overnight cover. Each site carries its own settings, so you can tighten one location without changing how everywhere else works.
Shift swaps
Decide whether this site's staff can swap at all, and who signs it off.
- Turn swaps on or off per site
- Set a maximum number of swaps
- Require approval, or let an agreed swap stand
- Name a team leader or manager as the swap approver
Cancellations
Let staff hand a shift back through the proper channel.
- Turn staff cancellation on or off per site
- Set a cutoff so shifts starting soon cannot be cancelled
- Require manager approval before it takes effect
- Notify the site manager or an administrator
Open shifts
Control who sees unfilled work, and how it gets filled.
- Require manager approval, so a request goes to the site's approvals queue
- Or let the first eligible worker be assigned automatically
- Choose whether secondary staff see the site's open shifts
- Choose whether relief staff see them too
- Eligibility checks still apply to everyone
Clock in and location checks
Record attendance at the site, with location where you need it.
- Turn clock in and clock out on for the site
- Record the worker's location with the shift when it is available
- Enforce a radius so a worker must be at the site to clock in
- Set the radius in metres
- The site's position comes from its street address
Sites also carry their own reminder settings, their own choice about collecting staff interest before assignment, and their own rule on whether a manager must give a reason when editing a shift.
Connected operations
Set the site up once, and the rest of the platform reads it.
The site is where rostering gets its team, its requirements and its rules. Smart Rostering builds each period against the site's pattern, checks candidates against the site's requirements, and respects the site's own settings on approval and publishing.
From there the same site record carries through: staff see the site name on their shift in the app, documents and reports attach to the site, and the evidence a site produces is available when audit preparation comes around.
One place to change it. Everywhere reads the same answer.
- Site
- Participants and staff team
- Requirements
- Roster period
- Published shifts
- Timesheets
- Audit evidence
Give every site a record worth trusting.
Start your free trial, or book a demo to see sites, teams, requirements and per-site rules working together with the roster.