Procedures for Submitting Changes to Update the RPM

Revised 03/07

Responsible Managers initiate updates when there are (1) changes in applicable laws, regulations, directives, or University of California policies; or (2) changes in Berkeley Lab organizations, operational activities, or business approach. There are three types of changes. Click on the appropriate type to view the procedures for making these changes:

1. Workflow for RPM Major Changes
   Go here to see a definition of a Major Change.


2. Workflow for Human Resources' RPM Major Changes Requiring 30-Day Notice to Lab Employees
   Go here to see a definition of a Major Change Requiring 30-Day Notice.


3. Workflow for Minor Changes
   Go here to see a definition of a Minor Change.

1. Workflow for RPM Major Changes

Go here to see a definition of a Major Change.

RPM §_________

Responsible Manager/Designee (RM/D)                                                                      

Who	Action	Date	Comments
RM/D	Change drafted.		Reason for change:_____________________________________ _____________________________________________________ _____________________________________________________
	Offices contacted whose policies might be affected by the change:
	Archived electronic approval signature from Associate Laboratory Director of Operations (ALDO).
	Change sent to CSO editor.
CSO	Uploaded Responsible Manager’s requested changes to the RPM Hold page.
RM/D	Finalized change with CSO editor.
	If required, send TABL blurb announcing policy change to CSO.
CSO	With approval from RM/D, upload edited change to the RPM Web document.
	If required, send edited TABL blurb to TABL editor. Confirm publication date.
	Documented change in the RPM Update Log.

2. Workflow for Human Resources' RPM Major Changes Requiring 30-Day Notice to Lab Employees

Go here to see a definition of a Major Change Requiring 30-Day Notice.

RPM §_________

Responsible Manager/Designee (RM/D)                                                                      

Who	Action	Date	Comments
RM/D	Change drafted.		Reason for change:_____________________________________ _____________________________________________________ _____________________________________________________
	Offices contacted whose policies might be affected by the change:
	Archived electronic approval signature from Associate Laboratory Director of Operations (ALDO).
	Proposed change sent to CSO editor.
CSO	Uploaded Responsible Manager’s requested changes to the RPM Hold page.
RM/D	Finalized change with CSO editor.
	Sent TABL blurb announcing proposed policy change to CSO editor.
CSO	Sent edited notice to TABL editor, and confirmed publication date.
	Uploaded change to the Proposed Policy page.
	Tracked the beginning and ending date of 30-calendar-day notice, and sent dates to RM/D.
RM/D	Significant changes needed due to employee feedback? Yes/No If yes, ALDO must review and approve new changes.
	Finalized change with CSO editor when 30-calendar-day notice ends.
	Sent TABL blurb announcing new policy to CSO editor.
CSO	As directed by RM/D when the 30-calendar-day notice ends:
	Uploaded change to the RPM Web document.
	Sent edited TABL announcement to TABL editor.  Confirmed publication date.
	Documented change in the RPM Update Log.

3.Workflow for RPM Minor Changes

Go here to see a definition of a Minor Change.

RPM §_________

Responsible Manager/Designee (RM/D)