Thanks for pointing this one out, Vic, Sounds like your just-update-the-planned-hours-as-needed Workaround is sufficient, and I'm a big fan of Baselines, too, but I was mulling over what a Better Way would look like (if there even is one). Using an example of a Task with 40 Planned Hours originally, and 15 Actual Hours done so far, but the realization that it's likely still going to take 35 hours to finish from this point (so an extra 10 hours above the 40, which is 50 in total): · At the Task Level, add a numeric text parm called "Additional Hours" (e.g. 10), a numeric calculated parm called "Estimate At Completion" (e.g. Planned Hours + Additional Hours = 50), and a numeric calculated parm called "Estimated Hours Remaining" (e.g. Estimate At Completion – Actual hours = 45), then add a Task view to show all of these in a grid for ease of data entry and gut checking (e.g. if Estimate At Completion > Planned Hours, show in Yellow, etc.) and as many groovy charts as you wish (since the data is persisted) · Same as above, but with additional numeric calculated parms for some interesting stats for the grids and charts such as "Estimate Over Planned As Percent", "Additional Over Planned As Percent", etc. · Similar to above, but – with the convention of always using having a default baseline in hand –replacing all the Planned Hours with the Default Baseline Task's Planned Hours instead, conceptually driving from the last approved Baseline (for stability) vs the Planned Hours (lest someone have changed them "inadvertently") As an aside, I the first two concepts in the (competing) software company that I owned before I changed jerseys and partnered with Workfront. You've reminded me how powerful they were! Regards, Doug