Which state processes in this post run on a 30-day clock?
Four state processes in this post are tied to a 30-day figure: the California report of alternative workweek election results, the Wisconsin arbitrator's order, the notice Washington must give before it revokes a variance, and the validity period of a Washington temporary variance. Each one starts from a different event, so a calendar entry needs the trigger date as well as the due date.
Key takeaways:
- Record the trigger event and its date, not only the due date, so the arithmetic can be checked later.
- The Wisconsin order may be extended by agreement or by the commission, but only up to an additional 30 days.
- Washington's revocation rule is a minimum notice period, so it sets an earliest revocation date rather than a final one.
- A Washington temporary variance may run no longer than 30 calendar days, and the source names no start event beyond the order's own dates.
- Write each open question into the calendar entry so it is not answered from memory.
The sections below take them in that order, and each links the official page it comes from.
What does the California election report clock require?
The employer must report the results of an alternative workweek election to the Office of the Director – Research, Department of Industrial Relations, within 30 days after the results are final. ( California Code of Regulations, Title 8, Section 11040) The clock starts when the results are final, not on the day the vote is held, so the calendar entry should point to the date the employer records the results as final. The same section says the report of election results is a public document, so treat the filed copy as something outsiders may read.
The same section sets the vote rules that come before that report. Upon a petition of one-third of the affected employees, a new secret ballot election shall be held, and a two-thirds vote of the affected employees is required to reverse the alternative workweek schedule. ( California Code of Regulations, Title 8, Section 11040) A team tracking a schedule change should log the petition date, the election date, the date the results became final, and the report due date as four separate entries, because each one sets up the next.
The section also refers to a 12 month interval between elections. It then makes an exception: a new secret ballot election to repeal an alternative workweek schedule adopted between October 1, 1999 and October 1, 2000 is not subject to that interval. ( California Code of Regulations, Title 8, Section 11040) The exception covers only schedules adopted in that window, so for any other schedule, read the full section before counting on the timing of a repeal election.
How long does a Wisconsin arbitrator have to issue an order?
The arbitrator must hand down the order within 30 days after appointment, so the appointment date starts this clock. ( Wisconsin Legislature, "Wisconsin Legislature: 111.395") For example, an appointment on March 3 puts the 30-day date on April 2. Record the appointment date itself, not just the due date, so the arithmetic can be checked later.
The period can be extended in one of two ways. The parties may agree to extend it, or the commission may extend it for good cause. Either way, the extension may not exceed an additional 30 days beyond the original period, so the calendar should carry any extended date only once the extension is in hand. ( Wisconsin Legislature, "Wisconsin Legislature: 111.395")
For a staffing team, the risk is planning around a later date before any extension exists. Keep the 30-day date as the working deadline, and move it only when an agreed or granted extension is in hand. Record who agreed or granted it and on what date, so the new date can be checked later.
How does an employer apply for a Washington variance?
An employer may seek a variance from the rules in chapter 296-126 WAC by submitting a written application to the director. ( Washington State Legislature, "Chapter 296-126 WAC") The quoted text sets no number of days for filing that application, so the team should not invent a deadline for it and should instead ask the director's office what applies to its case.
The director may allow the employer and any involved employee, or their representatives, an opportunity for oral presentation when the circumstances of the particular application warrant that additional procedure. ( Washington State Legislature, "Chapter 296-126 WAC") That presentation is discretionary, so do not plan around one. If one is held, note in the file whether it was requested and whether the director allowed it.
After reviewing the application, the director shall grant the variance if the director determines that there is good cause. ( Washington State Legislature, "Chapter 296-126 WAC") Good cause is therefore the test, so the file should record the reason the variance is needed as well as the request itself. A file that shows only the request gives a reviewer little to check against that test.
How much notice does Washington require before it revokes a variance?
The director may revoke or terminate a variance order at any time, after giving the employer at least thirty days' notice before doing so. ( Washington State Legislature, "Chapter 296-126 WAC") The clock runs from the notice, not from the date of revocation. The calendar should therefore carry the notice date and the earliest revocation date, which falls 30 days after the notice. If a notice arrives on June 1, the earliest revocation date in this example is July 1.
A variance a team plans around can end on a date the team did not choose. When a notice arrives, review every schedule and placement that depends on the variance, and note which ones would need to change by the earliest revocation date. The quoted sentence sets only the notice period, so check the full chapter for any other steps the director must take first.
How long can a Washington temporary variance last?
The director may issue a temporary variance valid for no more than thirty calendar days. That limit applies when the employer demonstrates good cause and immediate action is necessary pending further review by the director. ( Washington State Legislature, "Chapter 296-126 WAC") Thirty calendar days is the maximum, so a shorter validity period is also possible. The quoted text does not name a start event for the period, so read the start and end from the dates written on the order itself rather than treating any other event as settled.
The same provision says that an employer need not meet the requirement in subsection (1)(b) of this section in order to be granted a temporary variance. ( Washington State Legislature, "Chapter 296-126 WAC") The quoted text does not say what subsection (1)(b) requires, so this post does not describe it. Read the full chapter before relying on that point in a specific case.
For the calendar, find the start of validity on the order itself, count no more than thirty calendar days from that date, and set a reminder early enough to plan for the end of the order.
How do the four clocks compare?
The table puts each clock's trigger, period, and any extension or limit side by side, using only the figures the quoted text states.
| Clock | Trigger in the source | Period in the source | Extension or limit stated |
|---|---|---|---|
| California election results | Results become final | Report within 30 days | None stated |
| Wisconsin arbitrator's order | Appointment | Order within 30 days | Extension of no more than an additional 30 days |
| Washington variance revocation | Notice to the employer | At least 30 days' notice before revoking | None stated |
| Washington temporary variance | Not stated; read from the order's own dates | No more than 30 calendar days | The 30 days is itself the maximum |
Only the Wisconsin row names an extension in the quoted text. The other three rows show a 30-day figure with no extension stated, so their dates should be entered once and checked against the source rather than adjusted on a hunch.
The wording of each rule changes how the date should be read. The California report and the Wisconsin order are deadlines, so the calendar should show the last day on which the step can be completed. The Washington revocation rule is a minimum notice period, so the calendar should show the earliest date the revocation can take effect. The Washington temporary variance is a cap on how long the order may run, so the calendar should show the date validity ends. Treating all four as the same kind of date is the simplest way to put one of them in the wrong place.
Why does the trigger date matter more than the due date?
A due date alone cannot show whether it is right. If a team records April 2 with no note of the March 3 appointment, nobody reviewing the file later can tell whether the date was calculated correctly.
The same logic applies to the team's own records. The California report, for instance, is tied to the date results are final rather than the date of the vote, so two teams that held the same vote on the same day could record different due dates if one team marked its results final later. A reviewer should be able to start from the trigger, apply the period, and arrive at the due date. If that path cannot be followed on paper, the calendar is only a list of dates, and a list of dates does not show that anything was handled on time.
Which details in these four rules are still open?
Several details are not in the quoted text, so a team should not fill them in from memory or from a colleague's recollection. The open points are the following:
- The number of days, if any, for filing a Washington variance application.
- What subsection (1)(b) requires before a temporary variance can be granted.
- Where the 30-day period for a temporary variance begins, beyond the order's own dates.
- Whether the director must take any step before revoking a variance, beyond giving at least thirty days' notice.
- Whether the Wisconsin commission's extension for good cause needs a particular form or record.
Each open point is a question for the issuing office or for the full chapter or section, not a reason to assume an answer. Write the question into the calendar entry so it is not forgotten.
How should you check a date against its source page?
Open the linked page, find the section named in the calendar entry, and read the whole section before relying on a date. The quoted sentence may be one part of a longer rule with an exception, a cap, or a condition that changes the count. The California section, for example, pairs its reporting period with a repeal exception that applies only to schedules adopted in one window. Checking the page again whenever the entry is reviewed keeps the calendar tied to the current text rather than to an old note.
What should each clock's calendar entry contain?
Each clock should have one calendar entry with four parts: the trigger event and its date, the period from the source, the due or earliest date, and a link to the official page. Store the trigger date in the record itself, so the file shows when the clock started without anyone needing to remember it.
For the Wisconsin row, add a note field for any extension, with the party or commission that granted it and the date. For the Washington revocation row, add a note field for any notice received. For the temporary variance row, add the start and end of validity from the order. Keep these notes with the entry rather than in a separate email thread, so the calendar and the file stay in one place.
Related reading on this site: Conviction timing rules for 3 jurisdictions and Hiring claim filing deadlines: 3 state clocks follow the same trigger-plus-period method for other state deadlines.
What should a team do when two clocks overlap?
Two clocks can run at once. A team might have a schedule election report due while a variance is still in its validity period. Give each clock its own entry, check the calendar on the same day each week, and mark any entry that falls within the next thirty days so it gets a named owner.
When a state office or another party replies with a date, update the entry the same day and note the source of the change. A wrong trigger date gives every later entry the wrong start, so fix the trigger first, then recheck every date that depends on it.