In Case of Disruption

A Nimbus Operational Resilience Guide for Remote Team Members

Helping You Soar in Stormy Weather™
1 / 12
Comments
TM
Tanya M.2d ago
Updated from v8 to reflect new terminology guidance. Also swapped “Preparedness” for “Resilience” in the subtitle per the branding refresh — Comms said “preparedness” tested as “alarmist” in the last employee sentiment survey. This version feels much more empowering!
A Message from Leadership

At Nimbus, our people aren’t just our greatest asset — they’re the engine that powers everything we do.

That’s why we’ve developed this guide: to make sure every member of the Nimbus family has the tools and confidence to stay connected, stay productive, and continue delivering for our customers and stakeholders no matter what challenges arise in your area.

Because when you soar, we all soar.

— The Nimbus Leadership Team

2 / 12
Comments
TM
Tanya M.2d ago
Legal flagged “family” — do we need to update this? The new EO redefines family for federal benefits purposes and I want to make sure we’re not inadvertently using the word in a way that creates liability. Waiting to hear back from compliance but in the meantime I left it in because it’s in the brand voice guide and we’d have to change the website too.

What We Mean by “Volatility”

Today’s operating environment includes a range of potential disruptions. At Nimbus, we don’t see disruption as a setback — we see it as an opportunity to demonstrate our core values in action.

This guide covers strategies for maintaining productivity during:

Scheduled and unscheduled power outages
📡Internet service disruptions
🏗Regional infrastructure events
🏘Civil activity in your area
🌤Atmospheric and environmental events

Remember: Nimbus is a remote-first company. Your workspace is wherever you are — and so is your commitment to excellence.

3 / 12
Comments
TM
Tanya M.2d ago
Should “civil activity” be “community activity”? I saw the President posted something on X about not using certain words in federal communications and I’m not sure if that applies to us but Jake in Legal said better safe than sorry.
TM
Tanya M.2d ago
Also, does anyone know if “atmospheric” is okay? I don’t want it to sound like we’re taking a position on climate. Marking for review.
01
Scenario

Power Outage

Losing power doesn’t mean losing momentum!

Keep your laptop charged to 80% at all times using the Nimbus Power Readiness Protocol
Identify two backup locations within a 30-minute radius with reliable power and internet (we recommend co-working spaces, libraries, or retail establishments with customer WiFi)
If you anticipate an outage lasting more than 4 hours, notify your manager and update your status in NimbusConnect™ to “Working — Modified Environment”
Outages exceeding 8 hours without a status update may be flagged by the automated attendance system. This is not punitive — it helps us support you!
4 / 12
Comments
TM
Tanya M.1d ago
Love this slide! One note — can we get a stock image that’s more diverse? The current one reads a little homogeneous.
TM
Tanya M.1d ago
Also, Chris asked if we should include guidance for people whose backup locations are also experiencing outages, but I think that’s an edge case and we don’t want to overwhelm the deck. Keeping it simple and empowering!
02
Scenario

Internet Disruption

In today’s connected world, a dropped connection doesn’t have to mean a dropped ball.

Nimbus employees are expected to maintain a personal mobile hotspot as part of their remote work toolkit (see Equipment Policy 4.7b for approved devices and reimbursement caps)
Use NimbusConnect™ mobile app to log tasks and update ticket queues from your phone
If connectivity is unavailable in your area for more than 12 hours, you may request Discretionary Offline Work authorization from your direct manager
Note: Discretionary Offline Work hours are tracked separately and subject to retroactive productivity review
5 / 12
Comments
TM
Tanya M.1d ago
I know some people on the last survey said the retroactive review felt “surveillance-y” (their word!) but it’s really just about making sure we can verify the work was done. It actually protects the employee! Maybe we add a line about that? Something like “This process exists to ensure your contributions are recognized even when you’re offline.” Thoughts?
03
Scenario

Regional Infrastructure Events

Sometimes the disruption is bigger than your block.

Whether it’s road closures, utility failures, or damage to local infrastructure, Nimbus is here to help you stay on track.

