So sorry I did not see your post earlier!!
(Was celebrating our son's 16th bday -- pretty thrilled and overwhelmed that we've got him to this age alive and in one piece. You will understand in a few years yourself.
)
First, I'm reminded of a couple of threads (here and old place -- Schools and OffTopic) as to "Do NOT Feed this Child!" directives.
Offering to feed is the same as
intent to feed in my personal definition of things. I am not an attorney. I'm just interpreting the English language. Proving intent is always hard -- for lay persons AND legal authorities.
Sounds like part of the "retrain" needs to include a black-and-white, printed up list of definitions. This would be attached to the 504. I'm serious and not joking here. Remember how we used to have to define "tree nut" (well, some of us still need to be doing that) . . . with all the nuts listed?
Besides the retraining and serious discussion and WRITTEN understandings, there needs to be a signature page for the 504 (referenced in the accommodations) which requires EACH AND EVERY staff member that has ANYTHING to do with the student to read and sign the 504 with something to the effect of "I have read and fully understand ____ (child name) 504 and will comply."
As to the email suggested by CMdeux -- I put my own email addy in the "to" line. I send it to myself. I go back later (after steam is no longer coming from me ears and I am not yelling bad words) and sit down, open, and pretend I am the other person now reading my email.
It has kept me -- MOST of the time -- from sending something I might later regret.
Then I change it in MSWord (copy, paste) and send what needs to be sent.
However, I believe something of this seriousness (your candycane situation) should be addressed by parents within 24 hours, or it can be argued (by other side) that it really wasn't "all that important".
For extreme situations, we've sent emails within 4 hours and delivered a printed copy of the email (by hand) to the main office / admin in charge.
If you've not become familiar with the great documentation resource that I love -- here is the link:
Re: DOCUMENTING (cya)