Hi Adam, Weeeeeellllll. Sort of. I guess it depends on what you use your schedule for. You can go to Setup > Project Preferences > Projects and change Typical Hours per Day. Then in the Project don't select a schedule and it'll default to this. But the behavior is the same as if you used a schedule with these same settings. You can set this to 8 hours and not touch your schedules. Not sure if that helps, but it's an option. I'll let someone else chime in if they use a 9.5 or 10 hour schedule. For us, we use 8 hours in the schedule and the days line up appropriately. If people spend 10 hours in a day, they just log it in their Actuals. If I estimate they're going to spend 10 hours a day for a week, I just put 50 hours in the Planned Hours to calculate the estimated cost (but it doesn't impact the timeline). Basically, you're telling the tool what you want a Day to represent. In MS Project you would enter the Hours of Effort (i.e. Planned Hours) and it would do the Duration calculation for you (in this very same way – depending on how you define a "day" in the schedule). In WF it's thinking the same way, but it's using Duration instead to do the same thing. It's thinking about it in terms of effort. So it equates 1 day to whatever you define in the schedule. WF ignores the Planned Hours in regards to timeline. Even if you set that Task Duration Type to Effort Driven, it's going to change your Planned Hours to coincide with your schedule and duration (as opposed to calculating your Duration). What is the drawback to setting the schedule to 8 hours a day?
