Two related changes that flow together: introduce configurable cut-off windows per state variant, and update the Monthly ASHA Status derivation engine to read those cut-offs. Together they replace the old generic cut-off treatment and the fixed 2-day delay rule (§7, §10.2, §11). 

1. Configurable cut-off dates per state variant

• Add two configurable cut-off windows per state variant, editable by the program admin team without a code change: (a) ASHA submission and re-submission window. (b) Verification deadline for ASHA Supervisor, CHO, and ANM. 

• The cut-off applies to every Supervisor (and the downstream CHO/ANM) mapped to that variant. 

• Seed defaults at first rollout:  

• Utprerona (Assam): ASHA submission 1st–12th of every month; verification by the 12th. 

• Mitanin (Chhattisgarh): ASHA submission 1st–3rd of every month; verification by the 5th. 

• Provide an admin configuration surface to view and edit the two windows per variant. 

1. Monthly ASHA Status derivation engine changes

• Add a new derived state called "Unclaimed". An ASHA's monthly status is Unclaimed when the ASHA has not submitted any incentive claim for the selected month by the end of the submission window read from the cut-off config. This drives the new "ASHA Unclaimed" tile and the U chip on the drill-down screen (Ticket 1). 

• Change how "Overdue" is derived:  

• Old rule: a claim was Overdue once it had been Pending with Supervisor for more than 2 days. 

• New rule: a claim is Overdue once the configured verification cut-off date for the active state has passed and the claim is still Pending with the verifying actor (Supervisor, CHO, or ANM). Overdue is no longer a fixed day-count. 

• All other derived states stay unchanged: Pending with Supervisor, Partially Verified, Verified by Supervisor, Pending with CHO/ANM, Verification Completed. 

• The status engine must recompute automatically on every activity transition and whenever a cut-off date elapses. The updated status must surface across the Supervisor Dashboard tiles, drill-down ASHA rows, ASHA Monthly Detail header, and the ASHA app. 

1. Otherbehavioursthat now read the cut-off config (replacing earlier hardcoded rules) 

• Auto-routing of Pending-with-Supervisor claims to the CHO/ANM dashboard is triggered once the configured Supervisor verification cut-off has passed (instead of the old 2-day rule). 

• The Supervisor Dashboard month selector must respect the cut-off config and disable months outside the allowed window. 

• All notification timings that depend on these windows (ASHA submission reminders, Supervisor / CHO / ANM verification reminders, Medical Officer escalation) are owned by Ticket 4 (Notifications). 

Affected modules: Configuration service; Admin tooling; Monthly ASHA status derivation engine; Activity workflow service (Overdue derivation, auto-routing trigger); consumers of monthly status (Dashboard API, drill-down API, ASHA Monthly Detail API, ASHA app status view); Supervisor Dashboard (month selector availability).