Skip to main content
On this page

Partner Capacity Building

Partner capacity building develops IT capabilities within implementing partner organisations through structured training, technical mentoring, and resource sharing. Execute these procedures after completing initial partner onboarding when assessment has identified specific capability gaps requiring development. The outcome is measurable improvement in partner technology operations with a clear path to sustainability beyond the partnership period.

Prerequisites

RequirementDetail
Partner assessmentPartner Technology Assessment completed with documented capability gaps
Partnership agreementCapacity building commitments defined in partnership documentation
Budget allocationTraining and mentoring costs approved (typical range: ÂŁ2,000-15,000 per partner annually)
Staff availabilityIdentified trainers and mentors with allocated time (minimum 4 hours weekly per active partner)
Partner commitmentNamed partner staff assigned to capacity building with protected time
Baseline metricsCurrent capability levels documented for progress measurement
Resource inventoryAvailable training materials, documentation, and tools catalogued

Confirm partner readiness before initiating capacity building:

Partner readiness checklist:
[ ] Named IT focal point with decision-making authority
[ ] Minimum 8 hours weekly staff time allocated to learning
[ ] Basic connectivity for remote sessions (1 Mbps minimum)
[ ] Management endorsement documented in writing
[ ] Current system access for hands-on practice

Procedure

Phase 1: Capacity needs assessment

  1. Review the partner technology assessment to extract capability gaps requiring development. Categorise gaps by domain using the standard capability framework:
   Capability domains:
   - Infrastructure management (networks, servers, endpoints)
   - Security operations (access control, incident response, data protection)
   - Application administration (core systems, integrations, user support)
   - Data management (backup, quality, reporting)
   - Service delivery (help desk, change management, documentation)

Document each gap with current state, target state, and priority. A partner assessment identifying “no formal backup procedures” translates to: current state is ad-hoc file copying, target state is automated daily backup with tested restoration, priority is critical given data loss risk.

  1. Conduct a detailed skills inventory with partner IT staff. Use structured interviews covering each capability domain. Record proficiency levels using a four-point scale:

    LevelDefinitionIndicator
    0 - NoneNo exposure to topicCannot describe basic concepts
    1 - AwarenessUnderstands conceptsCan explain purpose but not execute
    2 - PractitionerCan execute with guidanceCompletes tasks with reference materials
    3 - ProficientIndependent executionTroubleshoots issues, trains others

    For a partner with two IT staff members, a completed skills inventory might show:

   Staff member: Amara K. (IT Officer)
   Infrastructure management: 2
   Security operations: 1
   Application administration: 2
   Data management: 1
   Service delivery: 1


   Staff member: David M. (IT Assistant)
   Infrastructure management: 1
   Security operations: 0
   Application administration: 1
   Data management: 1
   Service delivery: 2

  1. Map organisational requirements against current capabilities. Partner programme activities determine which capabilities require immediate development versus longer-term investment. A partner managing beneficiary registration needs application administration and data management capabilities before infrastructure optimisation.

    Create a requirements matrix:

   Programme requirement: Beneficiary data collection
   Required capabilities:
   - Application administration (mobile data collection platform): Level 2+
   - Data management (sync, backup, quality): Level 2+
   - Security operations (access control, encryption): Level 2+


   Current gap analysis:
   - Amara: App admin sufficient, data management needs development
   - David: All areas need development for backup coverage

  1. Prioritise capacity gaps using a weighted scoring model. Assign weights based on programme criticality (40%), security risk (30%), and operational impact (30%). Score each gap from 1-5 on these dimensions and calculate weighted priority.

    Example calculation for “backup procedures” gap:

   Programme criticality: 5 (data loss stops operations)
   Security risk: 4 (beneficiary data at risk)
   Operational impact: 4 (recovery requires external support)


   Weighted score: (5 Ă— 0.4) + (4 Ă— 0.3) + (4 Ă— 0.3) = 4.4
   Priority ranking: Critical (scores above 4.0)
  1. Document the capacity needs assessment in a formal report. Include capability gap inventory, skills inventory by staff member, requirements mapping, and prioritised development areas. Submit to partner leadership and your organisation’s partnership manager for endorsement before proceeding to training plan development.

Phase 2: Training plan development

  1. Define learning objectives for each prioritised capability gap. Learning objectives specify observable outcomes using action verbs. Avoid vague objectives like “understand backup concepts” in favour of specific, measurable targets.
   Capability gap: Backup procedures


   Learning objectives:
   1. Configure automated daily backup for file server using Duplicati
   2. Execute restoration of individual files from backup archive
   3. Perform full system restoration to alternate hardware
   4. Document backup schedule and verify completion logs
   5. Troubleshoot common backup failures (disk space, network, permissions)


   Success criteria: Learner completes all objectives without guidance
   Assessment method: Practical demonstration with simulated failure

  1. Select delivery methods appropriate to each objective, partner context, and available resources. Different objectives require different approaches, and partner constraints around connectivity, time zones, and learning preferences shape viable options.

    Delivery methodBest forRequirementsTime ratio
    Self-paced modulesConceptual knowledge, awareness buildingReliable connectivity, learning platform1:1 (1 hour content = 1 hour learning)
    Live remote sessionsProcedural skills, demonstrationsVideo conferencing, screen sharing1:2 (1 hour session = 2 hours including prep)
    On-site workshopsComplex hands-on skills, team buildingTravel budget, venue, equipment1:3 (1 day workshop = 3 days total investment)
    ShadowingOperational practices, tacit knowledgeStaff travel or extended remote access1:4 (1 week shadowing = 4 weeks elapsed)
    Mentoring callsProblem-solving, ongoing guidanceRegular scheduling, relationship buildingOngoing (1-2 hours weekly)

    A backup procedures training plan might combine self-paced conceptual modules (4 hours), two live remote sessions for configuration (3 hours total), and monthly mentoring calls for troubleshooting support (ongoing).

  2. Sequence learning activities to build progressively. Earlier activities establish foundations for later skill development. Attempting advanced topics before foundations are solid wastes time and frustrates learners.

   Backup procedures training sequence:


   Week 1: Foundation
   - Self-paced: Backup concepts and terminology (2 hours)
   - Self-paced: Duplicati interface orientation (1 hour)
   - Assignment: Document current backup state


   Week 2: Configuration
   - Live session: Configure first backup job together (1.5 hours)
   - Practice: Create backup jobs for remaining critical data
   - Assignment: Document backup schedule


   Week 3: Restoration
   - Live session: Restoration procedures and practice (1.5 hours)
   - Practice: Restore test files independently
   - Assignment: Complete restoration drill documentation


   Week 4: Operations
   - Self-paced: Monitoring and troubleshooting (1 hour)
   - Mentoring call: Review logs, discuss issues (1 hour)
   - Assessment: Practical demonstration

  1. Identify and prepare training resources. Resources include documentation, video tutorials, practice environments, and assessment materials. Prefer existing resources over custom development where quality materials exist.

    Resource checklist for backup training:

   [ ] Duplicati documentation (official, current version)
   [ ] Video walkthrough of configuration (internal or vetted external)
   [ ] Practice environment (test server or VM image)
   [ ] Sample backup schedule template
   [ ] Troubleshooting guide (common errors and solutions)
   [ ] Assessment checklist (practical demonstration criteria)
   [ ] Certificate template (completion recognition)

  1. Estimate total time investment and calendar duration. Training plans fail when they underestimate the time required from both trainers and learners. Build in buffer for rescheduling, slower progress, and competing priorities.

    Time estimate example:

   Backup procedures training


   Learner time:
   - Self-paced content: 4 hours
   - Live sessions: 3 hours
   - Practice and assignments: 6 hours
   - Assessment: 1 hour
   Total learner time: 14 hours


   Trainer time:
   - Preparation: 4 hours
   - Live session delivery: 3 hours
   - Assignment review: 2 hours
   - Assessment: 1.5 hours
   - Mentoring (4 calls): 4 hours
   Total trainer time: 14.5 hours


   Calendar duration: 6 weeks (including buffer)
  1. Complete the training plan document using the template in Appendix A. Obtain sign-off from the partner IT focal point and your partnership manager before commencing delivery.

Phase 3: Training delivery

  1. Schedule all training activities with calendar invitations. Include connection details, preparation requirements, and materials links. Send reminders 24 hours before each session. For partners in different time zones, rotate session times to share inconvenience.
   Calendar invitation template:


   Subject: [Partner Name] IT Training - Backup Configuration Session 1


   Date/Time: Tuesday 14 March, 10:00-11:30 GMT
   Location: [Video conference link]


   Preparation required:
   - Complete self-paced modules 1-2 (links below)
   - Have Duplicati installed on training machine
   - Identify 3 folders to use for practice backup


   Agenda:
   - Review concepts from self-paced content (15 min)
   - Configure first backup job together (45 min)
   - Practice independent configuration (20 min)
   - Q&A and next steps (10 min)


   Materials: [Link to training folder]

  1. Deliver self-paced content through an accessible platform. Options include shared document folders, learning management systems, or video hosting. Track completion to identify learners falling behind before live sessions.

    Low-bandwidth delivery

    For partners with constrained connectivity, provide downloadable content packages. A 50MB zip file containing documentation and compressed videos downloads in under 15 minutes on a 500 Kbps connection, compared to hours of streaming or repeated failed downloads.

  2. Conduct live sessions following adult learning principles. Begin with a brief review of prerequisite content, demonstrate procedures while explaining reasoning, provide guided practice with immediate feedback, then allow independent practice. Avoid lecturing for more than 10 minutes without interaction.

    Live session structure:

   0:00 - 0:10  Check-in, technology test, agenda review
   0:10 - 0:20  Review: key concepts from self-paced content
   0:20 - 0:45  Demonstration: trainer performs procedure with narration
   0:45 - 1:05  Guided practice: learner performs with trainer guidance
   1:05 - 1:20  Independent practice: learner performs alone
   1:20 - 1:30  Debrief: questions, assignment explanation, next session preview
  1. Assign practice activities between sessions. Practice transforms knowledge into skill. Assignments should require applying learned procedures to real work, not artificial exercises.
   Assignment: Backup configuration practice


   Tasks:
   1. Configure backup jobs for your organisation's:
      - Financial records folder
      - Programme data folder
      - Email archive (if applicable)


   2. Document each backup job:
      - What is backed up (folder path)
      - Where backup is stored (destination)
      - Schedule (frequency and time)
      - Retention (how long kept)


   3. Run each backup job manually and verify completion


   4. Attempt to restore one file from each backup


   Submit: Documentation and screenshot of successful restore
   Due: Before next session
  1. Review assignments and provide constructive feedback. Feedback should be specific, actionable, and timely. Generic praise (“good work”) provides no learning value. Identify what was done well, what needs improvement, and how to improve.
   Assignment feedback example:


   Backup job configuration: Well done
   - Correct folder selections covering critical data
   - Appropriate schedule (daily at 22:00 when office closed)
   - Good retention settings matching your policy


   Documentation: Needs improvement
   - Missing: backup destination capacity monitoring
   - Add: what to do when destination drive is 80% full
   - Add: who to contact if backup job fails


   Restoration test: Successful
   - All three test restores completed correctly
   - Good practice restoring to alternate location first


   Action for next session: Update documentation to address gaps above
  1. Adjust delivery based on learner progress. Some learners advance faster than planned; provide extension activities or accelerate the schedule. Others struggle with prerequisites; provide additional support or revisit foundations before proceeding. Rigid adherence to a plan that is not working wastes everyone’s time.

