Skip to main content
GullySystem

Rostering cooks, packers and counter staff

A sweet shop runs on people who start before dawn and stay late through festival weeks. This feature rosters cooks, packers and counter staff, shows who is on which shift and notes overtime when a rush pushes hours up. Managers read the roster beside the order book, so the shop is staffed for the load it expects.

What a shift roster holds for each person

Think of a grid of people against days and shifts. Each cell says who works, in which role and at which outlet. Overtime is noted beside the shift it belongs to. Extra festival hours are on record. Nobody keeps this in a head.

Staff list by role

Each person is entered with a name and a role, such as cook, packer or counter staff. A person who covers two jobs is shown under both. The list is the base for every shift. Changes are made once.

Shift start, end and place

A shift has a start, an end and a place, such as the central kitchen or a named outlet. Cooking shifts begin before the shop opens. Counter shifts follow the opening hours. Packers sit between the two.

Roster for the week

It is laid out for the week ahead, with days off marked. A gap, such as a counter with no one on Saturday, shows as an empty cell. Filling it comes before the week starts.

Overtime noted for festival weeks

When a festival week pushes hours up, the extra time is noted against the person and the shift. It carries the date and a reason, such as a wedding order. Pay is worked out elsewhere.

Staffing a festival week from Monday to Saturday

A festival week asks the same people to do more. Cooks start earlier, packers stay later and the counter faces a longer queue. Here the shop decides who covers what. Strain shows when cover is missing. Decide early, and name the people who will carry the heaviest days.

Reading the order book before rostering

First, the festival calendar and the order book are opened. The days with the heaviest load need extra cooks and packers. Rostering is built around them. Quiet days can spare a hand. Moving cover beats just adding it.

Putting packers on the late shift

Gift box packing peaks the day before pickup. A late packing shift is added, and a named person covers it. The packers know their hours ahead, not on the day. Short notice causes quarrels and no-shows.

Overtime noted at close

At close on a heavy day, the manager notes which cooks and counter staff stayed late. It sits beside their shift. Hours are already written down when pay is prepared. Nobody argues from memory. Dates and reasons are kept.

A cook falls sick

A cook calls in sick on the morning of a big pickup. A look at the roster shows who else can cook. A shift is moved. The change is visible to the whole team. The kitchen is not left guessing.

Cooks, packers and counter staff: who sees the roster

A roster is a shared page. Everyone reads their own line, and the manager reads the whole grid. Cover and overtime are the owner’s reading. The head cook reads who is free for the next batch.

For the head cook scheduling the kitchen

The head cook sees which cooks and helpers are on each shift. Batches are built around those hands. When the roster is thin, the cook asks the manager for cover or trims the plan. Staffing becomes part of the plan.

For counter staff reading their own shifts

Counter staff see their own shifts, the outlet they are placed at and any overtime noted. A change to a shift is visible to them. Questions about hours start from one page. No one relies on a hand-written chit.

For shop managers building the roster

Shop managers assemble the roster, fill gaps and note overtime. They compare cover with the festival calendar and the order book. A heavy day with a thin team is spotted early. That is a desk decision. Nobody makes it in a rush.

For owners reading cover and overtime

Owners read the number of people on each shift at every outlet. Overtime used in a festival week is read beside it. The figures guide next year’s hiring. Wages are the accountant’s area. Cover becomes a number, not an impression.

Shift patterns and overtime rules to agree

Rosters reflect choices the owner has already made about hours and fairness. Writing them into the shift pattern avoids quarrels during festival weeks. Sit down with the head cook first. Managers join too.

Cooking shift start against opening time

Decide how early the first cooking shift begins before opening. Milk sweets need hours on the stove. Dry sweets can be made the evening before. The answer sets when the first cook arrives. Cooks should hear it at hiring.

Festival weeks and the extra shift

Decide which weeks count as festival weeks. Fix how an extra shift is offered and who is asked first. State whether overtime is optional or expected. Afterwards it records the choice. Surprise breeds resentment. A fair rule is known in advance.

What the overtime note must say

Overtime needs a date, a person and a reason. Decide who writes the note and who agrees it. A manager’s initial is one choice. Owner agreement for long hours is another. Pay rules belong with your accountant.

Cover when a packer or cook is absent

Decide who covers a gap in each role. A packer may stand in at the counter. A counter hand may lend a hand at packing. List who may cover for whom. It then shows real alternatives, not hopes.

Where the roster meets orders and the plan

Staffing does not stand alone. Staffing makes sense only against the work. The festival orders and the kitchen plan are read beside it to see where hands are needed. An outlet needs people to receive trays, so branches read it too. Owner reports put cover beside sales.

  • Festival and wedding advance orders show the heavy days
  • Kitchen production plan shows the cooking load per shift
  • Gift boxes and assortments show packing hours needed
  • Branches and central kitchen need staff to receive trays
  • Counter weighing and billing shows busy hours at the till

Limits of staff and shift planning

Who works and when is recorded, and overtime is noted. It does not work out wages, track leave balances or apply labour law. Pay, deductions and legal rules for hours and rest stay with the owner and an adviser. A shop with a handful of staff on fixed hours may find a printed timetable enough. Start there if the team is small.

FAQ

Frequently asked questions

Can the roster show overtime for festival weeks?

Yes, extra hours are noted against a person and a shift, with a date and a reason such as a wedding order. That note is a record. Your accountant works out how overtime is paid. The notes are read together.

Does it handle both kitchen and counter staff?

Yes, the roster covers cooks, packers and counter staff, each with their own shifts and places. A person who works two roles is shown under both. One grid covers the whole shop. Nobody is left off the page.

Can we plan the roster before a festival?

Yes, the manager can read the festival calendar and the order book, then build the roster around the heavy days. Cover is fixed before the rush. Extra hands are planned, not begged for on the day.

Does it work out wages or salaries?

No. What it records is shifts and overtime notes. Your accountant or payroll method calculates wages, deductions and statutory payments. The notes support that work. They do not replace it. Pay is outside this feature’s job. Say so early in set-up.

How do staff see their own shifts?

Each person’s shifts, outlet and overtime notes sit on the roster page. Staff read their own line. How the roster is shared in the shop is the manager’s decision. Questions about hours start from one page for everyone.

Where it fits

How this feature fits the system.

Sweet Shop Management Software: the parts that work with this feature, the trades that use it and the ways to put it in place.

Counter weighing and billing

Weight, rate, packing and tax meet on one bill, printed at the counter in a festival queue.

Point of Sale Billing

Festival and wedding advance orders

Bulk orders keep their date, advance and balance, and the kitchen sees what is due each day.

Order Management

Kitchen production plan

Trays to cook are set from sales history, the order book and festival dates.

Production Planning
Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements