Open Shift Pickup Rules: First-Come, Seniority, or Lottery

If you only have time for one decision, make it this one: pick a single rule for who gets an open shift, write it down, and post it before the first shift goes up. First-come, first-served is the easiest to run. Seniority is the easiest to defend. A lottery is the easiest to call fair. Which one fits depends on how many people want your open shifts and how much a bad pickup can cost you, and the rest of this post walks through both.

Most of what ranks for this topic is software documentation, which tells you where to click. This is the other half: how to decide, what each model does to your team when it goes wrong, and which pickups quietly push someone past 40 hours.

What is an open shift pickup policy?

An open shift is a shift on the schedule with nobody assigned to it. It exists because someone called out, because demand went up, or because you published the week with a hole in it on purpose. A pickup policy is the rule for how that shift gets claimed.

Without a written rule, the rule is whoever the manager texts first. That works until two people notice the same shift went to the same person three weeks running. Then it is a fairness complaint, and "I just asked whoever was around" is a hard answer to defend.

A good policy answers five questions in plain language:

• Who is eligible to claim a shift (everyone, or only people qualified for the role and location)
• How long a shift stays open to claims before you close it
• What decides between two people who both want it
• What the manager checks before approving a claim
• What happens if nobody claims it

The three models below differ mainly on the third question.

How do first-come, seniority, and lottery pickups compare?

None of the three is the right answer in general. The right answer is the one that matches how your team actually behaves when a shift appears.

When does first-come, first-served work, and where does it break?

First-come is the default in most scheduling tools because it needs no judgment from the manager. Someone claims the shift, the manager approves it, and the shift is filled. For a same-day call-out where you need a body in 40 minutes, nothing is faster.

The failure mode is that it rewards availability to a phone, not reliability or need. The people who get the shifts are the ones who check the app most often. That is usually a handful of people, and it usually ends up the same handful. Everyone else learns that open shifts are not really open, and stops looking.

It also tends to produce the quiet overtime problem. The fastest claimant is often someone already scheduled for 36 or 38 hours, because they are the keenest to pick up more. First-come does not know that. You have to check it before you approve.

That is why Shift Amp has a manager approve each open shift claim instead of giving it to whoever taps first. Filling the shift is only part of the decision. The manager may know things the claim does not show, like a performance concern, and we wanted to keep a manager in the loop on every change.

If you run first-come, two guardrails help:

1. A short delay before claims count (say 15 minutes after the shift posts), so the winner is not just whoever was holding the phone
2. A manager check on projected weekly hours before approval, which is covered below

When does seniority make sense, and what are the legal edges?

Seniority is the most common answer in unionized workplaces and in healthcare, and it has a real advantage: everyone can see the rule and nobody has to argue about the draw. Longer-tenured staff get first call on the better shifts, which also serves as a retention lever.

The failure mode runs the other way. Newer employees, who often most need the hours, never get any. If your open shifts are mostly the awkward ones, such as closing shifts and holidays, seniority can push the least desirable shifts onto the most junior people, and that is fine only if everyone knows it going in.

There is also a legal edge worth knowing. Under Title VII, a bona fide seniority system gets protection that a manager's informal preference does not. The EEOC's compliance guidance describes a seniority system as one that allots rights and benefits according to length of employment, and says an unwritten system counts only if covered employees were told its terms and it is administered systematically and objectively. The same guidance says the protection does not cover differences that are the result of an intention to discriminate, and that making exceptions for some employees and not others falls outside it.

The practical read for a manager: if you use seniority, write the tenure rule down, apply it every time, and keep the record of who was senior to whom on each claim. A rule you bend for favorites is not a seniority system. It is a preference with a policy attached to it.

A union contract or state law can change this, so check yours.

How does a lottery work for open shifts?

A lottery fits when popular shifts attract a rush of claims at once, such as a Saturday that everyone wants or a holiday that pays a premium. You open a claim window (24 hours is common), collect everyone who raised a hand, and draw one name.

Its strength is that it removes the manager from the decision, which removes the accusation of favoritism. Its weakness is that a draw cannot see anything. It treats a person with three recent no-shows the same as your most dependable employee, so most teams add an eligibility gate first: only people in good standing and qualified for the role go into the draw.

A lottery also needs to be visible to be believed. Draw it where people can see it, log the result, and keep a short history. If staff suspect the draw is rigged, you are worse off than with a plain first-come rule, because now the unfairness is a secret.

