> 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/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/microplanning.md). # Microplanning ## Overview Health campaign microplanning is a detailed planning approach used to ensure that health interventions, such as immunisations or disease prevention campaigns, are effectively delivered to target populations. Microplanning helps to know: 1. Who needs the intervention? 2. Where is the intervention needed? 3. How many resources (medical supplies, people, commodities, etc.) are needed for the intervention? 4. How will we reach the intervention site? ## Problems Addressed The Microplanning feature addresses the following challenges. * Prone to Errors: The microplanning process relies heavily on Excel, requiring meticulous care for resource estimation calculations, making it highly susceptible to errors. * Fragmented Management: Each district manages its microplan independently, resulting in a back-and-forth process for collaboration—incomplete data from any district results in faulty resource estimation for the entire campaign. * Complex Data Collection: Gathering and validating population data for microplan estimation is a tedious and poorly defined process. Incorrect population estimates can lead to inaccurate resource estimations for the campaign. * Time-Consuming Collaboration: Microplanning involves multiple people from various administrative levels to administer and validate resource estimations. Offline collaboration is time-consuming and increases the risk of errors if not managed carefully. * Lack of Reusability: Microplan estimations are created from scratch for each new campaign, making the process lengthy and time-consuming without the benefit of reusing previous plans. ## Goals & Benefits * Enable countries to be able to collect and validate accurate population data for better & accurate microplan estimation. * Enable countries to have better accountability mechanisms and controlled access to ensure transparency and authorised access for microplan execution. * Enable countries to more accurately estimate and distribute resources, ensuring targeted regions are reached and health campaigns are executed smoothly. * To reduce the time to set up and finalise a microplan from an average of 3 months to 1 month. The Microplanning feature helps build capabilities to maximise campaign coverage, enhance access for health campaigns and fairly estimate resources. The key benefits are listed below: * Improve population denominator: Leverage data triangulation from multiple sources and validation from community leaders at the village/settlement level to identify and improve the population denominator. * Targeted Interventions: Leverage data to pinpoint high-risk and unsettled areas and tailor campaign strategies to specific geographic populations. * Optimised Resource Allocation: Analyse population distribution and resource needs to ensure efficient deployment of personnel, vaccines, and supplies. * Improved Outreach & Accessibility: Identify underserved communities and map optimal routes for campaign teams, maximising outreach and access. * Increased Transparency & Accountability: Provide a clear picture of campaign coverage and resource distribution, promoting accountability to stakeholders and communities. ## Key Features Set up & manage microplan * Capture campaign details & administrative boundary * Manage microplan data: Top-down population & facility data ingestion * Configure microplan assumptions & estimation formula * Create microplan users & manage their access * Re-use existing microplan Validate & finalise population data for microplanning * Validate the top-down ingested population data of the villages * Edit & update the ingested population data of the villages * Approve or reject the updated/edited population data of the villages * View status logs and user comments whenever population data is updated * Finalise the microplan population data for the campaign region Assign facilities or point-of-services to their catchment areas * View the list of facilities belonging to the user’s jurisdiction * Assign the catchment areas under the user’s jurisdiction to the facilities for service delivery * De-assign the already-assigned catchment areas under the user’s jurisdiction * Finalise the facility-to-boundary mapping for the campaign region Validate & finalise the microplan estimation * Validate microplan estimation * Approve or reject the microplan estimation * View status logs, change logs, and user comments whenever the microplan estimation gets updated * Finalise the microplan estimation for the campaign region * Download and view the finalised microplan as an Excel Geospatial view of microplan estimation * View the microplan estimation for catchment boundaries on the geospatial map * View the resource estimation for facilities on the geospatial map * View the geospatial map with multiple base map layers ## User Roles 1. System administrator - This user is responsible for setting up the microplanning platform, such as selecting campaign boundaries, setting up the data, configuring the microplan assumptions, etc. This user will belong to the national/country-level administrative hierarchy. 2. Population data approver - This user will have access to the microplan module to view, validate, and approve the population of the assigned jurisdiction, such as province, district, etc. The approved population will be used for the estimation of resources of the microplan. 3. National population data approver - This is a national/central-level population data approver who will have access to approve and finalise the population data for the villages/settlements within the campaign boundary. 4. Facility boundary assigner - This user will have access to the microplan module to assign the facilities to their catchment boundaries, concerning the user’s assigned jurisdiction, such as province, district, etc. 5. National facility boundary assigner - This is a national/central level user, who will have access to the microplan module to assign the facilities to their catchment boundaries and finalise the facility to catchment area assignment for the villages/settlements within the campaign boundary. 6. Microplan estimation approver - This user will have access to the microplan module to view, edit, and approve the microplanning estimation concerning the user’s assigned jurisdiction, such as province, district, etc. 7. National Microplan estimation approver - This is a national/central-level user who will have access to the microplan module to view, edit, and approve the microplan estimation and finalise the microplan estimation for the villages/settlements within the campaign boundary. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/microplanning.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.