---
title: Close a pipeline project
description: As a sourcing manager, you can close the pipeline project when all the activities related to the sourcing pipeline project have been completed.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/source-to-pay-operations/sourcing-and-procurement-operations/close-pipeline-project.html
release: australia
product: Sourcing and Procurement Operations
classification: sourcing-and-procurement-operations
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 1
breadcrumb: [Using Sourcing Pipeline Management, Use, Sourcing and Procurement Operations, Finance and Supply Chain]
---

# Close a pipeline project

As a sourcing manager, you can close the pipeline project when all the activities related to the sourcing pipeline project have been completed.

## Before you begin

Ensure that you’ve qualified all the relevant suppliers, and have received all the bids and responses from them, before you begin the awarding process. At this point, the sourcing event that you plan to work on, and all its associated negotiations, sourcing requests, and purchase lines must be in the Requires Decision state.

Role required: sn\_shop.procurement\_specialist

## Procedure

1.  Navigate to **Source-to-Pay Workspace**.

2.  Select the list icon \(\[Omitted image "cases-list-icon.png"\] Alt text: List icon.\) and do one of the following:

    -   Navigate to **Lists** > **My work** > **Pipeline projects**.
    -   Navigate to **Lists** > **All work** > **Pipeline projects**.
3.  Open the pipeline project that is in Work in progress state.

4.  Select **Close**.

    The system checks that all related objects, such as sourcing requests and sourcing events, are closed. If any of the related objects are open, an error message prompts you to close them.

    The Close pipeline project dialog box is displayed.

    \[Omitted image "pipeline-close.png"\] Alt text: Close pipeline project.

    The **Hard savings** field is auto-populated and displays the cumulative savings from all sourcing events associated with the pipeline project. This value is calculated by summing the Negotiated savings from all closed purchase requisition lines \(PRLs\) within the sourcing events.

    You can edit the **Hard savings** field if you’d like. If you edit the **Hard savings** field, a warning message appears indicating that the entered value differs from the cumulative negotiated savings on PRLs. This warning is shown only if there are negotiated savings on any PRL.

5.  Enter the project's financial data in the **Estimated spend**, **Hard savings**, **Targeted savings**, **Cost avoidance**, **Final spend**, **Other savings**, and **Lost savings** fields.

6.  In the **Closing notes** field, enter a brief summary of the pipeline project that provides context for future reference, auditing, or reporting.

7.  Select **Close**.

    The pipeline project moves to the Closed Complete state.


**Parent Topic:**[Using Sourcing Pipeline Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/use-pipeline-sourcing-mgmt.md)