Branch-First + Bulk Actions
Click a branch → see all its settings in tabs. Select multiple branches from the table → apply a setting to all selected. The approach we've already prototyped.
Strengths
- Simple mental model — “click branch, see everything”
- Already prototyped with working code
- Each branch is self-contained and clear
Weaknesses
- Bulk editing feels bolted on (checkbox → pick setting)
- Hard to compare settings across branches at a glance
- 50+ branches means lots of scrolling
Select branches from table → pick setting → configure → apply to all selected
Settings Matrix
Start from the setting, not the branch. See one setting across ALL branches in a comparison table. Spot differences at a glance and edit in-place or in bulk.
Strengths
- See differences across branches instantly
- Bulk editing is native to the UI
- Great for compliance auditing across locations
Weaknesses
- Loses the “complete view of one branch”
- Complex settings don't fit table cells well
- New mental model for existing users
Filter branches by group → “Edit All Visible” → configure once → applies to filtered set
Configuration Templates
Create named templates (“Ireland Standard”, “US NYC Compliance”). Assign to branches with one click. Track deviations from the template.
Strengths
- Bulk application is the primary flow
- Scales to 100+ branches naturally
- Deviation tracking shows exactly what differs
Weaknesses
- “Templates” is a new concept to learn
- Adds a layer of indirection
- Edge case: branch needs mix of two templates
Create template → select branches → assign → all branches get the full config in one action
These aren't mutually exclusive
A hybrid is possible: A + B (branch-first as default, with a matrix view toggle for comparison). Or A + C (branch-first for day-to-day, templates for onboarding new locations). The question for the team: which mental model should be primary?