Overtime, Night Premium and Meal Penalties for Event Crews: A Practical Guide

Live event labor is not paid like retail labor, and the gap between the two is where production companies quietly lose margin. A crew that works from 06:00 Saturday to 02:00 Sunday can touch straight time, overtime, double time, a night premium window and a missed meal penalty in a single call. If those rules live in someone's head and get applied by hand on Monday, they get applied inconsistently.

This is a practical guide to the rules that actually come up on a production dock, and how to set them up once so they apply themselves.

What pay rules apply to event crews?

The five that come up on almost every show:

Daily overtime. Most production agreements pay a multiplier after a set number of hours in a single day, commonly eight or ten, rather than after forty in a week. This is the biggest difference from retail scheduling software, which is almost always built around a weekly threshold. A crew member on a twelve-hour load-in has earned overtime that day regardless of whether they work again that week.

Double time. A second, higher threshold, often at twelve hours, sometimes called golden time. Not every company uses it. If yours does, it needs to be configurable separately from the first threshold.

Night premium. A multiplier or flat uplift applied to hours worked inside a defined window, typically something like midnight to 06:00. It exists because a 04:00 truck unload is harder to staff and harder on the body. The window is a company or agreement decision, not a legal constant.

Meal breaks and meal penalties. An unpaid break of a set length, due after a set number of continuous hours. If the break is missed, shortened or pushed past its window, a penalty is owed. This is the rule most often forgotten in the moment and most often disputed afterwards.

Turnaround. The minimum rest between the end of one call and the start of the next. A crew that wraps at 02:00 and is called for 08:00 has had six hours, which many agreements treat as a violation requiring premium pay. This one is a scheduling constraint as much as a payroll rule: the time to catch it is when you are building Sunday, not when you are running payroll.

Minimum call also belongs on the list. Most companies guarantee a minimum number of hours for showing up, commonly four, so a two-hour strike still pays four.

A worked example

One technician, one Saturday, using common values. Overtime after 8 at 1.5x, double time after 12 at 2x, night premium 00:00 to 06:00 at a 1.15x uplift, unpaid 30 minute meal due after 5 hours.

Call at 06:00. Meal taken 13:00 to 13:30. Wrap at 02:00 Sunday.

Total on the clock: 20 hours, 19.5 paid after the meal deduction. Four separate rate bases in one shift. Now do that for twenty-six people across three sites, by hand, on a Monday, and you understand why production payroll weeks disappear.

Note what happens if the meal had been missed. The 30 minutes stays paid and a penalty is added, which changes both the hours and the cost, and nobody remembers it three days later unless something recorded it at the time.

How do you keep this from becoming a manual reconciliation?

Set the rules once, at the company level. Overtime threshold and multiplier, double time threshold, night premium window, meal break length and trigger, minimum call. These are company policy. They should be entered in one place and then applied to every time card automatically.

Print them on the call sheet. If the crew had the rules in hand before the first hour, disputes mostly do not happen. This costs nothing and it is the highest-return thing in this article.

Capture punches at the time, not at the end. A clock-in at 06:02 recorded at 06:02 is evidence. A crew head reconstructing the day at 02:00 from memory is not, and the reconstruction always drifts in one direction.

Make the exception visible while the day is running. A supervisor who can see at 12:30 that a meal window closes in thirty minutes can send people to eat. Finding out on Monday that four people missed a meal is just a bill.

Approve, then export. Somebody with authority reviews the week, fixes the two cards that need fixing, approves, and the file goes to payroll with the rates already attached per role. That review should take minutes, not a day.

Tinds implements exactly this set: daily overtime threshold and multiplier, double time, a night premium window with its own start and end, meal break length and deduction, all configured in Settings, printed on every call sheet and applied to every timesheet before export.

Rates live on the role, not the person

This is the detail that generic scheduling software gets wrong most often, and it is worth stating plainly.

The same technician can be an Electrician at one rate on Tuesday and a Crew Head at a different rate on Friday. In retail, a person has a wage. In production, a person has a set of qualifications and earns whatever the role they are filling pays on that call.

Any system that attaches a single hourly rate to an employee record will produce wrong numbers the first time someone steps up. The rate has to attach to the assignment, and the timesheet has to know which role was worked on which day.

Frequently asked questions

Is daily overtime a legal requirement?
It depends on the jurisdiction. California, for example, has daily overtime and meal break law that applies regardless of what an agreement says. Many states do not, and daily overtime is instead a matter of a union agreement or company policy. Check your own jurisdictions, and configure by rule rather than assuming one setting covers every market you work in. This article is operational guidance, not legal advice.

What is a meal penalty?
A payment owed when a required meal break is not provided within its window, or is cut short. The amount and the trigger vary by agreement. The practical point is that it has to be detected on the day, from actual punch times, or it will be missed.

How is a night premium different from overtime?
Overtime depends on how long someone has worked. Night premium depends on what time of day the hours fall. They stack: an hour at 01:00 on hour fourteen of a call can be both.

What is turnaround and why does scheduling software need to know?
Turnaround is the rest between calls. Software needs it because the violation is created when you build the schedule, not when you run payroll. A warning at the moment you assign someone to an 08:00 after a 02:00 wrap prevents the cost entirely.

Related reading: From timesheet to payroll for event labor, How to write a call sheet for a live event, Live production crew glossary.