Enabling an Information Policy for expiring content

This article relates to Microsoft Office SharePoint Server 2007 (MOSS) and Microsoft Windows SharePoint Services V3.0 (WSS).

A useful, but little used feature in SharePoint is the ability to add Information policies to Sites to provide enhanced control on information.  SharePoint has a few that are provided ‘in the box’ which are ready for use straight-away.  These are:

  • Labelling Content – used for adding a label to an item.

  • Auditing - actions carried out on an item (such as opening, editing , checking in or out, etc) are logged.

  • Assigning barcodes to an item.

  • Expiration of content – items are deleted after a certain time or managed based on a Workflow activity.

The first three are useful for keeping track and monitoring activities on content but the final one may see odd – why would you want to delete content?

There are some scenarios where this could be useful, for example, a company whose staff create purchase orders for office supplies which are stored within a SharePoint Site.  The Purchase Order form is required for the suppliers to see what has been ordered, for tracking the order, and for the customer to confirm that the correct items are delivered. Once this is completed the form becomes redundant. In this scenario, there is no need to maintain the completed forms, they are now redundant and need to ne removed from SharePoint to keep the Library trim. We can do this by setting up an Information Policy.

Setting up an Information Policy

Site Collection Policies

An Information Policy can be created at the Document Library, Site or Site Collection level.  For the purpose of this post I will create it at the Site Collection level. To do this go to the Site Settings page for the Site Collection and select the Site Collection Policies link under Site Collection Administration.  An Information Policy is given a name and the options set depending on the type of Information Policy you require.  For the Expiration Policy you need to check the Enable Expiration checkbox and specify the retention period and what happens to an item once that time period has expired.


Below shows the Expiration settings that can be assigned to an Information Policy.

expiry policies JOINT

Because the Expiry Policy is set at the Site Collection level it means it can be referenced by all Sites that sit within the Site Collection.  This means that Information Policies can be created at the top level of a Site Collection and set across many Libraries.

Once the Information Policy is created it can then be applied to a Library or List:

policy settings on a library

Below is the Information Policy created at the Site Collection level specified in a Document Library:

Document Library settings

This can also be applied to a Content Type as well - this allows for many different types of documents to be associated with the Content Type and have the same Information Policy applied. 

Testing your Information Policy

Once this is completed you can then test that the policy works.  To do this:

  1. Change the Date and Time for the SharePoint Machine running the Central Administration Site to a date and time beyond the retention period (if this is a VM machine you may need to change this on the host machine).

  2. Go to Central Administration Site and select the Operations Tab.

  3. Under the Security Configuration Section Select  Information management policy configuration.

  4. Select the Expiration Policy and then select the Process Expired Items Now.

The item that was subject to the Information Policy should now disappear!


  • Documents subject to an expiry policy are sent to the Site Recycle Bin.  At this point they are subject to the Recycle Bin settings defined at the Web Application level.

  • The option to start a Workflow is not available when defining a policy at the Site Collection level. A Workflow can be assigned to a policy at the Document Library Level (after one is associated with the Document Library) or against a Content Type.  The Workflow must be created first before the policy is created.


Rob Finney
Microsoft Consulting Services UK

Click here for my bio page

Comments (6)

  1. Top News Stories Google's Wave: 'Rethinking How People Work' (Internet News) Like a slow

  2. Lou says:


    We are setting up a policy on a document library to run based on a modified date and to execute a workflow.  The workflow sends an email to the author of a doc to update the doc or it will be deleted.  We were thinking that the workflow can then pause for a few days then send a reminder. after a couple reminders delete the document.

    But, if the author modified the document, the workflow stops.

    We thought the Policy would fire again when the rule for expiration was again met. will this be the case or is there a flag we have to flip to get to rerun?


  3. Ben says:


    When items expire they’re marked as exempt from policy to prevent them from expiring again and again. You can remove this exemption to have them expire a second (or third, etc) time. The easiest way is through the View Properties page of the item.

  4. easrut says:

    It might be the easiest way but it's not practical in our business. Is there an alternative to removing the exemption without code?

  5. I can't find expire in the an Information Policy says:

    I can't find expire in the  an Information Policy ..any tip?

Skip to main content