# District Guide (IDSA)

Version: 2026-02-04

This file is a DOCX source for offline generation. Do not generate DOCX at runtime.

## 1) District role in IDSA hierarchy

District is an oversight layer focused on:

- routing correctness
- compliance and approval discipline
- monitoring and evidence-first escalation

District coordinates with Branch Office and Admin to correct problems via approved workflows.

## 2) Routing: post_office_code and branch assignment rules (high priority)

Key terms:

- `branch_office_id`: servicing branch for operations and reporting
- `post_office_code`: routing granularity and coverage mapping

Rules:

1) Active CSC requires `post_office_code` (mandatory).
2) Branch assignment must match servicing branch for the CSC area.
3) If one Partner has CSCs mapped to multiple branches, treat as a risk and escalate.

## 3) Approval oversight: ensure Partner/CSC compliance

Partner oversight:

- identity and contact verification (as per policy)
- mapping to intended operational area

CSC oversight:

- routing completeness (`post_office_code`, branch assignment)
- operator details and shop details present

## 4) Reporting: what to monitor weekly

Weekly checks:

- new partners and CSCs: routing completeness
- recurring routing issues (missing or inconsistent `post_office_code`)
- status mismatch trends
- commission backlog patterns

## 5) Audits: reading JSON sections

Run:

- `C:\\xampp\\php\\php.exe scripts\\audit_branch_partner_csc.php`

Interpret:

- `summary.counts`: totals per issue group
- `orphaned_*`: missing/invalid links
- `status_mismatches`: status consistency
- `commission_issues`: missing mapping and aged pending items
- `routing_issues`: missing/inconsistent routing; derived routing may be used when schema fields are absent

## 6) Do/Don't + escalation

Do:

- standardize checklists and enforce routing discipline
- store audit outputs as evidence artifacts
- escalate with a complete, minimal evidence bundle

Don't:

- do not perform/request DB edits
- do not bypass workflow gates due to urgency
- do not accept disputes without `booking_reference`

Escalation checklist:

- timestamp
- partner_id / csc_id / booking_reference
- screenshots
- audit JSON and sample rows