Coverage you can see, with the human still making the call.
GA Applications designs workforce and scheduling dashboards that show availability, assignments, role and competency requirements, coverage and schedule exceptions. Capacity is defined in writing, personal information is minimised, fatigue and preference context is handled carefully, and allocation decisions stay with people who can weigh the circumstances.
Scheduling is a judgement call made under constraints. A good scheduling view makes the constraints visible — qualifications, coverage gaps, conflicts — and leaves the judgement to the person accountable for it.
Demonstration uses fictional staff names and rosters. Real builds follow your privacy and employment obligations.
Coverage matrix — week 32
Interface demonstration — fictional data| Person · role | Mon | Tue | Wed | Thu | Fri | Note |
|---|---|---|---|---|---|---|
| R. Wiki · electrician | OK | OK | OK | OK | OK | licence current |
| T. Kauri · electrician | OK | WC | WC | OK | OK | 4th consecutive shift Tue–Wed — review prompt |
| A. Morehu · apprentice | OK | OK | OFF | OK | OK | supervision required on live work |
| S. Baird · installer | GAP | OK | OK | OK | ? | Mon unfilled · Fri availability unconfirmed |
| J. Fox · installer | OFF | OFF | OK | WC | OK | Thu double-booked across two jobs |
- Monday: installer shift unfilledowner: planner · respond by Fri 16:00 (rule W-02)■Gap
- J. Fox double-booked Thursdayowner: planner · jobs JOB-2219 / JOB-2224 conflict▲Conflict
- S. Baird Friday availability unconfirmedroster feed 30h old · request sent◐Stale
Built for the planner, not instead of the planner
This direction serves workforce planners, roster owners, team leaders and the operations managers accountable for coverage. Its decisions are human ones with real consequences: Can Monday's schedule actually run? Is T. Kauri's stretch of consecutive shifts acceptable under our fatigue policy? Who resolves the double-booking — and does anyone know it exists yet? The view makes constraints visible so a person can weigh them; it never makes the allocation call, and it never will.
The target operating outcome: coverage gaps, competency mismatches and conflicts surface days ahead with a named owner and a response deadline — instead of a 6am phone tree. Personal information stays proportionate, and every allocation remains a reviewable human decision.
Coverage as a matrix, capacity as a written definition
The matrix reads like the roster thinks
People down the side, days across the top, and each cell answering one question: is this person appropriately assigned for this day? OK means assigned with required role and current competency. WC (covered with warning) means assigned but flagged — a consecutive-shift review prompt, a double-booking, a competency nearing expiry. GAP means a rostered shift with no qualified assignee. OFF means not rostered. ? means the source cannot currently say — availability unconfirmed, feed stale — and unknown is never rendered as covered.
Capacity is a definition, not a vibe
"Do we have enough people?" only means something against a written capacity definition: ordinary hours, agreed utilisation limits, how leave and training count, how on-call is treated. Two teams in the same business often need different definitions — the view carries each team's definition beside its numbers, versioned and owned, so 'at capacity' means the same thing in every conversation.
Exceptions are prompts, not verdicts
Fatigue patterns, preference mismatches and conflicts surface as review prompts for the planner, under policies you supply. GA Applications does not build workforce tooling that makes opaque hiring, eligibility, disciplinary or other adverse decisions — these flags exist to inform a person's judgement, and the reasons behind every prompt are visible to the person reviewing it.
Privacy boundary — what planning sees
Design pattern- Shown
- Not shown
- Constraints shown as
- Who sees the matrix
- Review prompts
The operational board needs to know someone is unavailable; it does not need to know why. Sensitive context stays in the HR system where it belongs.
Definitions this view typically carries
Coverage gap
A rostered shift with no assigned person holding the required role and current competency, as at 16:00 the prior day. Leave without approved replacement counts as a gap.
Competency currency
Days until expiry per required competency per person. Expired or unknown = not held, and assignments requiring it are flagged, never silently permitted.
Consecutive-shift review prompt
Assignment beyond the agreed consecutive-shift threshold (policy F-01, e.g. 3 shifts). A prompt for human review — not a violation finding and not an automated block.
Utilisation vs capacity
Assigned hours divided by capacity per the team's written definition. Reported at team level to avoid per-person surveillance; individuals see their own row only.
Roster, register, reality — and the gaps between them
Sources
- Roster system: shifts, assignments, availability
- Training register: competencies, expiry
- Timesheets: actuals (lagging, provisional)
Governed layer
- Capacity definitions per team, versioned
- Review-prompt rules (fatigue, preference) from your policies
- Privacy boundary: constraint facts only
- Refresh: roster 30 min, register daily
Views
- Planner matrix + exception queue
- Team leader: own team
- Individual: own row, own prompts
- Manager: team-level capacity
The most dangerous scheduling state is a confident roster built on unconfirmed availability — so unconfirmed stays visible. If the roster feed ages past its window, affected cells drop to unknown with a stale treatment and the planner is alerted, because acting on a 30-hour-old roster is how double-bookings happen. If the training register cannot confirm a competency, the assignment is flagged as unverified rather than assumed valid. And when the roster and reality disagree — someone worked a different shift than planned — the variance is recorded for review, not silently overwritten.
What we need from you, and how delivery runs
Inputs
- Read access to roster and training systems, subject to interface review
- Your capacity definitions per team — or a working session to write them
- Your fatigue, preference and supervision policies as rules we can encode as prompts
- Your privacy boundary: what planning may see, and what stays in HR systems
Delivery & acceptance
- Decision workshop with the planner and team leaders
- Source profile, including privacy review of every personal field
- Prototype against two real roster weeks, including historical exceptions
- Pilot alongside current practice; prompts tuned with the planner
- Acceptance: gaps and conflicts found before the day, not on it; unknown never renders as covered; review prompts show rule and reason; individuals see only their own row; table equivalents and keyboard access pass
Right fit
- Coverage depends on roles and competencies, not just headcount
- Gaps and conflicts are currently discovered on the day
- You want planning visibility with a defensible privacy boundary
Wrong fit
- You want automated rostering decisions or performance scoring of individuals
- You want leave reasons or medical context on an operational board
- There is no roster system or capture discipline to read from yet
Related directions and services
Frequently asked questions
Will the system decide who works when?
No. The view shows availability, requirements and conflicts so a planner can decide. GA Applications does not build workforce tooling that makes opaque hiring, eligibility, disciplinary or other adverse decisions, and allocation always remains a human, reviewable call.
What personal information does a scheduling view need?
As little as possible: name or identifier, role, relevant competencies, availability and assignments. Medical details, leave reasons and similar sensitive context should not appear on an operational board; where a constraint matters, it can be shown as 'unavailable' without the why.
How is capacity defined?
In writing, per team: ordinary hours, agreed utilisation limits, on-call arrangements and how leave and training count. Two teams rarely share one definition, so each capacity measure carries its definition and owner in the metric glossary.
Can it flag fatigue or preference conflicts?
It can surface patterns your policies define — consecutive shifts, short breaks, stated preferences — as review prompts for the planner. These are flags for human consideration, not automated verdicts, and the policies behind them must come from you.
What happens when the roster system and reality disagree?
That gap is exactly what the exception queue is for: unfilled shifts, double-bookings, competency mismatches and unconfirmed assignments are listed with an owner and a response path, and stale roster data is aged visibly rather than presented as current.
Where does your roster break first — coverage, competency or communication?
Describe how rosters are built and where exceptions surface today. We will scope a view that shows coverage and conflicts clearly, handles personal information proportionately and keeps allocation decisions with the people who own them.