When an employee leaves an organization, an admin needs to change that user’s settings to “Inactive.” That’s always a best practice!
Beyond that, you need to follow some steps if that former employee is included in your company’s forecast. So here’s a sure-fire way to make sure that your company’s forecasts do not include that former employee’s data:
- Create a new role, and name it “Inactive.”
- Go to the User Detail page for that former employee.
- For Role, select this new Inactive role.
- For Reports To, clear the field. In other words, remove the value so that it’s blank.
Why is this so foolproof? First, because the Inactive role is not included in your forecast paradigm. Second, because a forecast won’t run if the Reports To field is blank (unless that person is the top person in the forecast hierarchy).
Now let’s turn our attention to users who reported to the former employee:
- Go to the User Detail page and update their Reports To field.
- Verify that the employee you select for the Reports To field is assigned a role that is included in your forecast hierarchy.
Remember that forecasting requires an unbroken chain leading to a single top-level user. Everyone’s role in the chain must be included in the forecast hierarchy.
- After you save your changes, run through the Forecast Definition wizard to refresh your company’s forecast settings: Admin > Data Rules & Assignment > Forecast Definition > Update button
