Change Log

The goal of the Master Change Log (MCL) is to create a single unified workflow in Blueprint that can capture, manage, and track changes to plans and/or budgets for previously approved work. Examples of reasons to submit a change log request may be changes to architectural plans or a finish schedule for a development. 

Create a new Change Request

Simply navigate to "Change Log" on the global navigation bar and click the blue button at the top right to, "Create New".

Note: The Default on the Change Log screen is to only show "your requests" To see all requests uncheck the box.

From here you will need to fill out details regarding the Change Requests. The Required Fields are Title, Description, The Change Source, What Development or Lots are impacted and the level of urgency. 

On the right you can also select the Change Type and what Assets are affected in the drop down. If you choose you can also upload an image or document as back-up to the Change Request. Once submitted you will be able to make changes to details about the request in the side panel.

Note: Assets will be auto-selected based on the "Change Source". Assets can be removed using the drop down.

To Do's Created when a Change Log Request is Submitted

Change Request utilize the To Do's feature to ensure that work and review are completed. 

Note: Comments should be made on the Change Log Request itself and not the TO DO. In Order to Reject a review leave a comment on the Change Request but still mark the To-Do as complete. 

• The first set of "Initial Review To Do's" is for the user to add impact. A requested change can impact budget, revenue, margin, schedule, and any number of assets. If you are an impact reviewer, you should review the detailed description of the proposed change, fill out the impact fields as relevant to your role, and review the list of impacted assets already selected. Keep in mind, the list of impacted assets may not be complete when it reaches you and it is the impact reviewers' responsibility to select any additional assets that might be impacted.
  Once all impact to-dos are marked complete and the request is sent for approval, updates can no longer be made to the change request.. 
• Once the Change Log Request is Approved a second round of To Do's will be generated to implement the change. These To Do's will be directly related to the "Assets" on the Change Request. For example this could be a To Do prompting the Designer to update the Finish Schedule. 

Approvals

Once the "initial review" and "impact" To Do's  are marked as complete an Approval will be generated. The Approver will be based on the Change Type. This Approval flow works just like other approval flows work and will surface on the Approvers Dashboard. 

After the "Change Request" is approved implementation To Do's will be created. 

Note that the "Reject" button at the bottom of the drawer can be used to rescind a Change Log request. 

Status

The status of a "Change Request" will be as follows as the request runs through the process:

• Needs Review - After the request is initially created but before the Initial Review To Do's are Completed
• Ready for Review - Once the Initial Review To Do's are Completed but before the Add Impact To Do's are completed
• Ready for Approval - Once the Add Impact To Do's are created but the Change Request is still waiting for Approval
• Approved - Once the Change Request is Approved
• Denied - If Approval is Rejected
• Completed - if the Implementation To Do's have been marked Complete
• Reversed 

Adding a new Asset

Assets are things like Finish Schedules or Architectural plans. When submitting a Change Request you can select an "Assets" that will need to be updated as part of this change. If an asset is missing from the drop down list you can add an asset by clicking on the gear icon ⚙️ at the top right and the Functions. From there you can choose your Function and click the pencil icon ✎ to make changes or add assets.

Understand To Do Assignees and Change Types

There will be a series of To Do's generated when a Change Log Request is submitted. The To Do's are based on the business functions associated with the Change Types.  Choosing a Change Type will impact which Business Functions need to be a part of reviewing, approving and implementing the requested change. If you click on the gear icon ⚙️ and then "Functions" you can see the relationship to business functions at Homebound. Below is an example:

Relationships between Change Requests

Using the buttons in the drawer on the right a Change Request can "Block a Change Request", "Add a Dependency" and or "Add a Link" to other Change Requests. Here is how these work:

• Blocking Other Change Requests - Mark this Change Request as Blocking another one. If this one is then rejected, the other is not needed.
• Dependent on Other Change Requests - Mark this Change Request as Dependent on another. If that one is then reject then this one is not needed.
• Related To - Link this Change Request to another without status dependencies. If one is then rejected, the other will not be affected. 

Questions? Feedback? Email us at Product-Support@Homebound.com or chat with us in Blueprint!