Most teams name files by feel. Here's why that's a problem — and how AFO, Clade, and Luminary solve it systematically.
Here's a scenario that plays out in every office. You need the Q3 capital call document for a fund. You search the drive. You find: CapCall_Final.pdf, CapCall_Final_FINAL.pdf, BV Capital Call Q3.pdf, and 2025-08 capco (1).pdf. Which one is it?
Nobody decided to create chaos. It just happened — over months of different people, different moods, different conventions. Each file made sense to whoever named it, in that moment. The problem is structural: there was never a system.
"Inconsistent naming isn't a people problem. It's a methodology problem. Fix the methodology, and the people follow."
Naming science is the discipline of creating document identity systems that remain consistent across teams, time, and tools. When done right, a filename tells you exactly what a document is, who it belongs to, what it contains, and when it was created — without opening it.
A naming convention does four jobs simultaneously:
Identification — The name uniquely identifies the document with no ambiguity. No two documents share a name. No document has multiple names.
Classification — The structure encodes the document's category, owner, and type. You can filter by client, by document type, or by date without metadata tags.
Sortability — With a consistent date format (YYYY-MM-DD), files sort chronologically in any file system. No more "Jan 5" sorting before "Feb 12" because months aren't zero-padded.
Auditability — When a regulator or auditor asks for "all K-1s for fund Blackwater III from 2024", a structured naming system lets you find every one of them in seconds — not minutes.
Most naming guides stop at advice like "use underscores, not spaces" or "always include a date." That's hygiene, not methodology. NamingKit goes further: we define the semantic structure — what each position in the name means, why it's in that order, and which system to use for which document class.
Different document types have different identity axes. A client document is primarily identified by the client. An investment document is primarily identified by the fund. An estate document is primarily identified by the entity. NamingKit's three systems encode these different primary identities.
AFO is built around the client relationship. The primary identifier is the client code — a short, consistent abbreviation of the client's name. This means all documents for a given client sort and group together naturally, making client-level reviews fast and complete.
Clade organizes documents by investment vehicle. The primary identifier is the fund or investment name, followed by a series or tranche number. This structure ensures all documents for a given fund — capital calls, K-1s, quarterly reports — are co-located and version-trackable across multiple fund generations.
Luminary is designed for the estate planning and trust administration context, where documents are organized by legal entity rather than person or fund. Trust names and entity abbreviations serve as the primary anchor, enabling clean separation between multiple trusts for the same family while keeping all documents for a given trust together.
The most common question when implementing a naming methodology: what happens when a document touches multiple domains? A capital call notice goes to specific clients — is it an AFO document or a Clade document?
The rule is simple: use the primary organizing identity — the entity that determines where you'd look for this document first.
| You're looking for… | Primary axis | Use |
|---|---|---|
| All documents for a specific client | Client | AFO |
| All capital calls for a specific fund | Fund | CLA |
| All K-1s issued by a fund to all investors | Fund | CLA |
| A specific client's K-1 for a specific fund | Client | AFO |
| All distributions from a trust this year | Entity | LUM |
| Trust formation documents for a new entity | Entity | LUM |
| An investment policy statement for a family | Client | AFO |
When in doubt: if you'd file it under the client's name in a physical filing cabinet, it's AFO. If you'd file it under the fund name, it's Clade. If you'd file it under the trust or entity name, it's Luminary.
The most common objection to a naming methodology is that it feels rigid. "Our team is smart — they'll name things sensibly." The problem is that sensible to one person is confusing to another, and both are confusing to the person who joins the team in 18 months.
Consistency compounds. A team of two following a methodology creates a searchable archive. A team of ten without one creates a searchability problem that grows with every hire. A methodology removes the decision from each individual — the structure decides, not the mood of the moment.
There's also a compliance angle. Any office under regulatory oversight needs to be able to produce specific documents on short notice. "We name things consistently" is not a compliance strategy. "Here is our naming convention documentation, and here are all 47 documents matching this query" is.
"The best naming system is the one your whole team actually uses. That means it has to be fast, predictable, and require zero creative decisions."
NamingKit generates the name for you. You select the system, fill in the fields, and get a structured, date-stamped name that's ready to copy. No thinking about format. No guessing about date order. No remembering whether you use dashes or underscores. The methodology is baked in.
Adopting a structured naming system doesn't require renaming your entire archive on day one. Start forward — use the new system for every document created from today. After six months, the new documents are easy to find, and you'll naturally want to backfill the old ones.
The fastest path is to make the new system the path of least resistance. That's what NamingKit is built for: generate a correct name in under 10 seconds, copy it with one click, move on. When the tool is faster than improvising, the team uses the tool.
Three systems. One tool. Zero ambiguity.
Ready to bring methodology to your naming?
NamingKit generates AFO, Clade, and Luminary names in seconds. Free to use.
Try NamingKit Free