The shared folder where everything is called final
A six-person project team keeps all documents in one network folder called Projects on a shared drive. There are 1,240 files in a flat list, many named final_v2_REAL_final.docx or draft (copy).docx. Two staff regularly overwrite each other's edits because they open files directly from the share. When someone works from home they copy folders onto a USB stick and paste them back, and last month an entire quarter's subfolder was deleted; it was restored only because the nightly backup from two days earlier still existed. The client now requires that every document have a traceable owner and a revision history. The team has no budget for new software beyond what is already included in Microsoft 365.
1. Identify the root causes of the overwriting and lost work, then propose a folder and naming convention with one concrete example filename.
Read the worked answer
Root causes. (a) A flat structure: 1,240 files with no hierarchy means nobody can find the current version, so people recreate it. (b) No naming rule, so words like final and REAL carry no meaning and sort arbitrarily. (c) Direct editing on a plain share, which has no co-authoring and no version history, so the last save wins silently. (d) USB round-trips, which create divergent copies that later get pasted back over newer work.
Convention. Top level by client, then year, then document type; a working area separate from issued documents. Filenames use ISO date, document type, owner initials and a two-digit version: 2024-06-14_Contract_ClientA_SM_v02.docx. Rules: never use final or copy, increment v01 to v02 rather than editing in place, avoid ampersands and hash characters, and move superseded versions to an Archive subfolder instead of deleting them. Completed work becomes read-only.
2. Design the access model for the share. Explain why giving everyone Full Control is a problem, what the intern should get, and how groups simplify this.
Read the worked answer
Full Control includes Change Permissions and Take Ownership as well as Delete, so one careless drag can remove a folder and alter who can fix it afterwards. That is exactly how the quarter's work disappeared. Staff should get Modify on the folders they own, with delete rights limited to a small named group; issued and archive folders should be Read-only for everyone except the document controller.
The intern should get Contribute to one staging subfolder and Read-only elsewhere: enough to work, not enough to destroy or approve.
Assign permissions to security groups (Team-Staff, Team-Interns, Team-Archive-Admins) rather than to individuals. Joiners and leavers then become a single membership change, permissions stay auditable, and nobody accumulates leftover rights from an old project. Because the team already has Microsoft 365, put the working area in a SharePoint document library or a synced team site: version history, co-authoring and a recycle bin are included, and the USB stick stops being part of the workflow, which also removes an uncontrolled copy and a malware route.
3. A colleague saves over a document that another staff member had been editing for two days. Describe the recovery steps in the order you would try them, and one change that makes the next occurrence a non-event.
Read the worked answer
Recovery, in order.
- Ask the person who overwrote it to stop editing and to leave the file open or untouched; every further save reduces the chance of recovery.
- Check the Recycle Bin, but expect nothing: deletions made over a network share usually bypass the local Recycle Bin entirely.
- Check Previous Versions or Volume Shadow Copies on the server for the folder.
- Check the SharePoint or OneDrive version history and the site recycle bin, which typically retains versions and deleted items for a set period.
- Restore from the nightly backup, always to an alternate location first and never over the live file, then compare before replacing.
Prevention. Make version history automatic by moving the working file into the SharePoint library, and stop sending copies as attachments. Then the next overwrite is a two-click restore rather than a two-day loss, and the restore point is measured in minutes, not in the 24-hour gap of the tape cycle. Test one restore per quarter so the team knows the process works.