Create a Change Event

​

Prerequisites

• The project is already created.
• You have access to the Change Events tool.
• You know the reason for the change and what source record, budget code, and estimated cost impact should be tracked.

​

What you’ll update

​

Create the change event

1

Open the new change event form

In the project’s Change Events tool, click Create.

2

Complete the general information

Enter the fields that describe the change clearly.

Field	What to enter
Number	Leave blank to auto-generate or enter the number your team uses.
Title	A short name that clearly identifies the change.
Description	A plain-language summary of what changed and why it matters.
Type	The type that best describes the change.
Change Reason	The reason, such as owner request or unforeseen condition.
Scope	Whether the change is in scope, out of scope, or still to be determined.

3

Set the origin

If the change came from another project record, set Origin and link the Origin Record so the event stays traceable.

4

Review revenue handling

If the change may be billed upstream, set the revenue fields before pricing the event.

Field	What it controls
Expecting Revenue	Whether the change may be recovered from the owner or another upstream party.
Line Item Revenue Source	Where revenue values are calculated or entered.
Prime Contract	The contract used for owner-facing markup or pricing when revenue is expected.

5

Add cost line items

Add one line for each cost impact and assign the right budget code.

Field	What to enter
Budget Code	The code that should carry the estimated cost.
Description	The cost or scope covered by the line.
Quantity / Unit Cost	Use these when the estimate is unit based.
Revenue values	Enter or review them if the change is expected to be billed upstream.

6

Attach supporting documents

Upload RFIs, drawings, photos, vendor quotes, or other backup that explains the change and supports pricing.

7

Create the change event

Review the form, then click Create Change Event.

​

Verify the result

​

Troubleshooting

• The change should be tied to another record: Set the origin before saving so the event is traceable from the start.
• The cost impact is incomplete: Add the missing line items or backup before using the event to create a PCO.
• The event may be billed upstream: Review the revenue-handling fields before the pricing moves into owner-facing workflows.

​

Related tasks

• Change Events overview
• Create a Prime PCO
• Create a Commitment PCO