You ask an assistant to extract tasks from an old message. It says the file should arrive tomorrow, but tomorrow was relative to the sender's original message, not the day you pasted it into the chat. A plausible schedule can be wrong from its first assumption.
Provide the original message timestamp and relevant time zone when you have them. Ask the assistant to preserve the relative phrase beside its proposed calendar date. If the timestamp is missing, mark the date as unresolved instead of using today's date automatically.
Try a harmless example: a message sent on a Monday says tomorrow afternoon. The intended day is Tuesday relative to that message. A forwarded copy arriving on Thursday does not change the original reference point. “Afternoon” still does not specify an exact time; leave the hour unresolved rather than inventing one.
Check quoted replies separately. One thread can contain several messages written on different days, each with its own tomorrow or next week. Keep each instruction attached to its author and message date. Before creating real calendar events, confirm unresolved dates with the responsible person. Turning vague wording into a precise timestamp should expose the assumptions, not hide them.