Project description
Our duty roster is a laminated sheet on the corridor wall. A supervisor draws the month in marker, and every change after that is an erasure on top of an erasure. By the twentieth day nobody can say for certain who was moved where, the accounting office collects the numbers by phone, and the monthly timesheet is assembled by hand out of two notebooks and somebody's memory. When a person is ill, the shift is covered by whoever answers the call first, and that arrangement exists nowhere except in a chat.
I want the whole thing moved into a web application. A planner builds next month's grid for a department, sees at once who is short of hours and who is well over the norm, and publishes it. An employee opens the same grid on a phone, asks a colleague to take a shift, and the swap becomes real only after the head of the department confirms it — the request, the answer and the time of both are kept. Vacations, sick leave and other absences live in the same calendar, so a planner never puts a person on a day they cannot work. At the end of the month the application assembles the timesheet itself, shows the overtime summary, and prepares an export file that our accountants can load without retyping a single figure.
Three points are conditions rather than wishes. The system counts by the rules that our HR service approves, and disputed cases of overtime and night hours are decided by HR and not by the program: where a rule is ambiguous, the application must show the case and wait for a human decision instead of quietly rounding it. Sick leave records are visible only to HR and to the head of the department, and diagnoses are not stored at all — only the fact of absence and its dates. The shift check-in marks an arrival for the roster and must not turn into constant tracking of an employee: no location history, no stopwatch on breaks, no background monitoring of any kind.
What we need built:
— monthly shift planning for a department, with templates and hour norms;
— shift swap requests with confirmation by the head of the department;
— vacation, sick leave and absence records in one calendar;
— automatic monthly timesheet with an overtime summary;
— an export file for the accounting office;
— reminders before a shift begins;
— a department calendar visible to the whole team;
— a mobile view for employees: roster, requests, check-in.
I want the whole thing moved into a web application. A planner builds next month's grid for a department, sees at once who is short of hours and who is well over the norm, and publishes it. An employee opens the same grid on a phone, asks a colleague to take a shift, and the swap becomes real only after the head of the department confirms it — the request, the answer and the time of both are kept. Vacations, sick leave and other absences live in the same calendar, so a planner never puts a person on a day they cannot work. At the end of the month the application assembles the timesheet itself, shows the overtime summary, and prepares an export file that our accountants can load without retyping a single figure.
Three points are conditions rather than wishes. The system counts by the rules that our HR service approves, and disputed cases of overtime and night hours are decided by HR and not by the program: where a rule is ambiguous, the application must show the case and wait for a human decision instead of quietly rounding it. Sick leave records are visible only to HR and to the head of the department, and diagnoses are not stored at all — only the fact of absence and its dates. The shift check-in marks an arrival for the roster and must not turn into constant tracking of an employee: no location history, no stopwatch on breaks, no background monitoring of any kind.
What we need built:
— monthly shift planning for a department, with templates and hour norms;
— shift swap requests with confirmation by the head of the department;
— vacation, sick leave and absence records in one calendar;
— automatic monthly timesheet with an overtime summary;
— an export file for the accounting office;
— reminders before a shift begins;
— a department calendar visible to the whole team;
— a mobile view for employees: roster, requests, check-in.
Web programming Cash, Bank transfer
