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

# Create a change notice

> The entry points that open a change notice, the fields on the create form, and how change notices surface back on a part or tool page.

Create a change notice from the standalone form, an item, a method version, or a quality issue. Every entry point opens the same change-notice detail page.

## Entry points

FieldType

<details>
  <summary>**Items → Change Notices → New**</summary>

  The standalone form. Start here when the change spans several parts or you haven't opened a specific one yet.
</details>

<details>
  <summary>**Part or Tool header → Create Change Notice**</summary>

  Opens the create form as a modal with the current part or tool pre-attached as the first affected item.
</details>

<details>
  <summary>**Parts table → row menu → Create Change Notice**</summary>

  A one-click start: mints a change notice named **Change for** the part, attaches that part as a **Version** change, and drops you on its detail page.
</details>

<details>
  <summary>**Method version menu → New Change Notice**</summary>

  On a part's method, the same version menu that holds **New Version** offers **New Change Notice** — the natural place to reach for a change while you're looking at the recipe.
</details>

<details>
  <summary>**Quality issue → Create Change Notice**</summary>

  From a non-conformance, this opens the create form with the issue linked and its id as the name, so the engineering fix is traceable back to the problem that prompted it.
</details>

NOTE

**Starting from a part pre-attaches it.**

The part-header, tool-header, parts-table, and method-version entry points all pre-select that part or tool as
the change notice's first affected item (as a **Version** change you can switch), so you land ready to pick a change type and edit. The standalone form
starts with no affected items — you add them on the detail page. Change notices accept Parts and Tools only; other item types are skipped with a message.

## The create form

The header form describes and assigns the change. Add affected items after creation.

FieldType

<details>
  <summary>**Name**required</summary>

  What this change is, in a line.
</details>

<details>
  <summary>**Category**</summary>

  The change-notice type, drawn from your configured categories. See [Categories & actions](/docs/reference/change-orders/setup.md).
</details>

<details>
  <summary>**Reason for Change**</summary>

  Why the change is needed. Rich text.
</details>

<details>
  <summary>**Description of Change**</summary>

  What's changing, in narrative. Rich text.
</details>

<details>
  <summary>**Owner**</summary>

  The employee responsible. Defaults to you.
</details>

<details>
  <summary>**Priority**</summary>

  Low, Medium, High, or Critical. Defaults to Medium.
</details>

<details>
  <summary>**Open Date**required</summary>

  Defaults to today in the company's time zone.
</details>

<details>
  <summary>**Due Date**</summary>

  Optional target.
</details>

Any custom fields defined for change notices appear at the end of the form.

The form does not include affected items. Add them on the detail page. Item-based entry points pre-attach the selected item; the quality-issue entry point links the non-conformance. Saving creates the change notice in **Draft** and opens its detail page.

NOTE

**There's no separate change-notice permission.**

Change notices are gated by the **Parts** permission: creating one needs create access on Parts, and
advancing or releasing needs update access. If someone can manage parts, they can manage change notices.

## Where change notices surface on a part

Parts and tools display the change notices that affect them:

* **Open change notice alert.** When a part is on one or more change notices that are still open (**Draft**,
  **Start**, **Engineering Complete**, or **Implementation**), its detail page shows a card: *"This item is on 1
  open change notice"* (or *"This item is on # open change notices"*), with each change notice id linked. This is the guardrail against two people revising the same part blind.
  It's informational, not a lock — [parallel change notices on the same
  part](/docs/reference/change-orders/lifecycle.md#parallel-change-notices-on-the-same-part) are allowed.
* **Change Notices history.** A card lists every change notice that has touched the part, newest first, with
  released ones de-emphasized — the full "why did this part change?" trail.
* **Used In.** The part's **Used In** view lists the change notices that reference it, each linked with its status.

NOTE

**Change notices are numbered CN-.**

Each change notice gets a per-company readable id like **CN-000001** from the `change-order` number series. That's the id you'll see in the alert
and the history card. The prefix and size are configurable under [Sequences](/docs/reference/sequences.md).

## Related

**Change types**

What you set on each affected item once it's attached.

[Open](/docs/reference/change-orders/change-types.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.