Header
Clear title, event identification, and version number. Include organizer name, ballot ID, and instructions for eligibility to prevent confusion during distribution and initial processing, and contact information for questions.
The Event Shed Ballot standardizes input, improves accuracy of community decision-making, and produces an auditable record. It reduces ambiguity in outcomes, protects procedural fairness, and supports legal enforceability when electronic signatures meet ESIGN and UETA requirements.
Typical users include organizers, property owners, and municipal officials responsible for event decisions and permitting.
Proper role assignment ensures ballots are collected and certified by authorized personnel and that results are traceable.
Clear title, event identification, and version number. Include organizer name, ballot ID, and instructions for eligibility to prevent confusion during distribution and initial processing, and contact information for questions.
Step-by-step voting rules, selection limits, and tie-breaking procedures. Define marking conventions (X, checkboxes) and clarify how ambiguous responses will be handled to reduce counting disputes during canvass.
Fields capturing voter status, residency, or membership. Instructions should state who may vote and any supporting documentation required to verify eligibility during review and timeline for verification.
Clearly list each option or proposal with concise descriptions. If numerical votes are used, provide calculation method and examples and provide sample filled ballot to avoid interpretation errors.
Specify acceptable signature methods and any required authentication steps. For electronic ballots, require consent and a verifiable signer identity traceable in the audit record, including timestamp and IP.
State retention period for completed ballots, draft versions, and audit logs. Include export formats and procedures for long-term archival and legal hold scenarios and responsible custodian.
| Field | Configuration |
|---|---|
| Authentication Method | Email link, SMS code, or KBA |
| Signing Order | Sequential or parallel signer routing |
| Conditional Fields | Show/hide fields based on responses |
| Retention Policy | Automatic archival after signature capture |
Digital delivery and signing require platform support for secure transport, authentication, and audit trails across devices.
Date ballots become available to voters
Final date and time ballots must be received
Start and end dates for tallying returned ballots
Date officials certify results and publish outcomes
Window for filing disputes after certification
| Criteria | Electronic Signature | Digital Signature |
|---|---|---|
| Legal Status | esign/ueta accepted | esign accepted; pki preferred |
| Technology | varied methods | pki certificate |
| Non-repudiation | audit-trail evidence | strong cryptographic proof |
| Typical Use | general ballots and approvals | high-assurance regulated records |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | Yes, 7-day free trial | No | No | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |