---
title: "Close out a project"
url: "https://help.altus.pro/de/article/close-out-a-project"
language: "de"
last_updated: "2026-06-22T04:33:54.000Z"
---

# Close out a project

Closing out a project ensures that:

-   All work has been completed and validated
-   Financials are accurate and finalised
-   Outstanding risks, issues, and actions are resolved
-   Project data is complete for reporting and governance

Project closure in Altus typically involves **coordinated updates across multiple areas**, not a single action.

> **Important:**  
> Project closure processes may vary depending on your organisation’s **governance standards, lifecycle configuration, and approval requirements**.
> 
> -   Always follow your organisation’s **internal project management processes and policies**
> -   Some steps (e.g. approvals, stage progression, or financial validation) may be **mandatory or automated based on configuration**
> -   Your implementation partner or administrator may have applied **custom workflows, checklists, or controls** that change how closure is performed
> 
> 👉 If you are unsure, refer to your organisation’s internal guidance or consult your PMO before closing a project

* * *

## Where This Is Performed

Project close-out activities occur across:

-   **Project → Information (Header / Status)**
-   **Tracking (Risks, Issues, Decisions, Changes, etc.)**
-   **Financials**
-   **Resource Plan**
-   **Lifecycle / Stage Progression (Business Process Flow)**

* * *

## Step 1: Validate Project Delivery

Confirm that all project work is complete:

-   All deliverables are completed
-   All project tasks are finished
-   Acceptance criteria have been met
-   Stakeholders have provided required approvals

* * *

## Step 2: Finalise Resource and Effort Tracking

Ensure all resource activity is complete:

-   All **timesheets are submitted and approved**
-   No outstanding or missing time entries remain
-   Resource activity reflects actual work performed

> **Tip:**  
> Approved timesheets drive **actual resource effort and cost**, so accuracy at this stage is critical.

* * *

## Step 3: Update and Close Risks and Issues

Review all tracking registers and ensure closure:

-   Close or resolve:
-   -   Risks
    -   Issues
    -   Decisions
    -   Changes
    -   Other active registers

> **Important:**  
> Projects should not be closed with unresolved high-impact risks or issues unless formally accepted through governance processes.

* * *

## Step 4: Finalise Financials

Ensure all financial data is complete:

-   Import:
-   -   Timesheet actuals
    -   Resource forecasts (if required)
-   Validate:
-   -   Budget vs Actual vs Forecast
    -   Variance values

> **Tip:**  
> Finalising financials ensures accurate reporting across **project, program, and portfolio levels**.

* * *

## Step 5: Align Resource Plan and Commitments

Review the Resource Plan:

-   Confirm **Proposed vs Committed** effort is aligned
-   Ensure no outstanding resource demand remains
-   Validate effort reflects actual delivery

* * *

## Step 6: Update Project Status

Update the project header:

-   Set **Project Status** to:
-   -   Completed, or
    -   Closed

> **Important:**  
> Advancing lifecycle stages does **not automatically update Project Status** unless configured to do so.

* * *

## Step 7: Advance Lifecycle to Final Stage

Progress the project lifecycle:

1.  Navigate to the lifecycle stages at the top of the project
2.  Select the current stage
3.  Complete required checklist items
4.  Select **Next Stage**
5.  Repeat until the final stage is reached

> **Important:**
> 
> -   Lifecycle configuration varies by organisation
> -   Some stages may require approvals or conditions
> -   Once fully closed, reopening may require admin involvement

* * *

## Step 8: Capture Final Project Data

Ensure all information is complete and current:

-   Final status updates
-   Project documentation
-   Lessons learned (if applicable)
-   Benefit tracking updates

* * *

## Step 9: Validate Reporting and Insights

Confirm project data is correctly reflected:

-   Review **Insights (Power BI reports)**
-   Validate:
-   -   Actual effort
    -   Financials
    -   Project completion status

* * *

## Step 10: Archive or Transition the Project

Depending on governance:

-   Transition the project to a **closed or archived state**
-   Restrict further updates if required
-   Retain for reporting and audit purposes

* * *

## Key Considerations

-   Project close-out is a **multi-step process**, not a single action
-   Lifecycle progression and project status are separate controls
-   Data accuracy impacts reporting and portfolio insights
-   Some actions may require approvals or governance sign-off
-   Reopening closed projects may require administrative access

* * *

## Tips

-   Follow a consistent close-out checklist for all projects
-   Ensure timesheets are fully approved before closure
-   Close all risks and issues or document accepted exceptions
-   Validate financials thoroughly before finalising
-   Confirm lifecycle stage and project status are aligned