Phase 4: Technical mentoring

  1. Establish a regular mentoring schedule. Weekly calls of 30-60 minutes provide consistent support without overwhelming either party. Schedule at a fixed time to build routine. Protect this time from cancellation except for genuine emergencies.
   Mentoring schedule example:


   Partner: Hopeful Futures Foundation
   Mentor: Sarah T. (Senior Systems Administrator)
   Mentee: Amara K. (IT Officer)


   Schedule: Thursdays, 14:00-15:00 GMT
   Platform: Microsoft Teams
   Backup contact: WhatsApp for urgent issues


   Standing agenda:
   - Progress since last call (10 min)
   - Current challenges discussion (30 min)
   - Planning for coming week (10 min)
   - Documentation of action items (10 min)
  1. Use mentoring calls to address real operational challenges. Mentoring differs from training: rather than following a curriculum, you respond to issues the partner encounters in daily work. This contextual learning builds problem-solving capability, not just procedural knowledge.
   Mentoring call notes example:


   Date: 16 March 2024


   Issue raised: Backup job failing for past 3 days


   Discussion:
   - Reviewed error logs together (screen share)
   - Identified cause: destination drive full
   - Discussed long-term solutions:
     - Option A: Larger drive (cost consideration)
     - Option B: Cloud destination (connectivity consideration)
     - Option C: Reduce retention (data consideration)
   - Decided: Reduce retention from 90 to 30 days as immediate fix,
     budget for cloud backup in next quarter


   Actions:
   - Amara: Adjust retention settings, monitor space usage
   - Sarah: Share cloud backup options comparison document
   - Both: Review cloud backup approach on next call

  1. Guide mentees toward independent problem-solving rather than providing answers directly. When a mentee asks how to solve a problem, first ask what they have already tried and what they think might work. Provide hints and resources rather than solutions. The goal is capability development, not task completion.

    Mentoring conversation pattern:

   Mentee: "The network printer stopped working. What should I do?"


   Avoid: "Check if it's turned on, then ping it, then reinstall the driver..."


   Prefer: "What have you tried so far?"
   [Mentee describes attempts]


   "Good start. What do you think might cause a printer that was working
   to suddenly stop?"
   [Mentee hypothesises]


   "Those are reasonable possibilities. How could you test each one?"
   [Mentee develops diagnostic approach]


   "Try that approach and let me know what you find. If you get stuck
   on a specific step, I'm here to help."

  1. Document mentoring interactions for continuity and accountability. Keep a running log of issues discussed, guidance provided, and outcomes. This record supports progress tracking, identifies recurring challenges, and enables handover if the mentor changes.

  2. Transition from regular mentoring to on-demand support as capability matures. When a mentee consistently solves problems independently and mentoring calls become brief check-ins without substantive issues, reduce frequency. Move from weekly to fortnightly to monthly to as-needed. This transition should be explicit and celebrated as an achievement.

Phase 5: Resource sharing

  1. Identify resources suitable for partner use. Not all organisational resources are appropriate for sharing. Consider licensing restrictions, customisation requirements, and support obligations before sharing.

    Resource typeSharing considerationsPreparation needed
    Documentation templatesUsually shareable, remove internal referencesBrand neutralisation, context adaptation
    Training materialsCheck licensing on third-party contentPermission verification, localisation
    Software toolsVerify licence allows partner useLicence review, configuration guidance
    Configuration examplesRemove sensitive specificsAnonymisation, generalisation
    Vendor contactsConfirm vendor accepts referralsIntroduction protocol

  2. Prepare resources for partner context. Organisational resources often assume infrastructure, processes, or scale that partners lack. Adapt resources to be useful in partner environments.

   Resource adaptation example:


   Original: Organisation backup policy (assumes enterprise backup software)


   Adaptations for partner use:
   - Replace enterprise software references with Duplicati
   - Simplify retention requirements for smaller data volumes
   - Remove references to tape rotation (partner uses disk only)
   - Add section on cloud backup for offsite copy
   - Adjust monitoring procedures for manual verification


   Result: Partner backup guidelines document
  1. Establish a resource sharing mechanism. Options range from simple shared folders to dedicated partner portals. Choose based on number of partners, update frequency, and access control requirements.
   Simple approach (1-5 partners):
   - Shared cloud folder per partner
   - Resources copied and adapted per partner
   - Updates pushed manually


   Structured approach (5-20 partners):
   - Central resource library (master copies)
   - Partner-specific folders for adapted versions
   - Update notification process


   Portal approach (20+ partners):
   - Dedicated partner portal or wiki
   - Self-service resource access
   - Version control and update tracking
  1. Provide context and guidance with shared resources. A template without explanation has limited value. Include cover notes explaining purpose, how to use, and where to get help.
   Resource cover note example:


   Resource: Incident response checklist


   Purpose: Guide systematic response when IT security incidents occur.
   Use this when you suspect a security breach, malware infection,
   or data exposure.


   How to use:
   1. Download and save locally (you may lose network access)
   2. Follow checklist sections in order
   3. Document actions taken in the notes column
   4. Contact [mentor name] for guidance on unfamiliar steps


   Customisation needed:
   - Add your emergency contact numbers on page 1
   - Update escalation contacts with your leadership names
   - Review and adjust response timeframes for your context


   Questions: Contact [mentor name] at [email]
  1. Track resource usage and gather feedback. Understanding which resources partners find valuable guides future development. Simple tracking through access logs or periodic surveys provides useful signal.

