# Features The DIGIT Health Campaign Management (HCM) app is designed to support registrars, frontline workers, and supervisors in delivering health campaigns efficiently. It’s simple, offline-ready, and packed with features that guide users, reduce errors, and provide real-time support. *** **πŸ“‹ Registration & Data Management** * Add new households and individuals * Search and update existing records * Reuse beneficiary data for future campaigns **πŸ’‰ Service Delivery** * Record healthcare services delivered during single-round campaigns * Auto-calculate required resources based on pre-set rules **πŸ“¦ Stock Management** * Record stock received, issued, returned, damaged, or lost * Auto-reconcile available stock in the warehouse * View all stock transactions and counts offline **πŸ› οΈ Complaint Management** * Log complaints directly in the app (even offline) * Search, sort, and filter complaints using defined parameters **🧾 Supervision & Monitoring** * Use custom checklists for supervision activities * Track campaign progress using a daily work progress bar * Record GPS locations with offline support **🌐 Additional Capabilities** * Multi-language interface * In-app notifications to remind users of pending tasks * Web portal for user and access management πŸ—“οΈ **Attendance tracking** * Record attendance once or twice for campaign-related staff or training events * Operates offline and preserves data integrity πŸ’°**Payments workflow** * Review and approve attendance registers * Musters are generated and collated by boundary/event * Payment reports are exportable in Excel or PDF formats --- # Agent Instructions: 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: ``` GET https://docs.digit.org/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/features.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.