How to mark a task as complete without adjusting the actual work

[J Wishart]

Say you have a task that takes only 4 hours. A miracle occures and you finish
the task in 2 hours.

HOW! Do you specify that that task is complete without the Actual hours
changing and therefore the cost all being used etc.

I want the task to be checked (Completed!!) and i want to be able to say
that i was able to complete this task in half the time and tell the boss that
i saves this much money on this task.

 

[Jan De Messemaeker]

Hi,

Use the fields actual woork and remaining work.
Put Actual Work to 2 and remaining to 0
HTH

 

[John Sitka]

I want the task to be checked (Completed!!) and i want to be able to say
that i was able to complete this task in half the time and tell the boss that
i saves this much money on this task.

I use a view that includes a custom task field (number) that is the exact original estimate.
It is a non calculated enduring value. Baseline does the same thing and is nice because of the native
Gantt chart representation but sometimes that is too sophisticated. As Jan said the reporting comes
in; in your case;

Use the fields actual woork and remaining work.
Put Actual Work to 2 and remaining to 0

The custom task field has an enduring value of 4 which is the original work estimate, with no need to
understand baselines. I did it most for the convienence of not having to explain baselines to other users.
then just made them nice reports that show "We beat estimate!" on this task or "We went over estimate
on this task" Almost immediately there was a gain in focus on each assignment to beat estimate. PM's tightened
estimates, resources responded, and a balance was struck. "TRUE" estimates became visable, not ones with built in
bloat, trust was built between resource and scheduler. Resource started looking for root causes of why an assignment
would take longer or shorter. Almost always it had to do with someone messing with their flow, That is interruptions OR waiting
on a needed preconditon.