One variant is worth considering for a mixed team: weight the draw so that anyone who has gone unselected in the last few windows gets an extra entry. It keeps the randomness and quietly fixes the "same people always win" problem.

What do predictive scheduling laws say about offering extra shifts?

In some cities, the allocation rule is partly written for you. If you operate in a place with a fair workweek law, extra hours often have to go to existing staff first, and sometimes by a stated process.

New York City's fast food rules are the most specific of the four. DCWP's guidance says employers must post a notice for three consecutive days where workers will see it, send the information electronically, and give workers three days to accept. If several workers at the location accept, the employer must prioritize those who meet the stated criteria, can use any criteria that are not discriminatory or otherwise unlawful, and must put those criteria in the posted notice. Workers at the location where the shifts are available come before workers from other locations. That is, in effect, a legally required written pickup policy.

Seattle's Secure Scheduling Ordinance has the same shape. The city's summary says covered employers must post notice of available hours for three days and offer them to qualified, current employees before hiring new ones, unless an exception applies. That summary page is not the ordinance, which is SMC 14.22, so read the code itself before you build policy on it.

Chicago's ordinance, in section 6-110-060 of the municipal code, says the employer shall first offer additional shifts to existing covered employees, and that whenever practicable the hours go first to part-time covered employees. The distribution system must not discriminate on protected characteristics. The section text does not set a posting window, so check the city's implementing rules before you rely on a specific one.

Oregon takes a different route. Its predictive scheduling law, covered by BOLI's worker page, applies to retail, hospitality, and food services employers with at least 500 employees worldwide. An employee can request in writing to be added to shifts, and employers may keep a voluntary standby list of people willing to work additional hours, provided those employees asked to be on it in writing and were told how the hours will be offered.

Two takeaways. First, if you are a small employer in one of these cities, you may be below the coverage threshold, so check coverage before you assume any of it applies to you. Second, even where it does not apply, the NYC model is a sensible template: a posted notice, a stated criterion, a fixed window. These laws change, so verify current text for your city and date.

How do you stop a pickup from creating overtime?

This is the part most policies skip, and it is where the real money is.

Under federal law, overtime is counted by the workweek. The Department of Labor's overtime fact sheet says covered employees must receive overtime pay for hours worked in excess of 40 in a workweek, and that averaging hours over two or more weeks is not permitted. The regulation on that point, 29 CFR 778.104, says the same thing from the other direction: an employee who works 30 hours one week and 50 the next is owed overtime in the second week even though the two weeks average 40.

Here is the worked example, with invented numbers so the arithmetic is easy to follow. A server earns $18 an hour and is scheduled for 36 hours. A coworker calls out of a Friday 8-hour shift. The server is first to claim it.

• Hours worked: 36 + 8 = 44
• Overtime hours: 4
• Straight-time pay on those 4 hours: 4 x $18 = $72
• Overtime pay on those 4 hours at time and a half ($27): 4 x $27 = $108
• Extra cost of letting this particular person take the shift: $36 for that week

Thirty-six dollars is not a disaster. The problem is that it repeats. If the same eager claimant picks up a shift every week, you are paying a premium on every one of them, and nobody chose to do that. It just happened because the policy was silent on weekly hours.

We see this most often in small businesses that still manage the schedule by hand rather than with dedicated scheduling software. Without a planned week, the gaps get filled by the same few "hero" employees, and the overtime builds up one helpful pickup at a time. This simple example also uses a flat $18 hourly rate. Bonuses and other pay can change the regular rate, so actual overtime pay is not always that tidy.

There is a second cost beyond pay. A study in CDC's NIOSH library, using a national longitudinal survey, found jobs with overtime schedules had a 61% higher injury hazard rate than jobs without, and working 12 or more hours a day was linked to a 37% increased hazard rate. That is a study of its own period and sample, not a prediction for your kitchen, but it is a reason to care about who is picking up the long days.

The guardrail is simple. Before you approve any claim, check the claimant's projected hours for the workweek, using your actual workweek definition. DOL's fact sheet notes the workweek is a fixed, recurring period that need not match the calendar week, so a Wednesday-to-Tuesday week means Monday's pickup counts toward a different total than Wednesday's. Then decide in advance what happens at the line:

• Hard stop: a claim that creates overtime is declined unless a manager approves it
• Soft stop: the claim goes through, but the manager sees a flag and chooses
• Pre-approved exception: certain roles or situations, such as a nurse covering a gap that would otherwise close a unit, are allowed

