Client Change Request (CCR) Projects
How to request a client change in HubSpot
Overview
A client change request (CCR) project is how we log and track a change a client has asked for. Each CCR is a HubSpot project in the Client Change Request pipeline and is always associated with the client's company record.
Use a CCR project for any of the eight request types listed under Sub-Type Guide below. The properties you fill in when creating the project determine the tasks it generates, so accuracy at creation is what makes the project work.
Dependent properties drive the tasks
The dependent properties are imperative because they drive the tasks on the project. They SHOULD NOT BE CHANGED AFTER THE PROJECT IS CREATED.
The task list is built from the values chosen at creation. Check every dependent property before you save the project, and enter each one carefully the first time.
How to create a CCR project
- Go to the Customer Success workspace and open the client's Company record. Create the CCR project from the Company record, not from the general Projects area.
- Set the Pipeline to Client Change Request.
- Name the project using the standard format: Client Name – CCR (for example, "Sample Client – CCR").
- Complete every dependent property (see Field Reference below).
- Enter a summary of the request in Description.
- Under Associate Project With, confirm the Company the request is for is associated. Every CCR project must be associated with its client's Company.
- After choosing Create project, go to the Overview tab on the project and fill out the additional fields provided for the sub-type you chose. Every sub-type has its own additional fields.
- Complete the Client Documentation task.
Field reference
All nine properties below are dependent properties. Do not change them after the project is created.
|
Property |
What to enter |
Options |
|
App loc (CCR) |
The location the client is on |
Greenville or Shreveport |
|
Sub-Type (CCR) |
The type of change requested |
One of the eight sub-types below |
|
Freight Payment Type (CCR) |
How the client's freight is paid |
Settlement or Voucher |
|
LTL CM |
Whether the client is an LTL CM client |
Yes or No |
|
Parcel Acct Update (CR) |
Whether a parcel account is affected by this change |
Yes or No |
|
Change Effective Date |
The date the change should take effect |
Date |
|
Location Name/LocNo |
The location name or LocNo the change applies to |
Free text |
|
Division |
The client division the change applies to, if any |
Free text |
|
Address |
The address the change applies to |
Free text |
Description is not a dependent property but is still needed. Use it to summarize the client change request.
Sub-type guide
Choose the one sub-type that matches the request. Pick carefully, since it cannot be changed after creation.
Each sub-type adds its own fields to the project's Overview tab. Fill these out after the project is created.
|
Sub-Type (CCR) |
Use it when |
Clients |
|
Billing distribution changes |
You need to change AFS invoice distributions and/or Greenville Obligation distributions. That is all this sub-type covers. |
See note below |
|
Business rule request – Greenville clients only |
The client is requesting a business rule update, addition or removal. |
Greenville only |
|
Close location |
You need to close a location. |
Greenville and Shreveport |
|
New location |
You need to add a location. |
Greenville and Shreveport |
|
Update location |
You need to update a location. |
Greenville and Shreveport |
|
Parcel account updates |
You need to add, close or update a parcel account. |
Greenville and Shreveport |
|
Gl coding changes |
You need to request a GL coding change. |
Greenville and Shreveport |
|
New carrier setup |
You need a new carrier set up. |
Greenville and Shreveport |
Other reporting distributions. Billing distribution changes covers only AFS invoice distributions and Greenville Obligation distributions. Any other reporting distribution change goes through IT or the SQL Client Report Manager. See How do I update a SQL report subscription?
Checklist before saving
- Name follows Client Name – CCR.
- Project was created from the client's Company record in the Customer Success workspace.
- Pipeline is Client Change Request.
- Every dependent property is filled in and correct, because none can be changed later.
- Description summarizes the request.
- The project is associated with the client's Company.
- The sub-type's additional fields on the Overview tab are filled out.
- The Client Documentation task is complete.