Can this document be signed electronically?

Yes. Electronic signatures are generally enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted. Exceptions may apply for certain court filings, wills, or other state-specific exclusions. Ensure intent, consent, attribution, and retention are documented.

Is notarization required for signatures?

Notarization requirements vary by state and by document purpose. Many jurisdictions accept electronic attestations; some require in-person or remote online notarization with identity proofing and recorded audiovisual sessions. Verify state notary rules before assuming notarization is optional.

What fields are most commonly completed incorrectly?

Common errors include mismatched legal names, omitted firmware hashes, truncated serial numbers, missing timestamps in chain-of-custody logs, and unsigned attestations. These mistakes can invalidate certification, trigger retesting, or lead to administrative penalties; use validation checks before final submission.

How long must records be retained?

Retention depends on record type and regulation: federal tax-related procurement records often require a minimum of 3 years, HIPAA-covered health data six years (45 CFR §164.530(j)), and some states impose longer retention. Retain machine certification records per state election authority guidance.

Can RON be used for notarization?

Remote online notarization (RON) is permitted in most states but requirements vary. Typical requirements include identity proofing, audiovisual recording, and durable journal entries. Verify the specific state's RON statutes and operational standards before relying on RON for election equipment attestations.

How is e-signature evidence preserved?

Signed records should include a complete audit trail capturing timestamps, IP addresses, signer authentication method, and certificate of completion. Export signed PDFs in ISO-compatible format and maintain encrypted storage with access controls to support reproducibility and legal admissibility.

Electronic Signature
Templates
Miscellaneous
Election Voting Machines Document

Election Voting Machines Document

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

ELECTION VOTING MACHINES AGREEMENT

This Election Voting Machines Agreement ("Agreement") is made effective as of between the parties identified below.

Election Authority: Election Authority Address: Vendor: Vendor Address:

WHEREAS

WHEREAS, the Election Authority requires the supply, delivery, installation, acceptance testing and on-going maintenance of voting machines and associated software to conduct public elections in a secure, auditable and certified manner; and

WHEREAS, the Vendor represents that it is duly qualified, experienced and able to provide the voting machines, software, training and support described in this Agreement in compliance with applicable certification standards, security, chain-of-custody and election law requirements; and

WHEREAS, the parties desire to set forth their respective rights and obligations regarding the procurement, acceptance, operation and maintenance of the voting machines.

SCOPE OF WORK

The Vendor shall supply, deliver, install, commission and provide training and support for the voting machines and related software as set forth below. The Vendor shall perform all work in a professional manner consistent with industry standards and all applicable election laws and certification requirements.

Detailed Scope of Work (deliverables, installation, training, acceptance testing, maintenance): List of Machines and Serial Numbers:

PAYMENT TERMS

Total contract price: $

Payment Schedule (milestones, percentages, due dates): Payment Method:

Late payment: interest shall accrue on any undisputed past-due amount at percent per month (or the maximum lawful rate, if lower), and any collection costs and reasonable attorneys' fees incurred by the unpaid party shall be recoverable.

Invoice Address for Payments:

TERM AND TERMINATION

This Agreement commences on and, unless earlier terminated in accordance with this Agreement, continues until .

Either party may terminate this Agreement for material breach by the other party if the breaching party fails to cure the breach within days' written notice. The Election Authority may also terminate for convenience upon prior written notice as set forth below.

Additional termination provisions:

Termination for cause permitted
Election Authority may terminate for convenience upon notice
Automatic renewal (if checked, specify terms below)

ACCEPTANCE, DELIVERY AND TESTING

Estimated delivery date: . Delivery location:

Acceptance Deadline: Acceptance Criteria and Testing Procedures:

WARRANTY, MAINTENANCE AND SUPPORT

The Vendor warrants that hardware and software shall be free from material defects and shall perform materially in accordance with specifications for a period of months from the date of acceptance. Warranty remedies shall include repair, replacement or service at the Vendor's expense.

