SharePoint 2010 – Using Retention Stages to Manage the Lifecycle of Information
Guest Author: Jeff Carr
With hundreds or thousands of employees generating information on a daily basis, there’s bound to be a buildup of ROT (content that is “Redundant, Outdated or Trivial”). When left unattended, this content can quickly evolve into a negative user experience, particularly in search as users are forced to sift through pages of irrelevant results. Automating processes that address the review, archival and/or disposition of information in the organization on a regularly scheduled basis can ensure both the relevance and timeliness of information.
The implementation of retention schedules in SharePoint 2010 can be associated with specific types of content through the application of information management policies. Retention Stages are defined within the settings for a content type.

Selecting the option to add a new Retention Stage offers the ability to establish events, actions and recurrences for the chosen content type.
- Event – Definition of the event that needs to take place in order for the Retention Stage to be carried out. Typically based on the passing of a defined time period since document creation or modification.
- Action - Definition of the action required to take place once the event has been triggered. Some types of content may require immediate archival or just a standard review, while others are to be permanently deleted. More often than not, an associated workflow will be kicked off to notify an individual or group responsible for the item.
- Recurrence - Definition of how often the Retention Stage is required to be repeated. Typically based on the passing of a defined time period since the activation of the last Retention Stage.
SharePoint 2010 makes the automation of retention schedules a fairly straightforward activity. The majority of the work behind the definition of retention is sure to take place outside of the technological environment, as part of the organizational information management, records management or legal compliance strategy.
Guest Author: Jeff Carr
Jeff Carr is an Information Architect and Search Consultant with Earley & Associates specializing in user centered information design. Working with SharePoint since 2003, he has been involved in the design, development and integration of web-based solutions from intranets and extranets to public facing websites for a variety of large enterprises across a wide range of industries.
- SharePoint 2010 - What You Need to Know About Taxonomy, Metadata & Information Architecture
- SharePoint 2010 - Using Taxonomy & Controlled Vocabulary for Content Enrichment
- SharePoint 2010 - Using Social Features for Personal Classification & Improved Findability
- SharePoint 2010 - Using Taxonomy & Metadata to Improve Navigation & Browsing
- SharePoint 2010 - Using Taxonomy & Metadata to Improve Search & Discovery
- SharePoint 2010 - Share Content Types Across Site Collections
- SharePoint 2010 - Using Retention Stages to Manage the Lifecycle of Information
- SharePoint 2010 - Administering Taxonomy Using Term Store Management
- SharePoint 2010 - Importing Taxonomy Using the Managed Metadata Import File
- Taxonomy, Metadata and Information Architecture in SharePoint 2010 - Series Summary and Conclusions
Hello Jef,
In our Sharepoint 2010 testenvironment I have set up a retention stage for a specific contenttype
2 days after creation move to recycle-bin. I upload a document of this contenttype, but after 2 even 3 days nothing happens. What more do I need to do make this retention stage work?