Page 22 - Unanet GovCon: Managing Project Execution and Control - Participant Guide (ILT)

TOTAL
PROJECT CODE TO-DATE BACKLOG REMAINING
BOT - EOT FUNDED
PM3-FORECAST-CP

PM3-FORECAST-FP

PM3-FORECAST-TM

Corrective Actions
To address the findings revealed by the periodic review, Unanet recommends using
corrective actions to monitor and control project performance. There are three viable
options to correct a project that is not meeting established metric thresholds: do nothing,
rebaseline, or reforecast. In this lesson, you will review the circumstances under which
each corrective action should be applied and how it should be implemented, then
perform the appropriate corrective action for Gus Lead’s project.

Corrective Action: Do Nothing
There are a few common reasons to “do nothing” despite a particular project or task
exceeding the monitoring thresholds for one or more of the corporate KPIs. If project
managers are aware of upcoming overtime or paid leave, anticipate expense reports
being submitted shortly, or expect to receive subcontractor time or expense charges in
the near future, the appropriate action is to do nothing until actuals have been
submitted. Unanet recommends creating a Project Note to document the circumstances
leading to a decision to do nothing during each periodic review.

Tour 3.2 – When and How to Do Nothing
Log in as Gus Lead (glead/welcome), the Project Lead. Users with the Project
Manager role can also perform the recommended process.

Tour Highlights
• Review the use of Project Notes and Note Types
• Add a Note to a Project

LESSON 3: MONITORING AND CONTROLLING PROJECT PEFORMANCE
©2022 Unanet. All rights reserved. 22