By the end of this lesson you will be able to
- Apply a naming convention that sorts files in a sensible order.
- Design a simple folder system for a project, a class or a job.
- Keep versions of a document without losing work or confusing colleagues.
- Explain in plain words what version control does and why people use it.
- Avoid characters and habits that cause file name errors.
Almost everyone has seen a folder containing report.docx, report_final.docx, report_final2.docx and report_REALLY_final.docx. Nobody knows which one is right, including the person who made them. A few small habits in naming and organising files solve this. They make your own work easy to find in six months, and they make it possible for a colleague to pick up your files without calling you first.
A name is a label other people must understand
A file name has two jobs. It should tell a person what is inside, and it should help the computer sort files into a useful order. Names like new.docx, scan0023.pdf or Document1 do neither. A rule that every file follows, a naming convention, takes the guesswork out. It needs no software, only agreement and a little discipline.
A simple naming convention
A good recipe for most people is: date, topic, detail, version, separated by hyphens or underscores, with no spaces. Put the date first as year-month-day, because then the files sort in time order automatically. Use lower case or a consistent style so that you never wonder about capitals.
2025-03-14DateYear-month-day sorts correctly_separatorbudgetTopicWhat it is about_separatoreventDetailWhich one_separatorv02VersionTwo digits.xlsxExtensionFile type; leave it aloneRead this figure as text
The file name 2025-03-14_budget_event_v02.xlsx split into date, topic, detail, version and extension.
The file name 2025-03-14_budget_event_v02.xlsx is split into five parts. 2025-03-14 is the date, written year, month, day so that files sort in time order. budget is the topic. event is the detail. v02 is the version number, with a leading zero so that v10 sorts after v09. .xlsx is the file extension, which tells the computer the type and should not be changed by hand.
| Poor name | Problem | Better name |
|---|---|---|
| final_final2 (copy).docx | Nobody knows which is latest; brackets and spaces are awkward | 2025-04-02_report_science-fair_v03.docx |
| 14-3-25 budget.xlsx | Day-month-year does not sort by time | 2025-03-14_budget_event_v02.xlsx |
| Scan0023.pdf | Says nothing about the content | 2025-02-20_electricity-bill_jan.pdf |
| Amina's CV!!.docx | Punctuation can cause errors in some programs and websites | amina-wanjiru_cv_v04.docx |
| Photo of the trip with Joseph and everybody at the lake in July.jpg | Too long, and may be cut off | 2025-07-12_lake-trip_group.jpg |
A folder system other people can follow
Folders work like drawers in a cabinet. The aim is that anyone can guess where a file is. Keep the structure shallow, usually no more than three or four levels, and group by something stable, such as project, subject or year. Avoid a folder called Misc or New folder, which will fill with things nobody can find.
- science-fair-2025
- 01-planningBrief and timetable
- brief.pdf
- 02-researchNotes and sources
- 03-draftsWorking versions
- 2025-04-01_report_v01.docx
- 2025-04-03_report_v02.docx
- 04-finalThe one to submit
- 99-archiveOld versions
Read this figure as text
A tree of folders for a school science fair project with planning, research, drafts, final and archive folders.
A folder named science-fair-2025 contains five folders. 01-planning holds the brief and the timetable. 02-research holds notes and downloaded sources. 03-drafts holds working versions of the report, for example 2025-04-01_report_v01.docx. 04-final holds the one finished version to submit. 99-archive holds old versions and anything no longer needed. The numbers at the start of folder names keep them in the order of the work.
Use the same structure for each new project. When every project looks the same inside, you stop thinking about where things go. Put files in the folder as soon as you create or download them, not at the end of the week.
Versions: keeping the past without the mess
A version is a saved state of a document at one point in time. You keep older versions for good reasons: you might want to go back after a bad edit, compare two drafts, or show who changed what. The simplest method is to save a new file with the next version number whenever you make a significant change, and to keep the old ones in the drafts or archive folder.
- Step 1: v01First draft
- Step 2: v02Save As after a big change
- Step 3: v03After feedback
- Step 4: FinalCopy to the final folder
- Step 5: ArchiveMove old versions away
Read this figure as text
A flow from version 01 through version 03 to the final file and archive.
Five steps. 1: create v01, the first draft. 2: after a significant change, use Save As to create v02 and carry on in v02. 3: after feedback from a teacher or colleague, save v03. 4: when it is approved, copy the file as the final version into the final folder, with a name that ends in final or the submission date. 5: move earlier versions into the archive folder, so the working folder has only the latest.
Many online tools do this for you. Cloud office tools and cloud storage keep a version history, which lets you see earlier saved versions and restore one. It is a good safety net, but it does not replace your own naming. It also depends on the service, so check how long old versions are kept.
Version control: the same idea at scale
Version control is software that records the history of a set of files automatically. Instead of you copying files and typing v02, the software keeps a series of snapshots. You choose when to take a snapshot and write a short message saying what changed. Later you can see exactly what changed between any two snapshots, go back to an old one, and let several people work at once and combine their changes. You met the best known tool, Git, in the web project lessons, where each snapshot is called a Commit.
- Files named v01, v02, v03
- Good for one document, one person
- Relies on your discipline
- Does not record exactly what changed
Simple and enough for most documents.
- Snapshots with a message each
- Good for projects and teams
- Records who changed what and when
- Compare any two versions, restore old ones
Worth learning for code and large projects.
Read this figure as text
A comparison of manual file versions and version control.
Two columns. Manual versions: you save new files named v01, v02 and v03; good for a single document and one person; relies on your discipline; many copies take space and the history of exactly what changed is not recorded. Version control: software takes snapshots with a message on each; good for code and projects with many files and many people; records who changed what and when; lets you compare any two versions and restore an old one.
You do not need version control for a school essay. You do need to know it exists, because many workplaces use it, and because the habits it teaches are the same ones you can practise now: small, named, recorded changes.
Common mistakes
✖ Instead of: Using words like final, new or latest in the file name.
✔ Do this: Use version numbers and dates. 'Final' is true only until the next change.
✖ Instead of: Changing the extension by hand, for example from .docx to .pdf.
✔ Do this: Renaming does not convert a file. Use Export or Save As to make a real PDF.
✖ Instead of: Keeping everything in Downloads or on the Desktop.
✔ Do this: Move files into their project folder as soon as you save or download them.
If something goes wrong
- Windows says 'The file name you specified is invalid' or 'A file name can't contain any of the following characters'.
- Remove the characters \ / : * ? " < > | from the name. Use a hyphen instead.
- I cannot tell which of several files is the latest.
- Look at the Date modified column in your file manager, open the likely file to check, then rename it with the next version number and move the others to the archive folder.
- My files do not sort in the order I expect.
- Check that the date comes first as year-month-day and that version numbers have two digits (v02, not v2), so that v10 comes after v09.
Key terms
- Naming convention
- An agreed pattern for naming files so they are easy to find and sort.
- Version control
- Software that records the history of a set of files, so you can see changes, compare them and go back to an earlier state.
- Version history
- A record of earlier states of a file, so that you can go back to an older one.
- Git
- A tool that records the history of changes to your project files so you can go back to earlier versions.
- Commit
- A saved snapshot of your project in Git, with a short message saying what changed.
Practise it for real
Reading is not the same as being able to do it. Complete these on your own computer, then tick only what you have actually done. These ticks are your own honest record: nothing checks them for you.
Rename and organise a practice set
Create a folder called naming-practice inside your practice folder. Inside it, create six empty or sample files with poor names such as Document1.docx, final copy.txt and IMG_0042.txt. Rename each using the convention date, topic, detail, version. Create folders 01-planning, 02-drafts and 99-archive and move the files to suitable places. Do all of this only with made-up files.
Challenge: design a system for your own studies
On paper, design a folder structure and naming convention for something you really do, such as a course, a small business or family paperwork. Write the rule in one sentence, draw the folders up to three levels deep, and write five example file names. Then ask a friend to find a given document using only your rule.
Knowledge check
6 questions. You need 80% to pass. Mistakes here are part of learning, and you can retry as often as you like.
Summary
- A naming convention of date, topic, detail and version makes files easy to find and sort.
- Write dates as year-month-day and avoid spaces, punctuation and very long names.
- Use a simple, shallow folder structure and use it the same way every time.
- Save numbered versions with Save As and archive old ones; versions are not backups.
- Version control software does the same job automatically for projects and teams.
Checklist: can you do these?
Marking a lesson as read does not prove you can do it. Skills count as demonstrated when you pass the quiz (not yet) and complete the practical tasks (not yet).
Related lessons
References and further reading
Official sources for details that can change between versions.
- Pro Git book (Git)
- Naming conventions for files and folders in Windows (Microsoft Learn)