Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Close a project

Log in to subscribe to topics and get notified when content changes.

Close a project

Closing the project involves more than just changing the project state to closed.

Before you begin

Role required: it_project_manager

About this task

Post-project activities include viewing baselines and actual values to evaluate how much the project slipped from its original estimates. They also include following up on related incidents, problems, or changes that are linked to the project through the instance.

When you close a project, all project tasks are closed automatically. Normally, you should not reopen a project after it is closed. Updating the project state from Closed to Work In Progress, Pending, or Open is not allowed. If you still need to reopen a closed project, reopen an existing project task or add a new task to the project. This moves the project from Closed to Work in Progress state without affecting the other closed tasks.

You can cancel the associated future resource plans and complete the Allocated resource plans for a closed project.

Procedure

  1. Verify that the work is completed for all tasks in the project.
  2. On the Project form, change the State field to one of the closed states:
    • Closed Complete the project is finished and all tasks are complete.
    • Closed Incomplete the project is finished, but tasks remain unfinished.
    • Closed Skipped the project was abandoned.
    Alternatively, close every project task first, starting with the lowest-level child tasks. The closed states roll up to parent tasks, and when the highest-level parent tasks are all closed, the project state changes to closed. However, the default closed states for parent tasks and for the project is Closed Complete. Therefore, even if you change any or all project tasks to Closed Incomplete or Closed Skipped, the project state is changed to Closed Complete.

    Also, change the Phase value to Closing. The project phase is for reference only and is not linked to or dependent on the State field.

  3. After the project is complete, create a final baseline to see how closely the actual project values came to the estimated values.
    Note: Baselines compare only planned start and end date values with actual start and end date values. Use reports to compare effort and cost.

Result

For projects created from an incident, problem, or change, updating the project state does not automatically update the related incident, problem, or change request record. You must update the related record manually. For example, if the completion of a project also means that a related change can be closed, go to the change record and modify its State field. It is also a good idea to update the work notes field on the related record to include any relevant information about the project.

What to do next

  • Cancel the resource plans associated with the project if:
    • there is a corresponding resource plan in Confirmed, Planning, or Requested state. Or
    • there is a resource plan in Allocated state with start date later than the project end date.
  • Complete the resource plans associated with the project if:
    • there is a corresponding resource plan in the Allocated state. And,
    • the resource plan start date is less than or equal to the project or task actual end date.
Feedback