This is a story about a small, fictional editorial team that maintained an online directory of professional listings, one page per city and practice area. The work was steady and the team was careful, but they were losing hours to something they never put on a task list: not knowing what their own files, drafts and pages were called. What follows is how they noticed, what they changed and what they learned. It is a story about organisation in a publishing workflow, and it makes no claims about any profession or any individual listing.
A normal Tuesday that went wrong
The team had four people: an editor, two content coordinators and a part-time designer. On the Tuesday in question, the editor asked for the current draft of a city page. One coordinator opened a folder and found “guwahati-page”, “guwahati-page-v2”, “guwahati-new” and “guwahati-latest-edit”. Nobody could say which was live, which was the most recent draft and which was an abandoned experiment. The designer had worked on one version, the second coordinator on another, and the editor’s comments referred to a fifth that lived in an email thread.
It took the whole of the afternoon to untangle, and the page went out a day late. Afterwards the editor said something that shaped the next month: “We did not lose the work. We lost the names.”
Counting the cost
The team did not have precise measurements, and they did not invent any. Instead they kept a running note for two weeks listing every time somebody asked a “which one?” question. The note was short but telling. Most entries were about drafts, images and spreadsheets, and nearly all of them could have been prevented by a label that said what the item was and what state it was in.
The editor summarised the finding in a single sentence for the team: “We are not disorganised; we are unlabelled.”
The agreed fix: a few plain rules
Over one lunch break the team wrote down a handful of naming rules. They were deliberately small.
- Name the page by city and practice area, in that order, such as “guwahati-intellectual-property-listing”.
- State the status in a folder, not in the file name. Three folders: “drafts”, “ready-for-review” and “published”. No “final” or “latest” anywhere.
- Name images for what they show and where they belong, such as “guwahati-listing-header-illustration”.
- Keep one spreadsheet per task, named for its purpose, for example “listing-fields-checklist-intellectual-property”.
- Write the rules on one page and pin it in the team channel.
Four weeks in
Week one felt slightly fussy. The coordinators renamed their drafts and moved them between folders, grumbling a little. By the second week the grumbling had stopped, because they noticed that the editor’s review requests now arrived with a link to a clearly named file in the “ready-for-review” folder. Questions about “which version?” almost vanished from the channel.
One coordinator discovered an unexpected benefit. Because city and practice area came first in each name, her file list sorted itself into a map of the directory. She could see at a glance which cities had pages for a given practice area and which did not. The naming scheme had become a coverage chart.
The part nobody expected: onboarding
A few weeks after the change, a new freelancer joined to help with a backlog of city pages. In the old world, her first day would have been a guided tour of the shared drive, with a running commentary of “ignore that one” and “that is the old version”. Instead, the editor sent her the pinned page and a link to the “drafts” folder. By lunchtime she had picked up a page, named her working file according to the rules, and moved it to “ready-for-review” without asking a single question about where things went.
The editor later said that this was the moment the rules stopped feeling like overhead. A convention that a stranger can follow on day one is a convention that works.
A disagreement worth recording
Not everything went smoothly. The designer argued for shorter names, worried that long labels would be cut off in the file picker. The coordinators argued for fuller names, worried about ambiguity. They settled on a compromise: the first four words must carry the meaning, so even a truncated name remains readable. It is a small rule that has since saved them from several near-misses, and it shows that a convention improves when the people who use it are allowed to argue about it.
Applying the same idea to reading material
The team also kept reference pages, such as the pages in their own directory, in a shared “reading” folder for research. They gave each saved link a name that stated its purpose. A saved page about the Guwahati intellectual property listing was stored as “reference-guwahati-ip-listing-layout”, and its sibling for Madurai as “reference-madurai-ip-listing-layout”. When the designer wanted to compare layouts across cities, both pages were in the same folder with matching names, and the comparison took a minute.
What the team learned
The editor wrote down the lessons in plain words.
- Names are part of the product, even if readers never see them.
- Status belongs in a folder, which can change, not in a name that will become wrong.
- A convention works only if it fits on one page.
- The best time to rename is the moment of creation.
The limits of the fix
The team was careful about what a naming rule can and cannot do. It makes work easier to find and hand over. It does not make a page accurate, does not settle what a listing should say and does not replace the checks any directory should apply before publishing. Those remain editorial decisions made by people with the right knowledge, and any reader who needs legal help should consult a qualified professional directly.
A small side story about local events
One of the coordinators was planning a visit to Gujarat for a family occasion and saved a link to GujaratOrbit, a Gujarat events site that groups its content into listings, venue pages, a forum and a blog, under the name “gujarat-events-reading-personal”. Her colleagues teased her about the label being longer than the trip, but they all admitted it was easy to find, which was exactly the point.
How you can run the same experiment
- For two weeks, tally every “which one?” question your team asks.
- Read the tally and group the causes: drafts, images, spreadsheets, status confusion.
- Write five rules on one page. Make status a folder, not a word.
- Apply them to one live project first.
- Review after a month and trim whatever nobody follows.
An ending, a month later
On another Tuesday, the editor asked for the current draft of a city page. The answer came back in seconds: a link, a folder name and a status. Nobody needed to ask which one. The team’s afternoon went to writing, which is what they were there to do. The editor looked at the pinned rules page and observed that it was the shortest document the team had ever written and probably the most useful.
Related posts:

Legal-Support Careers: Skills That Are Good Enough to Start

Why More People Now Catalogue Their Own Records Before Hiring Help

How Open Process Information Is Changing Legal Help in India

Memory, Full Notes or Three Lines? Recording a Legal Meeting

Why Filings Come Back, and the Pre-Filing Checks That Help
