How can a team continue shared work during a temporary internet outage?
Quick answer
Before an outage, identify tasks that do not require live access and confirm which tools and files are actually available offline. Agree on a temporary place to record edits, decisions, owners, and times, and avoid having several people independently change the same item. During the outage, capture changes rather than assuming they have synced. When service returns, compare records, resolve conflicts with the relevant owners, and confirm the final version.
The question, the details, the next step.
Our team may lose internet for part of a workday. How can we keep shared work moving without making a mess of everyone’s files?
Make a small offline plan rather than treating every task as if it can continue normally. First divide work into three groups: work that is ready to do offline, work that can proceed only if its files are already available, and work that needs a live connection or another person’s input. Check the actual tools and files your team plans to use; do not assume that an app’s offline behavior is the same across devices or documents.
Choose one temporary change log that everyone can access by an agreed method during the outage—for example, a paper sheet in a shared workspace or a local file prepared in advance. If the team cannot access a shared location, each person can keep a copy and assign someone to combine the entries afterward. The plan should say where updates go, who records decisions, and who resolves conflicts.
What should go in the change log? We need enough detail to reconstruct what happened, but it shouldn't become a second project.
Keep each entry short and traceable. Record the time, person or role, affected task or file, what changed, and whether the change is complete or waiting for review. Add a brief decision note when the team agreed to do something differently. Use a task name or file name that the team already recognizes; avoid creating a new naming system in the middle of the outage.
A copyable template is:
Time | Person/role | Task or file | Change or decision | Status | Follow-up owner
Example using placeholders:
[10:15] | [Editor A] | [Draft: launch outline] | Rewrote section 2 in local copy; left section 3 unchanged | Needs merge | [Project lead]
The example is only a format. Use names, times, and task references your team can identify, and follow any workplace rules for handling sensitive material.
How do we decide what people can work on while we're disconnected?
Assign tasks that have a clear starting point and do not depend on live information or another person’s immediate response. Examples might include drafting from material already available, reviewing a printed agenda, or making a list of questions for a later discussion. Treat these as possibilities, not guarantees: check that the needed material is accessible and that the task can be completed without opening a service that requires internet.
For work that could overlap, name one owner or assign separate sections. If two people must edit the same item, agree in advance who will make the main copy and how the other person will submit suggestions. For tasks dependent on live data, approvals, or shared updates, pause them or prepare a clearly labeled offline draft rather than treating an old copy as current.
When the internet comes back, should everyone just upload their saved work?
Not as a first step. Reconnect, check what has already updated, and compare that with the change log before replacing, merging, or renaming anything. One person can coordinate the review, but the owner of an affected task should confirm which edits and decisions are intended to remain. If two versions differ and the intended result is unclear, preserve both temporarily and ask the relevant people to resolve the difference rather than guessing.
Then update the agreed working version, mark each log entry as merged, rejected, or still unresolved, and tell the team where the current version lives. Close with a short note listing any remaining actions and their owners. This process cannot guarantee that every tool will preserve offline edits or resolve conflicts cleanly, so check the result in the relevant tool and keep a separate copy until the team confirms the work is complete.
A practical checklist
List tasks that can proceed offline, tasks needing prepared files, and tasks that should pause.
Check that each planned offline task and its required materials are available to the person doing it.
Choose a temporary change log and agree who records decisions and who coordinates reconciliation.
Assign one owner per shared item or define how overlapping edits will be submitted.
After reconnection, compare versions, resolve unclear changes with their owners, and confirm the current version and outstanding actions.
A few more useful answers
What if some teammates can get online and others cannot?
Keep the same change-log approach and make each entry clear about its status and owner. Avoid assuming that an online teammate’s view includes edits made offline elsewhere; compare records before treating a version as final.
Can we use personal copies of shared documents during an outage?
Only if your team’s rules allow it and the copies are appropriate for the material. Label copies clearly, record where changes were made, and agree how to reconcile them rather than silently overwriting the shared item.
What should we do if two people changed the same section?
Keep both versions while the difference is reviewed. Ask the relevant owners to choose or combine the changes, record the decision, and then update the agreed working version.