What to Do When Your Jobsite Loses Access to Project Files

Reviewed by Adam Pittman, founder and president of Computerbilities.

When a jobsite cannot open project files, establish what is affected, verify which drawing revisions are approved, and agree on a fallback with the project lead and IT provider. Give the field one clear contact and a time for the next update.

A superintendent opens a tablet and the drawing set will not load. The office can see some files, but the field cannot confirm which revision is current. Before someone starts emailing old copies or sharing a login, the team needs to know which work depends on the missing information.

The following construction IT downtime checklist gives the office, project team, and IT provider a shared starting point. If a ransom note or other sign of compromise appears, follow the security-incident step below before attempting a workaround.

1. Establish the scope of the interruption

Ask one person at the affected location to coordinate the report. Record when the problem started, which application or folder is unavailable, and the exact error message. Then establish whether it affects one employee, everyone at that jobsite, or people at several locations.

Be specific about what still works. Can the superintendent open other business applications? Can the office access the same project folder? Is the device connected, but access to one file denied?

Those observations help IT distinguish a connection problem from an account, permissions, application, or file issue. Repeatedly restarting equipment before reporting the symptoms can make the sequence harder to reconstruct.

Use your approved support channel. Remove passwords and sensitive project details from screenshots shared outside that channel.

Copy this into your outage report:

• Affected jobsite and project:
• Time first noticed:
• Application, folder, or device affected:
• Exact error message:
• People or locations affected:
• What still works:
• Work or deadline waiting on access:
• Project contact and callback number:

2. Confirm which information the field can trust

An available file is useful only if the team can establish that it is the correct approved version. A recent download date does not establish that a drawing is current.

Have the person responsible for project documents confirm the revision, approval status, and intended use of any temporary copy. The project lead should decide which activities can continue under the site’s existing safety and document-control procedures.

For example, a delivery may be recorded while access is being restored, but a task that depends on an unverified drawing detail needs the project lead’s decision. IT should not make an unofficial design or field-work decision through a technical workaround.

Tell crews which source is approved and who will communicate any change. Avoid circulating several competing document sets without a named owner.

3. Choose a fallback that fits the actual problem

Depending on your systems and site conditions, an approved fallback might include a tested secondary connection, a controlled offline document set, or an office employee retrieving a verified file for the field.

Have IT confirm that the workaround addresses the interruption. A backup internet connection will not resolve every permissions problem or cloud application outage. Offline access also depends on whether the required documents and permissions were prepared before the connection failed.

Keep company files in approved locations and use individual authorized accounts. Moving plans into a personal file-sharing account or sharing another employee’s credentials introduces a different problem while the original one remains unresolved.

Write down who approved the fallback and when it should end. For temporary field records, agree on how to capture time, photos, delivery information, and notes—and who will enter or reconcile them when the normal system returns.

4. Escalate signs of a security incident

A missing connection and a suspected account compromise need different responses. A ransom note, unexpected changes to file extensions, or unexplained account activity should trigger the company’s incident-response procedure.

Contact IT through a known phone number or another approved channel that does not depend on the affected system. Let the response team direct containment and restoration. Do not have several employees attempt unrelated fixes while a possible security incident is being assessed.

The joint CISA, FBI, NSA, and MS-ISAC StopRansomware Guide recommends keeping incident-response and communications plans available offline. Make sure the people who need the plan can reach it without opening the system that may be unavailable.

5. Agree on recovery priorities and the next update

Tell IT which business deadlines are closest. A bid due this afternoon, a payroll cutoff, and drawings needed for tomorrow’s work may require different systems. Operations should identify the business priorities; IT should confirm the technical recovery sequence.

Ask for the next update time even if a restoration time is not yet known. Give the field a short, factual message:

Project-file access is affected at [location]. [Name] is coordinating with IT. Use [approved fallback] for [approved activities]. The next update will be at [time].

This is a communication template, not a promise that every outage has a safe fallback. Replace each bracketed item with confirmed information before sharing it.

6. Check the recovery and close out temporary work

When access returns, have the document owner confirm that the correct files and revisions are available and that the right people can open them. A successful login is only one part of that check.

Reconcile temporary records, identify conflicting copies, and tell employees when to stop using the workaround. Record the established cause, the work affected, and the time required to recover. Assign an owner and date to each improvement you choose to make.

One practical follow-up is a test restoration of a sample project folder. Ask which data is protected, who can restore it, and whether the recovered files are usable. The StopRansomware Guide recommends offline encrypted backups and regular recovery testing. Discuss how your provider applies those principles to your systems; a successful synchronization or backup status message is not a completed recovery test.

Build the plan before the next interruption

Download Keep Your Projects Moving: Construction IT Checklist & Downtime Plan. It includes 15 readiness checks, a downtime-cost worksheet, an outage and recovery plan, and a 30-day action planner.

Complete it with your project lead, office team, and IT provider. Start with one active project so your contact list, fallback arrangements, and recovery priorities are specific enough to use.

Based in Cary, Computerbilities helps construction businesses with 10–250 technology users across Raleigh, Cary, Durham, and the NC Triangle. Explore our construction IT support or book a free 15-minute IT risk call. You can also call 919-469-5060.