Design, Build and Pilot:
KP Justice Data Dashboard

Legal Aid Society (LAS) Pakistan has been awarded ICRC funding for Phase 1 (Design and Validation) of the REACH KP: Justice Hubs for Women, Children and Families initiative. The six-month project runs from June to December 2026 and is centred on Peshawar District, with the objective of developing a pilot-ready Justice Hub model for a 12-month pilot in 2027 and subsequent KP-wide scale-up.

This consultancy covers the KP Justice Data Dashboard component, Deliverable D3, under Section 7.1 of the REACH KP Concept Note dated 14 April 2026. The assignment will run for four months from September 2026 to 15 December 2026.

LAS currently operates two data assets relevant to this component: the SLACC legal helpline, which has assisted over 550,000 calls since inception and captures KP-origin data on legal need patterns, GBV incidence and referral outcomes; and NAZ Assist, LAS's AI legal information chatbot, which generates structured interaction data. The dashboard will consolidate these with a third stream, Justice Hub case management data once the hubs become operational.

The assignment will design, build and pilot a BI-integrated Justice Data Dashboard for KP, providing a near-real-time view of legal need patterns, GBV incidence, documentation barriers and institutional response rates. The dashboard architecture must be finalised and tested with live data by 15 December 2026. Full activation will follow in Phase 2 once Justice Hubs are operational.

The delivery model is delivery-model neutral and may be fulfilled through internal technical capacity or external procurement.

To design, build and pilot a BI-integrated Justice Data Dashboard for Khyber Pakhtunkhwa that consolidates:

1. Justice Hub case management data.
2. SLACC helpline analytics for KP-origin calls.
3. NAZ Assist chatbot interactions.

The dashboard will provide a single near-real-time view of legal need patterns, GBV incidence, documentation barriers and institutional response rates across KP.

The dashboard architecture must be finalised and tested with live data by 15 December 2026. Full activation will follow in Phase 2 once Justice Hubs are operational.

The scope is directly drawn from Deliverable D3 of the REACH KP Concept Note dated 14 April 2026. The delivering party must not exceed this scope or commit to outputs not included in the Concept Note.

1. Requirements and Indicator Definition

• Agree with LAS programme and MERL leads on the indicator set.
• Define required disaggregations including gender, age, district and case type.
• Define user roles for LAS leadership, programme team and donor reporting.

2. Data Audit and Source Mapping

• Profile the SLACC case database and live call records for KP-origin data quality.
• Map NAZ Assist interaction logs.
• Define the intake data model for the Justice Hub case management data stream.

3. Architecture and Pipeline Build

• Design and implement the data warehouse schema.
• Develop extraction and transformation pipelines from the three source systems.
• Align the solution with LAS's existing BI infrastructure, including PostgreSQL and Metabase, to avoid duplicative tooling costs.

4. Dashboard Development
Develop dashboard views covering:

• Provincial overview
• GBV trends
• Documentation barriers
• Referral outcomes
• Institutional response rates
• Role-based access for LAS leadership, programme team and donor reporting

5. Testing with Live Data

• Load and validate live SLACC and NAZ Assist data.
• Reconcile dashboard figures against source systems.
• Document known data quality caveats.
• Conduct user acceptance testing with LAS programme and MERL teams.

6. Handover

• Produce administrator and user documentation.
• Train nominated LAS staff.
• Prepare a Phase 2 activation plan, including Justice Hub case management integration once hubs become operational.

Activities and Timeline

September 2026

• Inception
• Requirements and indicator workshop with LAS programme and MERL leads
• Data audit of SLACC and NAZ Assist sources
• Architecture options note submitted for LAS approval

October 2026

• Data model and pipeline build
• KP-origin data extraction and cleaning
• First dashboard wireframes signed off by LAS Programme Lead

November 2026

• Dashboard build
• Live-data testing and reconciliation
• User acceptance testing with LAS programme and MERL teams

December 2026, by 15 December

• Refinement based on UAT feedback
• Administrator and user documentation
• Staff training
• Phase 2 activation plan
• Final acceptance by LAS leadership

Governance and Reporting

