You open your laptop. You need the inspection report from last week. You know it exists. You saved it yourself.

But where?

Was it in the OneDrive project folder? The network drive? The local Projects directory? Did you email it to yourself at some point? Is there a copy on the desktop from when you needed to edit it quickly?
You spend three minutes finding it. Then you need the Excel load calculation that goes with it. Another two minutes. Then the CAD drawing the client sent. Another two.

Most engineers know the feeling intimately: six File Explorer windows open simultaneously, each navigated to a different folder, none of them closed because closing means losing the location. It is not disorganisation. It is a coping mechanism for a system that offers no better way to hold multiple places at once.

You haven't done a single minute of actual work yet. You've just been navigating folders. This is not a you problem. This is a structure problem.

See how Deckspace solves this in 2 minutes:

How Files Actually Get Scattered
The way most professionals store files makes complete sense in isolation. CAD files go on the network drive because that's where the licence server is. Client correspondence lives in OneDrive because it needs to be shared. Working files stay local because the network is slow. Downloads pile up in the Downloads folder because that's the default.

Each decision is logical. The result is chaos.

A single project say, a structural inspection for a bridge might have files in six different locations simultaneously, one in working folder, another in the "reference folder" "client docs" etc. There is no single place to go. There is only the mental overhead of remembering where each piece lives.

For engineers and consultants juggling three or four active projects at once, this compounds fast. The cognitive load of maintaining a mental map of where everything is stored is real, invisible, and exhausting.

Why Folder Structures Don't Solve It
The standard advice is to build a clean folder structure. One top-level folder per project. Subfolders by document type. Consistent naming conventions.

This works until it meets reality.
Reality is a client who sends files via email. A colleague who drops something on the shared drive in the subfolder that is most relevant for the organisation. A CAD file that has to live on the network drive regardless of your folder hierarchy. A downloaded PDF you forgot to move.

Folder structures are fragile because they depend on every file ending up in the right place every time. They break the moment the real world gets involved, which is immediately and always.
The deeper problem is that Windows organises files by location. You work by project. Those two things are fundamentally misaligned, and no folder structure fixes that mismatch, it just manages it.

The Actual Cost
Fifteen minutes a day finding files is a conservative estimate for anyone running multiple simultaneous projects.

Across a five-day work-week that is over an hour. Across a year it is more than sixty hours. A full working week and a half spent doing nothing except navigating a file system that was not designed for the way you work.

That number does not include the subtler cost: the context switching. Every time you go hunting for a file, you lose the thread of what you were doing. Getting back into deep focus after an interruption takes time. The file hunt is not just fifteen minutes. It is fifteen minutes plus the recovery time.

What Actually Helps
The fix is not a better folder structure. It is decoupling project organisation from file location.

Instead of moving files into the right place, you keep files wherever they naturally live and create a project-based view on top. The files stay on the network drive, in OneDrive, on the desktop, wherever they are. You simply maintain a workspace that connects them together under a project context.

This is how tools like Deckspace approach the problem. Rather than asking you to reorganise your file system, it lets you create project workspaces where you drag in links to your actual files, portals, in the app's language. The file stays where it is. The portal remembers the connection. Open your Bridge Upgrade workspace and every file for that project is right there, regardless of which drive it actually lives on.

The original files are untouched. The folder structure your IT department mandates is untouched. Nothing moves. You just stop having to remember where everything is.

A Practical Starting Point
Whether you use a dedicated tool or not, the principle holds: stop trying to force your files into a single location and start building a project-based index on top of wherever they live.

If you are on Windows, the simplest version of this is a pinned folder in Quick Access for each active project, with shortcuts to the most-used files inside. It is manual and fragile but it is better than nothing.

The more robust version is a tool that maintains those connections persistently, survives file moves with a relink, keeps notes and comments attached to individual files, and shows you exactly what you opened and when.

Either way, the goal is the same: open your laptop in the morning and go directly to your project. Not to a folder tree. Not to a search bar. To the work itself.

Fifteen minutes a day is too much to spend looking for things you already have.

Deckspace is a file workspace manager for Windows and macOS. It lets you create project workspaces and drag files from anywhere on disk into them as portal shortcuts. No files are moved or copied.
Lifetime purchase, no subscription. Can be tried free for 14-day without any commitment at deckspace.com.au.