There can be several legitimate versions of a floorplan. The problem is when nobody can explain what each one is or which one the team should use.
A base room plan, a proposed event layout and the approved banquet diagram all have different jobs. Call all three “the floorplan” and a reasonable file library turns into a guessing game.
Fix the meaning before you fix the filename.
Separate the room from the event
The base plan describes the physical room. It comes from the architect or engineering and changes only when the building does.
The event layout describes one proposed use of that room: rounds of 10 for 280, stage on the north wall, bars in the corners.
The approved diagram is what banquets will actually set.
They’re connected, but they’re not the same thing. And when the room changes (new airwall, moved doors, a renovation) someone needs to check every event layout that depended on the old plan.
Make the clues visible
Every plan should say which space it is, what it’s for, which revision it is, whether it’s approved and who owns it. Event layouts should also carry the event reference and the assumptions they show.
A file called “Grand Ballroom dinner proposal” should never be mistaken for the approved diagram after the client moves the stage. Keep the revision history, and move superseded working copies somewhere clearly labeled as old.
A version label doesn’t prove the scale is right. It just tells you which one you’re looking at.
Decide what happens after a change
Who checks the proposals that used the old layout? Who tells the planner? Who updates the banquet diagram? Which printed copies and emailed PDFs need replacing?
Updating one shared file doesn’t change the attachments already sitting in a planner’s inbox. Check what people are actually looking at.
Keep the process short and focused on changes that matter. Nobody needs a revision ceremony for a typo.
Test the team, not the folder
Ask sales and banquets to each pull the approved plan for one upcoming event and explain how they know it’s the right one. If they come back with different files, fix the process before the room gets set.
Track corrections caused by outdated plans and the time spent sorting out conflicting versions. That’s enough evidence to justify a fix without pretending every stray file costs a specific dollar amount.
The answer to “how many versions are there?” might be more than one. The answer to “which one are we using?” should be obvious.
Related: Why One Named Space Should Have One Verifiable Identity.
