File naming: consistent, descriptive, sortable, versioned

A file name is useful in an office workflow when it lets anyone find, sort, and identify the right version without opening the file. The key is consistency: use the same pattern every time, such as date first (YYYY-MM-DD), then project code, then content type, then version number, and optionally the owner's initials. For example, '2025-03-21_ProjectX_Report_v02_JW.docx' sorts chronologically, shows what it is, and marks the version clearly. The contrast is a name like 'Report_FINAL.docx' — it sorts alphabetically under 'R', tells you nothing about the date, and 'FINAL' is ambiguous because there might be a 'FINAL_v2' later.

A common exam trick is to offer a name that seems descriptive but breaks sorting, such as 'March Report v3' — months sort alphabetically, not chronologically, so April comes before March. Another trap is a name with no version marker, like 'ProjectX_Report_JW.docx' — you cannot tell if it is draft one or the final. To eliminate wrong options, check if the name starts with a date in YYYY-MM-DD format, includes a version number (e.g., v01, v02), and avoids words like 'final', 'draft', or 'old' that are not part of a standard pattern. If a name uses 'final-final' or 'latest', it is almost certainly wrong because it is not sortable and invites confusion.

To test a file name quickly, ask: would it sort correctly in a list of 50 files? If the date is not first or the version is missing, it fails. A memory aid: think of the acronym 'DCVO' — Date, Content, Version, Owner — and check that each element is present and in a logical order. If a question gives you a name like 'Report_v2_2025-03-21.docx', notice the date is not first, so it will not sort by date; that is a clear sign to reject it.