Manager Dashboard
Actions, service FTE position and contract horizon for the selected pay cycle.
Manager actions
Live prompts for data risks, upcoming decisions and workforce gaps.
Team FTE budget — selected cycle
▾Contract horizon
Temp contracts and dated movements by time to expiry — soonest first.
Rotation Planner
Who is working in each role, in each pay cycle. Plan ahead, and see where leave or over-allocation gets in the way.
An assignment puts one person from the Staff Register into one role for a date range, with its own FTE. A role can hold several people and a person can be split across roles. Assignments are your plan; leave and cover are read live from Movements and flagged when they clash with the plan. Teams and roles are built in Settings.
Plan ahead — next 8 pay cycles
Assigned FTE / funded FTE per role, starting from the selected cycle.
Staff allocation — selected cycle
Register FTE against FTE assigned to roles. Shows who is unallocated or over-allocated.
Cover is counted only where it overlaps the absence in this fortnight, so sequential backfills no longer look over-filled.
FTE Gaps
Each person with an absence — what is vacated vs what is backfilled.
Auto-built live from movements. Vacated = leave / secondment-out / partial parental return. Backfilled = backfill movements owned by that person. Totals sum across the whole movement, not a single fortnight.
Budget Summary
Effective FTE per classification across 13 fortnights.
Fortnight Planner
Where every staff line is working, week by week. Heavier line = fortnight (pay cycle) boundary.
1.0 = working substantive FTE
Class code = acting up in that class
P 0.4 = parental (vacated FTE)
L = leave
S = secondment out
X = contract ended
Staff Details
Select a staff member to view their current position, backfill arrangements and movement timeline.
Active Movements
The single source of truth. One movement = one row.
Staff Register
Every staff member and their substantive line(s). Split substantive = multiple rows.
Audit History
Local change log for staff lines, movements, settings and administrative changes.
The audit history is stored locally in this browser and included in exported backups. It is not a formal enterprise audit log, but it gives a practical history of what changed and when.
Settings
Service identity, teams & roles, classification budget, and pay-cycle calendar.
Service identity
Drives the banner, the browser tab and the backup file name.
Teams & roles
Build your own service structure: teams, and the roles inside each team.
A team is any grouping you use (a ward, service line, rotation area). A role is a funded position inside a team. Each role has a classification (pay grade) and funded FTE. Funded FTE on roles adds up to the baseline for each classification, so the budget stays in step. Staff lines are then assigned to a team and role in the Staff Register.
Classification budget
Add, rename or remove classifications and set the funded FTE for this service.
Baseline FTE = your funded establishment for that classification. Where roles use a classification, its baseline is added up from those roles automatically; otherwise you can type it here. Ceiling = the most you are permitted to run. Additional approved = extra FTE signed off outside the baseline (e.g. new grant funding) — it is added to the ceiling, not the baseline.
Pay-cycle calendar
▾Standard Queensland Health fortnight runs Wed–Tue. Change the anchor only if the pay calendar shifts.
Backup & data
▾Your data auto-saves to this browser on every change. The backup file is your insurance — export it regularly and keep a copy somewhere safe.