A practical blueprint for building one-stop-shop services that connect legal support, housing, healthcare, language learning, childcare and employment into a single, coherent journey for refugees from Ukraine — and for anyone navigating a fragmented support system.
The Blueprint isn't meant to be read cover to cover. It's built so each type of reader can go straight to what matters for their role.
Case managers, social workers, employment counsellors, psychologists, legal advisers, interpreters and intercultural mediators working directly with people day to day.
Start with the service pathway and the toolkit
NGOs, public employment services, municipalities, education, healthcare and psychosocial providers, and social-economy organisations delivering the work on the ground.
Start with the service model and implementation plan
Local, regional and national bodies designing or strengthening coordination mechanisms, governance structures and funding frameworks.
Start with governance, sustainability & funding
Employers, social enterprises, refugee-led organisations and community actors who contribute knowledge, opportunities and connections.
Start with the service model & governance chapters
The Blueprint is meant to be adapted, not replicated. Where a local service or procedure already does the job well, keep it — the goal is to fill genuine coordination gaps, not to redesign what already works.
Legal status, housing, health, language, childcare and employment interact constantly. Unstable housing can block a job search. No childcare can shut someone out of a language class. A single missing document can stall everything else. That's the case for treating support as one connected system, not a set of separate queues.
Some groups face compounding barriers — single parents, people with disabilities or chronic conditions, older people, survivors of violence, and those with limited digital access or support networks. But vulnerability isn't the whole story: most beneficiaries also bring real skills, resilience and resources that a good pathway should build on, not overlook.
Eight principles underpin the whole model — a shared foundation that still leaves room for local context.
Support reflects the person's own priorities, capacities and resources — not a fixed template.
Language, disability, digital literacy and caregiving barriers are actively designed around, not left for the person to solve.
One thread of responsibility runs through assessment, referral, follow-up and review — proportionate to need.
Clear roles and real information-sharing let separate organisations act as one system.
People are treated as rights-holders, with dignity, fairness and appropriate safeguarding.
Dedicated support is explained clearly and designed to avoid resentment or parallel systems with host communities.
Delivery builds safety, predictability and trust — without assuming trauma or forcing disclosure.
Interpreters and cultural mediation keep language and culture from becoming barriers to rights.
Every beneficiary moves through the same functional pathway, even when different organisations deliver different parts of it.
One clear door into the system, whichever channel someone arrives through — in person, by phone or online.
Urgent safety, protection or basic needs are addressed first, before deeper assessment begins.
A proportionate look across the relevant dimensions of someone's situation — no more than necessary, no less than needed.
Needs are ranked and turned into a personalised action plan built with the person, not for them.
The plan connects to real services — inside the ecosystem or through an external specialist referral.
A case manager keeps multiple services aligned while support is actively underway.
Progress is checked against the plan, and the plan adjusts as circumstances change.
The case closes with a clear outcome — or transitions cleanly to longer-term support.
Modules aren't a checklist everyone completes — they're switched on according to what assessment actually finds, and several can run at once.
Resolving status, paperwork and administrative barriers that block access to everything else.
Finding and stabilising accommodation and covering urgent material needs.
Helping people register with and actually use the health system, including continuity of care.
Support for wellbeing and coping, delivered without assuming trauma in every case.
Building the language and local know-how that everything else depends on.
Keeping children and young people's schooling on track through disruption.
Removing the care gaps that otherwise block language classes, work or appointments.
Matching skills and qualifications to real opportunities in the local labour market.
Support for those building their own livelihood rather than seeking employment.
A pathway is only as good as the system holding it together. Three areas of the Blueprint cover how to build and keep that system working.
Drawn from the research, piloting and expert validation behind the Blueprint.
Keep entry, assessment, prioritisation, referral, case management and follow-up intact — adapt how they're configured, not whether they exist.
Multiple access channels should still lead into a single intake and support logic.
Every priority need identified should lead to a real service, a clear owner and an actual outcome — not just a record.
Match intensity to actual risk and need, and design out language, disability and digital barriers.
Governance, prepared staff, active partnerships and data-sharing agreements need to be in place before scaling.
Coordination and case management need stable funding — not just the frontline services people see.
This page distills the highlights. The full 127-page Blueprint includes detailed operational sheets for every module, the complete implementation toolkit, and the research behind the model.
EU4UA is delivered by a four-organisation consortium in Poland and Romania, co-funded by the European Union, with five associated partners contributing expertise across Europe.
The source report does not include separate artwork for each partner organisation's logo, so names are shown as text here. If you can share the individual logo files, they can be dropped in in place of these labels.