I have a script that sets a date/time field on our cases for use with our initial response time. We were having some time zone wackiness that I think I have solved and now I am tying to find those that were set wrong.

I feel like I should explain that. When a script (if you use the right parameter) or workflow sets the date/time field it respects the users localization preference. We were unaware that when a user gets their login they have a preference based on our office location (west coast) and so when a user would trigger the script to set the value it would show in the UI as west coast time, even if they were east coast, but the system notes always showed the right time, so I would imagine that the system notes date set field key off