Build a workable roster. See the gaps before the shift.
An HR system for staff records, availability, leave and permissions, with roster configuration and automatic allocation. Give employees a clear request route and managers control over approvals, staffing gaps and the published schedule.
Compare required staffing with available people and their approved skills. Make unfilled shifts and the reasons behind them visible before the roster is published, rather than presenting an infeasible plan as complete.
02
Less repeated reshuffling
Generate a candidate allocation from current availability, leave and approved scheduling rules. When an input changes, review the affected assignments instead of rebuilding the plan without a clear starting point.
03
Staff records and requests in one place
Give employees access to their own agreed profile details, availability and request status, and managers a clear route to review changes. Keep access permissions explicit and approved information available to roster planning.
The pilot would compare planning effort, coverage and manager corrections with the current process. These are intended benefits to test, not measured results.
Propose a roster. Let a person approve it.
Start with authorised staff profiles, roles and self-service permissions. Employees submit requests and managers approve the changes that affect planning. Automatic allocation proposes assignments for human approval.
Build the next roster
1
Confirm staff records, roles and coverage
Maintain authorised staff profiles, operational roles, skills and access permissions. Agree which details employees can view or request to correct. Set the period's staffing needs and use confirmed availability, working patterns and approved leave; flag missing or stale information.
2
Separate constraints from preferences
Configure the mandatory availability, skill, rest and coverage rules supplied by the responsible people. Record preferences separately so they can guide a proposal without silently weakening a hard constraint.
3
Generate a candidate allocation
Propose assignments within the approved constraints and show unresolved gaps. Explain which requirements prevent an assignment and where preferences could not be met; do not invent staff availability to fill an empty shift.
4
Review before publishing
An authorised manager checks the plan, adjusts assignments and approves it for sharing. Revalidate changes against the rules and retain the approver and reasons for permitted overrides.
Respond to a change
1
Submit and review a request
Employees use self-service to submit availability updates, leave requests or corrections to agreed profile details. A manager reviews the request under the defined permissions. Pending requests remain distinct from approved leave or confirmed availability.
2
Review the affected assignments
Bring approved updates into the staffing inputs, show conflicts and propose eligible alternatives within the rules. Respect agreed locked assignments and make remaining unfilled work explicit instead of quietly assigning an unsuitable person.
3
Approve and share the revision
The manager reviews and publishes the approved changes through the chosen route. Staff can see their request status and the roster view their permissions allow. Keep a revision history so the current schedule is clear.
Fit the planning process around your existing records.
Start with a manageable input and publication route. Existing HR, payroll and communication systems need an actual compatibility and permissions review.
01
Basic HR and planning workspace
Maintain the pilot's authorised staff profiles, roles, availability and leave in a workspace with defined access. Employees view their permitted details, submit requests and track status. Managers approve changes, configure the roster and review assignments before publication.
02
Supported HR or scheduling connection
Read approved staff, role and leave records through a supported interface where available, keeping ownership of each source explicit. Check refresh timing, identifiers, request status and access rights. A connection to a particular system is not assumed or promised.
03
Reviewed import and export
Use agreed files for inputs and export the approved roster into the existing process when direct integration is unavailable. Count manual preparation and handoff work in the pilot; payroll changes need a separately agreed scope.
Start with one team and one planning period.
Limit the HR workspace to agreed profile fields, one request-and-approval flow and a roster period. Keep manager approval in place and agree success measures before relying on the proposals.
1
Agree the team, rules and permissions
Select a limited team and planning period. Confirm profile fields, employee self-service access, request approvers and source owners, alongside coverage, skills, availability, leave, rest rules and roster approval permissions.
2
Compare a proposal with the current plan
Generate a candidate without automatically publishing it. Review assignments, blocked conflicts and unfilled shifts with the manager. Correct inputs or rule definitions through an authorised review.
3
Run a controlled review cycle
Approve a limited trial and follow an employee request from submission to manager decision and any roster revision. Compare request handling, planning effort, coverage and corrections before deciding whether to expand the scope.
What we would measure together
Manager time spent preparing, reviewing and revising the roster.
Required coverage achieved and shifts left unfilled with an explanation.
Availability, skill, rest and leave conflicts blocked or raised for review.
Number and reasons for manager edits and permitted overrides.
Preference fulfilment and unresolved trade-offs reviewed with the manager.
Time and manual work needed to approve and share a changed roster.
Request review time and clarity of pending, approved and declined status.
Keep the rules and the decisions explicit.
Who sets the rules, and how do preferences affect allocation?
The business's responsible HR and scheduling people provide and approve the team's rules. Mandatory constraints and preferences are separate; unmet preferences and coverage trade-offs stay visible for review. The pilot does not invent legal limits or promise that every preference can be met. Rule changes need an authorised review.
What happens when there are not enough eligible people?
Leave the shift visibly unfilled and explain the blocking requirements. A manager can review staffing needs, correct source records or consider eligible alternatives. The system must not conceal a gap by violating a mandatory rule or assuming someone is available.
What can employees do through self-service?
Employees can view the profile fields and roster information their role permits, submit availability or leave requests and see the decision status. A submitted request is not approved leave. Managers review requests under the agreed process before approved changes affect staffing inputs.
Can a manager change the proposed assignments?
Yes. Authorised managers review and adjust the plan before publishing it. Changes are checked against the rules and permitted overrides retain a reason. A mandatory rule cannot be bypassed silently; any change to the rule itself requires the agreed approval process.
Will this connect to our current HR or payroll system?
The systems, interfaces and permissions need checking. Agreed imports and reviewed exports are an alternative where a connection is unavailable. Payroll calculation or changes are outside the initial roster pilot unless separately scoped.
How are staff information and decisions handled?
Limit access to the staff profile, availability, skills and leave information needed by each role, and agree retention and correction responsibilities. The tool proposes rosters for human approval. It does not autonomously make hiring, dismissal, disciplinary or other adverse employment decisions.
Project scope
A proposed basic HR workspace with roster configuration and automatic allocation for a defined team and planning period. The initial scope covers authorised staff profiles and roles, permitted employee self-service, availability and leave requests, manager review and approval, and the approved inputs used for scheduling. Roster planning adds required coverage, configurable constraints and preferences, explained gaps and human approval before publication. Access, source ownership, retention, permitted overrides and supported connections would be agreed before a pilot. Payroll calculation and broader employment-process automation are outside the initial scope; the system does not invent legal limits or autonomously make adverse employment decisions.
Stage
Proposed pilot
Project by
Coding Reality
Scope and pricing
This is a proposed pilot. Scope and pricing depend on team size, staff-record and request workflows, permissions, scheduling rules and supported connections. No fixed price, launch date, guaranteed coverage or measured saving is being offered.
Where do staff requests and rosters take the most work?
Tell us about the team, request approvals and planning process you want to improve. Help shape a focused HR and roster pilot; expressing interest is non-binding.