How The Gambia's World Bank-funded Higher Education Management Information System validated the Capability Bridging Framework at national scale. Real decisions, real numbers, real outcomes.
The Gambia's Higher Education Management Information System was designed to give the country a single source of truth across its entire higher education ecosystem. Public universities, private universities, tertiary institutes, government ministries. All reporting to one platform. All contributing to national data that would inform policy, planning, and investment decisions.
The challenge was immediate. The ecosystem was not uniform. Some institutions ran cloud-based ERP systems capable of real-time API integration. Others managed everything in Excel. Two had servers that were completely non-operational. All of them had to connect to the same national platform.
The standard approaches offered two options. Build for the most capable and exclude the rest. Or simplify for everyone and compromise what the system could actually deliver. Neither was acceptable.
The Capability Bridging Framework emerged from refusing both options and finding a third path that served every institution without compromising the system.
Project Credentials
World Bank-funded
RISE Initiative, Government of The Gambia
TOGAF 10-compliant
Enterprise architecture framework applied throughout
Ministry-led
Ministry of Higher Education, Research, Science & Technology
National scale
100% of The Gambia's higher education ecosystem
Open source platform
No vendor lock-in by design
Instead of embarrassment, there was relief. Everyone could see the diversity was real, shared, and nobody was alone in their constraints.
Before any technical design work commenced, a multi-day stakeholder consultation brought representatives from across the entire higher education ecosystem to the Ministry in Banjul. Institutions described their operational realities to each other openly, many for the first time.
Some institutions spoke about cloud ERPs and API readiness. Others quietly admitted they managed everything in Excel. A few were still largely paper-based.
The diversity that emerged was not a problem to be managed. It was the design requirement. That collective honesty became the foundation of everything that followed.
Field visits to all 30 institutions then confirmed and classified what the consultation revealed, placing each institution accurately on their integration pathway.
A comprehensive integration readiness assessment conducted November to December 2025 across all 30 priority institutions. Every institutional type represented. Full geographic coverage across The Gambia.
9 institutions with cloud or web-based ERP systems ready for real-time API integration. Includes public universities and private institutions with modern infrastructure.
1 institution operating a LAN-based ERP system requiring a specialised integration approach. Can export data immediately for HEMIS submission.
18 institutions managing data primarily through Excel or Access. Ready for structured template submissions with training. The majority of the ecosystem.
2 institutions requiring emergency system restoration or capacity building before integration. One had servers completely down. Both received dedicated support.
Every single institution, regardless of their level classification, could integrate within the project timeline with the appropriate pathway and support. No institution was excluded. No institution was asked to wait.
Integration Feasibility
Three lessons from HEMIS that do not appear in any architecture diagram but matter enormously in practice.
When we first presented the framework, we called the levels capability tiers. Institutions resisted immediately. Being placed in a tier felt like a judgment on their adequacy, a public declaration of inadequacy that undermined their willingness to participate honestly.
We changed one word. Tiers became pathways. The same framework, described as offering choice and direction rather than hierarchy, achieved substantially higher institutional buy-in. This is not a superficial communications observation. It reflects a genuine principle of inclusive design: the framing must honour the dignity of every participant.
The technical challenge of building four integration pathways was less complex than the governance challenge of maintaining a single authoritative source of truth when data arrives continuously from one stakeholder and monthly from another.
The framework required explicit governance rules: authoritative source designation for every data element, time-stamped versioning across all submission types, and documented conflict resolution protocols agreed with stakeholders before system launch. This took longer to design than the technical integration itself.
Several institutions assessed as Level 1 capable chose to operate at Level 3 for economic reasons. API development and maintenance carries a cost that some organisations could not absorb within their budget cycles. Their vendor quoted a price that did not fit their planning cycle.
The framework accommodated this without penalty. Pathway selection reflects an organisation's full operational reality, not only its technical capability. A framework that penalises rational economic decisions is not truly inclusive.
Managing data integrity across four different integration mechanisms requires explicit governance rules, not assumptions. HEMIS implemented three specific mechanisms.
Every data element has a documented primary source. When the same data point arrives from two different levels, the designated authoritative source wins. Always. No exceptions. Agreed by all institutions before system launch.
Every submission, whether API, bulk upload, or manual entry, is logged with a timestamp and source identifier. Full audit trail. Always traceable. No data point exists without a documented origin and submission time.
When a Level 1 real-time submission contradicts a Level 3 monthly upload, the conflict is flagged automatically, routed to a designated data steward, resolved within a defined timeframe, and the resolution is logged against both records.
The Capability Bridging Framework was developed in higher education. The design problem it solves exists wherever public sector stakeholders have unequal technical capabilities.
National health reporting systems connecting tertiary hospitals, district clinics, and rural health posts operating across a wide spectrum of digital capability.
Data collection platforms serving commercial farms with sophisticated management systems alongside smallholder farmers with no digital infrastructure.
Service delivery reporting systems covering urban centres with enterprise platforms and remote communities with paper-based operations.
Compliance reporting systems serving large corporations, small and medium enterprises, and informal sector operators across entirely different capability levels.
If your stakeholders are not uniform, your architecture should not assume they are.
Start with the free integration readiness assessment. Find out exactly where your organisation or ecosystem sits and which pathway fits your reality. Takes less than ten minutes.
