I'm interested in folder structures people are using to hold project documentation. There are probably an infinite number of ways to do this. I have seen the set up done several ways each with its advantages and disadvantages.
All the ones I've seen start with the project identifier (Number, name, whatever) as the root level but after that the subfolders go down many paths. The next level may be simply ADMIN and Technical or PMBOK project phases or ...
I've also seen some organizations use a general e-mail folder and others have an e-mail folder as a subfolder off of other such as an e-mail subfolder off the Plans folder so that e-mails related to plans are stored in it.
Jumping on an old thread
There are several ways to manage it, while we prefer simple PMI standard functions:
Schedule Management
Budgets
Quality
Communication
Resources
Risks
Procurement
Stakeholders Saving Changes...