Phase 6: Progress tracking

  1. Establish baseline measurements before capacity building begins. Without baseline data, progress cannot be measured. Use the capability levels from the initial assessment as the starting point.
   Baseline record example:


   Partner: Hopeful Futures Foundation
   Assessment date: 15 January 2024


   Capability baselines:
   - Infrastructure management: 1.5 (average of staff scores)
   - Security operations: 0.5
   - Application administration: 1.5
   - Data management: 1.0
   - Service delivery: 1.5


   Overall baseline: 1.2
  1. Conduct quarterly progress assessments using the same measurement approach as the baseline. Consistency in measurement method is essential for valid comparison. Reassess the same capabilities with the same criteria.
   Progress assessment example:


   Partner: Hopeful Futures Foundation
   Assessment date: 15 April 2024 (Q1 review)


   Capability scores:
   - Infrastructure management: 1.5 → 2.0 (+0.5)
   - Security operations: 0.5 → 1.5 (+1.0)
   - Application administration: 1.5 → 2.0 (+0.5)
   - Data management: 1.0 → 2.5 (+1.5)
   - Service delivery: 1.5 → 2.0 (+0.5)


   Overall: 1.2 → 2.0 (+0.8)


   Training completed this quarter:
   - Backup procedures (target: data management)
   - Access control basics (target: security)
   - Help desk fundamentals (target: service delivery)


   Largest improvement: Data management (backup training impact)
   Area needing focus: Security operations (more development needed)
  1. Track training completion against the plan. Monitor which activities have been completed, delayed, or skipped. Identify patterns in delays to address systemic issues.
   Training completion tracking:


   Backup procedures module:
   [x] Self-paced content 1: Concepts (completed 20 Jan)
   [x] Self-paced content 2: Interface (completed 22 Jan)
   [x] Live session 1: Configuration (completed 25 Jan)
   [x] Practice assignment 1 (completed 1 Feb)
   [x] Live session 2: Restoration (completed 8 Feb)
   [x] Practice assignment 2 (completed 15 Feb)
   [x] Assessment (completed 22 Feb, passed)


   Status: Complete
   Duration: 5 weeks (planned: 6 weeks)
   Notes: Learner progressed faster than expected

  1. Document capability improvements with evidence. Progress claims require supporting evidence. Collect examples of partner staff successfully applying learned skills.

    Evidence types:

   Procedural evidence:
   - Screenshot of successfully configured backup job
   - Log showing backup completion over 30-day period
   - Documentation created by partner staff


   Problem-solving evidence:
   - Incident resolved independently (with notes)
   - Troubleshooting approach documented
   - Mentor confirmation of independent resolution


   Outcome evidence:
   - Reduced support requests on trained topics
   - Faster incident resolution times
   - Positive feedback from partner leadership
  1. Report progress to stakeholders quarterly. Stakeholders include partnership managers, donor reporting requirements, and partner leadership. Tailor reporting depth to audience needs.
   Quarterly progress report structure:


   Executive summary (for leadership):
   - Overall capability score change
   - Key achievements
   - Challenges and mitigations
   - Next quarter priorities


   Detailed progress (for partnership managers):
   - Training completion statistics
   - Capability score changes by domain
   - Evidence of application
   - Resource utilisation
   - Mentor time investment


   Partner feedback (for relationship management):
   - Partner satisfaction indicators
   - Requests and suggestions
   - Relationship health assessment

