Staff scheduling · Mishmarotix

Shifts, availability and team requests in one place. Create shifts by date, time, site and role, then assign employees. Review the draft before publishing

• جدول واحد يراه الجميع بدل جدول بيانات ومجموعة محادثة.
• توفر مُقدَّم مسبقاً، فلا يُجدول أحد في يوم لا يستطيع العمل فيه.
• تبادل ورديات يبدأ من الموظف وينتهي بموافقة المدير.
• نمط ورديات جاهز لكل مجال، قابل للتعديل.
• عدة فروع وأقسام، كل قسم يرى نفسه فقط.

Shifts, availability and team requests in one place, with conflicts flagged before the schedule reaches anyone.

Build the schedule

Schedules are built a week at a time. Create a shift with a date, start and end time, site and role, then assign someone to it. Each shift can carry a note and a task list, be marked as on-call, or be locked so it cannot be changed by accident.

While it is a draft only managers can see it. The team sees the schedule when it is published, so you can build, move things and change your mind without every adjustment reaching somebody as a notification.

Availability and time off

Employees submit availability for the week: which days and which parts of the day they can work, a free-text note, and the most shifts they are asking to work that week.

Time off is requested separately, with a type, a date range and a reason. A manager approves or declines and can attach a note, and the request keeps who decided and when.

What is checked before you publish

As you assign, the schedule is checked against what is already known and warns about an overlap with another shift, too little rest between shifts, someone who said they were unavailable, leave that has already been approved, a missing qualification the role requires, and going over the weekly hours cap. Night shifts are flagged separately.

The warnings do not block the manager. They are shown so the decision is made knowingly, rather than discovered later on a payslip.

Qualifications and expiry

Each employee can hold qualifications with an expiry date, and a role can require one. Qualifications about to lapse are flagged in advance, so it is not discovered on the day somebody needs to be scheduled.

Changes after publishing

A schedule is published, and then life happens. An employee can ask to swap with a colleague, or claim a shift nobody took. Every request goes for approval according to permissions, and keeps who asked, from whom to whom, the reason, who decided and when.

So “who approved this?” always has an answer, including two months later.

Sites, departments and roles

The business is described the way it is actually arranged: sites, the departments inside them, and roles. An employee can belong to more than one site and hold more than one role, and the schedule is built per department.

Who it is for

Shift teams in restaurants, support desks, security, clinics, warehouses, retail, manufacturing and driving schools. Configure departments, roles and shifts to match your business, so the system fits the structure you already have rather than asking it to change.