I like the idea of submittal checklists, indeed this is a part of our business that maps very literally to what our users need to do: complete a list of tasks before submitting an electronic bill.
However, equating submittal checklists to something including stand ups seems weird to me. Would you really have a checklist saying "Did stand up meeting today." and if so, why?
The point of a checklist is to put knowledge of what needs to be done for a task in the world instead of keeping it in the head (I've borrowed this idea from The Design of Everyday Things). Checklists are for complicated things, like the aircraft checklist you mention, that require every step to be checked otherwise people may die.
I'm a fan of small checklists for software development that determine when a user story is completed. In Tracker there's tasks you can add to a story that can be used as acceptance criteria, for example.
But what good is a communication checklist? Is it really a desire to have a checklist that includes items such as "had standup meeting?" And if so, why?