Maintenance and Support Response Time: Software Licensing and Updates:

CONFIDENTIALITY

Each party shall treat as Confidential Information all non-public information disclosed by the other party that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure. Confidential Information shall include software source code, firmware, encryption keys, chain-of-custody logs, ballots, and election operations data.

The receiving party shall not use Confidential Information except to perform its obligations under this Agreement and shall protect such information with at least the same degree of care as it uses to protect its own confidential information, but in no event less than reasonable care. Confidential obligations shall survive termination for years.

INSURANCE, LIABILITY AND RISK ALLOCATION

Insurance Requirements (types and minimum limits):

The parties' aggregate liability for direct damages shall be limited to $ except that neither party shall be limited in liability for willful misconduct, fraud, or breaches of confidentiality involving ballot or voter data.

COMPLIANCE AND CERTIFICATION

The Vendor represents and warrants that all equipment and software delivered under this Agreement shall comply with applicable election equipment certification standards in force at the time of procurement, and that the Vendor shall cooperate with any audits or inspections required by election authorities.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of without regard to its conflict of law principles.

ENTIRE AGREEMENT

This Agreement, including all exhibits, schedules and attachments expressly incorporated, constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior and contemporaneous agreements, proposals and communications, whether written or oral. Any modification must be in a written instrument signed by authorized representatives of both parties.

CONTACTS FOR NOTICES AND TECHNICAL COORDINATION

Election Authority Contact - Name: Election Authority Contact - Phone and Email: Vendor Contact - Name: Vendor Contact - Phone and Email:

By signing below, each party certifies that it has the authority to enter into this Agreement and that the information provided herein is true and complete. Signatures below constitute binding agreement to the terms set forth above.

Election Authority:

By:

Date:

Vendor:

By:

Date:

What the Election Voting Machines Document Is

An Election Voting Machines Document is a formal record used by election officials, vendors, and certifying bodies to describe, certify, and authorize voting equipment for use in public elections. It typically documents device make and model, firmware and software versions, security configurations, chain-of-custody procedures, maintenance history, testing results, and certification status. The document supports compliance with applicable federal and state election laws, helps coordinate procurement and deployment, and provides a permanent record for audits, incident response, and post-election reviews by authorized oversight entities.

Why this document matters for certification and audits

This document clarifies device provenance, operating configuration, and certification status to reduce deployment errors, enable post-election audits, and support legal defensibility. It centralizes evidence needed for compliance with ESIGN/UETA where e-signatures are used and for state election commission review processes.

Who typically prepares and relies on this document

Typical users include election officials, certification labs, equipment vendors, and procurement officers responsible for machine compliance and deployment.

State and county election officials managing acceptance testing, inventory, and deployment.
Independent testing laboratories documenting conformance to functional and security standards.
Vendors and integrators providing firmware, maintenance, and chain-of-custody records documentation.

Use-case differences often depend on jurisdictional certification rules, procurement contracts, and whether machines are used for early voting, absentee ballot tabulation, or polling place voting.

Essential sections to include in a professional document

This document should include device identifiers, software and firmware details, security controls, testing outcomes, maintenance logs, and signatory attestations to form a complete certification record.

Device ID

List manufacturer, model, serial number, hardware revision, and unique asset tag. Include manufacturer lot numbers and any aftermarket modifications to ensure accurate traceability across procurement and audit trails.

Software/Firmware

Record firmware and software versions, build numbers, cryptographic module versions, and applied patches. Note update sources, installation dates, and verification checksums to support reproducible configuration and forensic review.

Security Controls

Describe access controls, physical tamper-evidence, authentication methods, audit logging, encryption in transit and at rest, and remote update safeguards. Specify any federal or state security standards the device meets.

Testing Results

Summarize functional, interoperability, penetration, and conductive testing results. Attach test protocols, pass/fail criteria, dates, testers' identities, and any corrective actions or re-tests performed and version-controlled evidence files.

Chain of Custody

