This workflow routes a document or item to a group of people that have been selected to provide feedback. The reviewers can provide feedback, which is then consolidated and sent to the initiator of the workflow in an e-mail. This workflow type is useful for document review and collecting feedback from co-workers. Instead of individual e-mails from each reviewer, it is all consolidated. By default, this workflow is associated with the Document content type and therefore it is automatically available in all document libraries.

This predefined workflow routes a document or item to a group of people that have been selected as approvers. The Approval workflow is sequential in nature. The first set of approvers can undergo the review and approval process, then the next set of approvers, and so on until completion. Each stage or approval set can also have its own specific behavior. For example, members of the first group of approvers can do their review in serial order (one after the other), members of the second group can do their review in parallel (in any order), and so on.

By default, this workflow is also associated with the document content type and therefore it is automatically available in all document libraries. A variation of the approval workflow is also associated with the pages library on a publishing site, and can be used to manage the approval process for the publication of web pages.

This workflow manages document retention and expiration by letting participants decide whether or not they want to keep or delete expired documents.

The disposition approval workflow supports record management processes. It is primarily intended for use in a records center site. This workflow can be started automatically, manually, or when an item changes and the approver is presented with the following screen, with the options to either delete or retain the document.

This workflow allows you to route a document that was created in a Microsoft application to a group of people to collect their digital signatures. This workflow must be started in applications in the 2007/2010 Microsoft Office suites such as Microsoft Word. The participants must complete their signature tasks by adding their digital signatures (login) to the documents in the respective client programs. By default, the Collect Signatures workflow is associated with the Document content type, and therefore is automatically available in all document libraries. However, the Collect Signatures workflow appears for a document in the document library only if that document contains one or more Microsoft Office Signature Lines.

This workflow manages manual document translations by creating copies of the document to be translated and by assigning translation tasks to translators.

This workflow is only available for Translation Management libraries.

This workflow routes an issue to team members for resolution. It presents a web page to the user who is then able to enter new issues as they arise. As an issue progresses through the different workflow states, the web page that the user sees will change to reflect appropriate events.