I’ve been delivering and employing SharePoint Document Sets for well over 10 years. This powerful feature has streamlined dozens of assignments and simplified the lives of countless staff - especially busy Project Managers and their overworked teams.
![](https://static.wixstatic.com/media/f4ef069707a041f8884add9497584f48.jpg/v1/fill/w_980,h_923,al_c,q_85,usm_0.66_1.00_0.01,enc_auto/f4ef069707a041f8884add9497584f48.jpg)
A Document Set is a group of related documents – but that’s just the ‘label’. In action SharePoint delivers a wealth of feature benefits – as I’ll outline later.
So why aren’t you, your colleagues or your company using Document sets? Chances are it's because no one has heard of them...! Document Sets are now seldom promoted by Microsoft which is focusing on more recent launches, improved user interface features, plus of course the ever expanding Teams and 365 domains. This post seeks addresses this knowledge gap and act as a reminder to leverage this forgotten and fine feature.
A project is a perfect example of why you should be using Document Sets. Even a simple assignment will have the following document and spreadsheet files
Business Case
Project Charter
Project Communications Plan
RACI Matrix
Work Breakdown Structure
Etc Etc
All these separate files are best stored under a single and common ‘project’ umbrella.
![](https://static.wixstatic.com/media/5e6cfb_32c7cc93811e4dd7bdd9c7b43d25e06b~mv2.png/v1/fill/w_868,h_240,al_c,q_85,enc_auto/5e6cfb_32c7cc93811e4dd7bdd9c7b43d25e06b~mv2.png)
Employing a Document Set at ‘project initiation’ not only creates the full SET of required documents, but also names them AND ensures they are based on the companies current set of templates – at last no more searching for latest file versions or reading the process manual to see what documents have been forgotten..!
Two simple steps to create a Document Set
One simple click and updating one set of metadata fields..!
![](https://static.wixstatic.com/media/5e6cfb_5cd75b19b6a4421fb1212f6745e29457~mv2.jpg/v1/fill/w_788,h_495,al_c,q_85,enc_auto/5e6cfb_5cd75b19b6a4421fb1212f6745e29457~mv2.jpg)
![](https://static.wixstatic.com/media/5e6cfb_9da9d8c3fa9443ac849f7122feecd9dc~mv2.png/v1/fill/w_620,h_300,al_c,q_85,enc_auto/5e6cfb_9da9d8c3fa9443ac849f7122feecd9dc~mv2.png)
![](https://static.wixstatic.com/media/5e6cfb_f8bd4c4d0b3642f2b1c32f1b799eae0c~mv2.jpg/v1/fill/w_817,h_296,al_c,q_80,enc_auto/5e6cfb_f8bd4c4d0b3642f2b1c32f1b799eae0c~mv2.jpg)
Template and Document Set Libraries will both benefit from extending the views to including the additional metadata. The above example includes Content Type, Client Name. Project Name and Description plus Versions.
But that’s just the start… When fully leveraged SharePoint’s ‘Content Type’ features control the document content type complete with its underlying fields metadata ideal for populating documents (see below) provided of course, you’ve already defined these properties..!
![](https://static.wixstatic.com/media/5e6cfb_62467f4cf8c64439a3946ed1cd4c79cf~mv2.png/v1/fill/w_872,h_763,al_c,q_90,enc_auto/5e6cfb_62467f4cf8c64439a3946ed1cd4c79cf~mv2.png)
For more information see the Introduction to Document Sets from Microsoft.
Watch for a future post which will include a demo of the planning and a video of the Document Set creation process.
Comments