Work vs. Budgeted work

Work is a rollup field, so if a project has subitems you cannot set work at both the subitem and project level.  Budgeted Work (I think this used to be called budgeted hours) does not rollup and is designed to be a manually set field that you can set at any level.  I would recommend using the Work field whenever possible since that is what the system is expecting for processing other fields like Work Variance (difference between Actual Effort and Work). 

So if I set budgeted work on sub-items this will not roll up to the project level? I guess baselines are to be used then for tracking initial (budgeted) work vs. actual?

Do you have any suggested use for budgeted work? Or is it a relic?

Yes, it won't roll up.  Its original use case was to allow PMs to quickly add a high level estimate to the project level before building out the entire plan. 

I still don't get this field. Is seems to be calculated somehow. It's possible to add custom value but when pressing restore, the field is calculated.

I still don't get this field. Is seems to be calculated somehow. It's possible to add custom value but when pressing restore, the field is calculated.

Edit: Sorry I meant the field "Budgeted Cost".

Sidenote: Budgeted Work now rolls up.  

As for budgeted cost, this is calculated by default based on the assigned resource's rate and the number of estimated work hours (the Work field).  This field has always rolled up to the project level and can be manually overwritten.

Yes, Josh, you've listened :-)

I think we may find a need for this...