Dealer_Onboarding_Backend/docs/Offboarding_Requirement_Tracking_Matrix.md

Offboarding Requirement Tracking Matrix

Date: 2026-04-17
Baseline SRS: backend/docs/Re_New_Dealer_Onboard_TWO.md
Detailed analysis reference: backend/docs/Offboarding_Requirements_Implementation_Gap_Report.md

Status Legend

• Done = Implemented and aligned in both frontend/backend for core behavior.
• Partial = Implemented in parts, but missing standardization or edge-case handling.
• Missing = Not implemented or not yet aligned to SRS intent.

Tracking Matrix

Module	Requirement (SRS intent)	Current Implementation	Gap / Missing	Priority	Status
Resignation	Multi-stage review with role-based actions (Approve, Send Back, Revoke)	Core workflow and role visibility are implemented; legal/final flow integrated with F&F trigger path	Need cross-module send-back contract parity and common rollback behavior	High	Partial
Resignation	Send Back/Revoke must use Work Notes with mandatory remarks	Pattern exists and is used in module logic/UI communication	Need strict shared validation/payload consistency with other modules	High	Partial
Resignation	Dealer withdrawal only until NBH pending	Rule has been incorporated in behavior references and workflow handling	Validate all edge transitions and UI disable states for all roles	Medium	Partial
Termination	Workflow from initiation through NBH, CEO/CCO, Legal closure	Termination module backend now exists with stage progression, SCN, finalize APIs, and improved timeline rendering	Send-back paths not fully hardened/standardized across all stage transitions	Critical	Partial
Termination	NBH decisions (Go Ahead, Hold, Raise Query) and final (Approve, Reconsider, Reject)	Final decision endpoint and stage transitions are implemented	Need strict mapping and regression tests for all decision + rollback combinations	High	Partial
Termination	F&F trigger with LWD governance	Termination closure path supports handoff	LWD-gated trigger must be verified consistently in all finalization flows	High	Partial
Constitutional Change	Scenario-based constitution request with mandatory docs	Core request flow and checklist behavior are present	Need continuous validation for all constitution permutations and role-specific document constraints	Medium	Partial
Constitutional Change	Joint approval at ZM+RBM stage	Joint approval policy + backend logic + UI states implemented	On send-back to joint stage, approval metadata reset behavior must be explicit and deterministic	High	Partial
Constitutional Change	Work Notes + mandatory remarks for Send Back/Revoke	Supported by module patterns	Needs strict standardized contract parity with termination/resignation/relocation	High	Partial
Relocation	Role-based review with Approve, Send Back, Revoke	Core relocation flow exists with document tracking	Need validation that send-back/revoke use same strict contract and rollback semantics as other modules	High	Partial
Relocation	Work Notes/Audit traceability for reviewer actions	Logging and review traces are present	Ensure payload consistency and required fields are enforced centrally	Medium	Partial
F&F Settlement	Department-wise claims and finance validation separation	Ownership layering and reconciliation enhancements are implemented; finance draft seeding added	Add explicit final-summary label: "Final settlement uses Finance Validated values"	Medium	Partial
F&F Settlement	Finance actions (Approve, Request Clarification, Reject) with checklist	Settlement actions and finance flows are available	Expand UX cues and verify checklist gating across all entry paths	Medium	Partial
F&F Settlement	Work Notes as communication + audit trail	Implemented pattern available	Harmonize phrasing/contract with offboarding send-back communication model	Medium	Partial
Cross-module	Consistent role resolution (role/roleCode) and route visibility	Multiple fixes already implemented in sidebar/app/guard and module screens	Need full sweep to ensure no remaining module-level mismatches	Medium	Partial
Cross-module	Unified send-back contract and deterministic previous-stage routing	Implemented in module-specific ways, not yet unified	Build shared standard for action contract, remarks validation, rollback resolver, and audit payload	Critical	Missing
Cross-module	Module-level regression test coverage for approve/send-back/revoke	Manual and iterative fixes done	Add automated regression scenarios for each module and stage	High	Missing

---

Immediate Action Queue

1. Standardize send-back contract in backend (action, mandatory remarks, role check, previous-stage resolver, audit/work-note payload).
2. Apply the standard first to Termination (highest risk), then align Resignation, Constitutional, Relocation.
3. Add constitutional send-back reset for joint-approval metadata at ZM+RBM stage.
4. Close remaining F&F UX consistency items and run end-to-end role-based verification.