• Monthly written progress reports covering activity status, deliverable progress and risks.
• Mid-point review at the end of October 2026 to assess pipeline progress and dashboard readiness.
• Scope may be rebalanced within the approved budget at the mid-point review only with written agreement from LAS.
• All deliverable acceptance follows the Deliverables Schedule.
• Written sign-off is required before the next milestone is triggered.

Assumptions and Exclusions

• LAS will provide timely access to SLACC and NAZ Assist systems and data.
• LAS MERL team will provide input for indicator definition.
• LAS programme team will be available for UAT.
• Scope is limited to D3 of the REACH KP Concept Note dated 14 April 2026.
• No additional outputs will be accepted as deliverables under this ToR.
• Phase 1 excludes full production deployment. The assignment delivers a validated architecture tested with live data; full activation follows in Phase 2.
• Justice Hub case management system build is outside scope. Only the data model is scoped under this assignment.
• All other Phase 1 deliverables, D1 through D8 excluding D3, are outside scope.
• Any material scope change requires written agreement between LAS and the delivering party.

• Lean team capable of delivering all four deliverables within the four-month assignment term.
• One data engineer or BI developer as hands-on build lead responsible for pipeline, schema and dashboard development.
• Part-time data analyst support for indicator validation, data quality review and UAT.
• Part-time technical oversight for architecture review and quality assurance.
• Strong SQL and data pipeline development experience, including ETL or ELT.
• Experience with PostgreSQL and Metabase or equivalent open-source BI. Any departure from LAS's existing stack must be justified in writing.
• Experience handling sensitive case or personal data, preferably in a development or justice sector context.
• Familiarity with M&E indicator frameworks is an advantage.
• Prior experience developing dashboards for humanitarian or access-to-justice organisations is preferred.
• Applicants must be legally registered and eligible to contract with a non-profit organisation.
• Applicants must declare any actual or potential conflict of interest with LAS, ICRC or any partner institution named in the REACH KP Concept Note.
• Proposal content must be original.
• Phase 1 technology funds are limited, and proposals must reflect the lean validation-grade scope specified in this ToR.

All deliverables must be submitted to and accepted in writing by the named accepting party. No payment or milestone will be processed without written sign-off. The final deliverable must be accepted by 15 December 2026.

Applicants must submit:

• Full technical proposal responding to the ToR.
• Full financial proposal.
• Detailed budget with cost breakdown against each deliverable and activity.
• Staff costs by role and time allocation.
• Software/tooling costs and other direct costs.
• Proposed team structure and relevant experience.
• Details demonstrating relevant technical competencies and previous dashboard/data pipeline work.
• Relevant portfolio or examples of comparable work, where available.
• Declaration of any actual or potential conflict of interest with LAS, ICRC or relevant partner institutions.
• Confirmation of legal registration and eligibility to contract with a non-profit organisation.
• Confirmation that proposal content is original.

Proposals must be submitted by email to [email protected] by 30 September 2026. Late or incomplete submissions will not be considered. Shortlisted applicants may be invited for a clarification meeting before final selection.

• All SLACC, NAZ Assist and Justice Hub case management data remain the property of LAS.
• Access to data will be limited to what is strictly necessary for delivery and will require signed confidentiality undertakings before access begins.
• SLACC and NAZ Assist data contain sensitive personal information, including GBV-related records.
• Anonymisation or pseudonymisation is required for all analytical outputs.
• Raw data may not leave LAS-controlled infrastructure without prior written approval from LAS Leadership.
• A data protection protocol forms part of Deliverable A1 and must be approved by LAS before live data is accessed or processed.
• All software, pipelines, dashboards, documentation and other outputs produced under this ToR vest in LAS upon acceptance.
• Pre-existing tools and IP remain the property of their owners and will be licensed to LAS for use, maintenance and Phase 2 continuation.
• Applicants must comply with all confidentiality and data protection requirements specified by LAS.

• The delivering party must submit a detailed budget with a full cost breakdown against each deliverable and activity.
• The budget must clearly identify staff costs by role and time allocation, software/tooling costs and other direct costs.
• Phase 1 technology funds are limited, and the proposed budget must reflect the lean validation-grade scope of this ToR.
• No payment or milestone will be processed without written acceptance/sign-off of the relevant deliverable.
• Any material scope change affecting cost must be agreed in writing between LAS and the delivering party.