Open Availability: What You Actually Signed Up For

Somewhere near the start of the hiring process, a form asked you to shade in the hours you could work. Maybe you ticked every box. Maybe someone said the job would be easier to get that way, and they were right.

Nobody explained what the boxes were for.

Here is the plain-words version, because "open availability" is one of those phrases that everyone uses and almost nobody restates: it is not a promise to be helpful. It is a declaration that every hour the business operates is an hour you have agreed can be assigned to you. That declaration then sits in a system and quietly runs your calendar for as long as you work there.

It is not a legal status

Start here, because it clears up half the confusion.

"Open availability" appears in no labour statute. It is not a job classification, not a pay grade, not a legal obligation. It is a business practice — a preference employers ask about at hire because flexibility helps them fill scheduling gaps and respond to business needs.

That matters in both directions. Because it is not law, no statute forces you into it and no statute defines its edges. And because it is not law, its meaning is set entirely by your employer's policy and, if you have one, your contract. Two people saying "I have open availability" at two companies have not agreed to the same thing.

What it actually does to your schedule

The declaration does three things, and only the first one is obvious.

It makes you eligible for everything. That is the part people expect.

It removes the standing reason not to schedule you at the worst times. This is the part people don't. Scheduling software fills hard slots by elimination — it excludes everyone with a stated conflict first, then distributes what's left. Every restriction anyone else has declared is a filter that removes them from a slot. If you declared none, you are in every remaining pool. The 5am open, the Sunday close, the shift nobody bid on: you are not being singled out. You are simply the last person left after the filters run.

It becomes the default answer to "why did you say yes." Once a stated availability exists on file, "I can't do Thursday" reads as a change of position rather than a fact about your life — because the record says you could. That is a conversation about your reliability instead of a conversation about the schedule, and it is a much worse conversation to be having.

None of this requires a bad manager. A perfectly fair system will do all three, because that is what the input told it to do.

What it does not commit you to

Now the correction, and it is a big one.

There is a widespread belief that open availability means you have forfeited the right to say no. In a meaningful number of jurisdictions, that belief is simply wrong — and the laws that say so are worth knowing even if they don't cover your job, because they show what the two halves of the deal are supposed to be.

Oregon's predictive scheduling law gives covered employees a written schedule "at least 14 calendar days before the first day on the schedule," and the right to "decline any work shifts not included in the employee's written work schedule" (Oregon BOLI). Note what that right is attached to. Not to your availability — to the posted schedule. Declaring open availability makes you schedulable for anything. It does not make an unposted shift into a posted one.

Seattle's Secure Scheduling Ordinance is built the same way: employees have the "right to decline any hours not on originally posted schedules" (Seattle Office of Labor Standards).

Both also price the change rather than forbidding it. In Oregon, adding thirty minutes or more to a shift, or moving it without cutting hours, costs the employer an hour at your regular rate; cutting hours or cancelling a shift costs half your rate for each scheduled hour you don't work (BOLI, linked above). The shift can still change. It stops being free.

The coverage is narrow, and you should check before relying on any of it. Oregon's law reaches retail, hospitality and food service employers with 500 or more employees worldwide. Seattle's reaches retail and food service at the same 500-employee threshold, with full-service restaurants also needing 40+ locations. Most nurses, medics, firefighters and dispatchers are outside these laws entirely and are governed by a contract instead. The principle still travels: somewhere there is a document that says when your schedule becomes real, and that document — not your availability form — is what determines when you can decline.

The half of the deal you may be owed

Here is the part almost nobody asks for, and it is the natural counterpart to the form you filled in.

You told them your availability in writing. Under both ordinances, the employer owes you a written estimate back. Seattle requires a "written good faith estimate of median hours employees can expect to work and whether employees will work on-call shifts" at the time of hire, updated annually and when the schedule materially changes (Seattle OLS, linked above).

Read those two documents side by side and the deal is legible: you state which hours are possible, they state roughly how many you'll get and whether on-call is part of it. Almost everyone provides the first document. Far fewer people ever ask for the second — and the gap between "I gave open availability" and "I am getting twelve hours a week" lives exactly in that missing half.

Seattle attaches one more thing to it: before hiring anyone new, employers must "offer additional work hours to current employees" by posting available hours for three days first (Seattle OLS). Open availability is worth the most where a rule like that exists, and worth the least where new hires can be added while your hours stay flat.

Stating limits is not the same as being difficult

If you want to narrow your availability, one thing is worth knowing.

Oregon's law lets an employee "identify any limitations or changes in work schedule availability, including child care needs" and request not to be scheduled at certain times or locations. The employer "is under no obligation to grant the employee's request" — but "may not retaliate against an employee for making such a request" (BOLI, linked above). Seattle goes slightly further, requiring employers to engage with scheduling-preference requests and to grant those tied to major life events absent a bona fide business reason (Seattle OLS).

So the asking is protected; the granting is not guaranteed. Those are two separate facts and it is worth holding both, because the fear that keeps most people from ever revising their availability is a fear of the first one.

What is genuinely worth checking before you revise it: whether your employer's policy treats a reduction in stated availability as a voluntary reduction in hours. Some do, and the classification carries consequences — benefits eligibility thresholds and, in some places, unemployment claims turn on whether a reduction was voluntary. That is a policy question with a written answer, and it is much better asked before the change than after.

Four questions with written answers

None of these are confrontational. All four have a document behind them somewhere.

Where is my availability stored, and who can change it? It is a record, not a memory. Find out whether it lives in the scheduling system, in HR, or in a manager's notes — because that determines whether a change actually propagates or just gets agreed to verbally and then forgotten.

What is the good faith estimate of my median hours? Even where no law requires one, asking converts a vague expectation into a number someone has to say out loud. If the answer is far below what you assumed, you have learned that now instead of in six weeks.

When does the schedule become final, and what happens to changes after that? This is the question that decides whether your right to decline exists. "Posted two weeks out" and "posted Friday for Monday" are different jobs with the same job title.

Is reducing availability treated as a voluntary reduction in hours here? Ask before you need the answer.

Open availability is not a character trait, and it is not a favour. It is one line of input to a system, and the system will use exactly what you gave it — no more, and no less. Knowing what the line says is the whole difference between being scheduled and being surprised.

This is a general explanation of scheduling practice and publicly available scheduling ordinances, not legal or employment advice. Coverage thresholds, contract terms and employer policies vary widely — check the rules that apply where you work.