Phase 7: Sustainability planning

  1. Assess sustainability readiness at the midpoint of the capacity building engagement. Sustainability means the partner can maintain and continue developing IT capabilities without ongoing external support. Assessment identifies gaps requiring attention before the engagement concludes.
   Sustainability readiness assessment:


   Staff capability:
   [ ] At least one staff member at proficiency level 3 in each critical domain
   [ ] Documented procedures for routine operations
   [ ] Demonstrated independent problem-solving


   Organisational support:
   [ ] IT budget line established and funded
   [ ] Management understands IT requirements
   [ ] Staff time protected for IT duties


   External resources:
   [ ] Vendor support arrangements in place
   [ ] Peer network connections established
   [ ] Access to ongoing learning resources


   Knowledge management:
   [ ] Documentation maintained and current
   [ ] Procedures tested and validated
   [ ] Knowledge transfer to additional staff completed
  1. Develop a sustainability plan addressing identified gaps. The plan specifies actions required before engagement conclusion to ensure capability persistence.
   Sustainability plan example:


   Gap: Single point of failure (only one trained staff member)


   Actions:
   - Cross-train David on backup procedures (responsible: Amara)
   - Document procedures for reference (responsible: Amara)
   - Conduct knowledge assessment of David (responsible: mentor)
   Timeline: Complete by end of Q3


   Gap: No IT budget for software renewals


   Actions:
   - Calculate annual IT costs for leadership (responsible: mentor support)
   - Present budget proposal to management (responsible: Amara)
   - Establish budget line in annual planning (responsible: partner finance)
   Timeline: Include in next budget cycle


   Gap: No peer support network


   Actions:
   - Connect with regional IT network (responsible: mentor introduction)
   - Attend quarterly community calls (responsible: Amara)
   - Establish peer relationships for mutual support (responsible: Amara)
   Timeline: First community call by end of Q2

  1. Transfer knowledge to additional partner staff to eliminate single points of failure. Relying on one person for all IT knowledge creates fragility. At minimum, document procedures so others can follow them; preferably, train a second person to proficiency.

  2. Connect partners with ongoing support resources beyond your organisation. These include vendor support, regional IT networks, online communities, and peer organisations. External connections provide sustainability after the formal capacity building relationship ends.

   Support resource connections:


   Vendor support:
   - Microsoft 365: Partner enrolled in nonprofit support programme
   - Internet provider: Direct support contact established
   - Hardware: Local service provider relationship confirmed


   Peer networks:
   - Regional NGO IT community (quarterly calls)
   - Technology for social good Slack workspace
   - Local IT professional association


   Learning resources:
   - Microsoft Learn (free training modules)
   - Coursera nonprofit programme access
   - Saved bookmarks to quality documentation
  1. Plan the transition from active capacity building to alumni relationship. Define what ongoing contact looks like: periodic check-ins, access to resources, inclusion in community events. Clear expectations prevent either abandonment or dependency.

Phase 8: Engagement conclusion

  1. Conduct final capability assessment using the standard methodology. Compare final scores against baseline to quantify improvement achieved.
   Final assessment example:


   Partner: Hopeful Futures Foundation
   Engagement period: January 2024 - December 2024


   Capability progression:
                           Baseline    Final    Change
   Infrastructure mgmt:      1.5        2.5      +1.0
   Security operations:      0.5        2.0      +1.5
   Application admin:        1.5        2.5      +1.0
   Data management:          1.0        3.0      +2.0
   Service delivery:         1.5        2.5      +1.0


   Overall:                  1.2        2.5      +1.3


   Target achievement: 100% (target was 2.5 overall)
  1. Complete formal handover of all resources, documentation, and relationships. Ensure the partner has everything needed for independent operation.
   Handover checklist:


   Documentation:
   [x] All training materials provided (cloud folder access confirmed)
   [x] Customised templates transferred to partner systems
   [x] Procedure documents reviewed and partner-owned copies updated


   Access:
   [x] Shared folder access converted to partner ownership
   [x] Any temporary accounts deactivated
   [x] Resource subscriptions transferred or alternatives identified


   Relationships:
   [x] Vendor contacts introduced directly
   [x] Peer network connections established
   [x] Community membership confirmed


   Support:
   [x] Escalation path for emergencies documented
   [x] Alumni check-in schedule agreed
   [x] Contact information exchanged for ongoing relationship

  1. Document lessons learned from the engagement. Capture what worked well, what could improve, and recommendations for future capacity building efforts. This documentation benefits both your organisation’s practice improvement and the partner’s continued development.

  2. Celebrate achievements and formally close the active engagement. Recognition of progress motivates continued development. A closing meeting or brief ceremony acknowledges the work completed and marks the transition to alumni status.

  3. Schedule the first alumni check-in. A follow-up 3 months after engagement conclusion provides an opportunity to assess sustainability, address emerging challenges, and maintain the relationship.

Verification

Confirm capacity building success through multiple indicators:

Assessment verification:

Terminal window
# Calculate capability improvement
baseline_score=1.2
final_score=2.5
improvement=$(echo "$final_score - $baseline_score" | bc)
echo "Capability improvement: $improvement"
# Expected: 1.3 or higher for successful engagement


# Verify target achievement
target=2.5
if (( $(echo "$final_score >= $target" | bc -l) )); then
  echo "Target achieved"
else
  echo "Target not met - review gaps"
fi

Training completion verification:

  • All planned training modules show completion status
  • Assessment records confirm skill acquisition
  • Practice assignments submitted and evaluated

Sustainability verification:

  • Partner can articulate their IT support plan
  • Budget allocation documented for next fiscal year
  • Knowledge transfer to additional staff confirmed
  • External support resources connected and tested

