1. Document Overview
original-brd
Jump to Revision 2: Updated Verification Model
Mitanin is the mobile application used by Chhattisgarh's community health workers, called Mitanins, to record health care activities and generate monthly incentive claims. This document defines the requirements for the Incentive Verification module of the Mitanin application, covering two roles: the Mitanin Trainer (MT), who reviews a defined set of activities, and the ANM, who provides final approval or rejection of each Mitanin's monthly claim.
Target Users | Mitanin Trainer, ANM |
Primary Audience | Product managers, engineering and backend teams, UI/UX designers, program stakeholders |
Phase | Phase 1 |
Platform | Android mobile application |
Approval Level | Mitanin Trainer reviews four defined incentive activities. ANM reviews the complete monthly claim and gives the final approval or rejection. |
Future Scope | Web portal access, and any expansion of the Mitanin Trainer's reviewed activity list as decided by the program team |
Please refer to the for the clickable prototype.
2. Background and Context
Mitanins record their health care activities in the Mitanin app and generate monthly incentive claims. Verifying these claims today depends on manual checks and paper registers, which is slow and hard to audit. This module replaces that manual process with a digital, two-step verification workflow: the Mitanin Trainer checks a small set of activities she can personally confirm through her own fieldwork with the Mitanins she trains, and the ANM reviews the whole claim and gives the final decision for the month.
3. Problem Statement
No digital interface exists today for verifying Mitanin incentive claims.
Verification depends on paper registers, which is slow and inconsistent.
Delays in verification lead to delays in incentive payment.
There is no structured, auditable record of who verified what and when.
4. Product Vision and Goals
Vision
Give the Mitanin Trainer and the ANM a simple mobile interface to review and approve Mitanin incentive claims every month, with clear accountability for each decision.
Goals
Category | Goal | Description |
|---|---|---|
Process Digitisation | Digitise incentive verification | Replace the manual, paper based verification process with a fully digital workflow for the Mitanin Trainer and the ANM. |
Operational Efficiency | Reduce verification turnaround | Minimise the time between a Mitanin's submission and the ANM's final decision. |
Accuracy and Compliance | Improve verification accuracy | Reduce manual errors through structured review by both the Mitanin Trainer and the ANM. |
Transparency and Audit | Enable audit ready verification | Every decision by the Mitanin Trainer and the ANM is traceable, with identity, timestamp, and reasons where applicable. |
Adoption | Track usage of the module | Percentage of monthly claims verified digitally, and average turnaround time at each stage. |
5. User Personas
5.1 Mitanin Trainer (MT)
Reviews four specific incentive activities that she can personally confirm through her regular fieldwork with the Mitanins she trains.
Cannot approve or reject a Mitanin's overall monthly claim. Her decision is limited to the four activities in her remit.
Expected to act within 24 hours of a Mitanin's submission or resubmission.
Uses a smartphone as her primary device, with limited time between field visits.
5.2 ANM
Final approving authority for each Mitanin's whole monthly claim.
Reviews every activity the Mitanin has claimed, and can see whether the Mitanin Trainer has approved the four activities in her remit.
Approves or rejects the whole month's claim in a single decision.
Facility based, manages claims for all Mitanins mapped to her.
6. Scope
In Scope (Phase 1)
Separate, role based login for the Mitanin Trainer and the ANM.
Mitanin Trainer dashboard and activity level review for the four defined activities.
ANM dashboard, drill down list, and month level approval or rejection.
Status tracking, notifications, and audit logging for both roles.
Out of Scope
Recalculating or editing incentive amounts.
Payment disbursement.
Web portal access.
Any verifying role other than the Mitanin Trainer and the ANM. There is no additional layer between the ANM and final processing.
7. Roles and Verification Model
This module uses two roles instead of one, and they do not have the same authority.
Role | What they review | What they can decide | When it applies |
|---|---|---|---|
Mitanin Trainer | The four named activities listed in Section 8, when claimed by the Mitanin that month | Approve or reject each of those four activities. Cannot act on any other activity, and cannot approve or reject the whole month's claim | Only when a Mitanin's monthly claim includes one or more of the four activities |
ANM | Every activity the Mitanin has claimed for the month | Approve or reject the whole month's claim in one decision | Every month, for every submitted claim. This is the only route to final approval |
The ANM's decision on a claim becomes available only once the Mitanin Trainer has approved the four activities, if the Mitanin claimed any of them that month. This is not a limit on the ANM's authority. It simply means the ANM reviews a claim once the specific activities the Trainer can personally vouch for have already been checked. If a Mitanin's claim does not include any of the four Trainer activities, the ANM can review and decide on it without waiting on the Mitanin Trainer at all.
8. The Four Mitanin Trainer Activities
The following four incentive activities fall within the Mitanin Trainer's review. All four are meeting attendance or self reporting activities rather than clinical or beneficiary linked ones, which fits the Trainer's role: she can personally confirm attendance at these meetings and the completeness of the register during her own fieldwork with the Mitanin, unlike clinical activities such as antenatal visits or immunisation records.
S.No | Activity | Rate | Category |
|---|---|---|---|
23 | Attending monthly cluster meetings of Mitanins | Rs. 150 per case | Village Health Meetings |
24 | Organising and attending monthly meetings of the Village Health, Sanitation and Nutrition Committee (VHSNC) | Rs. 150 per meeting | Village Health Meetings |
25 | Filling prescribed information in the Mitanin register | Rs. 500 per month | Mitanin Register and Reporting |
40 | Filling 5 prescribed types of information in the Mitanin register | Rs. 1,000 per month | Mitanin Register and Reporting |
9. Timelines and Cut off Dates
Stage | Timeline |
|---|---|
Mitanin submission window | 1st to 3rd of every month |
Mitanin Trainer review window | 24 hours from the moment a Mitanin submits, or resubmits, a claim that includes one or more of the four Trainer activities |
ANM review and approval | By the 5th of every month, regardless of when the Mitanin Trainer's review is completed within that window |
Because the Mitanin Trainer's 24 hour window sits inside the ANM's overall cut off, a Mitanin who submits close to the 3rd leaves less time for the ANM to act. This document does not change the submission window or the ANM's due date; both roles are expected to act well within their own windows so the ANM still has enough time to review.
10. Mitanin Trainer Workflow
10.1 Login
The Mitanin Trainer is issued her own username and password, separate from the Mitanins and separate from the ANM. Logging in takes her directly to her own dashboard. She only sees the Mitanins mapped to her own geography.
10.2 Dashboard
The dashboard header shows the Mitanin Trainer's name and ID. It includes a month selector, defaulted to the current month, and a filter for the villages or clusters mapped to her, along with a search box for finding a Mitanin by name.
The dashboard shows the following counts for the selected month: Total Mitanins mapped to her, Activities Awaiting Her Review, Activities Approved, Activities Rejected (sent back to the Mitanin for correction), and Mitanin Unclaimed. These counts are based on claimed instances of the four Trainer activities, not on the Mitanin's overall status.
10.3 Mitanin Listing
Tapping into the dashboard shows Mitanins grouped by village or cluster, each with a short status label describing where her four activities currently stand: Awaiting Review, Approved, Rejected (awaiting the Mitanin's correction), or Not Applicable if she did not claim any of the four activities that month.
10.4 Activity Review and Approval
Opening a Mitanin shows her full monthly claim for context, with every activity she has claimed listed by category, serial number, activity name, number of claims, and amount, in read only form. Only the four Trainer activities, when claimed, carry an action: Approve or Reject.
Approving or rejecting one of these activities is final once submitted. The Mitanin Trainer cannot change her own decision afterward. A decision can only be reopened in two situations: the Mitanin corrects and resubmits after a Trainer rejection, in which case the Trainer reviews the corrected activity again, or the ANM later rejects the whole month's claim, in which case the whole claim, including these four activities, comes back to the Mitanin Trainer for a fresh review.
Rejecting one of the four activities opens a short reason field and sends only that activity back to the Mitanin for correction. It does not affect any of the Mitanin's other claimed activities, and it does not require the Mitanin to resubmit her entire month's claim, only the rejected activity.
10.5 Status Transitions for the Mitanin Trainer
A claimed instance of one of the four activities starts as Awaiting Review.
The Mitanin Trainer approves it, and it becomes Approved. This is final unless the whole month's claim is later rejected by the ANM.
Or the Mitanin Trainer rejects it, and it becomes Rejected, returning to the Mitanin for correction. Once the Mitanin resubmits, it returns to Awaiting Review for the Mitanin Trainer.
10.6 Notifications to the Mitanin Trainer
When a Mitanin submits, or resubmits, a claim that includes one or more of the four Trainer activities. This starts her 24 hour review window.
A reminder 6 hours before her 24 hour window ends, if she has not yet approved or rejected the activity.
11. ANM Workflow
11.1 Login
The ANM is issued her own username and password, separate from the Mitanins and the Mitanin Trainer. Logging in takes her directly to her own dashboard, scoped to the Mitanins mapped to her.
11.2 Dashboard
The dashboard header shows the ANM's name and ID, a month selector defaulted to the current month, a geography filter, and a search box for finding a Mitanin by name. Tiles show the count of Mitanins in each of the five statuses defined in Section 13: Verified, Pending, Overdue, Rejected, and Mitanin Unclaimed, along with a Total Mitanins tile.
11.3 Mitanin Listing
A grouped list of Mitanins by facility or geography, each with a status pill showing Verified, Pending, Overdue, Rejected, or Unclaimed for the selected month.
11.4 Monthly Detail and Approval
Opening a Mitanin shows every activity she has claimed for the month, grouped by category. Each category header shows the number of activities and the total amount claimed, and expands to show each activity's serial number, name, number of claims, and amount. On the four Trainer scoped activities, a short label shows whether the Mitanin Trainer has approved them, and when.
A single footer lets the ANM approve or reject the whole month's claim. Approve and reject apply to every activity claimed that month in one action. The approve action is available once the Mitanin Trainer has approved every one of the four activities the Mitanin claimed that month. If any of them are still awaiting the Trainer's decision, the approve action stays unavailable, with a short note explaining that it is waiting on the Mitanin Trainer. The reject action is always available to the ANM, whether or not the Mitanin Trainer has finished her review.
11.5 Rejection
Rejecting opens a short list of standard reasons, such as incomplete documentation, incorrect data, duplicate claim, or ineligible activity, with an option for other reasons that requires a written remark. Submitting sends the whole month's claim back to the Mitanin along with the reasons given.
11.6 Beneficiary Level Detail
For activities linked to individual beneficiaries, tapping the activity row opens a read only screen listing each beneficiary's details and the amount claimed for that beneficiary. This screen has no actions available on it.
11.7 Status Transitions for the ANM
A submitted claim starts as Pending.
The ANM approves it, and it becomes Verified. This is final.
Or the ANM rejects it, and it becomes Rejected, returning to the Mitanin for correction.
A Pending claim becomes Overdue once the ANM's due date, the 5th of the month, passes without a decision.
11.8 Notifications to the ANM
When the Mitanin Trainer approves the four activities and the claim becomes available for her review.
A reminder 6 hours before her own due date, the 5th of the month, if the claim is still pending her decision.
When she rejects a claim, confirming it has been sent back to the Mitanin.
When a Mitanin resubmits a claim following a rejection, once the Mitanin Trainer has approved the four activities again.
When she gives her final approval, confirming the claim is Verified and has moved forward for processing.
12. Shared Screens
Profile: both roles have a read only profile screen showing name, role, employee ID, mobile number, and mapped geography.
Navigation: both roles have a side navigation menu with Home, Profile, Sync, Help and Support, account actions, and Logout.
13. Status Lifecycle and Workflow
13.1 Statuses
Status | Meaning |
|---|---|
Mitanin Unclaimed | The Mitanin has not submitted a valid claim for the month by the ANM due date (the 5th). This also applies when a claim was sent back for correction and the Mitanin never resubmitted it in time. |
Pending | The claim has been submitted and is awaiting a decision, either from the Mitanin Trainer on her four activities, or from the ANM on the whole month, whichever stage the claim is currently at. |
Overdue | The claim is still Pending after the ANM due date (the 5th) has passed. |
Rejected | The ANM has rejected the whole month's claim and sent it back to the Mitanin for correction. |
Verified | The ANM has approved the whole month's claim. The claim is final and moves forward for processing. |
13.2 Standard Flow
Mitanin submits before the 3rd
-> Mitanin Trainer's 24-hour review window starts
-> Mitanin Trainer approves the four activities (if claimed)
-> Claim becomes available for the ANM
-> ANM approves the whole month's claim
-> Claim is verified, incentive is approved and moves forward for processing
13.3 If the Mitanin Trainer Rejects One of Her Four Activities
Step | What happens |
|---|---|
1 | Mitanin submits her claim. |
2 | Mitanin Trainer rejects one of the four activities within her 24 hour window. |
3 | Mitanin has 24 hours to correct and resubmit that activity. |
4 | Mitanin Trainer reviews the correction and approves it. |
5 | Claim proceeds to the ANM as in the standard flow. |
13.4 If the ANM Rejects the Whole Month's Claim
Step | What happens |
|---|---|
1 | ANM rejects the claim. It is sent back to the Mitanin along with the reasons. |
2 | Mitanin must resubmit the whole claim before the ANM's due date, the 5th, for it to be considered again. |
3 | If resubmitted in time, the Mitanin Trainer reviews and approves the four activities again on the new submission. |
4 | Once approved, the claim becomes available to the ANM again, who gives the final decision. |
5 | If the Mitanin does not resubmit before the due date, the claim for that month becomes Mitanin Unclaimed. |
14. Business and System Logic
Area | Rule |
|---|---|
Mitanin Trainer decision finality | Approving or rejecting one of the four activities is final once submitted. It can only be reopened if the Mitanin corrects and resubmits after a rejection, or if the ANM later rejects the whole month's claim. |
ANM decision mode | One decision covers every activity claimed that month. There is no per activity approve or reject for the ANM. |
Resubmission after a Mitanin Trainer rejection | The Mitanin must correct and resubmit within 24 hours for the Mitanin Trainer to approve it. |
Resubmission after an ANM rejection | The Mitanin must resubmit the whole claim before the ANM's due date. If resubmitted in time, the Mitanin Trainer reviews the four activities again before the ANM gives her final decision. |
Cut off and Overdue | The ANM's due date, the 5th of the month, does not change based on how long the Mitanin Trainer's review takes. A claim becomes Overdue once the 5th passes while still Pending, regardless of which stage caused the delay. |
Escalation | Escalation relies mainly on the notifications defined in Sections 10.6 and 11.8, timed to give both roles enough warning. Escalation to the Medical Officer by SMS or WhatsApp remains available as a fallback, but is expected to be rarely needed if these notifications are followed. |
Incentive freeze | Once the ANM approves a month's claim, all figures for that Mitanin's month become final and cannot be changed. |
Concurrency | If the underlying claim changes while a screen is open, the user is asked to refresh before taking any action. |
Flow.png
15. Data and Audit Requirements
Attribute | Description |
|---|---|
Mitanin Trainer ID | Identifier of the Mitanin Trainer performing the action |
ANM ID | Identifier of the ANM performing the action |
Mitanin ID | Identifier of the Mitanin whose claim is being reviewed |
Activity ID | Identifier of the specific activity, recorded for Mitanin Trainer actions since these are activity level decisions. Not required for the ANM's whole month actions |
Action Type | Trainer Approve Activity, Trainer Reject Activity, ANM Approve Month, or ANM Reject Month |
Timestamp | Date and time the action was performed |
Remarks | Reason given, where applicable |
16. Security and Access Control
The Mitanin Trainer and the ANM each log in with their own username and password and only see the Mitanins mapped to their own geography.
The Mitanin Trainer's access is limited to the four named activities. She cannot open or act on any other activity, and cannot act on the whole month's claim.
The ANM has access to every activity claimed by the Mitanins mapped to her, and is the only role that can give the final month level decision.
17. Assumptions and Items for Confirmation
This document assumes the following, and it would help to confirm these with the program team before development begins.
Mitanin Trainer rejection not corrected in time: If a Mitanin does not correct and resubmit a Mitanin Trainer-rejected activity within 24 hours, this document assumes the claim continues toward the ANM's existing due date, and the Overdue and Mitanin Unclaimed rules in Section 13.1 apply exactly as defined, without any separate rule for this specific situation.
revision-2
18. Revision 2: Updated Verification Model
Back to original BRD (Section 1)
This section updates the verification model described in Sections 7 through 16. Sections 1 through 6 and 8 are unaffected.
18.1 Summary of Changes
Area | What Changed |
|---|---|
Verification action (activity level) | The checkbox and individual activity model applies to both the Mitanin Trainer's and the ANM's activity lists. Tick the activities you are confident about, or open one activity individually to approve or reject it with a reason. A single Approve action commits every ticked activity; anything left unticked is rejected, with a reason. |
Beneficiary level review (ANM only) | For activities linked to individual beneficiaries, opening the activity now shows a list of beneficiaries instead of the earlier read only list. Each beneficiary has her own approve and reject action that takes effect immediately, with no separate bulk Approve step at this level. |
Visit level review (ANM only) | For beneficiaries under activities that need multiple visits (the four ANC check ups, the seven newborn home visits, the five first year immunisation doses, and the two second year booster doses), opening the beneficiary shows each visit with its date and either the place it happened or the vaccine given. Visits can be approved individually or ticked and approved together. Rejecting one visit rejects that beneficiary; rejecting one beneficiary rejects the activity claim, so the Mitanin knows exactly which visit caused the rejection. |
Mitanin Trainer to ANM dependency | Removed. Each role now reviews independently. |
Timelines | The Mitanin Trainer's 24 hour review window, the ANM's 5th of month due date, and the Overdue status are removed. Only the Mitanin's 1st to 3rd submission window remains. |
Activity visibility | Each role's screen for a Mitanin's month shows only the activities within that role's remit. |
18.2 Roles and Verification Model (supersedes Section 7)
Both roles now use the same model: approve or reject individually, or tick several and approve them together, with anything left unticked rejected with a reason. The Mitanin Trainer reviews her four named activities; the ANM reviews every other activity. Neither role's review depends on the other.
18.3 Timelines (supersedes Section 9)
Only the Mitanin's 1st to 3rd submission window applies. No fixed review window for the Mitanin Trainer or due date for the ANM at this time.
18.4 Mitanin Trainer Workflow (supersedes Sections 10.4 to 10.6)
Opening a Mitanin shows only her four Trainer activities, when claimed, each with a checkbox. Tapping one opens it individually for approve or reject with a reason. A single Approve action at the bottom commits every ticked activity; anything left unticked is rejected, with a reason, and returns to the Mitanin. Notifications: on Mitanin submission or resubmission only, the 24 hour reminder is removed.
18.5 ANM Workflow (supersedes Sections 11.2 to 11.8)
Dashboard and status pills reduce to Verified, Pending, Rejected, and Mitanin Unclaimed; Overdue is removed. Opening a Mitanin shows only the activities outside the Mitanin Trainer's four, each with a checkbox, using the same individual and bulk approve/reject model as the Mitanin Trainer at the activity level. Rejection at this level applies to the specific activity or activities left unticked, not the whole month.
For any activity linked to individual beneficiaries, opening that activity now shows a list of beneficiaries in place of the read only detail screen described in Section 11.6. Each beneficiary row has its own approve and reject action that takes effect immediately. There is no separate bulk Approve step for beneficiaries. Rejecting a beneficiary opens the same reason list used elsewhere and sends just that beneficiary's claim back to the Mitanin for correction.
For beneficiaries under activities that require multiple visits, namely the four ANC check ups, the seven newborn home visits, the five first year immunisation doses, and the two second year booster doses, opening the beneficiary shows each individual visit with its date and either the place it happened or the vaccine given. Visits can be approved or rejected individually, or ticked and approved together at the bottom of the visit list. If any one visit is rejected, that beneficiary's claim is rejected; if any beneficiary is rejected, the activity claim is rejected, carrying the rejection back up so the Mitanin knows exactly which visit caused it.
Notifications: due-date reminders are removed; submission, resubmission, and the ANM's own action confirmations remain.
18.6 Status Lifecycle (supersedes Section 13)
Overdue is removed. Mitanin Unclaimed means no claim was submitted for the month. A Mitanin's month is Pending while any activity is still awaiting a decision in either role's scope, Verified once every activity is approved, and Rejected if any activity is rejected and awaiting correction. Rejections and resubmissions now happen at the activity level in both roles, independently of each other.
18.7 Business and System Logic (supersedes Section 14)
ANM decision mode is now activity level, matching the Mitanin Trainer. Resubmission after a rejection, by either role, has no fixed time requirement. The cut off and Overdue rule is removed.
18.8 Data and Audit Requirements (supersedes Section 15)
Activity ID is now recorded for every action, by both roles. Action Types: Trainer Approve Activity, Trainer Reject Activity, ANM Approve Activity, ANM Reject Activity. Both a bulk Approve and a bulk Reject action log one entry per activity they resolve.
19. Revision 3: Refined Review Actions
Back to Revision 2 (Section 18)
This section refines the activity level and visit level review actions described in Section 18. Sections 1 through 17, and Sections 18.3, 18.6, and 18.7, are otherwise unaffected.
19.1 Summary of Changes
Area | What Changed |
|---|---|
Activity level review, both roles (supersedes 18.1 row 1, 18.2, 18.4, 18.5 activity paragraph) | Removed the single Approve action that also rejected everything left unticked. Ticking an activity is now only a selection, like adding an item to a cart; it does not approve or reject anything by itself. Two separate actions sit at the bottom of the list: Approve, which approves every ticked activity, and Reject, which asks for a reason and rejects every ticked activity. Anything left unticked keeps its current status untouched, and can be reviewed later from the Pending tile or by opening that Mitanin again. |
Visit level review, ANM only (supersedes 18.5 visit paragraph) | Removed the checkbox and bulk footer at the visit level. Each visit is now approved or rejected immediately with its own tick and cross, the same as the beneficiary level. There is no bulk action for visits. |
Mitanin Trainer single-activity screens (new) | For the Mitanin Trainer's activities that are not linked to beneficiaries (cluster meetings, VHSNC meetings), the detail screen now shows the date the meeting took place, alongside the claim amount, and uses the same tick and cross icon buttons as the beneficiary and visit screens, instead of separate Approve/Reject buttons. |
19.2 Activity Level Review (supersedes 18.1 row 1, 18.2, 18.4, 18.5 activity paragraph)
Ticking an activity only marks it as selected. It does not approve or reject anything by itself. Two actions sit at the bottom of the activity list: Approve, acting only on ticked activities, and Reject, which opens the same reason list used elsewhere and applies to ticked activities only. Anything left unticked is not touched by either action and stays available for review later. This applies identically to the Mitanin Trainer's four activities and to the ANM's remaining activities.
19.3 Visit Level Review (supersedes 18.5 visit paragraph)
Visits no longer carry a checkbox. Each visit is approved or rejected on the spot with its own tick and cross, exactly as beneficiaries are at the level above. There is no bulk approve or reject action for visits.
19.4 Mitanin Trainer Single-Activity Screen (new)
For the Mitanin Trainer's activities that are not linked to individual beneficiaries (cluster meetings, VHSNC meetings), the detail screen now shows the date the meeting or activity took place, alongside the claim amount, and uses the same tick and cross icon buttons as the beneficiary and visit screens. This keeps the review screen looking and working the same at every level: activity, beneficiary, and visit.
19.5 Data and Audit Requirements (supersedes 18.8, second sentence)
No change to what is logged. Both the bulk Approve action and the new bulk Reject action log one entry per activity they resolve.
20. Revision 4: Overdue Visibility for Both Roles, Fixed Payment Auto-Selection, and Meeting Dependency
Back to Revision 3 (Section 19)
This section updates Sections 18.3, 18.6, and 18.7 (Timelines, Status Lifecycle, Business and System Logic) and adds handling for the monthly honorarium. Sections 1 through 19 are otherwise unaffected.
20.1 Summary of Changes
Area | What Changed |
|---|---|
Overdue status | Reintroduced as a non-blocking tag, now on both roles' dashboards. An item still awaiting that role's action past the 5th of the month is labeled Overdue there. Approve/Reject stay available regardless of the tag. |
Monthly Honorarium (#52) | Added to the verification screen for the first time, shown on both MT's and ANM's screens, pre-ticked by default. |
Mitanin Trainer's four activities | Unchanged from Section 8. Cluster meeting (#23), VHSNC meeting (#24), and both register-filling activities (#25, #40) stay on MT's screen, unticked, requiring her active decision. |
MT-to-ANM dependency | Reintroduced, scoped to all four of MT's activities. |
20.2 Overdue Tag, Both Roles (supersedes 18.3, 18.6)
Neither role is blocked by date. Mitanin Trainer: an item among her four not yet actioned past the 5th is tagged Overdue on her own dashboard. This is new; the Mitanin Trainer previously had no Overdue concept. ANM: an activity not yet actioned past the 5th is tagged Overdue on her dashboard, restoring what Revision 2 had removed.
20.3 Monthly Honorarium and Fixed Payment Handling (new)
Monthly Honorarium (S.No. 52, Rs. 2,200 per month) appears pre-ticked on both the Mitanin Trainer's and the ANM's screens, alongside each role's other unticked claimed incentives. It carries the same Approve/Reject mechanism as any other ticked item; being pre-ticked only sets its default state, a reviewer can still untick and reject it.
20.4 Mitanin Trainer's Four Activities (confirms Section 8, no change)
All four activities from Section 8, cluster meeting attendance, VHSNC meeting attendance, and both register-filling activities, remain on the Mitanin Trainer's screen as unticked items requiring her active decision. None of the four move into the auto-selected bucket described in 20.3.
20.5 Mitanin Trainer Activity Dependency (supersedes 18.2, for MT's four activities)
None of the Mitanin Trainer's four activities are actionable on the ANM's screen until the Mitanin Trainer has approved or rejected them individually; until then they either do not appear on the ANM's screen, or appear without a checkbox. Once the Mitanin Trainer acts on one, it appears on the ANM's screen as an unticked, actionable item, tagged Overdue already if the Mitanin Trainer's action happened past the 5th, per Section 20.2.
21. Revision 5: Mitanin-Side Resubmission Behavior During the Pilot
Back to Revision 4 (Section 20)
This section answers a gap left open since Revision 2: once resubmission after a rejection had no fixed time requirement, nothing defined what happens to a rejected activity that is corrected and resubmitted very late, or never. Sections 1 through 20 are otherwise unaffected. Tracked in FLW-1177.
21.1 Summary of Changes
Area | What Changed |
|---|---|
Why no fixed cutoff exists right now | The module is being piloted in Chhattisgarh. For its first 2 to 3 months, submission and review are deliberately kept flexible, with no fixed cutoff dates, so the program team can observe how Mitanins, Mitanin Trainers, and ANMs actually use the app before deciding on permanent cutoff dates and restrictions. This is a temporary pilot state, not a permanent design decision. |
Working boundary during the pilot | The calendar month itself is the boundary. A Mitanin can submit or resubmit at any time within a given month, and the Mitanin Trainer or ANM can approve or reject at any time within that same month. |
Mitanin Trainer rejection not corrected in time (updates Section 17's assumption, which no longer applies once Revision 2 removed the 24 hour resubmission window) | If a rejected activity is not corrected and approved again before the calendar month ends, that specific activity's claim becomes Mitanin Unclaimed for that month. It does not carry over into the next month. |
Scope of the Unclaimed outcome | Applies to the individual rejected activity only, not the Mitanin's whole month. Every other activity she claimed and had approved that month is unaffected and is counted for incentive as normal. |
21.2 Interim Rule for the Pilot Period (supplements 18.7, 20.2)
During the pilot, within a calendar month, a Mitanin can submit or resubmit a claim or a corrected activity at any time in that month, and the Mitanin Trainer or ANM can approve or reject at any time in that same month, consistent with Sections 18.7 and 20.2. If an activity is rejected and the Mitanin does not get it corrected and approved again before that calendar month ends, that activity's claim goes to Mitanin Unclaimed for that month; it is not carried forward or re-evaluated against a later month's submission window.
21.3 Mitanin Unclaimed at the Activity Level (supplements 13.1, for the pilot period)
Because review now happens at the activity level (Revision 2 onward), the Mitanin Unclaimed outcome in 21.2 applies per activity, not per whole claim. If one activity misses the calendar month cutoff, only that activity is Unclaimed for the month. Every other activity the Mitanin claimed and had approved that month is unaffected, and is counted toward that month's incentive as normal.
21.4 What Still Needs Confirming
Whether the existing Mitanin Unclaimed status derivation, previously tied to the ANM's 5th of month due date, still correctly transitions a single rejected-and-uncorrected activity to Unclaimed at calendar month end under the current activity level, time unbound review model, without affecting the rest of that month's approved activities. If that logic no longer exists or is still tied to the removed due date, it needs to be rebuilt against calendar month end instead. Tracked in FLW-1177.