Issue/Symptom/Question

Why does the job that just started show a negative Projected Variance?

Applies To

Job Forecasting

Resolution/Fix/Answer

The Projected Variance is the difference between the Estimate and the Forecast at Complete.  

If a Job has a Forecast posted in the first month after the Estimate is loaded, then the next month the Estimate is backed out or moved to a different Costcode, the Forecast from the first month remains.  This can also happen if the Forecast is posted in the first month, and the Costcode is set to Inactive.  Future Forecasts will exclude the Costcode when the Costcodes are loaded.  This scenario has the likelihood of creating an unintended Projected Variance.  The Forecast from the first month not being corrected in the second month with the change in Estimate creates the difference between Estimate and Forecast at Complete.

To correct during Forecast Entry, enter the Costcode on the top half of the screen and enter the correct Forecast at Complete or Forecast to Complete.  If a message shows that the Costcode is Inactive, Active that costcode in the Costcode & Estimate Entry window, then load the costcodes again in the Forecast Entry window.  The Costcode should show up now so the Forecast can be set to match the Estimate, thus clearing up the Projected Variance.  Set FAC to zero or FTC to zero (when there is a zero estimate) to address the Projected Variance.