If local infrastructure events prevent you from accessing your primary or backup workspace, document the disruption with a photo or screenshot of a local news source and submit through the NimbusConnect™ Disruption Verification portal
All disruption claims are reviewed within 5–7 business days
Approved claims are categorized as Excused Downtime (capped at 16 hours per quarter)
Unverified downtime will be classified as Unapproved Absence per the standard attendance policy
6 / 12
Comments
TM
Tanya M.1d ago
The 5–7 business day review window is from the current policy, but given how things are going I wonder if we should flag to People Ops that there might be a volume issue? Last quarter we had 340 disruption claims and that was before the new infrastructure issues in the southeast. Anyway, not a slide problem — more of a process problem. Flagging for the ops sync.
TM
Tanya M.1d ago
Also, are we still requiring photo documentation? I saw some chatter on the internal board about people feeling uncomfortable photographing certain situations. I think it’s fine — it’s the same as submitting a doctor’s note. Just accountability!
04
Scenario

Civil Activity in Your Area

Your safety is our priority.*

If civil activity in your area makes it difficult to work, here’s what to do:

Remain indoors and away from windows if possible
Log into NimbusConnect™ and set your status to “Sheltering — Available” or “Sheltering — Limited Availability”
You are still expected to respond to priority tickets and manager check-ins within the standard 15-minute SLA unless you have formally activated Emergency Protocol (see Slide 10)
Do NOT post about civil activity on social media while identifiable as a Nimbus employee (see Social Media Policy 2.3, updated per Executive Order)

*Your safety is our priority within the limits of applicable company policy and at-will employment terms. See Employee Handbook Appendix C.

7 / 12
Comments
TM
Tanya M.18h ago
The asterisk was Legal’s idea and I think it’s smart — covers us without changing the tone.
TM
Tanya M.18h ago
Re: the social media policy update, I know there’s been confusion about what counts as “identifiable as a Nimbus employee” — does having Nimbus in your LinkedIn bio count? Jake says yes but I think that’s going to get pushback. Let’s discuss at standup.
TM
Tanya M.18h ago
Also, the President posted a new rule on X about the phrase “civil unrest” so I changed everything to “civil activity” across the deck. I think it actually sounds better! More neutral.
05
Scenario

Atmospheric & Environmental Events

Mother Nature doesn’t check your calendar — but you can still check your metrics!

Monitor local conditions using approved information sources only (see Approved Media List, updated quarterly by Compliance)
If air quality in your area drops below the federal threshold, you may close your windows and continue working normally
If your home becomes uninhabitable, notify your manager within 2 hours and begin the Relocation Protocol (see Equipment Policy 4.12)
Note: “Uninhabitable” is defined by FEMA standards. Nimbus reserves the right to request third-party verification for relocation claims.
8 / 12
Comments
TM
Tanya M.12h ago
Replaced “air quality index” with “federal threshold” because Jake said the AQI metric is from the EPA and we shouldn’t reference agencies that are under review. Updated the Approved Media List link — it goes to the new version that removed the outlets flagged in the latest EO.
TM
Tanya M.12h ago
Also wondering if we need to address the water situation specifically? A few people in the southeast Slack channel have been asking about boil advisories and how to document them, but I think that falls under “environmental events” generally. Keeping the language broad so we don’t have to update every time something new happens. Efficiency!
06
Scenario

Exposure to Hazardous Materials or Munitions

In rare cases, employees in certain regions may experience exposure to hazardous materials, including but not limited to chemical irritants, incendiary devices, or aerosolized agents.

Move to a safe location immediately and administer any available first aid
Once you have stabilized your situation, log into NimbusConnect™ and file a Disruption Verification claim with photographic or medical documentation
If you are unable to log in due to injury, a designated emergency contact may file on your behalf (see Emergency Contact Authorization Form 9.1)
Disruptions in this category are eligible for Extended Excused Downtime (up to 48 hours, with manager approval)
After 48 hours, standard attendance policy resumes
9 / 12
Comments
TM
Tanya M.10h ago
I went back and forth on whether to include white phosphorus specifically (some people in the Pacific Northwest channel have been asking) but Jake said it’s better to keep the language general so it covers everything without us having to take a position on any specific event. I think that’s right. The goal is to be supportive without being political!
TM
Tanya M.10h ago
Also — “munitions” was my word and I’m not sure it’s right. Does anyone have the approved terminology? I want to make sure we’re aligned with whatever Compliance is using. The last thing we need is for this deck to go out and have someone screenshot it with a word that’s on the list.
PROTOCOL

Activating Emergency Protocol

If you are experiencing a Level 3 disruption (see Disruption Tier Matrix, Appendix F), you may activate Nimbus Emergency Protocol.

