The message that became a promise
The school discussion club wanted to invite a local science writer to its next meeting. During a planning conversation on Monday, the organiser said that the writer might be available in the following month. She asked the students not to advertise the visit until a date had been confirmed. For the moment, they could prepare questions and suggest possible topics.
By Wednesday, a message in the class chat said that the writer would definitely come next Friday. Several students began making posters. Nobody intended to mislead anyone, but each retelling had removed a little uncertainty. A possible visit had become a promise, and an unspecified month had become a particular day.
Lena decided to check the original information. She did not accuse the student who had shared the message. Instead, she asked where the date had come from. He explained that another friend had mentioned Friday, but he could not find the earlier message. Together, they contacted the organiser and learned that no date had yet been agreed.
The group then posted a correction. It explained that the invitation was still being discussed and that a confirmed announcement would appear later. They also stopped printing the posters. Although the mistake caused extra work, correcting it early prevented visitors from making unnecessary plans.
At the next club meeting, Lena suggested a simple reporting rule. A summary should separate what somebody said, what the reporter thinks it means and what remains unknown. Exact quotations should be marked clearly, while uncertain information should keep words such as might or possibly. The rule did not make every message longer. It made the most important differences easier to see.