Hmmm, that is quite a challenge, I can see that now. Without knowing which task is the go live event, I don’t know how it would be possible to compare the project-level go-live date and anything found in the task list. I’m really inclined to recommend you create a custom task attribute, and then use that attribute to do the report. It gives you so many more options without requiring you deep dive into some Text Mode coding. This seems to be a more elegant solution, in my opinion. Sorry, I think a change in the way they represent the go live date is needed. We also have a custom task attribute called “Promise Date”. As sometimes happens, people make commitments (promises) when certain aspects of the project will be done. These promises may be fact-based or may not be. They may relate to the baseline or not. Okay, sometimes someone just commits to a date without checking with the PM. Anyway, we keep track of that promise date, so that we can compare the planned/projected dates with what was promised. If expectations need to be reset - if that promise needs to be adjusted - we can identify that straight away. This recognizes that sometimes work has multiple dates associated with it - last approved completion date (baseline), current forecast completion (planned), projected completion, and whatever date someone promised it would be done. Sorry I couldn’t be of more help. Eric