Before the Mince Pies: A Shared Drive Reset That Makes January Kinder

It is 12 November 2026, which means the Christmas adverts have started and at least one person in your team has already said the words ‘let’s pick this up in January’. Fair enough. But before everyone down tools, there is one small piece of housekeeping that pays back almost immediately: a shared drive reset.

Not a full digital deep clean. Not a records-management project with a consultant and a flowchart. A 45-minute team routine, done once, before the break. It is the difference between January starting with a calm ‘here it is’ and January starting with a group chat called ‘does anyone know where the…’.

Why shared drives sag (and why it is not a character flaw)

Small UK teams accumulate folders the way kitchens accumulate takeaway menus. Someone saves a document as ‘final’, then ‘final v2’, then ‘final v2 USE THIS ONE’. A client changes their trading name. A freelancer leaves and their access stays. A project finishes but nobody moves it, because moving it feels like a job for a quiet afternoon that never arrives.

A Bristol design studio I heard about had three folders called ‘Brand Assets’ — one in the main folder, one inside ‘Old Work’, and one on a freelancer’s desktop that had been uploaded ‘temporarily’ in March. Nobody was lazy. They were busy. That is the normal state of a shared drive.

The aim here is not a beautiful taxonomy. It is a drive where a colleague can find the latest version of a document without opening four files and a spreadsheet. Boring, useful, done.

The 45-minute routine: one screen, one timer, one checklist

Book a slot. Call it ‘Shared Drive Reset — 45 mins’. Keep it to 45 minutes. If you have a team of three to fifteen, one person should lead from a shared screen, ideally with admin access to the drive. Have a parking lot — a blank note or a chat thread — for anything that needs a longer conversation. The rule is simple: if it takes more than two minutes to decide, park it.

Minutes 0–10: catch the obvious duplicates

Search the drive for ‘copy’, ‘final’, ‘old’, ‘backup’, ‘v2’ and ‘use this one’. You are not opening every file. You are looking for duplicate folders and obviously abandoned versions. Pick one master folder per client or project. Move the rest into a folder called ‘_Archive 2026’. Do not delete. Archiving is reversible; deleting at 4pm on a Friday is not.

Minutes 10–25: agree a naming convention people will remember

This is where teams overcomplicate. You do not need a 12-part code. Pick one pattern and write it down. For many small businesses, client-first works: ‘ClientName_Project_2026’. If chronology matters, put the date first: ‘2026-11_ClientName_Project’. Use hyphens or underscores consistently, and avoid spaces if your cloud drive struggles with links. The important bit is not the pattern itself; it is that everyone uses the same one.

A Leeds accountancy practice might use ‘ClientName_Accounts_2026’. A Manchester e-commerce team might use ‘SupplierName_Christmas_2026’. Both are fine. What is not fine is ‘Smith stuff new’ sitting next to ‘SMITH - FINAL’. Agree that ‘final’ is banned unless it has a date next to it. ‘Final’ is a feeling, not a version.

Minutes 25–35: archive what is finished

A project is finished if the invoice is paid, the handover is done, and nobody has emailed about it in the last 30 days. Move it into ‘_Archive 2026’. Keep active work in one clearly named ‘Active Projects’ folder. This is the bit that makes January feel lighter: the first screen you see is current work, not a museum of 2024.

Minutes 35–42: check who still has access

This is the quiet security job. List everyone with access to the shared drive. Remove anyone who has left, changed roles, or was a temporary freelancer. Check external sharing links — especially ‘anyone with the link can edit’. For cloud drives, ask your admin to review permissions rather than sharing passwords. Keep a short record of who removed what and when. It is not glamorous, but it is the difference between a tidy drive and a tidy drive with a side door open.

Minutes 42–45: leave a note for January

Create a one-page document at the root called ‘Read me first — drive rules’. Include the naming convention, where the archive lives, who owns the drive, and the date of the next review. Book a 30-minute review in the first week of January 2027. Then close the laptop.

The checklist

• Duplicate folders moved to ‘_Archive 2026’
• One master folder per client or project
• Naming convention agreed and written down
• Finished projects archived
• Access list checked; leavers removed
• External sharing links reviewed
• Drive owner named
• January review booked

What if the team disagrees?

Park it. Seriously. The 45-minute reset is not the place to settle the great ‘client vs project first’ debate. Note it, assign one person to bring a proposal to the January review, and move on. A drive that is 80% tidy today beats a perfect system that never gets finished.

Why this is worth 45 minutes

Because January is busy enough without a scavenger hunt. Because a new starter should not need a tour guide to find the template. Because ‘where is that file?’ is a small question that quietly drains a team’s patience. And because a calm shared drive is part of a calm workplace — not the whole thing, but a useful start.

So before the mince pies, put a timer on. One screen, one checklist, one team. Your January self will thank you.