South African education institutions are increasingly adopting education technology (EdTech) to improve teaching and learning, strengthen assessment, and expand access. However, EdTech procurement is rarely straightforward: requirements shift, budgets tighten, suppliers vary in capability, and implementation realities often collide with contract promises.
This guide provides an exhaustive, practical deep-dive into the most common procurement challenges faced by schools, districts, TVET colleges, and universities across South Africa—and the specific steps you can take to avoid them. It also connects procurement to funding, implementation, and measurable outcomes, because the “right solution” is only valuable if it is delivered and used effectively in classrooms.
Understanding EdTech procurement in South Africa: where problems start
EdTech procurement usually fails for reasons that begin before you issue a tender or sign a contract. Institutions often start with the technology they want rather than the learning outcomes they need, and they underestimate operational and compliance requirements.
In South Africa, procurement complexity is intensified by realities such as variable connectivity, uneven device readiness, load-shedding impacts, procurement lead times, and the need to coordinate with provincial departments, school leadership, and educators.
The procurement lifecycle (and where EdTech differs)
Traditional procurement can focus on buying equipment. EdTech procurement must consider the full lifecycle:
- Needs and outcomes (learning goals, pedagogical approach, assessment needs)
- Solution design (platforms, devices, offline options, content)
- Funding model (who pays, when, and under what restrictions)
- Contracting and compliance (service levels, data protection, warranties)
- Implementation (rollout schedule, training, support model)
- Adoption and governance (who uses it, who manages it, escalation paths)
- Measurement and continuous improvement (ROI, usage analytics, reporting)
When institutions treat EdTech like hardware-only procurement, they inherit risk later—especially around sustainability, security, training, and support.
Challenge 1: Buying technology instead of solving a learning problem
What it looks like
A procurement decision is made because a product looks advanced, “matches a trend,” or resembles a solution used elsewhere. Requirements are written around features rather than pedagogy, assessment, and learner outcomes.
Why it happens in SA institutions
- Fast adoption pressure from leadership or external partners
- Limited time for curriculum alignment and needs analysis
- Confusion between “edtech platform” and “learning content ecosystem”
- Tendency to treat procurement documents as technical checklists rather than outcome plans
How to avoid it
Start with a problem-first approach that ties each requirement to an instructional goal.
Practical steps:
- Write a short Outcome Brief before procurement:
- What learning gap are we addressing?
- Which grades/subjects are affected?
- How will success be measured after rollout?
- Convert outcomes into functional requirements:
- Offline access needs, assessment workflows, language support
- Teacher dashboards, reporting formats, and data export
- Include pedagogical and workflow requirements:
- How teachers will prepare lessons, deliver activities, and assess learning
- How learners will access content and submit work
If you need guidance on aligning the procurement budget to what matters most, use this internal link: How to budget for education technology procurement in South Africa.
Challenge 2: Weak requirement definition (vague scopes and mismatched expectations)
What it looks like
You specify “a learning management system” but fail to define:
- user roles and permissions
- content management requirements
- assessment types and reporting needs
- offline/low-connectivity behaviour
- integration with existing systems (where applicable)
- support, uptime, and escalation mechanisms
Why it hurts procurement
Vague requirements allow suppliers to propose “closest fit” solutions that technically comply but do not meet operational needs. It also makes contract enforcement difficult.
How to avoid it
Create a Requirement Traceability Matrix: each tender requirement must map to a learning, operational, or compliance need.
Best practice requirement categories for EdTech:
- Learning & assessment
- quiz/test formats, marking logic, rubrics, analytics
- User experience
- language, accessibility, device compatibility
- Operational readiness
- deployment model, device management, provisioning
- Connectivity strategy
- offline-first approach, caching, sync windows
- Support & service levels
- helpdesk hours, response times, escalation tiers
- Security & governance
- data handling, retention, audit logs, admin access controls
- Training & change support
- teacher onboarding, champions program, refresher training
Before signing, ensure requirements translate into contract deliverables by reviewing: Key questions to ask before signing an education technology contract.
Challenge 3: Not accounting for total cost of ownership (TCO)
What it looks like
Institutions budget only for the initial license or devices, ignoring:
- devices lifecycle (repairs and replacements)
- content subscriptions and renewal costs
- connectivity costs and data bundles
- hosting fees, support staffing, and monitoring
- training refreshers and onboarding for new teachers/learners
- warranty expiry and end-of-contract transitions
South African context amplifiers
- electricity costs and load-shedding coping costs (chargers, battery packs, UPS)
- variable broadband quality in rural areas
- procurement delays that compress implementation timelines
How to avoid it
Use a TCO model that forecasts costs over at least 3 years (and preferably 5). Include both “run” costs and “change” costs.
TCO cost buckets to include:
- procurement (licenses, devices, accessories)
- implementation (setup, migration, integration, deployment)
- support (helpdesk, on-site assistance, replacement parts)
- training (initial + ongoing)
- connectivity (SIMs, routers, data plans, Wi‑Fi maintenance)
- sustainability (renewals, content updates, platform upgrades)
- governance (user management, audits, admin processes)
For more budgeting detail and how to structure realistic funding requests, see: How to budget for education technology procurement in South Africa.
Challenge 4: Procurement plans that ignore implementation constraints
What it looks like
A tender schedule expects a rapid deployment without accounting for:
- educator availability for training
- school timetables and exam periods
- device readiness and configuration time
- data onboarding and user rollouts
- school readiness checks (power, connectivity, storage, supervision)
Why it’s common
EdTech contracts are often awarded based on technical evaluation scores alone. Implementation capability may not be weighted heavily enough, even though it is critical for success.
How to avoid it
Procurement should include a rollout plan as a deliverable, not just a selling point.
Procurement must require:
- implementation timeline by phase (pilot → rollout → stabilization)
- onboarding workflow for teachers and learners
- on-site support availability during the first teaching cycle
- contingency plan for connectivity interruptions
- acceptance criteria (what “done” means)
Use this internal link for rollout planning: How to plan a successful EdTech rollout in South African schools.
Challenge 5: Inadequate vendor evaluation (scoring the wrong things)
What it looks like
Institutions evaluate vendors based on:
- flashy demos
- feature lists
- compliance statements without evidence
- generic case studies that do not match local realities
Sometimes the winner is not the partner most capable of implementation and support in South African conditions.
How to avoid it
Evaluate vendors using evidence-based criteria and local fit checks.
A strong evaluation approach includes:
- Proof of deployment in similar environments (rural/urban, connectivity constraints)
- technical assessment of offline/low-bandwidth operations
- support model: escalation pathways, response times, coverage
- training capacity: teacher onboarding approach, materials, and refresher cadence
- security posture: access controls, encryption, audit logs
- references with verifiable outcomes (not only testimonials)
- pilot plan with measurable acceptance criteria
For an SA-specific school-oriented vendor evaluation checklist, reference: A South African school's guide to evaluating EdTech vendors.
Challenge 6: Funding misalignment and procurement lock-in
What it looks like
Institutions procure systems that don’t match available funding. Common issues include:
- licensing that is funded for a short term but required to run long term
- donor-funded pilots without sustainability funding
- procurement designed around project budgets rather than institutional needs
- contracts that restrict procurement flexibility for renewals, scaling, or replacement
Why this is a big SA risk
In many cases, EdTech funding comes through a mix of departmental budgets, donor support, and grants. If funding restrictions aren’t understood early, you may lock your institution into costs that cannot be sustained.
How to avoid it
Treat funding and procurement as a single plan.
Practical steps:
- Identify the funding source constraints:
- is hardware allowed? is recurring cost allowed?
- can funds be used for training/support?
- Request a sustainability plan from vendors:
- renewal options and pricing transparency
- device and license replacement policies
- Negotiate modular procurement where possible:
- enable scaling after pilot validation
- structure options for extensions rather than forcing full commitment at day one
To explore the funding landscape in South Africa, use: Funding options for education technology projects in South Africa.
If you want to understand donor-driven support structures that influence implementation, see: How donor funding supports EdTech implementation in South Africa.
And for grant-related expansion strategies: The role of grants in expanding education technology access in South Africa.
Challenge 7: Procurement that ignores data privacy, security, and student protection
What it looks like
Contracts do not clearly define:
- who is the data controller/processor
- data retention duration
- data usage limitations (e.g., “for product improvement”)
- breach notification timeframes
- access control rules
- audit requirements
Why this is non-negotiable
Education data is sensitive. Inappropriate handling can expose learners and create compliance and reputational risk for institutions and education authorities.
How to avoid it
Make security and privacy requirements explicit in procurement documents and contracts.
Include contract clauses and technical requirements for:
- data encryption in transit and at rest
- role-based access control and admin auditing
- data minimization policies
- data retention and deletion terms
- breach notification and incident response responsibilities
- compliance alignment with South African privacy expectations (and any relevant sector guidance)
- secure data export for reporting and migration off the platform
Also ensure the vendor supports institutional governance:
- who can view learner performance reports?
- how do teachers manage sensitive information?
- what is the approval process for platform settings?
Challenge 8: Poor device and connectivity readiness planning
What it looks like
Devices arrive but cannot be used effectively because:
- apps are not compatible with school device configurations
- offline learning content wasn’t installed correctly
- accounts weren’t provisioned or were inaccessible due to authentication issues
- Wi‑Fi coverage is insufficient
- power constraints break charging workflows
How to avoid it
Procurement should require a readiness assessment and readiness deliverables.
Connectivity and power readiness checklist:
- offline/low-bandwidth mode tested in the actual school environment
- device charging workflow (chargers, cable management, storage)
- UPS/battery backup plan where necessary
- content caching policy (what learners can access without internet)
- network mapping for multi-classroom usage
- account provisioning prior to rollout
This is a procurement “must-have” because implementation success depends on classroom-level usability—not just technical feasibility.
Challenge 9: Underestimating teacher workload and change management
What it looks like
Teachers are trained once, then left to manage:
- login issues
- content creation and assignment workflows
- reporting requirements
- troubleshooting without escalation
Even a great product fails if it increases workload without support.
How to avoid it
Procurement should include change management deliverables and capacity-building.
Require the vendor/partner to provide:
- teacher onboarding with role-based instruction
- ongoing coaching or office hours during stabilization
- a “teacher champion” framework
- lesson plan support or templates tied to curriculum goals
- mechanisms for feedback and improvement cycles
- time allowances or structured schedules for adoption
For practical guidance on adoption in classrooms, see: Change management tips for introducing EdTech in South African classrooms.
Challenge 10: Weak acceptance criteria and performance measurement
What it looks like
Contracts focus on delivery of software licenses or device shipment, but not on outcomes or service performance. Institutions discover too late that:
- uptime is poor
- support response times are slow
- learning content doesn’t match expected grade/subject coverage
- reporting is hard to export or not usable by teachers
How to avoid it
Define acceptance criteria that cover both service and learning enablement.
Acceptance criteria examples (edit for your project):
- pilot completion within agreed timeline
- teacher satisfaction targets or usability scores
- measurable platform usage thresholds (e.g., active learners/weekly active teachers)
- helpdesk performance SLA compliance
- evidence of offline capability during simulated connectivity interruptions
- content coverage checks by subject and grade
And ensure you plan for measurement from procurement day—this is crucial for demonstrating value and informing future scale. For ROI methodology, use: How to measure return on investment for EdTech in South Africa.
Procurement “failure modes” seen in South Africa (and how to prevent them)
Below are common real-world failure patterns and the corresponding prevention strategies you can bake into procurement documents.
Failure mode: Pilot results don’t scale
Cause: pilot success wasn’t linked to a scale plan (training, devices, support, content, and governance).
Prevention:
- require scale-readiness assessment after pilot
- require pricing and service continuity for expansion
- define what “go/no-go” means with data
Failure mode: Contract disputes during renewals
Cause: pricing, renewal terms, and scope boundaries weren’t clearly documented.
Prevention:
- negotiate renewal pricing bands and scope clarifications
- require clear licensing models (per user/per device/per term)
- include transition assistance at end-of-contract
Failure mode: Vendor support collapses after go-live
Cause: support SLAs were either absent or not measurable.
Prevention:
- require SLAs with response and resolution time commitments
- specify escalation tiers and accountable contacts
- require quarterly service reviews
Failure mode: Learners can’t access content reliably
Cause: offline workflows and device readiness were not tested in situ.
Prevention:
- mandate offline testing at selected schools before full rollout
- include caching behavior, sync windows, and content packaging requirements
Step-by-step: How to run an EdTech procurement that avoids the biggest risks
This section gives a practical flow you can use for schools, districts, and institutions.
Step 1: Start with an EdTech outcomes brief (not a product brief)
Define the educational outcomes, target learners, and how success will be measured. Identify constraints like device availability, connectivity, and timelines.
Deliverables to produce:
- problem statement and target grade/subject
- learning outcomes and success indicators
- classroom context assumptions (power/connectivity/user readiness)
- constraints and “must/should” requirements
Step 2: Translate outcomes into requirements and scoring criteria
Convert outcomes into functional and operational requirements. Weight evaluation criteria to prioritize implementation capacity and real-world usability.
Tip: Make “ability to deploy and support in low-connectivity settings” a scored criterion—not a checkbox.
Step 3: Confirm funding fit early
Before you commit to a tender scope, align it with the funding source and allowable costs. If you’re using donor support or grants, ensure the procurement model supports the funding restrictions.
Internal resources:
- Funding options for education technology projects in South Africa
- How donor funding supports EdTech implementation in South Africa
- The role of grants in expanding education technology access in South Africa
Step 4: Require a rollout plan with deliverables and acceptance criteria
Ask vendors for a phased rollout plan including pilot testing, training timelines, and stabilization activities. Build acceptance criteria around service performance and classroom adoption.
Step 5: Run a capability and reference check (beyond the demo)
Check references for implementation quality, support responsiveness, and evidence of sustainability. Validate the vendor’s ability to handle South African conditions (connectivity, user skill levels, and operational support).
Use: A South African school's guide to evaluating EdTech vendors.
Step 6: Negotiate contract terms that protect your institution
Focus contract negotiation on measurable deliverables, service levels, data governance, and renewal/exit terms. Ensure responsibilities are clear: who supports devices, who answers helpdesk tickets, and who owns escalation decisions.
Use: Key questions to ask before signing an education technology contract.
Step 7: Plan rollout execution with change management baked in
Align training schedules with the academic calendar. Provide ongoing support beyond “go-live day” to ensure adoption.
Use: How to plan a successful EdTech rollout in South African schools and Change management tips for introducing EdTech in South African classrooms.
Step 8: Measure ROI and use data for improvement
Track both usage and learning enablement. Use outcomes data to decide whether to scale, adjust training, or improve implementation.
Use: How to measure return on investment for EdTech in South Africa.
Deep-dive: contract areas that commonly go wrong (and what to require)
Even when procurement is well planned, contracts often become the risk point. Below are critical contract components to get right.
1) Service Level Agreements (SLAs)
Require SLAs for:
- uptime targets
- response and resolution times
- escalation processes
- maintenance windows
- reporting on SLA performance
2) Support scope clarity
Define:
- what support includes (technical helpdesk, content troubleshooting, account management)
- what support excludes
- which party handles device repairs vs platform troubleshooting
- where support is delivered (remote, on-site, blended)
3) Training and onboarding deliverables
Include:
- training materials and formats (teacher guides, quick-start resources)
- training schedule and minimum hours
- onboarding sessions for administrators and school leaders
- refresher sessions or coaching during the first term post-launch
4) Data governance and exportability
Require:
- export formats for reports and learner performance data
- clear data ownership statements
- retention/deletion obligations at end-ofcontract
- audit log access requirements for administrators
5) Pricing transparency and renewal mechanics
Define:
- renewal pricing methodology
- price increases and notice periods
- licensing model changes (if any) and how they are governed
- optional extensions and scaling conditions
Example scenarios (South Africa) and how to handle them
Scenario A: A district buys tablets with an education platform, but rollout stalls
Symptoms:
- devices are delivered late
- login issues appear
- teachers report “no time to learn the system”
- learners have inconsistent access
Procurement root cause:
- contract didn’t include device staging, account provisioning timeline, and training readiness
- acceptance criteria were delivery-based rather than adoption-based
Fix:
- require staged provisioning and on-site support
- add teacher champion program and structured training cadence
- define acceptance criteria tied to pilot classroom readiness
Scenario B: A school signs a contract but offline use fails during connectivity drops
Symptoms:
- learners lose access during load-shedding + network outages
- teachers can’t retrieve work for marking
- data sync never completes
Procurement root cause:
- offline mode not tested in the actual school environment
- requirements for offline caching and sync windows were missing or vague
Fix:
- mandate offline testing in procurement acceptance
- require content packaging and sync behavior documentation
- include a contingency plan in the contract
Scenario C: A donor-funded pilot works but sustainability funding is unclear
Symptoms:
- pilot ends and licenses expire
- teachers stop using tools
- learners revert to paper-based workflows
Procurement root cause:
- funding model not aligned with multi-year costs
- contract lacked renewal options and transparent pricing
Fix:
- procure with a sustainability pathway (renewals + support)
- negotiate multi-year pricing options and exit/transition terms
- plan for ongoing training refreshers
Practical procurement checklist (copy and adapt)
Use this checklist to review procurement readiness before publishing tender documents.
Outcome and requirements
- Learning outcomes defined for each use case
- Requirements map to measurable indicators
- Offline/low-bandwidth requirements included
- Device compatibility requirements documented
Vendor evaluation
- Evidence of local deployments requested
- Support model assessed with SLAs and escalation clarity
- Training capability scored and referenced
- Security/privacy requirements assessed
Funding and sustainability
- Funding source constraints reviewed
- Multi-year TCO budget created
- Renewal and scaling pricing clarified
- Sustainability plan required from vendor
Contract and governance
- Acceptance criteria include service performance and adoption readiness
- Data governance clauses included (retention, export, breach notification)
- Exit/transition assistance included
- Responsibilities clearly assigned (platform vs devices vs support)
Implementation readiness
- Rollout plan includes pilots, training schedule, and stabilization
- Device staging and account provisioning timeline defined
- Change management plan built into rollout deliverables
Measuring and defending value: ROI and impact evidence
Procurement leaders need more than usage stats. For EdTech in South Africa, ROI should connect to:
- learning enablement (improved assessment feedback cycles, targeted support)
- teacher efficiency (reduced marking time, better reporting workflows)
- learner access (consistent content availability even during connectivity issues)
- operational effectiveness (support response, reduced downtime)
A strong measurement plan helps you justify budgets and secure continued funding. If you want structured guidance, use: How to measure return on investment for EdTech in South Africa.
Conclusion: procurement success is an outcomes-and-sustainability discipline
EdTech procurement challenges in South Africa are not just “technical procurement issues.” They are learning outcomes, funding alignment, implementation readiness, and governance challenges that must be addressed from the earliest planning stages through contracting and measurement.
By shifting from product purchasing to outcome-based procurement, by building strong requirements and acceptance criteria, and by integrating funding and change management into the deal, education institutions can avoid the costly failures that happen when technology is delivered but not adopted—or when promises don’t match classroom realities.
If you apply the steps in this guide and use the internal resources linked throughout, you’ll be better equipped to procure EdTech that is secure, usable, sustainable, and measurable—and that truly improves education outcomes across South Africa.