- Problem: manually collecting requests by SMS and paper takes days, and every change wrecks the whole table.
- Solution: structure, rules and capacities are defined once; requests register inside the system and are checked against rules automatically.
- Two methods: suggested shifts (priority logging + system arrangement) and preferred shifts (picking from allowed options, like seat selection).
- Trust guarantee: the system never violates rules to fill the table; it reports uncompletable shifts and explains arrangement reasons.
What is shift management and why is it vital?
Shift management is the process of planning, rule-based arrangement, conflict resolution and monitoring of shift workers' hours. Axis Puls is a web system for planning, arranging, managing and controlling shifts of large organizations — especially hospitals and care centers — and is not limited to nurses: physicians, security, guards, services and administrative shift workers are managed with the same system.
Traditionally, requests gather by paper, SMS, messenger or calls; the head nurse pieces them together, checks rules by hand, and with every leave or swap several table sections are corrected again. As headcount and rules grow, that same process can take days. Axis Puls turns this path into a structured process: define rules ← register requests ← automatic checks ← arrange ← constraint control ← approve ← manage changes and report.
Organization structure and rule & capacity definition
The system's most important concept is this: “a rule is defined once, but executed every month.” Managers never re-check every rule monthly from scratch.
🏥 Define organization & wards
A hospital is defined; then each ward (like ICU) is built with its own rules and conditions.
👥 Roles
Nurse, physician, guard, services and security; each ward has the roles it needs.
🕒 Shifts
A shift can be defined for one role or for the whole ward.
📏 Capacity & limits
Minimum and maximum headcount, role- and gender-based capacity, and daily, weekly and monthly limits.
So the system doesn't just know “this person must have a shift”; it knows who, in which ward, in which role, at what time, under which conditions and in what capacity can stand in a shift. Staff membership also happens with each ward's dedicated code: staff enter the code, pick a role, and managers review, correct if needed, then approve.
Suggested vs. preferred shifts — what's the difference?
Method one: suggested shifts
Staff pick the days and shifts they want and mark request priority (e.g., priority 1: highly desirable). Requests gather in the system, the head nurse sees them, and during arrangement the system checks requests against rules and capacities. Full details in the article Suggested shifts.
Method two: preferred shifts
Staff pick directly from shifts selectable for them under the rules — like seat selection in a ticketing system. If capacity exists it is selectable, and completed capacity deactivates for newcomers. The full comparison is in the article Preferred shifts.
In both methods, organization rules outrank individual choice. In suggested mode staff say “I prefer these shifts”, and in preferred mode “from the allowed options, I pick this one”.
Smart arrangement; no long waits, no rule violations
The arrangement engine places requests into the plan under rules and capacities, and can order requests by shift-capacity completion. With the re-arrange option managers build a fresh combination. As requests arrive, plan status is live visible: how many registered, how much capacity completed, which shifts still have room.
Two trust-building principles: first, if no suitable person can be placed under the conditions, instead of ignoring rules the system announces “this shift cannot be completed under the defined conditions”. Second, wherever logic is explainable, the system states why a person was or wasn't placed in a shift and which constraint blocked them; so managers never rely blindly on the final table.
Leave, shift transfer and automatic re-planning
Staff pick leave from inside their own shift list; the system identifies and suggests people who, under rules, limits, capacity, role and shift status, can take it, and after approval the plan is rewritten to the new state. In transfers too, staff or the head nurse create requests, eligible people are identified, and after acceptance the plan updates. The step-by-step guide is in the article Leave and shift transfer management.
Fairness, reporting, access, cartable and signing
The system can compute fairness in shift distribution from shifts and staff priorities so managers see distribution more precisely; it is a decision tool, not a judgment of individuals. Every management level sees reports matching its access (e.g., hospital director ← matron ← head nurse ← staff, adjustable). The cartable sends ready shift lists to managers for review and signing, and the signing module uses security mechanisms for authentication. Internal notifications and (when active) SMS, plus security layers — mobile login, access levels, activity logs, periodic backups and IP control — keep information with authorized people. Details in the article Fairness, access and reporting.
- A table only says who works where and when.
- Axis Puls manages the whole chain: structure ← rules ← roles ← shifts ← staff registration ← request intake ← limit checks ← arrangement ← approval ← leave ← transfer ← re-planning ← reporting ← signing.
The core message for head nurses, matrons and hospital directors
For head nurses: management isn't removed; repetitive calculation work shrinks. Head nurses still set rules, review plans and make final decisions, but move from “manual table-building” closer to “plan management and control”. For matrons: ward planning and head-nurse activity are managed in one visible, reportable structure. For hospital directors: instead of scattered processes, you get one integrated structure for defining rules, planning, changes and reports.
Rollout, trial period and pricing model
Starting covers structure discovery, defining the hospital and wards, rules and limits, roles, shifts and capacities, adding staff, user training, then trial use. New organizations use the system two months on trial under real conditions and compare metrics like plan-prep time, change counts and head-nurse experience. Under the current model, capacity up to 75 people: 2,500,000 Toman monthly and 19,000,000 Toman yearly; other capacities are priced per contract. Full details in the article Rollout, trial and pricing.
To know the system deeper read: Suggested shifts, Preferred shifts, Leave & transfer, Fairness & access, Rollout & pricing and Nurse shift management.
❓ FAQs about shift management (FAQ)
Define rules once; manage every month
Try two months in your own organization's real conditions, then decide.
Start trial period