A good filename is a label, not the whole record. It should help someone identify the subject and document without opening six files named “scan.pdf.” The record itself should still hold the verified dates and context.
Pick one pattern and define the date
A useful pattern is subject, document type, then a date: “Unit12_Registration_2026-10-13.pdf” or “DriverName_License_2026-10-13.pdf.” Decide whether that date means issue, expiration, or upload date and use the same definition consistently. If your office handles sensitive identifiers, leave them out of filenames unless your policy requires them.
File by the record, not the uploader
An employee credential belongs with the employee profile; a truck inspection belongs with the truck. Police contract evidence belongs with the relevant project, and an impound photograph belongs with the vehicle case. A shared inbox can be an intake point, but it should not be the only place another shift can find the evidence.
Do a retrieval test
Give a teammate a question: “Find the current document for Unit 12 and explain the next recorded date.” If two files look current, add context and verify the source before changing the date. If the file is blurry or cropped, ask for a better copy. Do not mark a record complete because the filename looks right.
TowAdmin attaches files to company records so the next reviewer has a place to start. The tow-truck paperwork guide and driver renewal guide show how naming fits into a broader review routine. Follow your company's retention and access rules for older versions.