As part of the implementation of our brand promise and a 100% complete home, we will be adding an additional task “QAI Verification” to coordinate 2M returning to the home. During their return they will be checking to see if all items discovered during the QAI have been addressed. There will be an exception process where items will be discarded with the approval of certain managers (this process to be outlined at a later date). Below are the steps that must be taken to ensure a smooth transition into using this task.
*The term PDS (Customer Meeting) refers to the New Home Orientation (NHO). We will be changing the name in the system to NHO at a future date
Existing Schedules with a QAI scheduled for 2/17 or later
On 1/16 at 6pm we will be manually adding the “QAI Verification” task to any schedule with a QAI date of 2/17 or later. The task was placed on the same day at the QAI.
Actions needed
QAI Verification to be placed 5 Business Days after QAI date
PDS (Customer Meeting) task to be placed 1 day after QAI verification
Settlement task to be placed 2 days after PSD (Customer Meeting)
IMPORTANT
If your QAI slips after 2/17 you do not needed to add the QAI Verification task
If you have communicated to your customer their New Home Orientation date or their Settlement date is set, you do not need to update
Existing Templates
On 1/16 at 6pm we will be manaully adding the “QAI Verification” task to ALL TEMPLATES. We will be making the following updates.
QAI Verification will be added 5 DUCs after the current location of your QAI task
PSD (Customer Meeting) will be moved to 1 Day after the QAI Verification task
Settlement will be moved to 2 days after the PSD (Customer Meeting) task
Actions needed
Update all supportive tasks to the sequence of you choosing (QAI Reclean, PSD Reclean, etc)
IMPORTANT
You should update your templates as soon as possible. As new schedules are created they will use this same sequence and require you to make updates in your schedule. Updating your templates will decrease the amount of long term work required
0 Comments