Why a weather or outage day is now a staffing question
Colorado's SB23-017 allows paid sick leave when a worker must leave home for inclement weather, loss of power, loss of heating, or loss of water. The bill also includes a broader closing phrase for other events.
Key takeaways
- The bill's quoted sentence names four triggers: inclement weather, loss of power, loss of heating, and loss of water.
- The same sentence ends with a broader phrase for any other unexpected occurrence or event that results in the need to evacuate.
- For each request, ask whether the event is the reason the worker has to leave home.
- The quoted sentence does not say how long a loss must last, so do not add a waiting period of your own.
When a storm knocks out power, a pipe bursts, or officials tell people to leave their neighborhood, the worker who needs time off rarely asks in advance. The message usually arrives later, sent from a shelter, a relative's house, or a hotel parking lot, and it may be short and urgent. The person who reads it is often a hiring manager or a member of a small staffing team who is also building the schedule, covering open shifts, and answering everyone else's questions.
Colorado's sick-leave bill speaks directly to this moment. Its text adds to the reasons a worker can use paid sick leave, and one of those reasons is having to leave home. Before you change how your team handles these requests, read the bill's current text and status on the Colorado General Assembly page for SB23-017. This post explains what the bill's wording says and how to think through the requests it describes. It is not legal advice, and it cannot tell you how the bill applies to your own workplace.
What the bill adds to paid sick leave
The bill's title, as listed on the General Assembly site, describes its purpose as "Concerning the addition of qualifying uses of paid sick leave, and, in connection therewith, making an appropriation." In plain words, the bill adds to the list of qualifying uses for paid sick leave. The title also mentions an appropriation. This post does not cover that part.
One of the added uses is evacuation. The bill's text reads:
> Evacuate the employee's place of residence due to inclement weather, loss of power, loss of heating, loss of water, or any other unexpected occurrence or event that results in the need to evacuate the employee's residence.
Source: Colorado General Assembly, SB23-017
Read that sentence closely, because it does three things at once. It names the reason as the need to leave the employee's place of residence. It gives four specific triggers. And it ends with a broader phrase that covers other events. Each of these affects how you respond to a request.
The four named triggers
The table lists the four named triggers in the order the bill gives them. The final row is not a named trigger, but it sits in the same sentence, so you need to account for it too.
| Trigger | Position in the sentence | Named as a trigger? |
|---|---|---|
| Inclement weather | First | Yes |
| Loss of power | Second | Yes |
| Loss of heating | Third | Yes |
| Loss of water | Fourth | Yes |
| Closing catch-all phrase | Last | No, a broader phrase |
Source: SB23-017 on the Colorado General Assembly site
Working through each named trigger
Each of the four triggers describes a different situation, and a single request may fit more than one. Thinking about them one at a time helps you ask better questions.
Inclement weather. This is the broadest trigger on the list. Do not build a checklist that rejects requests because the event is not on your own list. Instead, ask the worker what is happening where they live and whether they have been told to leave.
Loss of power. This is the trigger most managers picture first. A worker may need to leave because the home is without electricity. The bill names loss of power as its own trigger, so a request does not have to be tied to a larger disaster to fit. The question to ask is whether the lack of power is the reason the worker has to leave home.
Loss of heating. The bill lists heating separately from power, and that difference matters. A home can keep its lights on and still lose its heat, for example if a furnace fails. A worker who reports that their home has lost heat and cannot safely stay there is describing the loss-of-heating trigger, even if the electricity still works.
Loss of water. The fourth trigger covers a home that has lost its water supply. The quoted sentence does not say how long the loss must last, so do not invent a waiting period of your own. Rules on timing differ from state to state. Washington's paid sick leave rules, for example, say employers "may allow employees to use accrued, unused paid sick leave prior to the 90th calendar day after the commencement of their employment." That is a Washington rule and does not set the terms for Colorado. It shows why you should check the wording of the law where your team works rather than assume another state's timing applies. For more on other states' sick-time rules, see sick time rules for new hires. For loss of water, the question is again the same: is the loss of water the reason the worker must leave?
Handling the catch-all for other events
The closing phrase, quoted above, reaches beyond the four named items. Two parts of it deserve attention.
First, the test is whether the worker actually has to leave home. The label on the event matters less than that fact. A worker who says a fire in a neighboring building has forced them out, for example, is describing an event the bill does not name. That event is worth considering under the broader wording, and you should check the bill's full text rather than decide alone.
Second, the word "unexpected" carries weight. Whether an event counts as unexpected is a judgment call. Write down your reasoning when you make it, so that you apply the same approach to the next request and can explain the decision later.
For unclear cases, do not guess in either direction. Ask the worker for a short description of what happened, read the bill's text together, and if the decision affects pay or leads to a dispute, get advice from an employment attorney or the state labor agency. A quick check now costs less than a disagreement later.
Handling a request when it arrives
Start with the person, not the paperwork. If someone reports that they are leaving home, first make sure they are safe, that they have somewhere to go, and that they know to call emergency services if they are in danger. A schedule can be fixed later. A worker standing in floodwater cannot wait for a shift swap.
Acknowledge the message quickly. Even a short reply helps: you received it, you will follow up, and here is what you need from them. A prompt promise to respond properly is better than silence while the worker waits in a shelter.
Ask two or three focused questions. Which event is affecting them? Which of the four named triggers, or the broader wording at the end, seems to fit? Which shifts are affected, and for how long? Keep the questions short, because the worker may be on a phone with a low battery and no power at home.
Decide and confirm in writing. Once you know the trigger and the dates, reply with your decision, the leave type you are recording it under (see leave settings for small staffing teams), and what happens to their scheduled shifts. A written confirmation protects both the worker and the business, and it gives the worker something to refer to later.
Cover the shifts you can. Once the leave is approved, the schedule has to move. Reassign shifts using a list of people who have said they can pick up work, and tell them clearly what they are covering and when. For a clear process for approving swaps, see shift swap approval.
What a clear first reply looks like
Imagine a worker messages you at night to say that their building has lost power and they are staying with a friend across town. A useful reply might read:
> Thank you for letting me know, and I'm glad you are safe. The power outage you describe matches the loss-of-power item in the bill's list, so I'm treating this as evacuation leave for now. Which shifts can't you work this week? I'll confirm the changes in writing once I've moved them, and I'll check back with you tomorrow morning.
The reply does four things. It acknowledges the worker first. It connects the event to the bill's wording in plain terms. It asks only the question needed to schedule the shifts. And it says when the worker will hear back.
Mistakes that slow the response down
Several common habits make these requests harder than they need to be.
Do not treat an event as suspicious because you did not hear about it on the news. A worker's home is not a broadcast. A local outage may affect one street, and the worker may not have any way to report it except by message.
Do not ask for elaborate proof when a short description will do. Unless your own policy or the law requires documentation, asking for photos of damage, utility bills, or detailed medical information can delay the decision and expose private details you do not need. Check the requirements before you add any.
Do not let a request sit in an inbox over the weekend or during a storm. The workers most likely to send urgent messages are the ones who are most disrupted, and a slow answer tells them the business is not paying attention.
Do not make the answer depend on one person's availability. If only one manager can approve these requests, the request waits whenever that manager is offline. Name a backup before you need one.
Finally, do not promise a decision you cannot yet make. "I need to check the bill's wording, and I will reply by the end of today" is honest, specific, and useful. "We will sort it out later" is neither.
What to record, and what to leave out
Keep a record of each request: the date, the event as the worker described it, the trigger you matched it to, your decision, and the shifts affected. A short note in a shared file is often enough for a small team. The point of the record is to make the next decision consistent and to answer questions later, not to build a file on the worker.
Avoid collecting more than you need. You rarely need the worker's full address, a photo of the damage, or medical details to decide whether the bill's wording applies. Ask only for what helps you match the event to the bill's text and schedule the shifts. If you are unsure what records your state or your own policy requires, check with the state or an attorney rather than adding requirements of your own.
Store the record where only the people who handle requests can see it. Time-off notes can contain personal details, and they should be treated as private.
Planning before the next storm
Most weather and outage requests arrive with little warning, so the best preparation happens before the event.
Write a one-page plan. Name who receives urgent time-off messages, who approves them if that person is unavailable, and when someone will check messages outside normal hours. Share the plan with everyone on the team so that workers know where to send a request.
Keep a current cover list. For each role, note which workers can cover which shifts and how to reach them. Update the list when people change roles, leave the business, or ask to be removed from it.
Choose one channel for urgent requests. Requests that arrive in three different places are easy to miss. Pick the channel you will monitor, tell workers to use it, and check it on a schedule that matches the risk your team faces in bad weather.
Review the plan after each event. Note what worked, what slowed you down, and which question you wished you had asked. Then change the plan. A plan that is revised after each real event is more useful than one written once and forgotten.
Keeping your policy accurate
A written policy is only as good as its wording. Before you rely on this post or any summary of the bill, do three things.
Read the bill's current text and status on the Colorado General Assembly site. Bills change as they move through the legislature, and a summary can go out of date. The quoted sentence in this post is only one part of the bill.
Compare your existing time-off policy with the bill's wording. Note where your policy already covers evacuations, where it does not, and where the wording is unclear. Pay particular attention to how your policy handles the four named triggers and the broader wording at the end of the sentence.
Get advice on any unclear point. An employment attorney or the state labor agency can explain how the bill applies to your workplace. This post cannot, and it should not be used as a substitute for that advice.
Finally, train the people who answer requests. The person who first reads a message from a worker in a shelter should know the four named triggers, the broader wording, and where to find the written plan. A clear, calm reply, sent quickly, does more for a worker in a bad week than a perfect policy that nobody remembers.
Next step for today: open the bill's text on the Colorado General Assembly page for SB23-017 and list which of the four named triggers your current time-off policy already covers.
Frequently asked questions
Does the bill cover only the four named triggers?
No. The quoted sentence ends with a broader phrase for any other unexpected occurrence or event that results in the need to evacuate the employee's residence. Check the bill's full text before you decide.
Can loss of heating count if the power still works?
Yes, it can. The bill lists loss of heating as its own trigger, so a home that has lost heat and cannot safely be lived in may fit even if the electricity still works.
Does the bill set a waiting period before leave can be used?
The quoted sentence does not say how long the loss must last, so do not add a waiting period of your own.