The date next to a document in a shared folder can be misleading. It may be the day the file was copied, the day someone edited it or the date your computer assigned when it finished downloading. If you need to know when a bill arrived or which version of a handover went to a colleague, the file browser alone may leave you guessing. Give the important dates in shared files a purpose and a consistent home so everyone can read them the same way.
Decide which date tells the story
Suppose a repair takes place on 3 May, the invoice arrives on 6 May and you photograph it on 10 May. All three dates are real and each answers a different question. Putting 10 May in the filename makes sense for a batch of scanned paperwork. Putting 6 May in a payment tracker makes more sense if you sort by the day an invoice reached you. Keep the repair date in the record itself so you can find it without looking through every attachment.
Choose one date for the filename across a collection and write the rule beside the folder. For example, a household folder can use the printed invoice date, while a collection of meeting notes can use the day the meeting took place. Put a short description after the date, like 2026-05-06-kitchen-repair-invoice.pdf. That is easier to scan than a group of files called scan001.pdf and still tells you what the date refers to.
Use a date pattern people can read consistently
A name like 06-05-2026 might mean 6 May to one person and 5 June to someone else. A year-month-day pattern such as 2026-05-06 keeps the order clear. Use four digits for the year and two digits each for the month and day. This also makes filenames that begin with the date sort in chronological order when the folder is sorted by name.
For a handover that contains a range of dates, keep the first relevant date in the filename and put the entire range in the title or first paragraph. People looking at a crowded folder can spot when a project began. People reading the document can see whether it covers a single visit, an entire week or the period between two meetings. An attachment that describes several distinct events can use a short timeline inside the document.
Keep the local time when a deadline matters
A date on its own is enough for many files. If a deadline falls at a specific hour or several people are working in different time zones, record the local time together with the zone or the offset shown by the original notice. For instance, 2026-06-04 17:00 UTC+01:00 includes information that is missing from 4 June, 5 pm. If the original notice gives a named zone, keep that wording beside the converted time.
When a checkout screen says that a bonus ends at midnight, save the original wording and note which calendar day and time zone the terms use. An offer ending at midnight may be shown separately from the time your confirmation email arrived. Treat the two as separate entries. If the terms leave the zone unclear, enter “time zone unspecified” and keep the original message for reference.
Make room for uncertain or corrected dates
A family photograph marked “summer 1998” contains useful evidence. Assigning it a day and month creates a level of precision the original caption never supplied. Enter the year and season as written, or use a field for approximate dates. Where a spreadsheet requires a precise date, leave it empty and add an explanatory note in a separate column.
If someone later finds better evidence, make the correction easy to trace. A short note might say that the envelope originally gave June, while a printed receipt placed the event in July. Keep the source photo or note with the record. A correction log can be a line at the bottom of a document, headed “Date corrections,” with enough detail for a future reader to understand the change.
Separate a new version from a new event
Suppose a group sends a draft agenda on 12 July and edits one item the same evening. The meeting date can remain at the front of the filename. A short version label such as v02 tells the group which copy came later. For documents sent outside the group, record the sent time in the checklist or message that accompanies the file. A version label explains the sequence of edits and the sent time explains what a recipient actually got.
Apply this practice to the records people use and retrieve regularly. There is little benefit in renaming hundreds of old downloads in one sitting. Start with a shared folder whose contents currently cause questions, write a short naming note and use it for the next three files. Add the field notes index to the folder’s introduction so a new member of the group can find the date checklist when it is time to name the first file.
Shared file date checklist
- Write down the event that determines the filename date for this folder.
- Use a fixed year-month-day pattern, followed by a description readers can recognise.
- Preserve the original wording for dates or times received from another person.
- Add the time zone when a cutoff or a cross-zone handover depends on it.
- Give later drafts a version number and say which one was sent when that matters.
- Keep uncertainty and subsequent corrections beside the record.
Try the naming convention by asking someone else to locate a file from a description and a date. If they find the right item without asking where the date came from, the rule is working. If they regularly open a document for the wrong week, adjust which date appears in the filename or add the missing date where people look first.