Provide a chronological custody log with timestamps, handler names, locations, transport methods, and tamper-seal identifiers. Include storage conditions and environmental sensor data when available for audits.

Signatures

List authorized signatories with titles, organizational affiliation, and electronic or notarized signatures. State the authority basis for each signature and retention location for original signed records.

Step-by-step checklist to prepare and validate the document

This step-by-step checklist helps staff complete and validate an Election Voting Machines Document before deployment or certification submission.

01

Prepare document: Gather device specs, serials, and procurement references.
02

Run tests: Execute functional and security test suites with dated logs.
03

Collect attestations: Get authorized electronic signatures or notarized attestations.
04

Submit package: Send to state certification office and retain copies.

Recommended digital workflow settings for eSubmission

Configure a digital workflow to collect signatures, attach test evidence, and route approvals to certification authorities.

Field	Configuration
Document template	PDF with fillable fields and audit trail enabled
Signer order	Sequential or parallel routing per state rules
Authentication	Email + SMS OTP; KBA optional for higher assurance
Attachments	Attach test logs, firmware hashes, and photos
Retention	Set retention per jurisdiction and regulatory requirements

Typical eSubmission flow for signed records

Typical routing covers upload, field placement, signer authentication, signature capture, and automated delivery of completed records with audit logs.

Upload: Upload draft PDF and supporting evidence files.
Place fields: Drag signature, date, and checkbox fields onto form.
Notify signers: Send secure links or email invites with access codes.
Archive: Store signed record and audit trail in compliant storage.

Platform capabilities to support election equipment records

Ensure the signing platform supports PDF and DOCX, secure audit trails, and integration with election management systems to streamline submissions.

File formats: PDF, DOCX, XLSX supported
Integrations: Salesforce, NetSuite, Google Workspace
Authentication: Email, SMS OTP, SSO options

Security and compliance snapshot

Encryption in transit: TLS 1.2 and 1.3 in transit

Encryption at rest: AES-256 encrypted at rest storage

HIPAA: BAA required for PHI workflows

ESIGN/UETA: Compliant with ESIGN and UETA

21 CFR Part 11: Supports FDA-regulated electronic records

Certifications: SOC 2 Type II and ISO 27001

Common preparation mistakes to avoid

Incomplete firmware or software version records hinder reproducibility and can invalidate test results during certification or post-election forensic analysis.
Mismatched serial numbers, asset tags, or model identifiers between procurement lists and physical devices lead to inventory discrepancies and audit findings.
Lack of signed attestations or unclear signer authority complicates legal defensibility and may require re-verification or notarization.
Poorly documented chain-of-custody, missing timestamps, or absent tamper-seal identifiers increase the risk of contested results and regulatory scrutiny.

Potential consequences of incorrect or incomplete records

Certification rejection: Deployment delays and retesting required

Legal challenges: Increased litigation risk

Financial penalties: Contract penalties or fines

Evidence inadmissible: Unsigned records may be excluded

Security breach: HIPAA or data breach liabilities

Operational impact: Polling disruptions and voter confusion

Key timing considerations and deadlines

Key deadlines depend on procurement cycles, certification windows, testing schedules, and state election reporting requirements.

Procurement window:

Align with vendor lead times and contract milestones.

Certification period:

Submit test reports within state-defined certification window.

Firmware updates:

Schedule updates outside of ballot counting periods.

Record retention start:

Effective date establishes retention clock for audits.

Election day freeze:

No system changes within legally specified pre-election hold.

eSignature vendor comparison for Election Voting Machines Document workflows

Compare common eSignature vendor criteria relevant to Election Voting Machines Document workflows, focusing on price, compliance, and envelope limits.

	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	7-day free trial, no credit card	Varies by vendor and plan	Varies by vendor and plan	Varies by vendor and plan	Varies by vendor and plan
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently asked questions and quick answers

Answers to common questions about completing, signing, and storing an Election Voting Machines Document, including eSignature options and handling jurisdictional differences.

Need help? Contact support

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now