> ## 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.

# Change notices

> How Alforse drafts an engineering change against real methods, reviews it as a diff, and releases it so downstream planning supersedes the versions it replaces.

A **change notice** groups related part changes, stages each change in a hidden draft, and releases them together. Live methods remain unchanged until release.

Select affected items, then edit each item's method—its bill of materials and bill of process—inside the notice. Planning, jobs, and costing continue to use the live item until release. Change notices are under **Items → Change Notices** and require `parts` permission.

## The affected item is the unit of work

A change notice contains a header and **affected items**. The picker accepts Parts only. Each affected item has its own change type, edits, and cutover configuration.

Adding an affected item copies its **Active** method into a **Draft** method associated with the change notice. The draft is excluded from version selectors, copy targets, MRP, jobs, and costing until release. Edit it with the standard **Bill of Material**, **Bill of Process**, and **Part Properties** editors.

NOTE

**The draft is a real method, not a staged copy.**

Alforse does not mirror your edits into shadow tables. An affected item's edits live on an actual make method
whose change-notice id is set, which is why the diff is exact and release is just an activation. The draft is
invisible everywhere else precisely because that id is set — clearing it at release is what makes the draft
live.

## Find one in the list

**Items → Change Notices** lists every change notice. Because the affected item is the unit of work, each row
**expands** to reveal the parts it changes — one line per affected item, with its change type badge and, for a
Revision or Replacement Part, the old item number arrowed to the new one (**P000123 → P000124**). A New Part
shows a single id — it's net-new, with no predecessor to arrow from. You see what a change notice touches
without opening it.

To find the change notices that touch a specific part, use the **Item** filter. Pick one or more items and the
list narrows to change notices that affect them. The **Items** column that backs the filter is hidden by
default; turn it on from the column toggle if you want it in view or in a CSV export.

## How the pieces fit

**Create a change notice**

Every entry point — the standalone form, a part or tool header, the parts table, the method version
menu, and a quality issue — plus how change notices surface back on a part.

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

**Change types**

Version, Revision, Replacement Part, and New Part: what each lets you edit and what release creates.

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

**Lifecycle & release**

The five stages, the Implementation lock and Reopen, the diff review, the impact panel, and what release
actually does.

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

**Supersession & cutover**

How a released revision phases over, and how MRP and Get Method honor it downstream.

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

**Categories & actions**

The change-notice category lookup, the reusable action-task templates, and linking a task to Linear.

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

## Related

**Methods & sourcing**

Method versions, Draft/Active/Archived, and Get Method — the machinery a change notice drives.

[Open](/docs/reference/methods.md)


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