Plan the week in two layers and put a date beside every unknown: what is confirmed, what is still waiting, and the day you will chase it. The date is the part people skip. If you work in Oregon for a retail, hospitality or food services employer with at least 500 employees worldwide, that date is already fixed for you — the written schedule has to arrive at least 14 calendar days before the first day on it, the Oregon Bureau of Labor and Industries says. Where no ordinance sets the date, you set it yourself and you tell the scheduler what it is.
Ask for the median hours figure, because it makes a week plannable
Two layers of a calendar are useless without a number to fill them with, and there is a specific number worth asking for. A covered Oregon employer must give a written good faith estimate at hire stating the median number of hours you are expected to work in an average month, and must let you identify limitations or changes in your availability at hire and throughout employment, on that BOLI page. Seattle's Secure Scheduling Ordinance asks for the same thing on a schedule: a written good faith estimate of the median hours you can expect to work, given at hire, annually, and when the schedule changes significantly, the City of Seattle says.
That estimate turns "I don't know what next week looks like" into a planning figure. A median of 88 hours a month is roughly 20 hours a week, and 20 hours a week means three shifts, not five. You can decide what fits around three shifts. You cannot decide anything around an unknown.
Ask for it in one sentence, whether or not an ordinance covers you: "What is the median number of hours a month I should expect, and which day does the schedule go up?" A scheduler who cannot answer the second half has told you something useful — the date is not fixed, so build the week around the confirmed layer only.
Both pages carry a second mechanism worth naming. Oregon's BOLI page says the voluntary standby list is set up through a written employee request or agreement, so being asked to cover extra shifts is a thing you opt into rather than a default. Seattle's ordinance requires the employer to post available hours for three days and offer them to current employees before hiring new ones. Where you want more hours, those are the two doors.
Write two layers and one chase date
The confirmed layer holds anything with a time and a source: a posted shift, a booked appointment, an agreed pickup, a bus departure. The waiting layer holds anything with a time and no source: a probable Thursday shift, a friend's "maybe Saturday", a roster that has not gone up.
Every line in the waiting layer needs two extra fields, and this is the whole method: who can confirm it, and the day you will ask them. "Possible Thursday evening shift — scheduler, ask Wednesday morning" is plannable. "Possible Thursday evening shift" is a worry.
Leave a blank space blank. An unmarked gap in a calendar reads as availability to anyone else who opens it, including you at 9 pm when someone asks for a favor. Write "unknown" in it, or write what you intend it for.
If a second employer is in the picture, the fixed roster goes in first and the flexible one fills around it; putting two jobs on one calendar is a separate arithmetic problem with travel time in it.
Keep the dates, because the employer has to keep them too
Your own log is the cheap half of the record. The expensive half already exists: under the FLSA, an employer must keep, for each nonexempt worker, the hours worked each day and the total hours worked each workweek, and the Department of Labor's recordkeeping fact sheet says payroll records are preserved for at least three years while time cards and schedules are retained for two years.
Two years is long enough that a pattern you notice now is still documented later. That matters when what you want is not this week's Thursday but a different posting day altogether, which is a request with a date on it rather than a weekly scramble.
Take one week as the example. Say the roster is meant to go up Saturday for the week starting the 28th, and by Monday the 23rd there is nothing. Your waiting layer reads: "Week of 28th — roster due Sat 21st, still not posted Mon 23rd. Ask Priya today." Do that four weeks running and you are holding four dates, not an impression.
Copy these six lines into whatever you actually read each morning, and fill the last two before you close it:
- Confirmed this week, with travel time included:
- Waiting — what, who confirms it, and the day you ask:
- Median hours a month you have been told to expect:
- The day the next roster is due:
- One thing outside work you want to keep, and who else has agreed to it:
- What can stay undone: