Skip to main content
Most of the work in this knowledge base points at an asset that lives somewhere else. This page is the index of those locations. Check here before briefing new work. An approved asset that already exists, or crops to fit, is faster than a brief and has already cleared review.
Fill in the links, owners, and structures below with your own. Examples use Doughnut Labs, a SaaS company that sells disruptive Doughnut Technology.

​
The locations

​
What belongs where

Two questions decide where an asset goes: what kind of file it is, and whether it is finished.
Drafts and works in progress stay in the project folder they were made in. The drives hold approved assets, so that anyone pulling from them can use what they find without checking whether it was signed off.

​
Working with the drives

1

Search before you brief

Check the relevant drive first. Reusing an approved asset skips both production time and review.
2

Name it before you upload

Every file follows the file naming conventions. An asset saved under a name only its maker understands is not findable by anyone else.
3

Version, don't overwrite

Save a new version rather than editing over the old one, so the history stays intact.
4

Link it back to its brief

An asset should be traceable to the brief that produced it, and the brief should link to the finished asset.

​
Access

Keep this page current. A directory that points at a folder someone moved is worse than no directory, because it costs time before it fails. Review the links when a drive is restructured.
Last modified on August 10, 2026