> For the complete documentation index, see [llms.txt](https://inspired.epd.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inspired.epd.eu/guide/how-does-inspired-work-in-practice/a-dialogue-process-in-three-phases/monitoring-and-donor-alignment-phase/ensuring-the-alignment-of-donor-support-to-the-priorities-outlined-in-the-roadmap.md). # Ensuring the alignment of donor support to the priorities outlined in the Roadmap Interestingly enough, the multi-stakeholder approach adopted throughout the dialogue would allow both the donors and the stakeholders themselves to assess their actual capacities as a whole and according to the policy objectives contained in the Roadmap for Reform, instead of as isolated entities, which is, unfortunately, the way in which many institution-building programs are still being devised. In doing so, both governments and donors will be in a better position to avoid the capability traps resulting from what Andrews, Pritchet and Woolcock have called “*isomorphic mimicry: the tendency of governments to mimic other governments’ successes, replicating processes, systems, and even products of the “best practice” examples*” (see [Library](https://inspired.epd.eu/resources/library)). As a result, the Roadmap for Reform can contribute directly to the alignment of international assistance with the broader reform agenda developed by the key domestic stakeholders. This will, in turn, enhance local ownership over the definition of reform priorities while improving the coordination between democracy support activities and technical assistance. Which in the end should result in better-designed programs that take as their starting point the reality in the country and policy area to be supported instead of ideal models that seldom fit into the existing practices and tend to neglect the full potential and capacities of domestic actors. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://inspired.epd.eu/guide/how-does-inspired-work-in-practice/a-dialogue-process-in-three-phases/monitoring-and-donor-alignment-phase/ensuring-the-alignment-of-donor-support-to-the-priorities-outlined-in-the-roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.