You're evaluating compliance software for a regional bank with 47 branches. The vendor shows you a dashboard: 94% policy attestation, 312 monitoring reviews completed, 18 open issues. You ask which branches account for the missing 6%. The demo stalls.
That gap might be concentrated in two recently acquired locations still running the seller's procedures. Or it might be spread across branches where staff turnover is high. The institution-level number doesn't tell you, and if the software can't either, you're flying blind.
The Decision You're Facing
Do you configure your compliance platform to track and report at the branch level, or do you accept institution-wide aggregates and manage location-specific gaps through manual tracking?
This isn't about technology preference. It's about whether your compliance management system can produce the evidence an examiner will ask for when a violation surfaces at a specific location on a specific date.
The FDIC reported 1,155 consumer compliance violations in 2025, with 40% related to Truth in Lending and Regulation Z. These are transaction-level failures that happen where accounts open and loans close. In a branch network, that means they happen at locations your compliance function doesn't sit in.
Key Factors That Affect Your Choice
Network complexity: Count branches, states, and charters. If you operate under multiple state banking codes or recently completed an acquisition, location-level attribution becomes essential. The acquired branches arrive with a second policy set, different training records, and often a separate core system.
Sampling methodology: Volume-weighted samples systematically under-cover small and recently acquired locations. If your monitoring plan doesn't allocate coverage by location over a rolling period, you'll discover gaps only when an examiner points them out.
Supervisory expectations: The FDIC describes a compliance management system as board and management oversight combined with a consumer compliance program covering policies, training, monitoring, and complaint response. Independent audit provides assurance through risk-based review. Every software capability should trace to one of those elements, and every element should be testable at branch level.
Escalation paths: The FDIC recorded a 48% increase in complaints involving non-bank service providers, reaching 6,356 cases. If an issue originates at a branch involving a third-party vendor, your system needs to capture the source location, track local resolution attempts, and escalate when thresholds are breached.
Path A: Branch-Level Attribution on Every Record
Choose this path if you operate across multiple states, have completed acquisitions in the past three years, or face examination findings that reference specific locations.
Your platform must answer six questions with evidence, not percentages:
Policy attestation: Which locations have acknowledgment gaps, and for how long? The system produces attestation records by person, location, and policy version. When an examiner asks what procedure was in force at Branch 12 in April, you provide a timestamped record.
Monitoring coverage: How was the sample distributed across locations? The platform maintains a sampling frame that shows coverage by location over a rolling 12 or 24 months and flags locations whose coverage has lapsed.
Issue management: Which issues were closed locally without escalation? Each issue record captures the originating location, assigned owner, and escalation path. You can trace a disclosure failure from the branch where it occurred into board-level reporting.
Training completion: Which roles at which locations are overdue? Assignment and completion records are maintained by role and location, so you know which branches have gaps in specific training modules.
Risk assessment: How does branch profile change the residual rating? The assessment documents location-level factors including product mix, staff tenure, transaction volume, and state-specific requirements.
Complaint intake: Which channel and location did complaints arrive through? The record includes source location and resolution timing, so you can identify patterns by branch or region.
This path requires vendor configuration at implementation. Ask candidates to set up two locations, one large and one recently acquired, and run the same queries against both. Request the report the system produces when a location falls out of compliance. Enter an issue at one branch, escalate it, and follow it into executive reporting.
Path B: Institution-Wide Aggregates with Manual Tracking
Choose this path if you operate a small number of branches under a single charter in one state, and your monitoring plan already allocates samples by location through spreadsheets or other manual controls.
You'll accept institution-level dashboards and maintain branch-specific evidence outside the platform. This works when the compliance team is small enough to know which locations carry higher risk and where recent gaps have surfaced.
The tradeoff: you're building manual reconciliation into every examination cycle. When an examiner asks about a specific location, you'll pull records from multiple systems and reconstruct the timeline. If you acquire another institution or expand across state lines, you'll need to revisit this decision.
Path C: Hybrid Approach with Jurisdictional Overlay
Choose this path if you operate in multiple states but most branches follow identical procedures, with variation only where state law requires it.
Your platform tracks location as an attribute but doesn't require separate workflows for every branch. Policies carry effective dates and jurisdiction tags. When a state-specific requirement applies, the system flags affected locations and routes attestation or monitoring tasks accordingly.
This path works for banks that have standardized operations but need to manage exceptions for states with unique disclosure rules, interest rate caps, or licensing requirements. You're not managing 47 separate compliance programs; you're managing one program with documented state-level variations.
Summary Matrix
| Factor | Branch-Level Attribution | Institution Aggregates | Jurisdictional Overlay |
|---|---|---|---|
| Network size | Multi-state, multiple charters | Single state, <10 branches | Multi-state, standardized ops |
| Recent M&A | Yes, within 3 years | No | Depends on integration status |
| Sampling method | Location-allocated | Volume-weighted acceptable | Hybrid with state filters |
| Evidence requirement | Timestamped by location | Manual reconciliation | Automated for state rules |
| Examination risk | High if gaps are concentrated | Low if network is homogeneous | Moderate, state-specific |
The question isn't whether your software can track branches. It's whether the way it tracks them lets you answer an examiner's question about a specific location on a specific date without reconstructing evidence from three systems and a spreadsheet.
If you can't answer that question in the demo, you won't be able to answer it in the examination room.
