> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/public-finance/exemplars/pfm-implementations/odisha.md). # Odisha ## Overview Delayed payments to CBOs and wage seekers were a key scheme implementation challenge. Beneficiaries faced lengthy wait times, with a baseline study across two pilot urban local bodies (ULBs) finding that over 50% of completed tasks were not processed for payment, and the rest encountered delays exceeding one month. Wage seekers come from low-income households, and such delays undermine the scheme’s welfare objectives. Such delays arise largely from cumbersome, paper-based compliances, billing, and verification processes. Every step – from attendance tracking and bill submission to verification, approvals, and payment instructions – relied on manual processes. This increases the administrative burden on local government personnel, who are often already overburdened. These long-drawn processes also resulted in underutilisation of sanctioned funding, with funds parked idle in banks and limited transparency. ## Reference Applications [MUKTASoft ](/public-finance/exemplars/pfm-implementations/odisha/muktasoft.md) * Objective: Launched in April 2020 by HUDD Odisha * The scheme aims to generate sustainable livelihoods for the urban poor, while creating and maintaining climate-resilient community assets, nurturing inclusive and equitable urban development. * Community-Centric Implementation: Bottom-up scheme design ensures community participation in identifying and prioritising public works. * MUKTA empowers Community-Based Organisations (CBOs) as project contractors, driving recruitment and execution and fostering community-rooted initiatives. * Beneficiaries: Wage seekers, transgenders and women from Self-Help Groups are key recipients of the scheme’s benefits. --- # 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://docs.digit.org/public-finance/exemplars/pfm-implementations/odisha.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.