Skip to content
Phase 1
11 May – 16 Jul 2026
10 weeks · Foundation & core modules
Phase 2
20 Jul – 17 Aug 2026
4 weeks · Validation, testing & analytics
Phase 3
17 Aug – Sep 2026
~6 weeks · Pilot, rollout & production
Project timeline — May to Sep 2026
46
Total deliverables
13
Governance registers
3
Key personnel
28
Technical oversight items
Platform modules under M Hub oversight 5
Module 1 — mobilisation tools
Agent profiles; member registration; PPDT; VRIV; VMT / GOTV; pledge-to-vote; SMS/WhatsApp/voice campaigns; reminder scheduler; canvassing logs; response tracking; forum app
Sch. 1 | Primary phase: Phase 1 build, Phase 2 validation
Ph 1Ph 2
Module 2 — election day tools
Agent check-in; vote confirmation; digital tally sheets; photo evidence; AI photo processing; offline queue; call-centre fallback; incident and legal vault; War Room dashboard
Sch. 1 | Primary phase: Phase 1 build, Phase 2 testing
Ph 1Ph 2
Cross-module — projection & analytics
Projection tool (collection data, vote confirmations, social signals, DR submissions, exit polls); analytics and dashboard (geographic heatmaps, trends, gap analysis, filters, exports)
Sch. 1 | Phase 1 logic, Phase 2 finalisation
Ph 1Ph 2
Delivery channels — all tiers
Flutter mobile app; web dashboard; USSD; SMS/WhatsApp; REST API; WhatsApp/Telegram chatbot; forum app; call-centre data entry interface
Sch. 1 | M Hub to verify channel-by-channel readiness and test coverage
All phases
Non-functional requirements — verification targets
5–10M member records per tenant; 50,000 polling-station submissions in 4 hrs; sync under 2 min; 99.5% uptime standard / 99.9% on Election Day; APK under 30 MB; 7 days offline capacity
Sch. 1 | M Hub to verify load test, security audit and pen-test evidence in Phase 2
Ph 2QA
Phase 1 — Foundation & core modules
11 May 2026 to 16 Jul 2026
10 weeks
M Hub governance deliverables — due at Phase 1 commencement 5
Project governance structure established
Governance framework per Schedule 4 set up; all registers opened; master project plan baselined against Phase 1 scope and roadmap
Cl. 6.1–6.3 | By 11 May 2026
Governance
All 13 governance registers opened and live
Risk register, issue log, dependency register, change-control register, decision log, acceptance register, deliverables register, sprint tracker, defect register, action tracker, stakeholder comms log
Cl. 6.3 | By 11 May 2026; maintained continuously
Governance
Week 1 status report
First weekly written status report covering initiation progress, baseline plan, open risks, dependencies and decisions required from ICPC
Cl. 6.4 | By 18 May 2026; weekly thereafter
Reporting
Monthly governance pack #1
First full monthly pack including status, risk register, issue log, budget/time report, acceptance status, quality and data-protection status, developer performance assessment
Cl. 6.7 | End of May 2026
Reporting
Monthly governance pack #2
Second monthly pack covering mid-phase delivery progress, sprint performance, Phase 1 milestone trajectory
Cl. 6.7 | End of June 2026
Reporting
Technical oversight — Phase 1 modules M Hub must monitor and report on 7
Foundation & infrastructure oversight
Tenant provisioning; geo data load; authentication (JWT/MFA/TLS); roles and permissions; append-only audit log; per-country data-protection compliance; cross-tenant isolation
Sch. 1 Ph.1 | Cl. 7.1–7.2 | Chimwemwe (web) + Elias (mobile)
TechnicalSecurity
VRIV infrastructure review
Voter roll integration and verification infrastructure; M Hub to review architecture decisions, data flow, voter-roll restriction compliance, encryption at rest and security controls
Sch. 1 Ph.1 | Cl. 7.2 | Chimwemwe leads
TechnicalSecurity
Module 1 build oversight — mobilisation core
Agent profiles; member registration; gap analysis; mobilisation and GOTV (VMT); pledge-to-vote; canvassing logs; response tracking; targeted SMS/WhatsApp/voice campaigns
Sch. 1 Ph.1 | Cl. 7.1–7.2 | Both tech leads
Technical
Forum app delivery oversight
Review forum app data capture design, architecture, API integration, data-protection handling and handover artefacts
Sch. 1 Ph.1 | Cl. 7.2 | Chimwemwe (web) + Elias (mobile)
Technical
Module 2 build oversight — election day core
Agent check-in; vote confirmation; digital tally sheets; photo evidence capture; AI-enhanced low-resolution photo processing; offline queue; call-centre fallback; incident and legal vault
Sch. 1 Ph.1 | Cl. 7.2 | Elias (mobile) + Chimwemwe (web/API)
Technical
War Room dashboard oversight
Review architecture, real-time data pipeline, dashboard data integrity, access controls and demo evidence
Sch. 1 Ph.1 | Cl. 6.6, 7.2 | Chimwemwe leads
Technical
Projection logic oversight
Review projection tool design drawing on collection data, vote confirmations, social signals, DR submissions and exit poll entries; verify logic documentation
Sch. 1 Ph.1 | Cl. 7.2 | Both tech leads + Dr Sibande strategic review
Technical
Phase 1 milestone package — due by 16 Jul 2026 3
Phase 1 acceptance recommendations
Written accept / conditionally accept / reject recommendations for all Phase 1 deliverables with reasons, test evidence, defects identified, risk rating and remediation recommendations
Cl. 10.2–10.3 | By 16 Jul 2026
QA
Phase 1 source-code and repository access verification
Confirm Afrisoft has committed all Phase 1 code and artefacts to ICPC-controlled repositories; confirm ICPC admin access to repos, CI/CD and issue trackers
Cl. 7.5 | By 16 Jul 2026
Governance
Dr Sibande — mid-phase strategic review
Milestone approval input; risk governance update; stakeholder alignment notes; escalation memoranda if material issues identified
Sch. 2 | By 16 Jul 2026
Governance
Phase 2 — Validation, testing & analytics
20 Jul 2026 to 17 Aug 2026
4 weeks
M Hub governance deliverables — Phase 2 ongoing 2
Monthly governance pack #3
July pack covering Phase 1 closure, Phase 2 initiation, outstanding defects, testing plan status, load-test schedule and security audit readiness
Cl. 6.7 | End of July 2026
Reporting
Elevated governance meetings during testing windows
Increase meeting cadence during load testing, security audit, pen-testing and mesh sync stress-testing windows; produce minutes for each session
Cl. 6.5 | Throughout Phase 2
Governance
Technical oversight — Phase 2 validation deliverables 7
Analytics & heatmap finalisation oversight
Review analytics module completion, geographic heatmaps, drill-downs, predictive analytics, filters and export functionality against acceptance criteria
Sch. 1 Ph.2 | Cl. 7.2 | Chimwemwe leads
Technical
Load testing oversight and evidence review
Verify load-test evidence against non-functional targets: 5–10M member records per tenant; 50,000 polling-station submissions in 4-hour window; sync under 2 min; APK under 30 MB
Sch. 1 Ph.2 | Cl. 7.2, 10.2 | Chimwemwe + Elias
QATechnical
Security audit oversight and evidence review
Review security audit findings covering JWT, MFA, TLS, encryption at rest, encrypted local SQLite, client-side encryption of incident photos, cross-tenant isolation; ensure no critical findings carried forward without ICPC written risk acceptance
Sch. 1 Ph.2 | Cl. 7.2, 10.5 | Chimwemwe + Elias + Dr Sibande escalation
SecurityQA
Penetration testing oversight and evidence review
Review pen-test scope, methodology and findings; escalate any critical or high-risk findings to ICPC immediately; confirm remediation before Phase 3 entry
Sch. 1 Ph.2 | Cl. 7.2, 10.5 | Both tech leads
SecurityQA
Mesh sync stress-test oversight
Verify mesh sync stress-test evidence against the 7-days-offline capacity and under-2-minute sync targets; review offline queue behaviour under concurrent-agent load
Sch. 1 Ph.2 | Cl. 7.2 | Elias (mobile) leads
QATechnical
Training mode and simulation oversight
Review training mode design and simulation environment; verify that demo environments use real/representative test data and functioning software — not slide decks
Sch. 1 Ph.2 | Cl. 6.6 | Both tech leads
Technical
Uptime and 99.9% Election Day readiness verification
Verify evidence supporting 99.5% standard uptime and 99.9% Election Day uptime targets; review backup/recovery evidence and deployment readiness confirmation
Sch. 1 | Cl. 10.7 | Chimwemwe + Elias
QA
Phase 2 milestone package — due by 17 Aug 2026 3
Phase 2 QA gate evidence pack
Code review evidence, test evidence, security review, data-protection review, performance evidence, backup/recovery evidence, deployment readiness confirmation, handover completeness confirmation
Cl. 10.7 | By 17 Aug 2026
QA
Go / no-go recommendation to ICPC
M Hub written recommendation on Phase 3 pilot readiness, outstanding defects, risk rating and conditions precedent; Dr Sibande input on strategic alignment
Cl. 5.3, 10.3 | By 17 Aug 2026
GovernanceQA
Monthly governance pack #4
August pack covering Phase 2 results, testing outcomes, defect status, Phase 3 readiness assessment and recommendations
Cl. 6.7 | By 17 Aug 2026
Reporting
Phase 3 — Pilot, rollout & production
17 Aug 2026 to Sep 2026
~6 weeks
M Hub governance — elevated cadence 3
Daily reporting during go-live and election-day readiness
Where required by ICPC: daily status reports covering pilot issues, defect status, rollout progress, readiness confirmation and escalation items
Cl. 9.5 | On ICPC demand during critical windows
ReportingEscalation
Elevated governance meetings — pilot and production windows
Increase meeting cadence; convene and minute sessions for go-live, simulation, pilot, production, critical defect and election-day readiness
Cl. 6.5 | Throughout Phase 3 critical windows
Governance
Monthly governance pack #5
Pilot and rollout pack covering national rollout status, production environment confirmation, final defect status and post-election analytics readiness
Cl. 6.7 | End Sep 2026
Reporting
Technical oversight — Phase 3 production deliverables 3
Pilot deployment oversight
Monitor pilot deployment, capture structured feedback, escalate issues to ICPC, track defect remediation before national rollout
Sch. 1 Ph.3 | Cl. 7.1–7.2 | Both tech leads
Technical
National rollout oversight
Monitor per-tenant production deployments; verify each tenant provisioning against scope; confirm cross-tenant isolation; escalate any rollout failure immediately
Sch. 1 Ph.3 | Cl. 7.1–7.2 | Both tech leads
Technical
Production readiness verification
Final QA gate: code review, test evidence, security review, data-protection review, performance evidence, backup/recovery evidence, deployment readiness, handover completeness, 99.9% uptime evidence
Cl. 10.7 | Before production sign-off
QASecurity
Final deliverables package — M Hub acceptance recommendation 9
Source code handover verification
Verify all source code committed to ICPC-controlled repositories; confirm ICPC admin access; confirm documentation completeness
Sch. 1 Final | Cl. 7.5 | Chimwemwe + Elias
Final
Signed mobile app builds verification
Verify signed Flutter APK/IPA builds meet the under-30-MB target; confirm version control and release governance artefacts
Sch. 1 Final | Cl. 10.2 | Elias leads
Final
Demo environment acceptance recommendation
Verify demo environment uses functioning software and representative test data per Cl. 6.6; confirm scope coverage
Sch. 1 Final | Cl. 6.6, 10.3 | Both tech leads
FinalQA
Training materials and simulation mode verification
Review training materials and simulation mode against requirements; confirm coverage of all modules and channels
Sch. 1 Final | Cl. 10.2 | Both tech leads
Final
Documentation package verification
Verify all technical, API and handover documentation is complete, accurate and committed to ICPC-controlled systems
Sch. 1 Final | Cl. 7.2 | Chimwemwe leads
Final
Post-election analytics package oversight
Review post-election analytics deliverable specification and readiness; confirm ICPC receives final analytics package
Sch. 1 Final | Cl. 10.2 | Both tech leads + Dr Sibande sign-off
Final
Strategic closure input — Dr Sibande
Final strategic oversight notes; milestone approval input; stakeholder alignment notes; strategic closure memorandum
Sch. 2 | End Phase 3
Governance
Technical closure report — Chimwemwe (web)
Technical closure report on web systems; final security and performance evaluation; web QA checklist sign-off; final code-review report
Sch. 2 | End Phase 3
Final
Technical completion report — Elias (mobile)
Mobile technical completion report; final mobile performance and security assessment; mobile QA checklist sign-off; final mobile code-review report
Sch. 2 | End Phase 3
Final
RS
Dr Rachel Sibande
Technical strategist and overall lead
~15 hrs/week · elevated at initiation, mid-term review, go/no-go, closure
Required outputs (Schedule 2)
Strategic oversight notes Milestone approval input Risk governance updates Stakeholder alignment notes Strategic closure input Escalation memoranda
Timing
Initiation oversight
Approve overall scope, key deliverables and major milestones; confirm alignment with ICPC strategic priorities; provide strategic oversight notes
By 11 May 2026
Ph 1
Mid-term review
Milestone approval input; risk governance update; stakeholder alignment notes; escalation memoranda where required
Around 16 Jul 2026
Ph 1Ph 2
Go / no-go decision support
Strategic input to go/no-go decision for Phase 3 pilot; resolve high-level risks and resource constraints; communicate project value to ICPC
By 17 Aug 2026
Ph 2
Strategic closure
Final strategic oversight notes; closure memorandum; stakeholder alignment confirmation
End Phase 3 / Sep 2026
Ph 3
CC
Chimwemwe Chawinga
Technical lead — web systems
~20–25 hrs/week · elevated during core development, integration and testing
Required outputs (Schedule 2)
Web system architecture documentation Design diagrams Code review reports Approval logs Security and performance evaluation reports Web development standards QA checklists Test summary reports Technical closure report
Phase delivery obligations
Phase 1 — web architecture review and code reviews
Review web architecture for Laravel API, PostgreSQL, Python workers, Redis/Horizon; conduct code reviews for Module 1 and 2 web components; produce web development standards and QA checklists
Ph 1
Phase 2 — security audit, load-test, analytics review
Lead web-side security and performance evaluation; review load-test results; review analytics, heatmaps, drill-down and export modules; produce security and performance evaluation report
Ph 2
Phase 3 — production oversight and closure
Oversee web system production deployments; final code-review report; technical closure report
Ph 3
EM
Elias Mhango
Technical expert — mobile development
~20–25 hrs/week · elevated during intensive development and review cycles
Required outputs (Schedule 2)
Mobile architecture designs Mobile technical documentation Code review reports Approval logs Mobile performance and security assessment reports Mobile development guidelines QA checklists Test summary reports Technical completion report
Phase delivery obligations
Phase 1 — Flutter app and mobile architecture review
Review Flutter mobile architecture; code reviews for offline queue, mobile tally sheets, photo capture and AI processing modules; produce mobile development guidelines; enforce UI/UX consistency; ensure APK under 30 MB trajectory
Ph 1
Phase 2 — mesh sync stress-test and mobile QA
Lead mesh sync and offline capacity testing oversight; review 7-day offline evidence; mobile security review; mobile performance and security assessment report; QA checklists and test summary reports
Ph 2
Phase 3 — mobile production and completion report
Verify signed APK/IPA builds; confirm APK under 30 MB; oversee mobile production deployment; technical completion report
Ph 3
All Technical Governance Reporting QA Security Final