Invitations.

An invitation should explain who is asking, what is being decided, how to respond, when collection ends, and where assistance is available. Start with the original wording examples, then adapt them to the actual method and approved rules. The examples are not live messages or permission for a particular decision. Replace fictional details and verify every destination before using them in your organization’s own communication system.

Next, consider delivery and access together. A sent message is not proof that a member read it, and an activity signal is not a completed ballot. Prepare a controlled recovery route for missing invitations without creating additional entitlements. Review the message as readable text, then test the separate ballot’s keyboard, error, and confirmation paths where relevant. These connected guides help make the invitation understandable and the next step workable.