A File Naming System You Will Actually Follow

Start the name with the date in a sortable format, such as 2026-11-11. Use hyphens rather than spaces, which avoids problems when files move between systems. A vague complaint like slow or broken sends people to the shop; a measured symptom sends them to the setting.

Describe the actual problem

Keep the name descriptive but short, with the most important word near the start. Use a small set of categories rather than dozens of folders. Most home technology problems are configuration problems, and configuration is free to change.

Try the free fix first

Keep the folder structure shallow, usually two or three levels. Avoid special characters, which cause issues with syncing and backups. Changing several settings at once hides the cause and makes the next problem harder to solve.

Before changing a setting, describe what you expected and what actually happened. Most home technology problems are configuration issues, and a specific symptom points to a specific setting. Change one thing at a time, test it, and note the result, because several changes at once hide the cause. Keep the manual and the model number in one place so the next problem is faster to solve. A note of the model number, the current settings, and the date of the last change turns a frustrating afternoon into a five-minute fix. If a device has no manual, save the support page offline. The goal is not to memorise the system but to leave a trail that makes the next visit easier.

Use version numbers or dates rather than final and final-final. Keep a short note of what you changed and when, because the same fault usually returns.

Check these first

• Date first, sortable format
• Hyphens, no spaces
• Shallow folder structure
• Rename files on arrival

Change one thing at a time

Keep personal and work files separate at the top level. Archive old projects into a single archive folder rather than deleting them. Buy hardware only when the free options have been tested and written down.

Use search rather than remembering the folder. Agree the convention with anyone who shares the files.

Write down what worked

Rename files when they arrive, not later, since later never happens. Keep a short note explaining the convention where everyone can see it. A five-minute monthly check prevents most of the failures people describe as sudden.

If the first fix does not work, undo it before trying the next one. Stacked changes make a simple fault look complicated and cost more time than starting again. Write down what you changed, when, and what happened, so a returning fault is quicker to identify. Replace hardware only after the free options have been tested and recorded, not because the device feels old.

Back up the structure rather than individual files. Review the top-level folders once a year and merge duplicates. The best system is boring, consistent, and easy to explain in one sentence. If you want the wider picture, read Keep an Inventory of Your Home Devices before you decide.

For the underlying guidance, see the FCC home network guidance.