Work Schedule

iTefteri

You build the weekly shift schedule by dragging and dropping shifts onto color-coded departments — kitchen, floor, register. You see coverage and peak hours, so you're never left short-staffed. No Excel and no "it's on WhatsApp".

  • Drag-drop shifts onto color-coded departments (kitchen, floor, register)
  • Coverage and peak hours, so you're never left short-staffed
  • Types: work / day off / leave
  • Copy one week's pattern to many future weeks with one click
  • You work in a draft and publish it to the team
You log in from app.itefteri.gr. Every store has its own URL.
iTefteri weekly shift schedule

Where it belongs

A quick note about the plan.

Plan: ProModule● Live

What it gives you

A short description of the module, the way you use it in practice.

  • You drag and drop shifts onto color-coded departments — e.g. kitchen, floor, register — in a clean timeline.
  • You see coverage and peak hours per department and overall, so you're never left short-staffed.
  • You record shift types: work, day off, leave, so it's clear who's working and who's away.
  • You work in a draft, you publish it (published) to the team when it's ready, and copy one week's pattern to many future weeks with one click.
  • You print a weekly board for the counter and get totals per employee.

Weekly builder with shifts

You drag shifts onto the timeline — a clear picture without complicated forms.

  • Shift types — Work, Day off, Leave, Non-working.
  • Shift split — e.g. a break at 19:30 when the shift changes.
  • Copy and quick delete for shifts.
  • Planner step — 15, 30 or 60 minutes, depending on how detailed you want the schedule.
  • Autosave while you work, with a visible save indicator.
  • Pinned rows for employees and day headers, for easier navigation with a large team.
  • Compact mode for a quick scan of the whole picture.

Departments & coverage

You see when you're short-staffed and where you need to add people.

  • Departments — "Kitchen", "Service", "Register", each with its own colors and order.
  • Opening hours vs shift range — the first is when customers see you open, the second is when you can schedule staff.
  • Peak hours — you define peak windows (e.g. 13:00–15:30) and see whether you have enough staff there.
  • A second peak for businesses with two separate peaks (lunch/evening).
  • Coverage view per department and overall, in half-hour steps.
  • An indicator for a closed store on the schedule, when applicable.

Draft → Publish & copying weeks

You experiment quietly before the team sees it.

  • Statuses — Draft (private), Published (visible to the team), Empty.
  • Publish with one click when it's ready, and back to draft if needed.
  • Copying weeks — you build one "typical week" and copy it to as many future weeks as you need.
  • Copy the previous day within the same week, with one click.
  • Clear a day or an entire week when you want to start from scratch.

Printing & totals

A clean sheet for the counter and clear numbers for the owner.

  • A preview before printing, so you see the result.
  • Weekly board printout — a clean A4 layout, with no clutter.
  • Weekly totals per employee — scheduled hours and days.
  • Contract comparison — the difference in hours and days, so unpaid or excess hours never slip "past the eye".
  • Holidays & events on the board (e.g. public holidays), so you can adjust accordingly.

How you use it

A simple usage flow that doesn't wear you out.

  1. You set up departments (once, in the settings).
  2. You define opening hours, shift range and peak hours.
  3. You drag shifts onto employees for the week — the builder helps you.
  4. You check coverage per department and overall.
  5. You publish, print the weekly board and send/post it to the team.
  6. You copy the week into future ones, when the workflow allows it.

Holidays & events on the days

You plan knowing what's happening that week.

  • The Calendar's holidays and events appear on the corresponding days of the schedule.
  • So you see in advance when you'll need more staff (e.g. an event) or when the store is closed (a holiday).
  • You adjust the shifts accordingly, without checking a second place.

Which modules it pairs well with

Use them together and you get a clearer picture.

  • Work Hours — so the schedule ties in with the actual hours each person worked.
  • Employee Payments — so you have payment history right next to the schedule.
  • Calendar — so appointments/reservations show next to the shift schedule.

Use cases where it shines

See the use case pages where we recommend it.

Frequently asked questions

No. The Work Schedule is the planning of shifts before the week starts. Work Hours is the record of the actual hours worked. The two modules work together: you plan with one, you record with the other.

Yes. You build a model week and copy it to future ones. Then you only make the corrections that are needed.

You define peak windows (e.g. 13:00–15:30) and the system shows how many people cover each department during those hours. If a department is "empty" at peak time, you see it right away.

A weekly board on A4, with shifts per day and per employee. A clean layout to pin at the counter or send to the team.

It depends on the roles. Owner and Manager build and publish. Staff see what you've published, not the drafts.

Yes. The Calendar's holidays and events appear on the corresponding days, so you can adjust the shifts based on what's happening that week.

Next step

If you like, try it out and then we can tailor it to your specific use.

For the full picture, also see the Modules.