Related Posts
Hi everyone! having tackled virtual onboarding personally I wanted to write about my experience to help new starters and managers go through the process. I also spoke to two friends (one starting at Deloitte and the other at an early stage startup). Hope it helps you all! hipr.pl/37DgkAm
Has anyone sold at IQVIA? What’s comp like?
Is MBB hiring right now ?
Additional Posts in Excel Genius
New to Fishbowl?
unlock all discussions on Fishbowl.





Always include dates. 7.6.25,etc.
Good advice I like that a lot
Putting the word “final” in a file name invites the dark spirits of partners past to ensure there is at least one more round of iteration/churn
Very true haha
Always just put the date.
Everyone’s saying that here thanks
I never name anything final. It's always "DRAFT [date]" or v1, v2, etc.
Thanks for sharing
I don’t let my teams finalize their work until they have a well labeled excel with no dead tabs, useless tables etc. it’s just good hygiene.
Good hygiene is important in the world of excel haha
Love a date in every filename my logs generate, etc.
Excel's a no-brainer, though. Save to SharePoint. Use Version History.
Yess 🙌
v0.1, v0.2, v0.3, … , v1 (shared with client), v1.1, v1.2, v2 (shared with client), etc…
Interesting that’s a good use case
nomenclature matters (like everyone said, dates, times, etc) but it’s more about version control in my line of work (leaving check in comments).
files with a bunch of formulas and internal data should have _working appended to the file name (i.e. table1-1_data_working).
files that are sent to stakeholders should be static (copy+pasted as values from the working file). They should be saved without version numbering in the name as technically you’re providing that file as a near final deliverable (i.e. client_project_table1-1_data_20250707). It is possible that the stakeholder has comments or you catch an error, in that case you may choose to add “revised” or change the file date.
with all of that said, your approach will depend on the file use and how much collaboration is required. there’s many other ways to approach version control like folder structure, etc depending on your end goal (iterative updates, facilitating QC and review, or just sharing internally).
Thanks for sharing
I generally always use YYYY-MMDD-Project name v1.xlsx. However, with autosave, version history and cloud storage, I feel like there's no reason for version numbers anymore. At this point I just make the updates in the same file and can always go back to older versions if needed.
That’s what I do now haha
Sort by last modified. Changing the title won't do anything when there's multiple versions and people working on it.
Sharepoint helps alot and allowing only certain people to version control. If you want your own version, fine but you store it somewhere else.
No 20 versions of the same file in one folder. Agree with all stakeholders at certain intervals that one version is the current version and dump everything else into a superseded folder.
That sounds like a good workaround
I always put c at the end of whatever gets shipped to a client.
Ahhhh