
If you're back in your building after the fires, the tech side of recovery usually starts with one question: is any of this still safe to use?
Here's a straightforward way to check, without guessing your way through it.
It's tempting to plug everything in and see what still works. Resist that for a minute.
Take a look first. Anything with visible scorching, melted plastic, water exposure, or a strong smoke smell shouldn't be powered on until it's been checked out. Powering on damaged equipment can turn a fixable problem into a total loss.
If you're not sure whether something looks bad enough to matter, treat it like it does. It's a lot cheaper to have something inspected than to fry a server trying to save time.
Smoke damage isn't always obvious. A few things worth checking for:
Smoke residue is often corrosive. Even if a device powers on fine today, that residue can quietly damage internal components over the following weeks. This is one of those cases where "it seems fine" isn't the same as "it's fine."
If your power cut out suddenly instead of shutting down normally, that matters more for some equipment than others.
Workstations usually recover fine. Servers are more sensitive, since they're often mid-process when the power drops. An unexpected shutdown can lead to corrupted files or a server that won't boot cleanly the next time.
If you have a UPS (battery backup) on your server, check whether it actually did its job. If you don't have one, this is worth adding once things settle down, since it's one of the simpler ways to avoid this exact problem next time.
A single damaged workstation is usually an inconvenience. A damaged server can affect your whole team at once, so it's worth being more careful here.
Before assuming a server is fine, check that it boots all the way through, that shared drives are actually accessible, and that nothing is throwing errors on startup. If anything feels off, even something small, it's worth getting a second opinion before relying on it for daily work.
If a device doesn't turn on the first time, resist the instinct to keep trying repeatedly. Repeated attempts can sometimes cause more damage than the original event, especially with damaged wiring or a compromised power supply.
One attempt is reasonable. After that, it's worth having someone take a proper look rather than troubleshooting blind.
Once your equipment is back online, don't assume everything's working the way it did before. Worth checking:
This is a good moment to confirm your backups are actually running, not just installed, since that's easy to overlook when everyone's focused on getting back to normal.
Basic checks are fine to do yourself. Anything involving visible fire, heat, or water damage, or a server that won't boot cleanly, is worth a professional hardware inspection before you trust it with daily business use.
It's a small step that can save you from losing something you thought was already handled.
If you're just getting back into your building and haven't worked through the broader recovery process yet, the full recovery checklist is a good place to start.
No pressure, no jargon, just a clear, honest picture of where your business stands.