The problem
A delayed UNICEF situation analysis project in Palestine needed to recover its delivery window. The team had useful qualitative material, but the evidence was spread across interviews, notes, spreadsheets, draft sections, and partial working files. At the same time, the final report still needed clear methodology, ethics, safeguarding, limitations, findings, recommendations, and action-planning material. The real problem was not only late writing. The evidence system needed to be rebuilt quickly enough for analysis, recommendations, and drafting to happen together.
Context
The project ran in the last two weeks of February and the first week of March 2026. The final draft report is a UNICEF situation assessment on access to essential services for children and young people with disabilities in Gaza, the West Bank, and East Jerusalem, with chapters on methods, context, legal and policy frameworks, services, coordination, governance, cross-cutting issues, analysis, lessons learnt, recommendations, and annexes.
Before and after
- Before: The report process was under pressure. Useful material existed, but it was spread across interviews, notes, spreadsheets, draft sections, and partial analysis. Evidence retrieval was slow, and findings and recommendations still needed a clearer route back to source material.
- After: Source material sat inside a structured evidence base. Quotes, service-access issues, respondent details, geography, theory-of-change themes, findings, recommendations, and action-planning inputs could be retrieved and used together. This allowed evidence handling and writing to move in parallel instead of waiting for a long manual clean-up.
Constraints
The assignment had very little time left and the raw material could not stay scattered across interviews, notes, spreadsheets, draft sections, and partial analysis. The team needed a fast way to retrieve evidence by geography, respondent type, service area, issue, quote, and theory-of-change theme while keeping a clear line from source material to findings and recommendations.
What the team needed
- A clear evidence structure that could turn raw qualitative material into report-ready records fast
- A way to compare lived experience, service issues, and system-level findings across Gaza, the West Bank, and East Jerusalem
- A traceable workflow linking quotes, coded issues, theory-of-change themes, and report sections
- Drafting support that could move analysis and writing at the same time instead of waiting for full manual clean-up
- Recommendations and action points grounded in coded evidence rather than loose notes
When a delivery window is already compressed, check what slow reporting may be costing before adding more drafting pressure to the same workflow.
What I built
A structured qualitative evidence database, retrieval workflow, coded service-access entries, quote and excerpt tracker, theory-of-change evidence layer, recommendation matrix, action-planning material, and draft report support workflow.
Named systems and workflow pieces
- A structured qualitative evidence database with linked source, participant, coded evidence, service-access, quote, and theory-of-change layers
- AI-assisted organisation and retrieval support for faster review and drafting
- Evidence extraction and synthesis across interview, focus group, key informant, and desk-review material
- Supported report sections in line with the situation analysis structure
- Recommendation support and action-planning inputs tied back to the evidence base
- A workflow that let the team draft from organised evidence rather than raw transcripts
Where this connects to the services
This case study sits across Traceable Evidence Workflow Support and Data Use, Reporting & Communication Systems. It sits under Traceable Evidence Workflow Support because the project needed source records, coded quotes, service-access entries, theory-of-change links, retrieval fields, and source-traceable findings. It also sits under Data Use, Reporting & Communication Systems because the structured evidence needed to become report sections, recommendations, action-planning material, and a draft report for review.
The recovery workflow moved evidence and drafting in parallel
The build organised scattered qualitative material into a retrieval-ready structure so chapter drafting and recommendation work could move without waiting on a full manual clean-up first.
Collected interviews, notes, spreadsheets, and draft material into one working evidence base.
Turned qualitative material into records that could be filtered by service area, geography, respondent type, and issue.
Linked quotes, service-access patterns, and theory-of-change themes so the team could pull evidence quickly during drafting.
Used the organised evidence to shape chapter-ready findings, recommendations, and draft report support.
Interview or note to coded record to chapter-ready finding to recommendation and draft report support
How it worked
The workflow moved from raw material to usable output through a short sequence of controlled steps.
Process
- 01
Collected and organised raw material into one working evidence base instead of separate files and notes
- 02
Broke qualitative material into coded records that could be filtered by service area, geography, respondent group, and issue type
- 03
Linked quotes and excerpts to service-access patterns and theory-of-change themes for traceable use in drafting
- 04
Built retrieval paths that reduced repeated transcript reading and manual searching
- 05
Synthesised the coded material into chapter-ready findings, comparisons, and recommendation inputs
- 06
Worked in parallel on evidence handling and draft report support so the delayed report could return to a workable delivery rhythm
Outputs
These were the named assets, dated deliverables, and working materials left behind by the project.
Working outputs
- Qualitative evidence database with 59 source records
- Structured analysis sheets for adolescents, caregivers, KIIs, service access, quotes, and theory-of-change evidence
- 494 service-access entries
- 924 coded quotes and excerpts
- 651 theory-of-change evidence entries
- Draft report support dated 8 March 2026
- Recommendation matrix and action-planning material
Result
The delayed situation analysis was brought back into a workable delivery rhythm, with evidence retrieval, recommendations, and drafting connected inside one workflow.
Main result
- Recovered a delayed project and got it back into a workable delivery rhythm
- Completed draft report support inside a three-week recovery window
- Made evidence retrieval much faster for drafting and review
- Reduced repeated manual reading of transcripts and notes
- Gave the contractor a clearer line from source material to findings and recommendations
Report recovery is often evidence workflow recovery. When the source material is structured properly, writing and review can move faster without hiding the need for human judgement.
What this proves
- Report recovery support for delayed or under-pressure evidence-heavy projects
- Qualitative evidence structuring with source records, quote tracking, and coded excerpts
- Service-access issue coding and theory-of-change evidence mapping
- Evidence retrieval workflows by geography, respondent type, service area, issue, and theme
- Recommendation matrix development and action-planning support tied back to evidence
- AI-assisted organisation, retrieval, comparison, summarisation, and drafting support around approved source material
Best fit
These are the situations where this kind of evidence workflow tends to be the strongest fit.
Who this is best for
- Situation analyses, evaluations, donor reports, programme reviews, or qualitative assessments that are delayed or at risk
- Teams with interviews, notes, spreadsheets, and draft sections scattered across working files
- Projects where findings and recommendations need to link back to source material
- Writers spending too much time searching for quotes and examples
- Teams comparing geography, respondent type, service area, and issue categories
- Teams considering AI support but needing a practical recovery workflow, not a black-box analysis process
Service stack connected to this case study
This case study sits inside the same delivery work, service logic, and practical outcomes shown across the site.
Turn interviews, submissions, case studies, survey comments, documents, and field notes into coded evidence, quote banks, synthesis tables, findings, recommendations, and report-ready outputs.
Use structured data in reports, dashboards, internal tools, public microsites, applications, presentations, annual reports, and decision-support workflows.