On this page

At 9:40 a.m., the office can’t open shared files. People are asking whether to keep trying, work from downloaded copies or send customers home. The owner gets an email saying, “We’re investigating.” That may be true, but it leaves the owner to make three decisions with almost no information.

Two people discussing work with a tablet and smartphone
Photo: Alejandro Escamilla, CC0. Cropped and resized for display.

I’d rather have a short update that says what’s affected, what staff can do now and when we’ll talk again. The cause may still be unknown. There’s usually something useful to tell the business before we know exactly why a system stopped.

An update should help somebody decide what to do next

Here’s the sort of first update I’d want in that shared-file outage:

As of 9:45 a.m., we’ve confirmed that the office can’t open the shared drive. Email and phones are working based on checks with the front desk. We’re checking the file server and the connection to it. For now, keep working in email and avoid editing downloaded copies of shared documents unless your manager assigns someone to reconcile the changes. Dana will pass this on to staff. I’ll call Dana with the next update by 10:15, even if we’re still investigating.

That’s enough for Dana to send one message to staff and decide who needs a workaround. The update says how the phone and email information was confirmed and makes it clear that 10:15 is the next update. It gives the owner something more useful than a guess at when everything will be back.

For another business, the immediate question might be whether to pause shipping, route calls to another location or use a vendor’s downtime procedure. Whoever runs that part of the business should make the call. IT’s job is to explain the options and what could happen if employees start working in two places at once.

Give the next update when you said you would

If it’s 10:15 and the drive is still down, there’s still an update to give. Say what you learned, whether the advice to staff has changed and when they’ll hear from you again. “We can reach the file server, but employees still can’t open the shared folders. We’re checking access from an ordinary employee account. Continue using the earlier workaround. Next update by 10:45.” That’s more specific than another “still investigating” and gives the business a reason to keep using the current plan.

If email is part of the outage, make sure the update has somewhere to go. Agree on a call or text contact ahead of time and have a backup person. I’d keep the distribution simple. One person at the business should know who needs the update, and employees should know where to get it. Sending separate technical notes to everyone who reported a problem can leave staff acting on different versions of the story.

Close the loop with someone who does the work

When the share comes back, ask someone to open a real working file with their normal access and save an agreed test change. If staff created offline copies during the outage, tell them who will reconcile those before they put anything back in the shared folder. The owner needs to know which work can resume and which cleanup still belongs to someone.

Later, a short follow-up can explain the cause if it’s known, what was restored and whether there’s any work to prevent a repeat. If the cause is still under review, say who’s looking at it and when the business will hear more. You can use the IT support contract guide to compare how providers describe support obligations. I’d also ask them to show an example of an outage update. A response-time commitment tells you when someone should answer. The example shows what that answer will help you do.