What's built

Every item below is in the product today — nothing here is a plan.

Register your casual workers

Add a casual worker's name and a mobile number or email, and FlexiConnect sends them an invite to create or link their account.

Register someone who's already in FlexiConnect, and you're offered the existing worker to link instead of creating a second record.

Set up worker types — like RN, forklift or bar — and groups, and give each worker as many of each as apply, ready to target when you release a shift.

Build rosters

Create a roster with a date range, then add shifts to it — each with a start and end time, a headcount, and optionally a required worker type.

Every roster runs on your organisation's own Australian timezone, with daylight-saving changeovers handled automatically.

Duplicate a whole roster or week to a new start date when the next one looks the same, carrying its shifts and notes with it.

Release shifts to the right people

Build a roster of shifts, then release each one to everyone eligible, or just to a chosen group or worker type.

Before you confirm a release, FlexiConnect shows exactly how many workers it will reach — resolved by the server, not estimated on screen.

If a release would reach no one right now, you can release it anyway with one extra click, rather than being blocked outright.

Changed your mind before anyone's accepted? Recall a released shift and it comes off the roster's released list.

Releasing a shift sends a push notification to eligible workers' phones, except workers who have muted your organisation.

First accept wins

The first worker to accept a released shift gets it, by construction — the database allows only one winner, and everyone else sees that it's filled, not an error.

A worker can withdraw from an accepted shift until your cutoff — the exact time is shown on their withdraw button itself.

Watch it fill

Watch every shift's status — draft, released, accepted or unfilled — on a fill board that refreshes on its own, and assign a worker yourself before a shift starts, or unassign an accepted one.

Shift history

Look back at any worker's shifts, filter by date range and status, and see them all in one list.

Export what's on screen in the shift-history list to a CSV.

Attendance

With optional check-in and check-out switched on for your organisation, you see the variance against rostered times for every shift — plus a manual correction with an audit note when something needs fixing.

Reporting

See your organisation's fill rate and time-to-fill for a date range of up to a year, bucketed by day, week or month, with no-shows counted alongside them, plus a shift-by-shift report of who worked each shift and for how long — export either report to CSV.

One worker, every employer

Casual workers keep one FlexiConnect login no matter how many organisations register them.

Their calendar merges accepted shifts from every one of those organisations into a single view, colour-coded by employer.

Muting an employer is a preference about new shifts from them — it never removes a shift you've already accepted, and you can still see everything by opening the app.

If you try to leave an employer with upcoming shifts booked, FlexiConnect tells you how many and asks you to withdraw them first.

Workers get an hours summary per employer, for this week, this month, the last three months, or a custom date range, exportable to CSV for their own records.

Platform support

Platform staff create each organisation's tenant, set its home Australian timezone, and choose whether optional check-in and check-out is on, at creation.

Platform staff can suspend or reactivate an organisation's access — once suspended, its workers can no longer accept its shifts.

If FlexiConnect suspends or reactivates your organisation, its active org admin accounts get an email explaining what changed — staff accounts and workers are not emailed.

Platform support can correct any tenant's records through the same kind of screens that tenant's own admins use, with every override logged — who, what, before and after, and why.

Platform accounts require multi-factor authentication to sign in.

Questions about what's built or what's next? Talk to us.