Time tracking and holiday planning: Separating absence from work in the same period

When monthly reviews mix worked hours and approved absence in one conversation

In restaurant operations, I notice how quickly a monthly review turns into three different discussions at once. A team member remembers being away on holiday, I see a personal time tracking session at the start of the month, and a shift lead mentions an extra service shortly before the absence. If I treat all of that as one issue, the conversation becomes emotional and unclear. That is why my approach to time tracking and holiday planning always starts with separation. First I define the exact period we are talking about. Then I identify whether I am looking at an absence, a worked session, or the effect on the working time account.

With Bonzumo, I use three distinct levels for that discussion. I look at the recorded absence, the personal time tracking sessions with start and end, and the working time account as its own result layer. This helps me avoid treating approved leave like missing work or overlooking real work because holiday is nearby in the calendar. In practice, this structure calms the conversation. Instead of asking whether the whole month is wrong, I ask which entry type is in question and in which dates. That is the core of time tracking and holiday planning in my restaurant: keep absence and work visible at the same time, but never judge them as if they were the same thing.

The most common cause is simple: we discuss the same month, but not the same period

The biggest source of confusion is usually not a wrong entry but a blurred period. A holiday may begin on the twenty ninth of one month and end on the third of the next. In the meeting, the person remembers a full week away, while the month view only contains two or three of those days. If I do not define the reviewed period precisely, I compare a full memory with only a partial record. That makes time tracking and holiday planning feel contradictory even when the entries themselves are consistent. Many disputes disappear as soon as I ask one basic question: which exact dates belong to the month we are currently reviewing.

A second cause is that planning, actual work, and account balances get mixed up. A published schedule shows the planned assignment; actual working time is reviewed separately. The working time account is also not an explanation for a single day. It is the result of several recorded sessions, absences, and rules being considered together. So when someone asks why hours seem missing or too high, I do not begin with the total. I ask which session is meant, which absence overlaps the period, and whether the question belongs to the shift plan, the actual time record, or the account balance. That order keeps the discussion workable.

Case one: holiday overlaps the reviewed month and memory covers more than the report

When holiday overlaps the month we are reviewing, I never jump straight into totals. I start by marking the beginning and the end of the absence. Then I check which part actually falls inside the period under discussion. A broad statement like I was away for a week becomes a more useful operational question: which holiday days belong to this month, and which days belong to the previous or next month. This sounds simple, but it changes the whole tone of the meeting. In time tracking and holiday planning, people often remember the complete break, while my month review can only assess the slice that belongs to that month. Once we agree on the slice, the rest of the discussion becomes more factual.

In Bonzumo, the recorded absence gives me the fixed reference point, and I compare that with any personal time tracking sessions inside the same dates. If I find a session with a start and end on a holiday day, I do not assume an error immediately. I ask why it happened and whether the explanation is plausible. Someone may have finished a short closing duty before leave really began, or a session may have been left open by mistake. Every time correction, even when requested by an authorized person, still requires a check of the reason and the plausibility. That principle protects the team as much as it protects the record, because it prevents quick changes that later create bigger account questions.

Case two: an extra shift before leave is forgotten because the absence dominates the memory

A particularly sensitive situation comes up when someone takes an additional shift shortly before an absence. In the monthly talk, the holiday is what the person remembers first, so the extra shift from the day before can disappear from memory. Then the working time account looks too high at first glance, even though the additional hours come from a real service. I do not solve that by saying it probably balances out. I go through the days in order. I check which session exists, whether the assignment makes operational sense, and how it stands apart from the absence that followed. That day by day review takes discipline, but it prevents me from collapsing two separate events into one mistaken conclusion.

This is exactly where careful time tracking for restaurant staff becomes practical instead of theoretical. Not every extra hour is a problem, and the fact that work happened close to holiday does not make it suspicious on its own. In Bonzumo, I can review the personal time tracking session with its beginning and end separately from the recorded absence. If a supervisor asks for an adjustment because the extra shift was supposedly not approved, I still do not decide on authority alone. I need the operational reason and a plausibility check. Only then do I decide whether an exception should be handled or whether the recorded time should remain as it is. That keeps the review fair and traceable for everyone involved.

I discuss the working time account separately so single cases do not become broad judgments

I make a clear cut when we reach the working time account. I do not present it as proof that a holiday day or a shift was right or wrong. I treat it as the outcome of previously reviewed entries. That separation helps enormously in team meetings, because otherwise every question about one day turns into a general debate about fairness, trust, or missing recognition. My practical sequence is always the same. Which absence applies in the period. Which personal time tracking sessions belong to the same dates. What effect appears in the working time account after those two layers are reviewed. By asking those three questions in order, I keep each part understandable and open to verification without turning the conversation into a personal argument.

Bonzumo supports this way of working because working time accounts can have separate edit rights. That fits my operation well. Not every person should change the same things, and not every question should lead straight to an account adjustment. Shift leaders, office staff, and ownership each have different responsibilities, and roles and permissions help me reflect those responsibilities in the system. In practice that means a team member can see the relevant issue, a manager can review the exception context, and the appropriate person handles any account change. Even then, every requested time correction still needs a concrete reason and a plausibility check, including requests from someone who is fully authorized to raise the issue.

How I set up the Bonzumo workflow so the team asks the same questions in the same order

For daily operations, I set up the workflow so absences are maintained first, personal time tracking sessions are reviewed second, and only after that does the working time account become part of the conversation. When we discuss time tracking and holiday planning, I never start with the balance. I start with the calendar and the exact period. Then I look at session start and end times and mark the cases that really need attention. Only when that base is clear do I interpret what the account is showing. The process is not dramatic, but it prevents the same confusion from repeating itself every month. The team learns that not every surprising balance points to a missing holiday or a wrong shift record.

I also use roles and permissions so corrections do not come in from every direction without structure. One person can raise a question, another can review the exception reference, and the responsible role can decide what happens next. The shift plan remains its own layer, with draft and published status used only for planning. That matters because a published plan is still not the same thing as actually worked time. To support the routine, I make sure employee profiles are maintained and that relevant documents can be made available through the personal document inbox for reading or downloading where appropriate. Outside the system, I keep our meeting checklist simple so everyone knows which dates, reasons, and details to bring before we discuss a correction.

How I introduce the process to the team without turning it into a theory lesson

When I introduce this in the team, I do not begin with long policies. I begin with the three case questions that come up all the time. First, is the absence fully inside the reviewed period or only overlapping it. Second, is there a personal time tracking session before or during that period that needs explanation. Third, what effect appears in the working time account after those facts are separated. I rehearse this sequence first with shift leaders and office staff so monthly conversations sound consistent no matter who leads them. That makes time tracking and holiday planning easier to follow, because people hear the same logic each time instead of a different argument from each manager.

For the team, I keep the practical rule very concrete. If you raise a question, bring the date, the occasion, and your own recollection. If you request a correction, give the reason clearly and expect a plausibility review. If you want to discuss holiday and hours, do not speak about the whole month in a vague way when only a short section is actually affected. This creates fewer rushed assumptions and more reliable clarifications. In everyday restaurant life, that is exactly what I want from Bonzumo and from our internal process around it: absence and work in the same period should be discussed together, but always separated clearly enough that decisions stay understandable, fair, and operationally useful.