Well, everything's a comparison of that date, either as a straight date or as a calculated field. For us it starts with being able to have a real, unique way to filter on that task, so whether that is a unique name ("Send email" becomes a phrase that no other tasks can use) or some other identifier (a milestone iD, a template task ID, a unique assignment), we can pull a list of that task. (so that's the basic answer to your question) Next step is setting up any peripherals you need. If you look to see whether the project is completed on time, then you're looking at actual completion date of that task vs planned completion date of that task. However if your PMs have been coached to tweak their dates you might actually want to compare actual completion date or planned completion date of the task against the default baseline planned completion date. If you're trying to figure out durations, it might be difference in time between the project actual start date and the task actual completion date, and this might be a calculated field on the custom form tied to the task. If you're working on showing this in the perspective of a project deadline report, you might be running a project list with a collection report that is tied to looking for that task based on the unique identifier and reporting on the planned completion date. And so on. -skye