1Text “NIMBUS SAFE” to the automated Emergency Response line
2You will receive a confirmation code within 60 seconds
3Enter the code into NimbusConnect™ to suspend your attendance tracking for up to 72 hours
Important:
Emergency Protocol can only be activated once per quarter without VP-level approval
Failure to reactivate your attendance tracking within 72 hours will result in automatic status change to “Unresponsive — Under Review”
Emergency Protocol does not exempt you from deliverables with pre-existing client-facing deadlines
10 / 12
Comments
TM
Tanya M.8h ago
Is the 60-second confirmation window realistic? I’ve heard the system has been slow since they moved it to the new server. Also, “once per quarter” might be an issue given the current frequency of Level 3 events — I’ve seen three in the PNW channel just this month. But I think the VP approval workaround covers that. People just need to plan ahead!
TM
Tanya M.8h ago
One more thing — should we add a note about what happens if cell service is down and they can’t text in? I started writing something but it got complicated so I deleted it. Probably an edge case.

Frequently Asked Questions

Q: What if my internet AND power are out at the same time?
A: This qualifies as a Compound Disruption. Follow the guidance for whichever scenario has the longer estimated duration and file a single Disruption Verification claim noting both.
Q: Can I use PTO during a disruption instead of filing a claim?
A: Absolutely! Many employees prefer this option for its simplicity. PTO requests during active disruptions are approved automatically and do not require the standard 2-week advance notice.
Q: What if a disruption affects my entire team?
A: Managers should file a Group Disruption Report through the People Ops portal. Individual employees are still required to update their NimbusConnect™ status independently.
Q: What if an act of God or force majeure event prevents me from making contact?
A: After 72 hours without contact or NimbusConnect™ activity, your status will be changed to “Unresponsive.” After an additional 72 hours (6 calendar days total), Nimbus will presume you are among the missing and your access, benefits, and employment will be terminated. You will be marked as non-rehireable in our system. In the event that your designated next of kin contacts Nimbus within 90 days to return company equipment, a one-time survivor benefit of $2,500 (pre-tax) will be issued to the estate. For details, see Bereavement & Succession Policy 11.4.
11 / 12
Comments
TM
Tanya M.6h ago
Quick flag — Legal updated the “next of kin” definition to match the new federal definition per the latest EO, which I think changes some things for people with nontraditional family structures? But Jake said we just have to match the federal definition, not explain it, so we should be fine. I updated the link to the Bereavement policy.
TM
Tanya M.5h ago
Also, $2,500 feels low? I mentioned it to Chris and he said it’s been the same amount since 2019 and hasn’t been adjusted for inflation but that’s above my pay grade lol. The equipment return requirement makes sense to me — we can’t just write off a $1,400 laptop every time someone goes missing.

Together We Soar

At Nimbus, we believe that resilience isn’t just a response to adversity — it’s a core competency.

Every one of you brings something irreplaceable to this organization. Your talent, your dedication, your willingness to show up even when showing up is hard — that’s what makes Nimbus more than a company. It’s what makes us a force.

So as we navigate this quarter together, remember: the storm is temporary. Your impact is permanent.

Let’s soar.

Helping You Soar in Stormy Weather™
12 / 12
Comments
TM
Tanya M.3h ago
I LOVE this ending. So inspiring. I think this really captures who we are as a company. One tiny note — should “irreplaceable” stay? Given the FAQ, I want to make sure it doesn’t read as contradictory.
TM
Tanya M.2h ago
Can we get this finalized by Thursday? I want to present it at the all-hands. Excited to share! 🚀
TM
Tanya M.2h ago
Oh one more thing — Pexels requires attribution, so here are the image credits. Should I add them per slide or do a credits slide at the end?

Slide 1: cottonbro studio, pexels.com/photo/5483188
Slide 2: Earth Photart, pexels.com/photo/36497527
Slide 3: Tiger Lily, pexels.com/photo/7108454
Slide 4: cottonbro studio, pexels.com/photo/5473892
Slide 5: Andrea Piacquadio, pexels.com/photo/3894228
Slide 6: Mart Production, pexels.com/photo/7643797
Slide 7: Tima Miroshnichenko, pexels.com/photo/5725432
Slide 8: Isabella Mendes, pexels.com/photo/7822112
Slide 9: Derrick Della, pexels.com/photo/36004801
Slide 10: Christhian Gruhh, pexels.com/photo/4781398
Slide 11: Pixelcop, pexels.com/photo/2680270
Slide 12: Engin Akyurt, pexels.com/photo/5674762