Skip to Content
ProjectsChange Requests

Change Requests

Beta

This feature is in beta. It can change before it reaches every account, so this article may not match what you see yet. To try it, an account admin can turn it on in Settings > Account > Account Preferences, under Features. See Upcoming Changes for the planned date.

Use a change request to track added work after a project is signed. A change request copies the lines you pick into a new linked project that is approved on its own. Once that project is approved or won, its hours and revenue count toward the original project’s totals.

Use Re-Scope on the original project when you need to reopen and revise it. Your account may use a different label. Re-scoping requires Manage for the Request Approval permission.

Find the change requests list

Open the original project and go to Approvals > Change Requests.

On this screen: The Change Requests table shows Number, Cause, Status, Hours, Revenue, Reference, and Created, in that order. The Number opens the request. A row marked Reference only records work tracked in another system. Open its request summary to see the recorded hours and revenue.

Create a change request

Click + New Change Request. Choose Change scope in ScopeStack to create an Authored request with a linked project for the added work. Choose Tracked in another system to record work scoped and approved in your professional services automation (PSA) system.

On this screen: New Change Request shows both types above Why is the scope changing?. The form has Note, External Reference, and External URL, with https:// as the URL placeholder. Cancel and Save are at the top.

Select a cause. The choices are Customer requested additional scope, Original scope underestimated, External / vendor change, and Other. Add a note, a reference such as a ticket number, or a link if you need one. Use an http:// or https:// address for the link.

Change scope in ScopeStack

On this screen: The Professional Services grid and the managed services grid appear when the original project has those services. Each grid shows Service, Quantity, Effort (hrs each), Resource for addl effort, Hours, and Change $. Each line shows its original values below its name. Use Only changed lines to focus on your edits. If the project has governance, Project governance shows Governance, Calculated by, Hours, and Price.

  1. Enter the quantity and effort for the added work on at least one service or subservice. The grids list only services and subservices already on the original project. Use whole quantities. For lines with catalog-calculated hours, enter the quantity and ScopeStack calculates the effort. Choose a resource for the added effort if it differs from the original.
  2. Review governance if it appears. For a fixed-hours item, enter 0 to leave it out. If you see a minimum below the field, enter at least that many hours to include the item. Percentage-based governance uses the change request’s hours.
  3. Review Original as signed for the original project’s hours and revenue. This change shows the added hours and revenue. Project with this change shows the combined amounts. Review Margin, then click Save to open the request summary.

ScopeStack copies the services and subservices needed for the added work into a new linked project. That project starts in Building and goes through approval separately.

At each approval level, ScopeStack notifies the assigned approvers. Once the linked project is fully approved, ScopeStack notifies its Pre-Sales Engineer and Sales Executive. If an approver declines or cancels the project, or sends it back for re-scoping, ScopeStack notifies the Pre-Sales Engineer. Delivery follows the account’s and recipients’ notification settings. See Project Approval Levels for the approval emails.

Tracked in another system

On this screen: This type shows Hours and Revenue below the reference fields. The summary shows Original as signed, This change, and Project with this change.

  1. Enter the Hours and Revenue from your PSA. Both fields are required and accept zero or more.
  2. Click Save. The original project gets a reference record with the amounts you entered.

Review the request and its totals

ScopeStack numbers requests in order on each original project, starting with CR-1. A linked project is named for the original project followed by its request number, such as Project Name – CR-1. Start each new request from the original project.

On this screen: The request summary shows its number and status above the totals and Reason for Change. A scoped request has Open in Change Request Project plus sections for Services, Project governance, Travel/Expense, and Product if product quoting is enabled. A tracked request shows Hours and Revenue under Tracked in another system.

On this screen: The linked project’s banner shows the request number, the original project name, and the cause when you have access to the request. On the Projects list, linked projects have badges such as CR #1. Use the original project’s row toggle to show or hide its linked projects. A count such as 2 CRs shows how many it has.

Only active linked projects in Approved or Won add revenue and hours to the original project’s change request totals. The added hours include governance. In the list, As signed shows the original revenue, Approved change requests shows the added revenue and request count, and Project total with approved changes shows the combined revenue. Tracked amounts stay on the reference record.

Edit or delete a request

Open the request number and click Edit Details.

On this screen: The edit form shows the request’s Type as Authored or Reference only. You can update the cause, Note, External Reference, and External URL. For a tracked request, you can also update Hours and Revenue.

Click Save when you finish. To edit scoped work, use Open in Change Request Project from the request summary.

To delete an eligible request, click Delete on its edit form or select it in the list and click Delete. Confirm with Delete. Deleting a scoped request also deletes its linked project. A linked project in Approved or Won blocks request deletion.

Find the Change Requests project permission under Settings > Users & Groups > Roles.

  • View lets you open the list and request summaries.
  • Create also lets you add requests, edit the details of your own requests, and delete your own eligible requests.
  • Manage also lets you edit the details of requests created by others and delete their eligible requests.

Merge fields for template editors

V2 templates for a linked project can use the change_order merge field for the request number, cause, note, external reference and URL, original project details, service and subservice hours, and change totals. V2 templates for the original project can use the change_orders merge field for requests that count toward its totals and revenue_including_change_orders for the combined revenue. ScopeStack assigns the active template marked Default for change requests to new linked projects when one is configured.

New to ScopeStack?

ScopeStack automates scoping, pricing, and SOW generation for IT services teams. See how it fits your process.

Book a demoBrowse the docs
Last updated on