TERMS OF REFERENCE
Development and Operationalization of a Digital Management Information System (MIS)
Rwanda Women’s Network (RWN)
| Implementing organisation | Rwanda Women’s Network (RWN) |
| Proposed duration | |
| Funding source | Swedish International Development Cooperation Agency (Sida) |
1. Organizational background and strategic alignment
Rwanda Women’s Network (RWN) is a national humanitarian non-governmental organization established in 1997. RWN works to improve the socio-economic welfare of women and girls in Rwanda, advancing gender equality and supporting the prevention of and response to gender-based violence (GBV). Through its Women Safe Spaces and programmes, RWN supports women and girls to access services, rebuild their lives, strengthen their agency and participate in decision-making in their communities.
This initiative contributes directly to RWN’s 2030 strategic direction and its four mutually reinforcing pillars: HEAL, EMPOWER, TRANSFORM and SUSTAIN. In particular, the MIS is an institutional-strengthening investment under SUSTAIN: it will strengthen organizational systems, information governance, accountability and the capacity to deliver and sustain high-quality programmes. It will also support the evidence, coordination and organizational learning needed across the HEAL, EMPOWER and TRANSFORM pillars.
The initiative is designed for RWN’s internal operations. It is not intended to replace or duplicate the existing MEAL or Grant Management systems. Its scope, interfaces and data boundaries will be confirmed during the needs assessment and documented in the system design.
2. Problem statement and rationale
As RWN’s work is delivered across multiple teams and Women Safe Spaces, timely access to accurate institutional records, approved documents and management information is important for effective coordination, continuity and accountability. Where information is stored across paper files, individual devices, email accounts or disconnected digital folders, staff may face
delays in locating current documents, inconsistent version control, duplication, gaps in institutional memory and avoidable administrative workloads.
These challenges can affect the efficiency of internal workflows and management oversight, and may increase information-security risks if access, retention and backup arrangements are inconsistent. A fit-for-purpose digital MIS will provide a structured and secure environment for institutional documents, internal workflows, archiving and management reporting. The system will be configured around RWN’s actual business processes and the principle of collecting and retaining only information necessary for legitimate organizational purposes.
3. Overall objective and specific objectives
Overall objective: To strengthen RWN’s institutional effectiveness, accountability and organizational sustainability through the development and operationalization of a secure, accessible and user-centered digital MIS for internal operations.
Specific objectives:
- Assess and document RWN’s institutional information-management needs, business processes and user requirements.
- Design, configure and deploy a digital MIS that supports document management, institutional archiving, internal workflows and management reporting.
- Establish clear information-governance arrangements, including user roles, access permissions, retention, backup, recovery and data-protection controls.
- Build staff capacity to use and maintain the system effectively and consistently.
- Establish technical support, system maintenance and continuous-improvement arrangements to promote long-term functionality and value for money.
4. Theory of change
If RWN undertakes a participatory assessment of its information-management needs; procures and configures a secure MIS in accordance with its operational requirements; establishes appropriate governance and access controls; and trains staff with ongoing technical support, then staff and management will be better able to store, retrieve, share and use reliable institutional information. This is expected to reduce avoidable administrative delays and duplication, strengthen internal coordination and institutional memory, and support more timely, transparent and evidence-informed management decisions. These changes will contribute to RWN’s SUSTAIN pillar and strengthen the organizational systems that underpin its wider work for women and girls.
The contribution is primarily an organizational-capacity intervention. It is not expected to directly deliver services to survivors or beneficiaries. Its value to programme quality will be indirect, through stronger institutional systems and more reliable management of non-case-related organizational information.
5. Target users and beneficiaries
Direct users: RWN management, programme and project teams, finance and administration, human resources, procurement/logistics, communications and other authorized staff, as identified through the needs assessment.
Indirect beneficiaries: women and girls, including people accessing RWN’s Women Safe Spaces and services, and communities reached by RWN programmes. They may benefit indirectly from stronger organizational coordination and continuity.
The system must be accessible to staff with different levels of digital literacy and, where relevant, accommodate staff working from different locations and Women Safe Spaces.
6. Scope and key functional requirements
The final scope will be validated during the assessment. The proposed core modules are:
| Functional area | Minimum expected functionality | Key boundary / control |
| Document management | Central repository; metadata and search; version control; approval status; controlled sharing; document templates where appropriate. | Access based on role and business need; avoid uncontrolled public links. |
| Institutional archiving | Structured electronic filing; retention and disposal rules; archive and retrieval procedures. | Retention schedule to be approved by RWN; preserve audit trail for key actions. |
| Internal workflows | Configurable routing, review and approval steps; notifications; task status and ownership. | Map existing processes first; do not automate unnecessary or unapproved processes. |
| Management dashboards/reports | Operational dashboards and reports on system use, document status and workflow performance. | Use only approved, relevant institutional data; dashboards are not a substitute for MEAL. |
| Administration and security | User provisioning/deactivation; role-based permissions; activity logs; backup and recovery; security updates. | Named system owner; periodic access review; incident-response and recovery procedures. |
Explicit exclusions: The MIS will not be designed as a beneficiary case-management database, survivor GBV case-record system, medical records platform, MEAL database or grant-management/accounting system unless RWN separately approves a documented integration and completes the required data-protection and security assessment. Sensitive survivor and health information should remain in the designated systems with their own access controls.
7. Implementation approach and activities
Inception and needs assessment: Establish a project steering/working group; consult representative users and departments; map document repositories and workflows; assess connectivity, devices, digital skills and accessibility needs; identify data categories and risks; agree functional requirements and acceptance criteria.
System design and procurement: Prepare a detailed specification and costed requirements; conduct procurement in accordance with RWN’s approved procurement procedures and applicable Sida agreement conditions; assess vendors on functionality, security, interoperability, total cost of ownership, support, data portability and vendor lock-in.
Development/configuration and testing: Configure or develop the agreed solution; migrate only approved records; test functionality, user permissions, performance, backup and recovery; conduct user acceptance testing and resolve identified defects before go-live.
Deployment and change management: Roll out the system in phases; communicate the purpose and expected benefits; provide user guidance and accessible training materials; identify departmental champions or super-users.
Training and capacity building: Deliver role-specific practical training for staff and administrators; assess learning and user confidence; provide refresher training where needed.
Post-deployment support and review: Provide a defined warranty/support period; document service levels and escalation channels; monitor usage and system performance; review user feedback and agree improvements.
8. Expected results and indicative indicators
Targets should be set after the baseline/needs assessment and before the system goes live. The indicators below are proposed for RWN validation; they are not presented as existing performance data.
| Expected result | Proposed indicator | Means of verification | Target |
| 1. RWN has an operational MIS aligned with approved requirements. | MIS configured, tested and formally accepted against an approved requirements checklist. | Approved specification; test and acceptance reports; go-live sign-off. | 1 operational MIS |
| 2. Institutional information is more consistently managed and retrievable. | Percentage of agreed priority document categories migrated/filed using the approved taxonomy; average retrieval time for a sample of records. | System reports; document register; user testing / retrieval-time sample. | Baseline and target to be set after assessment |
| 3. Staff can use the system for their assigned tasks. | Number and percentage of designated users trained; percentage of trained users able to complete defined core tasks. | Attendance records; pre/post assessment; practical competency checklist. | Target to be set after user mapping |
| 4. System governance and continuity controls are in place. | Approved access matrix, retention schedule, backup/recovery procedure and support arrangement; periodic backup/recovery tests completed. | Approved SOPs; access review logs; backup and recovery test records. | All required controls approved and tested |
| 5. Internal workflows and management oversight are strengthened. | Number of priority workflows configured; user satisfaction / perceived improvement in access and coordination. | Workflow logs; user feedback survey; management review minutes. | Priority workflows and target to be confirmed |
9. Cross-cutting considerations and safeguards
9.1 Gender equality, inclusion and participation
The system will be designed through consultation with staff across functions and locations, including users with differing levels of digital confidence. RWN’s gender equality mandate will be reflected in inclusive participation, accessible training and equitable access to relevant information. The project will assess whether any design choices create barriers for staff based on role, location, disability, language or digital literacy, and will take proportionate steps to address them.
9.2 Human rights, confidentiality and do-no-harm
RWN’s work includes support to women and girls affected by GBV. The MIS must therefore apply a strict data-minimisation approach and must not expose survivor identities, case histories, health information or other sensitive personal data to general institutional users. Before any personal or sensitive data is processed, RWN must complete a data-protection and privacy impact assessment, confirm the lawful purpose and basis for processing, define data-controller/processor roles, and approve consent, access, retention, breach-response and secure-disposal procedures as applicable under Rwandan law and RWN policy. Where possible, management reporting should use aggregated or de-identified information.
9.3 Environmental sustainability
The project will promote paperless workflows where appropriate and assess energy use, equipment lifecycle, repairability, e-waste handling and responsible disposal of obsolete devices. An environmental screening will be completed early in implementation, with proportionate mitigation measures documented.
9.4 Accountability, transparency and anti-corruption
Procurement and contract management will follow RWN’s approved procedures and the applicable donor agreement. The process will document specifications, competition/market assessment, evaluation, approvals, conflict-of-interest declarations, contract deliverables and acceptance. Segregation of duties, traceable payments, asset registration and verification of deliverables will be maintained. Staff and suppliers will be made aware of applicable codes of conduct and channels for raising concerns.
9.5 Data protection and cybersecurity
- Role-based access, least-privilege permissions, strong authentication and timely removal of access when staff leave or change roles.
- Encryption in transit and at rest where supported; secure hosting and documented data location/sub-processing arrangements.
- Regular backups, tested restoration, security patching, audit logs and an incident-response/escalation process.
- Clear ownership of RWN data, full data export and migration capability, documented system configuration and administrator handover.
- A vendor agreement covering confidentiality, data processing, breach notification, subcontractors, service levels, business continuity and secure data return/deletion at contract end.
10. Risk analysis and mitigation
| Key risk | Potential effect | Proposed mitigation |
| Low staff adoption or resistance to new processes | Limited use; continued parallel paper/email processes. | Early user consultation; phased rollout; practical role-based training; champions; feedback and management follow-up. |
| Exposure, loss or unauthorised access to sensitive information | Harm to individuals, reputational/legal consequences and loss of trust. | Data minimisation; strict access controls; privacy/security assessment; encryption, backups, logs and incident response. |
| Vendor underperformance or cost escalation | Delays, incomplete functionality or unplanned recurring costs. | Clear specifications and milestones; competitive procurement; reference checks; acceptance testing; payment linked to deliverables; total-cost-of-ownership assessment. |
| Connectivity, power or infrastructure limitations | Uneven access and interruptions, particularly for remote users. | Assess infrastructure; design for low bandwidth where feasible; offline/continuity procedures; backup power/connectivity options as justified. |
| Vendor lock-in or loss of access to RWN records | High future costs or inability to retrieve organisational data. | Require open/exportable formats, documented APIs where relevant, data ownership clauses and exit/transition plan. |
| Weak ownership and maintenance after project close | System becomes outdated or unavailable. | Assign system owner and budget responsibility; maintenance plan; train administrators; document support arrangements and recurrent costs. |
| Procurement conflict of interest or misuse of funds | Financial loss and reduced confidence in the project. | Segregation of duties; declarations; documented evaluation; approvals; audit trail; complaint and whistleblowing channels. |
11. Management, governance and accountability
RWN will designate a project lead and a cross-functional working group with representation from management, IT/administration, programmes, finance, procurement and relevant information-governance functions. The working group will validate requirements, review progress, resolve implementation issues and recommend acceptance of deliverables. RWN management will approve the system scope, budget, procurement decision, data-governance arrangements and go-live.
The selected service provider will be accountable for the contracted design/configuration, deployment, documentation, training and support deliverables. RWN will retain ownership and control of its institutional data. Roles and responsibilities, milestones, acceptance criteria, service levels and escalation procedures will be set out in the contract.
12. Monitoring, evaluation, learning and reporting
Monitoring will track delivery against the approved workplan, budget, milestones, indicators and risk register. The project lead will maintain evidence of procurement, deliverables, testing, training, system acceptance and expenditure. User feedback will be collected after training and at agreed intervals following go-live. Management will review progress, lessons, risks and any required corrective actions. Narrative and financial reporting will follow the applicable SIDA agreement, including the agreed reporting periods, eligible-cost rules, budget-deviation approvals and audit requirements.
The MIS will support internal information management; it will not replace RWN’s existing MEAL framework or donor reporting systems. Any reporting indicator that overlaps with MEAL will be drawn from the approved source system, with clear data ownership and no unnecessary duplication.
13. Sustainability and exit considerations
Sustainability will be addressed from the outset through selection of a solution that RWN can operate and afford beyond the initial implementation period. The project will identify annual hosting/licensing, maintenance, connectivity, security and staff-capacity costs; assign an internal system owner and administrators; document operating procedures; and ensure RWN can export its data and configuration in usable formats. The final handover will include administrator credentials transferred securely, system documentation, training records, backup/recovery instructions, vendor contacts and an agreed support/exit plan.
15.Submission Requirements
Applicants shall submit:
- Company profile and relevant experience in similar projects
- Technical proposal describing the methodology and work plan.
- Detailed financial proposal.
- Evidence of previous experience in similar assignments (3Completion Certificate).
- EBM Certificate
- Tax Clearance Certificate
- RDB Company Domestic Registration Certificate
16. Submission of Applications
Interested applicants should submit their complete application by email no later than 30 November2026. All documentation should be assembled into one PDF file and sent to Email: rwawnet@rwanda1.rw
17. Conclusion
The proposed digital MIS is a strategic investment in RWN’s institutional capacity and sustainability. By improving how institutional information is stored, accessed, protected and used, the initiative will strengthen internal coordination, accountability, organizational memory and evidence-informed decision-making. With participatory design, robust information governance, appropriate safeguards, staff capacity development and a sustainable support model, the system will provide a practical foundation for RWN to deliver its mission and advance its 2030 strategic priorities.
Issued by
Rwanda Women's Network (RWN)
Date of publication: November 2026