AFRICA / CIVIC PARTICIPATION / 2026
ENFRPT
CIVIC TECH
FUND AFRICA

Practical application

Plan civic tech mentoring around a real delivery gap

A mentoring worksheet for an early prototype, a growing service or an established initiative.

The procedures and examples below are learning tools. They describe a possible approach, not a test conducted by the named initiative.

Current stage and gap → Mentor’s bounded task → Build / adapt / manual option → Team-owned deliverable → Handover and review
Plan civic tech mentoring around a real delivery gap · Original booklet · May 2024 Open the full-size diagram
  1. Current stage and gap
  2. Mentor’s bounded task
  3. Build / adapt / manual option
  4. Team-owned deliverable
  5. Handover and review

Match support to the actual stage

The pilot portfolio described in the May 2024 booklet separates four start-up initiatives, three scale-up initiatives and seven expansion initiatives. Those are categories of that historical portfolio, not eligibility rules for a current programme. They illustrate why support should depend on the team’s delivery gap. An early team may need to validate a public problem; a working service may need reliable operations; a mature initiative may need partnerships and a transferable method.

Write a support brief

Choose a problem the mentor can help solve and a deliverable that the team can maintain afterwards. State the current workflow, what has been tried, available time and the decisions the team still owns. Specify civic and technical needs separately. A mentor who reviews database access does not automatically provide the institutional relationships needed for a public response. Agree on confidentiality and access before sharing participant records.

Decide whether to build or reuse

Compare adapting an existing tool, a manual workflow and building new software. Include maintenance, accessibility, moderation, training and exit costs. Run the same representative task through each feasible option. Record the reason for the choice; novelty is not an outcome. Avoid assigning a numerical return or claiming a product test unless you actually have the required evidence. A prototype should demonstrate the process before committing to a larger system.

Make the handover concrete

Arrange reviews around deliverables rather than only meetings. A useful handover includes the workflow, responsible people, an access register, maintenance tasks, known limitations and a next-review date. Test that someone other than the mentor can complete the agreed task. Remove temporary access after the assignment. Record what remains unresolved so a short mentoring engagement does not create a false impression of readiness.

Working template

  • Current stage and gap
  • Mentor’s bounded task
  • Build / adapt / manual option
  • Team-owned deliverable
  • Handover and review

Illustrative example

An illustrative feedback team asks a mentor to compare an assisted intake process with an existing ticket tool. Its deliverable is a documented routing workflow and staff handover, not a promise that a new app will increase civic participation.

Build your project brief

Sources and provenance

Give the mentor one obstacle and a checkable handover

Turn “help us improve the platform” into one bounded assignment. The May 2024 booklet provides historical mentoring context; it does not establish a current application round. The exercise below is invented and makes no claim about a named initiative.

  1. Describe an observed obstacle and its evidence, without sending participant records. Use synthetic examples for the review.
  2. State the decision the team owns, the mentor's limited task, available time and an output the team can maintain. Reviewing a workflow is different from obtaining institutional approval.
  3. Define a handover task that another team member must complete. Decide in advance what counts as failure and who resolves it.
  4. Record the result, remaining questions and next review. Arrange any temporary access through the team's actual process; a meeting is not evidence that the handover worked.

Completed teaching brief M-1

Obstacle: synthetic reports with no category have no assigned route. Mentor task: review a one-page routing rule during one 30-minute session. Team-owned decision: who handles unclassified reports. Output: a dated rule and three invented examples, with no names or live records.

Acceptance task: a second teammate routes a blank-category example using only the rule. In the fictional result, the rule names no responsible role. Record handover failed; ownership decision still needed, rather than counting the meeting as completion. The team assigns a role and repeats the same check before closing the task.

Copyable brief: obstacle/evidence ___; team decision ___; bounded support ___; time/output ___; independent handover task ___; failure condition ___; result/open questions ___; next owner/date ___. This worksheet is not an application, funding offer or claim of programme results.

Fictional M-1: a blank-category report has no route. A second teammate cannot identify the owner from the rule. The handover fails; the team must decide ownership and repeat the check.
A completed meeting is not a completed handover. Fictional exercise. © Civic Tech Fund · CC BY 4.0.

Original booklet · May 2024