Whichever you choose, pay the overtime. A policy that says overtime must be pre-approved does not remove the obligation to pay for hours already worked. The DOL fact sheet says an employer's statement that overtime will not be paid unless pre-approved does not remove the right to pay for compensable overtime hours worked.

If your team has overtime rules already, link the two documents so they do not contradict each other. Our guides on setting an overtime policy and how to calculate overtime cover the mechanics.

What about rest between shifts and fatigue?

Weekly hours are not the only check. A pickup can also put someone on a closing shift one night and an opening shift the next morning, which some places treat as a premium-pay event.

Where it applies, the rule is concrete. Under Oregon's law, as BOLI describes it, an employer cannot schedule work during the first 10 hours after a previous day's shift ends unless the employee requests or agrees to it, and if the employee works inside that window the employer owes one and one-half times the regular rate for those hours. Seattle's summary describes time-and-a-half for hours between closing and opening shifts separated by less than 10 hours.

The detail that matters for pickups is the consent mechanism. In Oregon, an employee's own written request to pick up a shift is treated differently from an employer-imposed schedule change. So how you record the claim matters. A claim made by the employee, in writing, in the app, leaves a record. A phone call and a nod does not.

For the longer treatment of this, including cities and industries with their own rest rules, see our guide to minimum rest between shifts. Our post on predictive scheduling laws covers the notice and premium-pay side.

What are the right tie-breakers?

Even a clean first-come rule produces ties. Two people claim within the same minute. Three people have the same hire date. You need a rule for the tie before you need it.

Good tie-breakers are boring and checkable:

1. Fewer hours already scheduled this week, so the person with the most room gets it
2. Longer time since their last pickup, which rotates opportunities
3. Qualification for the role, if only one of the claimants is trained for the station
4. Draw by lot, as a final step so no manager has to choose

Avoid tie-breakers that depend on the manager's read of who "deserves" it. They are the ones that read as favoritism, and the ones that are hardest to defend when someone asks.

What is a copy-paste open shift pickup policy?

Edit the bracketed parts and add your own overtime rules. Treat it as a starting point for discussion: a union contract or a local scheduling law may require different terms.

Open shift pickup policy

Scope. This applies to any shift on the posted schedule that has no employee assigned. It applies to all [hourly employees / employees at the location where the shift is open] who are qualified for the role.

Posting. Open shifts are posted in [app or location] as soon as they are known. A shift stays open for claims for [24 hours / until X hours before the shift starts].

Who gets the shift. If one person claims it, they get it, subject to the checks below. If more than one person claims it within the claim window, the shift goes to [the first claim / the most senior claimant / a random draw among claimants]. Ties are resolved by (1) fewest hours already scheduled this week, then (2) the longest time since the person's last pickup, then (3) a random draw.

Checks before approval. A manager approves each claim after confirming that the employee is qualified, is not on a disciplinary hold, and has the required rest since their last shift ([10] hours).

Overtime. If a claim would take the employee past [40] hours in our workweek ([day] to [day]), the manager decides whether to approve it. Any hours worked past 40 are paid at the overtime rate regardless of whether the claim was approved in advance.

Unclaimed shifts. If nobody claims an open shift [X] hours before it starts, the manager may assign it to a qualified employee, following [the rotation / the seniority list].

Records. Every claim, approval, decline, and draw is logged with a time stamp.

What should a manager do on Monday?

Pick the model, write the policy, and post it. Then run one check you have probably never run: pull the last ten open shifts you filled and see who got them. If it is the same three people, you already know which failure mode you have.

Most teams do best with a simple default: first-come with a short delay, a weekly-hours check before approval, and a lottery or a rotation rule only when a shift is popular enough to cause a fight. Seniority is the right answer where a contract or a long-standing norm already points that way.

One related problem is outside the scope here. When a handful of employees take most of the open shifts, that is a hoarding problem with its own fixes, such as caps and cooling-off periods. The policy above will surface it, but it does not solve it.

If you schedule with Shift Amp, open shifts are claimed in the app, each claim shows how many hours that person is already scheduled that week, and a manager approves one. Set the weekly hours limit to Block and the app refuses an approval that would put someone over your cap. The principles above work on a whiteboard too.

This article is general information, not legal advice. Overtime, scheduling and seniority rules differ by state, city and contract, and they change, so check the current rules where you operate or talk to an employment attorney before you adopt a policy.