SPM project change request

ZeeshanA9684002
Tera Contributor

3 weeks ago

Hi Team,

 

Need to know ways to use of project change request which should be recommended to customer to use as per the servicenow best practice .

In my case project change request like adding new tasks and new cost plan or editing dates of existing tasks comes when project is in execution phase .

 

My project change request has approvals for that I can plan flow designer and trigger approvals .normally what else should be taken care 

Should be helpfull if any of your projects managing neat and clean project change requests 

Thanks in advance 

0 Helpfuls
  • 389 Views
1 REPLY 1

maliksneha9
Mega Sage

3 weeks ago

Hi,

 

From my experience working with SPM / Project Management in ServiceNow, Project Change Requests are typically used to control and govern any significant changes that occur after the project moves into the execution phase.

 

Here are a few best practices that have worked well in projects I have been involved in.

 

1. Use Change Requests Only for Meaningful Changes

It’s usually recommended to use Project Change Requests only for changes that impact the project baseline, such as:

 

  • Changes to project scope
  • Adding new tasks or milestones
  • Changes in planned start/end dates
  • Updates to cost plans or financial estimates
  • Resource changes that affect delivery timelines

 

Small operational updates are often handled directly within the project to avoid unnecessary approval overhead.

 

2. Define Clear Approval Governance

Typically, organizations include approvals from:

 

  • Project Manager
  • Project Sponsor / Business Owner
  • PMO or Portfolio Manager

This ensures that any impact on timeline, budget, or scope is reviewed before implementation.

 

3. Capture the Impact of the Change

One thing that helps keep change requests organized is capturing the impact analysis before approval. For example:

 

  • Schedule impact (timeline change)
  • Financial impact (budget increase)
  • Resource impact
  • Business justification

 

This helps approvers make informed decisions.

 

4. Update Baselines After Approval

After the change request is approved and implemented, many teams update the project baseline so the new plan becomes the reference point going forward.

This keeps reporting and variance tracking accurate.

 

5. Keep the Process Lightweight

One challenge I’ve seen is when the change process becomes too heavy. It’s usually best to:

 

  • Use change requests for major changes
  • Allow project managers to handle minor adjustments directly
  • This keeps the project moving while still maintaining governance.