Division Standard Naming Convention
This guide outlines the Division's standard file naming structure for all documents, images, and records uploaded into the electronic repository (Content Manager, Google Workspace, Windows Shared Drive, etc.).
Purpose
Consistent naming and tagging ensures:
- Clear identification of documents
- Improved searchability
- Long term organization
- Alignment across all departments
Naming Guidelines
- Use full words rather than abbreviations where possible
- Separate sections using dashes or underscores
- Use MM-DD-YYYY format for dates when a specific date is required
- Update the version number when revisions are made
- Ensure the title clearly reflects the content of the document
Naming Structure
All documents uploaded into Content Manager must follow the Division naming structure below. These elements should be separated by dashes:
Key Identifier
(Document or Record Type)
β
Version or Issue Number
β
Date
(Date Issued, Signed, or Approved)
Examples
- π Wellness_Newsletter_Issue_66_January_2026
- π Wellness_Newsletter_Issue_66_01-01-2026
- π Assistive_Technology_Device_Request_Form_v1_02-2026
- π HR_Annual_Report_2025
- π Finance_Atrieve_Procedure_v2_01-15-2026