The week is set. Your team sees it right away.

How it works in the app

You open the rota in the company account. The week runs from Monday to Sunday, in the time zone of the location, not in the time zone of the phone. With exactly one active location, the current week opens. With several locations, you choose the location and the week.

Each location has its own week. Several locations remain one company account. There is no extra charge per location. The plan depends on the number of active staff.

You create the shift in the grid. The fields are day, start, end, position and person. The end may fall on the next day. The published shift then shows that it ends on the following day.

In the person field, you can leave the shift open, with nobody assigned yet, or choose a person. The list separates people who match the position from other people. There is also a unit field, with an option for no unit. Staff see a shift in the department rota only if it has a unit.

If the start or end falls in an hour that occurs twice because of the clock change, the form asks you to choose. The legend asks you to choose the repeated time at the clock change. A time that does not exist on that day cannot be saved.

Shifts are created as a draft. Staff see them only after publishing. If the week is still empty, you can copy the previous week as a starting point. The copied version stays a draft.

As long as there is a planning conflict, the week cannot be published. Overlaps can show up as such a conflict.

Day off is a planned day off in the grid, with 0 hours. An empty cell stays unplanned. A day off is not placed over a shift that runs into the next day. In the display, an absence takes priority over a day off.

When the draft is ready, you tap the button to publish the week. From then on, this version applies to the team. A later change stays a draft until you publish again. Until then, the team sees the last published version.

Under "My shifts", every person sees their own shifts from the current published version, not from the draft. Each shift shows start and end, the location, the position, the planned minutes and the time zone of the location.

The same view shows the published, assigned shifts of the department the person belongs to on that day. It shows person, position, department and location. It does not show absence, availability, staff number, contact details or any permission of another person. Without a department assignment, this list stays empty.

Time tracking: clock-in, break, clock-out

Time tracking is called "My time". It shows only your own attendance. No role and no permission opens a view of another person there. Anyone without their own employee record does not record time there.

When you clock in, you choose the location. The time is recorded by the server when you submit. There is no field for entering a time by hand in this step. The confirmation shows the recorded time.

After that, you tap "Start break" and "End break". A session can have more than one break. At the end, you tap "Clock out". If a break is still running, you end it first, or you use "End break and clock out".

The history shows your own sessions from the last 30 days. For each session, you see clock-in, clock-out, every break, the attendance and the break total. Attendance is the time from clock-in to clock-out. The breaks are shown as a total next to it. The view does not subtract the breaks from the attendance and does not show an hours balance.

If the recorded times contradict each other, the session shows "inconsistent", and no duration is shown.

After clocking in, the status is "clocked in". During a break, it is "on break". The app does not save a second clock-in while an attendance is open. Nor does it save a second break while a break is open.

"My shifts" shows published shifts for 28 days, from the Monday of the selected week. There are buttons for earlier weeks and later weeks.

You set a day off for one day or for several days of a person. There is a button to enter it as a day off. You remove it with the button to remove the day off.

Absence in the weekly grid

You make the request under "My absences": type, first day, last day. The request shows "Requested" with date and time. The decision is shown with date and time. Types, approval and documents are described on the page Staff management.

The absence appears in the weekly grid only once it is approved. The marker says absent. Type and reason are not shown next to it. A request with the status requested does not block planning.

The marker is seen by people who may plan the week and may read staff data at the location. It applies to days that have not yet fully passed. In "My shifts", the department list shows no absence. Your own shift can show a note that it overlaps with your own approved absence. This note does not show the reason either.

What the app does when you save

After saving, the confirmation says "Saved" and gives the recorded time as server time. A second clock-in while an attendance is open stores nothing. Nor does a second break while a break is open. The app stores a clock-out during an open break only after "End break" or via "End break and clock out".

If the status has changed in the meantime, for example on another device, the submitted action changes nothing. The page shows the current status.

Several ended breaks of a session are listed separately in the history. From the second break on, the lines are numbered, "Break 1", "Break 2".

If no session of yours is recorded in the period, the history is empty. That is an empty state, not a missing permission.

Every publication stays in the list. It shows the version, whether it is the current one, the number of assigned shifts and the number of open shifts.

Who sees what

The words owner, head chef, shift lead and staff describe the business. A job position grants no permission in mnjam.mnjam. You decide in the company account which areas and locations a person sees.

The owner runs the company account and books the plan in the app under Profile, then Plan. Planning the week, reading staff data and deciding on absences are separate permissions and can go to other people. A permission at one location does not already apply to the next.

Staff see their own published shifts, record their own attendance and make their own absence requests, if they have an active employee record. They do not decide on their own request.

Who it suits

In a restaurant, you create lunch and dinner as shifts in the same week, with start and end. After publishing, a person sees their own shift, even if they did not see the notice board at lunchtime. You set the kitchen's day off as a day off.

In a hotel, you enter a night shift so that the end falls on the following day. Each property you run as a location has its own week. Approved annual leave shows as absent for people who plan, without the reason.

In canteens and contract catering, the week stays Monday to Sunday. You request annual leave as whole days. Only the approval puts absent into the grid.

In catering, you plan jobs that belong to a location as shifts of that location.

In a bar, shifts often end on the following day. You record clock-in, break and clock-out in the browser. The break is "Start break" and "End break", not a note on a slip of paper.

How it fits together

The employee record, documents and the decision on absences are on Staff management. The rota shows the approved result as absent.

Locations and invitations are on Company account and locations.

Tasks with person, location and due date are under Task planning. A task is not a shift. Readings with their time are under Temperature checks. The overview of all areas is on Features.

Plan

Rota, days off in the grid, time tracking and absences are included in Standard and Premium. They are not included in the free account.

Standard covers up to 20 active staff per business, Premium up to 50. The owner does not count towards this. More than 50 active staff is the Custom offer via Contact. The prices are on the Plans page.

Sign up for free

What this feature does not do

Time tracking has no hours balance and no assessment of overtime. It shows attendance from clock-in to clock-out and the break total next to it.

The grid shows no reason for an absence and no request that has not yet been approved. Time tracking shows no one else's attendance.

mnjam.mnjam does not replace a till or accounting. A hardware time clock is not included.

Questions

Frequently asked questions

When does the team see the week?

After publishing. Before that, the week is a draft. After a change, the team sees the last published version until you publish the new one.

What does day off mean?

A planned day off with 0 hours. An empty cell is unplanned. An approved absence is shown as absent in the grid and takes priority in the display.

Do you enter the time yourself?

No. The time is recorded by the server when you submit. There is no time field in this step.

What is in the history?

Your own sessions from the last 30 days, with clock-in, clock-out, every break, the attendance from clock-in to clock-out and the break total.

Do managers see the recorded times of others?

Not in "My time". The page shows only your own attendance.

When does an absence appear in the grid?

When it is approved, as absent, without type and without reason, for people with the permission to plan and the permission to read staff data at the location. A request that is only requested does not appear there.

Does the rota work on a phone?

Yes. You use mnjam.mnjam in the browser, on your phone too.

What does the rota software cost?

Rota, time tracking and absences are included from the Standard plan. You can find prices on the Plans page.