The short version: A few shared habits for naming and storing our documents make everyone’s work easier, and they help protect the college, too.
Today, we can create and share just about anything in minutes. A department can set up a new workspace, a colleague can try an AI assistant for a first draft, and a faculty member can collaborate with a partner across the state. That speed is a strength, and it’s a big part of how Rogue gets great things done.
With so many places to create and store things, though, it can get harder to find the right version when we need it. Most of us have opened a folder and found “Final,” “Final_v2,” and “FINAL_USE_THIS_ONE” sitting side by side. (IT included. We’ve all been there!)
Why a little structure helps
Clear, consistent file names are a quiet kindness to our future selves and our colleagues. They help us:
- Find things faster. Predictable names mean less searching and more doing.
- Be ready when it counts. When we need a recovery plan or an audit document, we’ll know where it is.
- Protect student and employee information. Knowing where sensitive records live is a big part of staying FERPA-, HIPAA-, and PCI-compliant.
- Keep our knowledge. When someone changes roles or retires, their good work stays accessible for the team.
- Get more from AI tools. They work best with well-organized content, and they’ll make confident mistakes with a messy pile.
A friendly place to start
You don’t need a 100-page manual. A few simple habits go a long way:
- Pick one naming pattern and use it everywhere. For example: Department_DocumentType_Title_Version_YYYY-MM-DD
- Use a short list of document types. Policy, SOP, Charter, SLA, Report, and Plan cover most needs.
- Use standard dates and version numbers. Dates like 2026-10-29 and versions like v1.0 or v2.1 sort neatly and make the current version easy to spot.
- Give every document an owner. A named owner keeps it accurate and up to date.
- Mark where it is in its life. Draft, Approved, or Archived tells everyone how much to rely on it.
- Know where sensitive information belongs. If you’re not sure whether a document is sensitive or where it should be stored, just ask.
- Review AI-assisted drafts. AI can be a great starting point. Before a draft becomes official, have a named person review it for clarity and relevance.
Rules, guidelines, and good habits
Some of these practices are required, such as sensitivity labels and where official records are stored. Others are guidelines that leave room for your judgment, such as how to title a document for your team. The rest are habits that strong teams find helpful, like an occasional review of shared folders. We’ll try to be clear about which is which, so you always know what’s expected and what’s simply a good idea.
IT is here to help
The best standards are the ones that feel easy, so IT will keep working on templates, defaults and training that make the right way the simple way. If you have questions or would like help getting your team started, please reach out through IT Help Me.
Rogue Community College already has The Rogue Way: Naming Conventions Guide. I encourage everyone in the Rogue family to take a look and try it out. Thank you for all you do to keep our college’s knowledge organized and secure. 😊
— Richard Plott, Chief Information Officer and Chief Information Security Officer (CIO/CISO)