Voter Management System Development Timeline

Allow notes and affiliation information to be saved, searched, uploaded, and included in approved reports.

Checking: Check old records, uploaded files, reports, and access restrictions.

Expected result: New voter information can be stored safely.

Show notes and affiliation in voter forms, profiles, lists, and filters.

Checking: Check long notes, blank information, existing records, and different screen sizes.

Expected result: Voter notes and affiliation completed.

Give Validators only the access needed to review voters and support the role in user management.

Checking: Check what each type of user can see and do.

Expected result: Validator access and permissions completed.

Record the assigned Validator, result, date, remarks, and reason when a voter needs correction.

Checking: Check reassignment, repeated actions, incorrect actions, and activity records.

Expected result: Voter verification foundation ready.

Give Validators a clear list of voters waiting for review, with search, filters, and review actions.

Checking: Check loading, errors, empty lists, and access restrictions.

Expected result: Validators can review voters.

Display the assigned Validator, verification status, date, and summary counts on voter pages and the dashboard.

Checking: Confirm that totals, filters, updates, and area-based access are correct.

Expected result: All requested features completed.

Correct issues affecting Leaders, assignments, notes, affiliations, and verification.

Checking: Perform a complete system check and confirm that it can be prepared for release.

Expected result: First complete test version ready.

Update system notes, user instructions, and the list of remaining concerns.

Checking: Run regular checks and correct minor issues only.

Expected result: Project records and instructions updated.

Warn users about possible duplicate voters and prevent invalid or incorrectly connected information.

Checking: Check similar names, repeated records, old records, and incomplete information.

Expected result: Duplicate and invalid records reduced.

Limit access to notes, affiliation, verification details, assignments, and reports by role and assigned area.

Checking: Try accessing restricted information using different user accounts.

Expected result: Sensitive voter information properly protected.

Keep clear records of Leader changes, assignments, verification decisions, reports, and permission changes.

Checking: Confirm that important activities show who performed them and when.

Expected result: Important system activities traceable.

Review sign-in protection, user permissions, request limits, and information-access rules.

Checking: Test incorrect, unauthorized, and suspicious actions.

Expected result: Main security protections verified.

Improve file checking, size limits, report permissions, and protection against unsafe spreadsheet content.

Checking: Test invalid files, very large uploads, incorrect formats, and unauthorized downloads.

Expected result: Voter file handling secured.

Review secure sign-in storage, opened links, internal communication, and update protection.

Checking: Test suspicious links, invalid requests, and secure-storage failures.

Expected result: Desktop security verified.

Improve start-up time, large voter lists, memory use, and background activity.

Checking: Measure start-up speed, memory use, screen response, and stability during long use.

Expected result: Faster and more stable desktop application.

Provide clearer messages and safer recovery when internet access is slow, interrupted, or restored.

Checking: Test slow internet, lost connections, reconnection, expired sign-ins, and failed updates.

Expected result: Connection problems handled reliably.

Improve searches, filters, dashboards, assignments, and work lists when handling many records.

Checking: Test many users, large voter lists, group assignments, searches, and long sessions.

Expected result: System performance confirmed for expected use.

Confirm that system information is backed up and an earlier version can be restored if needed.

Checking: Restore a backup and check voters, users, assignments, and verification history.

Expected result: Backup and recovery process proven.

Allow selected administrators, field personnel, and Validators to use the nearly finished system.

Checking: Record feedback and correct problems that would prevent normal use.

Expected result: Client-approved release version ready.

Stop adding features, apply final approved fixes, and prepare the installer, launch plan, and user guides.

Checking: Complete the final check of web access, desktop access, permissions, security, and stability.

Expected result: Final production version approved.

Publish the website, online services, new domain settings, system updates, and desktop application.

Checking: Confirm sign-in, user permissions, voter records, backups, and recovery readiness.

Expected result: Production launch and project handover completed.