Project Changes
Learning > Record Pages > Project Changes
NOTICE: Starting 5/16, add "@dot.state.co.us" to the end of your username when logging in to PMWeb.
The Project Changes record enables project teams to document significant changes during the lifecycle of their project, including changes in scope, schedule, and cost. Project teams use this record on an as-needed basis.
Access: This record is located in the Records module of PMWeb, under the "Custom Forms" section.
The following job aids and reference guides are relevant to the Project Changes record:
To request additional training or documentation, please submit a Help Request in PMWeb or contact your regional PMO representative.
The Main tab of the Project Changes record contains several sections: Record Information, Change Detail, and Impact Assessment. The Impact Assessment, in turn, contains three more sections: Scope, Schedule, and Construction Expenditures (cost).
Use the Record Information section to specify a project and provide details about the nature of the project change.
Use the Change Detail section to specify a reason, description, and rationale for the change.
Use the New Scope field to propose updates to the project's scope as a result of the change. Do not populate text in the Current Scope field. PMWeb will automatically fill in the current scope from the Project record when you save this record.
Use the Schedule section to propose updates to project milestone dates. Do not populate a date in the "Current Date" column. PMWeb will automatically fill in the current date for the specified milestone when you save the record.
NOTE: Wait for the Project Changes record with revised milestone dates to be approved before updating the Schedule record.
Use the Construction Expenditures section to propose revised expenditure plans, and to designate whether the expenditures meet the requirements of PD703.
The Project Changes records contain several tabs in addition to the Main tab.
Users may add supplemental information in the Notes and/or Attachments tab.
Users submit the record to workflow for review and approval in the Workflow tab.
Users may notify others that they have created a Project Changes record in the Notification tab.
For more information on standard tab types, please reference the Records Navigation page.
Regions may have differing requirements for the Project Changes record.
View requirements for Region 2.
Project Changes records may require approvals from the project's assigned PMO representative and/or Resident Engineer. Some Project Changes records do not require approval.
The Project Changes record contains two reporting options in "BI Reporting":
Project Changes: A record-level report that summarizes the information provided in a single Project Changes record.
Project Changes - Program View: A program-level report that lists all Project Changes records for a specified program, project, residency, or region.
The Project Changes record integrates with or triggers to/from the following:
In the Current Scope field, PMWeb pulls in the scope from the Project record.
In the Milestone Updates table, dates in the "Current Date" column are pulled in from the milestone dates from the Schedule record.
In the Construction Expenditures section, PMWeb pulls in the "Current Plan Expenditures" from the expenditure data listed in the Accounting sub-tab of the Project record's Additional Information tab (integrated from SAP).
I can't add a milestone to the Milestones Updates table. How can I fix this?
If your Milestone dropdown menu is blank, your Schedule record does not contain properly tagged milestones.
In your Schedule record, ensure that milestone activities have start dates and are tagged as milestones in the Milestone column.
I've specified a milestone in the Milestone Updates table. Why doesn't PMWeb automatically fill in the "Current Date" field?
If your "Current Date" field is blank, ensure you have saved the Milestone Updates table, then saved the Project Changes record as a whole. If you still do not see a date populated, go to your project's Schedule record and ensure there is a date in the "Start" column.