> ## Documentation Index
> Fetch the complete documentation index at: https://meganharrisonconsulting.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Change Events

> Track potential changes to the project before they become approved change orders.

Change Events capture potential changes to the project scope, schedule, or cost before they become approved change orders. Use them to price work, gather subcontractor input, and decide whether to proceed.

## Open Change Events

1. Select the project.
2. Open **Change Events** from the sidebar.
3. The log lists every change event with status, type, and estimated value.

## Status Workflow

* **Open** — newly created, no pricing or decision yet.
* **Pending** — pricing collected, awaiting internal review.
* **In Review** — under owner or design team review.
* **Approved** — owner approved; ready to roll into a change order.
* **Rejected** — declined or withdrawn.
* **Void** — cancelled with no impact.

## Create a Change Event

1. Select **Create Change Event**.
2. Enter a **Title**, **Description**, and **Type** (owner-initiated, field condition, design change, subcontractor PCO).
3. Set the **Originator** and **Date**.
4. Add cost line items by cost code and cost type.
5. Attach supporting documents (drawings, RFIs, photos).
6. Save the change event.

## Add Pricing

Each change event can hold multiple line items grouped by trade or cost code. For each line:

1. Choose the **Cost Code** and **Cost Type**.
2. Enter quantity, unit cost, and markup if applicable.
3. Optionally link the line to a **Vendor** or **Commitment**.

The total estimated value rolls up to the change event header.

## Convert to a Change Order

Once a change event is approved, generate a Change Order from it. See [Change Orders](/help/articles/change-orders).

## Related Articles

* [Change Orders](/help/articles/change-orders)
* [Budget Overview](/help/articles/budget-overview)
* [RFIs](/help/articles/rfis)