WORKSPACE SETUP & OFFICER ASSIGNMENTS
Your election. One connected workspace.
Select your electoral area, open its locations, and assign your team.
Live workspace. This page is connected to your VeryTally account. Locations, candidates and officers are the real records for the selected contest, and assignments and invitations take effect on the server immediately. Results are unofficial and follow the selected electoral area.
Election workspace
Preview roles use the first sample LGA, ward or PU as their assigned area. Browser controls simulate permissions only.
LOCATIONS AT THIS LEVEL0
PU AGENTS ASSIGNED0
PENDING INVITATIONS0
COUNTED PUs0
CONTEST RESTRICTION
Candidate list
Candidates inherit the selected contest. Lower locations retain that contest and restrict the geographic scope.
VALID VOTES0
COUNTED PUs0
FLAGGED PUs0
LEADING CANDIDATENo results yet
Candidate totals
Geographic breakdown
| Area | Counted PUs | Flagged | Leading candidate |
|---|
With no counted results, show “No results yet”. A lead is not a declared winner.Engineer handoff & acceptance checks
- Show the results dashboard at national, state, constituency/district, LGA and ward levels as applicable. Never show a results dashboard at PU level. Scope candidate totals, geographic breakdown, flags and exports to the selected contest and the officer’s authorized area.
- Preload authoritative electoral mappings. Navigation must work before officers are assigned. Preserve election, state and contest throughout drill-down.
- Constituency/district leader: assign or invite all levels below in their contest. LGA chairman: wards and PU agents in their LGA. Ward coordinator: PU agents in their ward.
- Restrict every API request by authorized workspace, contest and geographic area; never trust browser filters.
- Allow one active PU assignment per election workspace and PU. Use a database uniqueness constraint and atomic transactions to reject concurrent duplicates.
- Pending invitations reserve a PU until accepted, revoked or expired. On acceptance, verify scope and uniqueness again. Define expiry on the server.
- Authorized replacement/removal must be explicit and audited. This prototype exposes removal to the workspace admin only.
- Never render the nationwide Per state summary for House of Representatives, Senate or State House of Assembly. Use only mapped LGAs, wards and PUs within the selected contest, further restricted by officer permissions.
- Candidate, vote, percentage, result and export queries must use the exact contest. Before selection show a prompt; when records are missing show an empty state, never a broader list.
- Keep demo, pilot and live records separate. Run the same login-to-assignment tests across all three modes and Presidential, Governorship, Senate, House of Representatives and State House of Assembly.
- Verify persistence, invitation activation, direct-URL authorization, wrong-contest API rejection, concurrent PU assignment rejection, and error/retry states before deployment.
This page runs on your signed-in VeryTally account: locations, candidates, assignments, invitations and results all come from the live server, and every action is checked against your role and assigned area.