Hi Amy, Yeah they don't impact your project % complete. That'll be driven by your Planned Hours or Duration, depending on how you configured it. I hear you on the large disparities in the Projected vs Planned. And Doug's workaround is the only solution I know of if you want to go through that. Or the easiest way to accomplish what you want is to simply ignore the Commit Dates and the Project Completion Dates. They shouldn't hurt you. But I would consider viewing the Commit Date as your friend �� . I guess I view it as a valuable tool. It's another communication option for the PM and team members to communicate dates and obtain any early warning signals. For me the Project Plan is all about early warning detection. The sooner I know of a scheduling issue, the easier it is to recover. Like you, I use the Projected Completion Date to compare to the Planned Completion Date to tell me if something is off (early warning). This could actually be your early warning sign from the team. For example, why are they setting them so far out? If the answer is that's when they truly believe they'll get them done, you get your warning that the project (plan) is now in trouble and you can have an important conversation to determine what to do (i.e. remove other and/or outside tasks from their plate, reassign tasks, etc.). If they don't have a valid reason for moving the dates out so far, it's a training opportunity �� . And once they start using them effectively you'll gain another early warning tool. There's really no right or wrong, it'll just be up to your preference. But based on the WF constraints, I believe your options are boiled down to: Ignore Commit & Projected Completion Dates (even remove them from your View) Doug's method of unassigning and reassigning Embrace the Commit Dates �� . Best of luck!
