Who this guide is for
Anyone creating files, folders, datasets or shared collections that people, NAVI, integrations or future workflows will need to identify reliably.
The NAVI AI Enablement Journey · Guide 07A companion
Naming Files and Folders
A short guide to making shared work easier to recognize, sort, search, hand off, and maintain—especially when AI makes it possible to create more material, faster.
Core idea
A good name answers the next user’s first question without trying to tell the whole story. Use the shortest name that clearly distinguishes the item from the things around it.
When to use it
Use it when creating a structure, cleaning inconsistent names, resolving retrieval ambiguity or preparing content for collaboration, automation or long-term maintenance.
Decisions it helps make
Choose the minimum useful context, stable identifiers, dates, versions and status signals—and decide what unnecessary wording should be left out.
How to continue
Apply the naming rules inside the relevant Knowledgebase, Workspace or workflow design. This is a companion reference, not a required stage.
Ask NAVI to apply this guide
“Use Guide 07A to review these file and folder names. Recommend concise, consistent names that support human recognition and reliable retrieval without adding unstable or unnecessary detail.”
Why it
matters
matters
This feels trivial until it isn’t
Naming can feel unimportant until months or years of work accumulate. A few extra seconds of care now can prevent repeated confusion later. As files, folders, generated outputs, and automated workflows multiply, consistent names become part of the system’s working memory—for people and AI. It is a small habit that your future team—and your future self—will appreciate.
Two
pillars
pillars
Minimal and clear
These goals reinforce each other until a name becomes so short that it loses meaning—or so descriptive that it becomes a sentence.
Minimal
Do not repeat the folder path, add decorative numbers, preserve obsolete status words, or encode information that already lives reliably in metadata or version history.
Clear
Use familiar language, stable terms, and the most useful distinguishing idea. A new teammate should be able to make a reasonable guess about what the item contains.
Four useful
patterns
patterns
Choose the first element based on how the set will be used
There is no universal formula. The best convention depends on what people need to recognize or sort first.
Pattern A · Recommended default
Subject first
Primary question: What is this?
client-onboarding-checklist.html
pricing-model.csv
knowledge-content-lifecycle-sop.html
Use plain, specific language for most working documents, folders, guides, and reusable assets.
Strong fitEveryday work where topic and purpose matter most.
Watch forGeneric words such as notes, document, stuff, new, or misc.
Pattern B
Date first
Primary question: When did this happen?
2026-07-28-client-review-notes.md
2026-07-monthly-usage-report.pdf
2026-q3-planning-session.html
Use when chronological order is central: meeting notes, logs, recurring reports, releases, recordings, or dated snapshots.
Strong fitTime-series material that people naturally browse by date.
Watch forAdding dates to evergreen files merely because they were created on a date.
Pattern C
Sequence or identifier first
Primary question: Where does this belong in a defined system?
03-structuring-a-knowledge-base.html
PRJ-042-installation-plan.pdf
EP-017-mix-notes.txt
Use when the number communicates a real sequence, stable record ID, or documented category—not merely a preference to keep something at the top.
Strong fitOrdered guide series, cases, projects, episodes, assets, or controlled records.
Watch forNumbers that carry no distinct meaning or must be constantly rearranged.
Pattern D
Stable name with a qualifier
Primary question: Which kind, state, or version is this?
proposal-internal.docx
proposal-client.pdf
pricing-model-v03.xlsx
logo-dark.svg
Add a short suffix only when related variants must coexist and cannot be distinguished reliably through location, format, or system version history.
Strong fitExports, variants, deliverable formats, and deliberate version sets.
Watch fordraft-final-final2, latest, new, revised, or unexplained initials.
Numbers
Use numbers when they encode structure
Numbering is useful. Decorative numbering is not. The test is whether different numbers communicate different, durable meaning.
Numbers help when they represent
- A deliberate reading or operating sequence
- A stable project, case, asset, or record identifier
- A documented category system used by the team
- A large sequence that must sort predictably
Numbers create noise when they
- Exist only to force several items to the top
- Repeat the same prefix across unrelated folders
- Duplicate numbering at several levels without adding meaning
- Require a legend that nobody maintains or uses
If every important folder begins with
00, the number is no longer organizing the important folders. It has become visual clutter.Starting
point
point
A small convention is easier to keep
This is a practical starting point for most shared, AI-enabled work. Follow an established organizational, platform, or industry convention when one already applies.
Folders
Use short, plain-language names. Organize by a stable purpose or content boundary. Number only when order is intentional. Examples: Client Guides, Meeting Notes, Approved Templates.
Files
When no other convention controls, use concise words separated by hyphens for files that may move across systems or support automation. Lead with the subject unless date, sequence, or identifier is the primary retrieval key.
Dates
Use YYYY-MM-DD when the date is meaningful to identity or sort order. Do not date every evergreen document.
Numbers
Use the minimum digits needed for the real sequence. Apply leading zeros only when they preserve sorting across the expected set.
Versions
Prefer one current file and the platform’s version history. If versions must coexist outside that system, use a consistent suffix such as v01, v02, or a meaningful approved date.
Status
Let location carry status when possible. A file inside Draft or In Review usually does not need the same status repeated in its name. If location cannot communicate status reliably, use one team-approved qualifier.
Practical
discipline
discipline
Let folders, names and metadata divide the work
A filename should remain useful outside its folder, but it should not repeat every detail already supplied by the surrounding structure.
Seven rules worth remembering
- Name for future retrieval, not the moment of creation.
- Follow an established convention before inventing a new one.
- Put the most useful distinguishing element first.
- Use the same term for the same thing across the system.
- Do not make the filename repeat the full folder path.
- Avoid vague status words and unexplained abbreviations.
- Write down any convention complex enough to forget.
What about letting AI clean it up?
AI is useful for maintenance, especially for clustering, proposing names, identifying duplicates, and bulk-renaming a known set.
- It cannot always infer the intended authority, lifecycle, or required sequence.
- Renaming later can break links, references, automations, and shared expectations.
- Cleanup costs less when the starting system already contains consistent signals.
Use AI as a librarian—not as an excuse to stop labeling the shelves.
Thirty-second
check
check
Before you save
Do not optimize forever. Ask five quick questions and move on.
Specialized environments—legal matters, scientific data, production media, regulated records, software repositories, or digital archives—may require stricter naming, metadata, and version-control rules.