Evidence collection:

  • Before/after capability scores documented
  • Sample work products demonstrating skill application
  • Partner satisfaction feedback recorded
  • Mentor assessment of readiness for independence

Troubleshooting

SymptomCauseResolution
Learner not completing self-paced contentCompeting priorities, unclear expectations, content too longReduce module length to under 30 minutes, set explicit deadlines, check in on progress before live sessions
Repeated session cancellationsOvercommitted staff, insufficient management support, wrong priority levelEscalate to partner leadership, renegotiate time allocation, consider pausing until conditions improve
Skills not retained between sessionsInsufficient practice, gap too long between sessions, learning not applied to real workAdd practice assignments, shorten intervals, connect training to immediate work needs
Partner staff turnover during engagementNormal organisational change, insufficient knowledge documentationAccelerate documentation, cross-train remaining staff, assess whether to restart with new staff
Capability scores not improvingTraining not addressing actual gaps, insufficient practice time, wrong learning approachReassess gaps, try different delivery methods, increase hands-on practice ratio
Mentor relationship not productivePersonality mismatch, communication style conflict, unclear expectationsTry different mentor, clarify roles and expectations, adjust communication approach
Partner cannot sustain after engagementInsufficient organisational support, budget not secured, single point of failureExtend engagement, focus on sustainability prerequisites, escalate to leadership
Resource materials not usedWrong format, too complex, not relevant to contextSimplify materials, adapt to partner context, provide more guidance on use
Partner resistant to capacity buildingPrior negative experiences, perceived criticism of current practice, imposed without consultationRebuild trust, emphasise partnership approach, let partner lead priority setting
Progress reporting burdensomeOver-detailed requirements, manual data collection, unclear purposeSimplify reporting, automate where possible, explain how data is used
Remote training ineffectiveConnectivity issues, time zone challenges, lack of engagementProvide offline alternatives, rotate meeting times, increase interactivity
Assessment results disputedUnclear criteria, subjective evaluation, no evidence baseUse objective criteria, require evidence for ratings, involve partner in assessment

Appendix A: Training plan template 

# IT Capacity Building Training Plan


## Partner information


Organisation name: ________________________________
IT focal point: ________________________________
Mentor assigned: ________________________________
Plan developed: _____________ (date)
Plan approved: _____________ (date)


## Engagement overview


Start date: _____________
Target end date: _____________
Total duration: _____________ months


Baseline capability score: _____
Target capability score: _____


## Capability priorities


Priority 1: _________________________________
Current level: _____ Target level: _____
Training approach: _________________________________


Priority 2: _________________________________
Current level: _____ Target level: _____
Training approach: _________________________________


Priority 3: _________________________________
Current level: _____ Target level: _____
Training approach: _________________________________


## Training schedule


### Priority 1: [Capability name]


| Week | Activity | Delivery | Duration | Responsible |
|------|----------|----------|----------|-------------|
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |
| 4 | | | | |


Learning objectives:
1.
2.
3.


Assessment method: _________________________________
Success criteria: _________________________________


### Priority 2: [Capability name]


[Same structure as Priority 1]


### Priority 3: [Capability name]


[Same structure as Priority 1]


## Mentoring schedule


Regular call: _____________ (day/time)
Platform: _________________________________
Backup communication: _________________________________


## Resources required


| Resource | Source | Status |
|----------|--------|--------|
| | | |
| | | |
| | | |


## Time investment


Learner time (total hours): _____
- Self-paced content: _____
- Live sessions: _____
- Practice: _____
- Assessment: _____


Mentor/trainer time (total hours): _____
- Preparation: _____
- Delivery: _____
- Review and feedback: _____
- Mentoring calls: _____


## Progress milestones


| Milestone | Target date | Actual date | Notes |
|-----------|-------------|-------------|-------|
| Training plan approved | | | |
| Priority 1 training complete | | | |
| Priority 2 training complete | | | |
| Priority 3 training complete | | | |
| Mid-engagement review | | | |
| Final assessment | | | |
| Engagement closure | | | |


## Sustainability plan


Single point of failure mitigation: _________________________________
Budget sustainability: _________________________________
External support connections: _________________________________
Documentation ownership: _________________________________


## Approvals


Partner IT focal point: _________________ Date: _______
Partner leadership: _________________ Date: _______
Organisation mentor: _________________ Date: _______
Partnership manager: _________________ Date: _______

See also