The Conflict Challenge for UK Solicitors
Conflict of interest is one of the most common SRA compliance issues. Miss a conflict and you face potential intervention, insurance claims, and reputational damage.
Manual conflict checks are slow and error-prone. Names get misspelled. Records are incomplete. Checks happen late in the process.
Automation addresses these failures - but must be built on solid SRA compliance foundations.
SRA Conflict Rules
Code of Conduct Paragraph 6.1
You must not act if there is a conflict of interest or significant risk of conflict, except in limited circumstances with informed consent.
Code of Conduct Paragraph 6.2
You must not act where:
- Your own interests conflict with client interests, OR
- Duty to one client conflicts with duty to another current/former client
Types of Conflict
Own interest conflict: Your financial, personal, or other interests conflict with client interests.
Client conflict: Duty to one client conflicts with duty to another.
Former client conflict: Confidential information from former client could be used against them.
What Conflict Automation Must Do
1. Comprehensive Search
Search must cover:
- Current clients (all matters, all offices)
- Former clients (all matters, retention period)
- Prospective clients (consultations that did not convert)
- Related parties (witnesses, experts, other side)
- Connected companies (subsidiaries, parent companies)
2. Intelligent Matching
Names are not unique. Matching must handle:
- Spelling variations (Smyth/Smith)
- Nicknames (William/Bill)
- Company name variations (Ltd/Limited, plc variations)
- Trading names vs. registered names
- Historic names (maiden names, company name changes)
3. Relationship Mapping
Conflict is not just about names. It is about relationships:
- Corporate group structures
- Key individuals at companies
- Professional advisers
- Family relationships (where known)
4. Matter Context
Same parties may be clients on some matters and adverse on others. System must capture:
- Role in each matter (client, other side, witness)
- Matter type and subject
- Time period
Building the Conflict System
Data Requirements
For every matter, capture:
- Client identity (company, individual)
- Key contacts at client
- Related parties and their roles
- Other side parties
- Subject matter description
- Date range
For individuals:
- Full name
- Known aliases
- Date of birth (where appropriate)
- Company associations
For companies:
- Full registered name
- Trading names
- Registration number
- Group structure
Search Process
Step 1: New matter intake
Collect all relevant names:
- Proposed client
- Key individuals
- Known other parties
- Subject matter keywords
Step 2: Automated search
Run against full database:
- Exact match
- Fuzzy match (configurable sensitivity)
- Phonetic match (Soundex)
- Alias match
Step 3: Results triage
Classify results:
- Clear conflict (definite match, adverse role)
- Potential conflict (needs human review)
- Related but clear (same client, related matter)
- No conflict
Step 4: Human review
Solicitor reviews flagged items:
- Is this actually a conflict?
- Is conflict waivable?
- What conditions apply?
Step 5: Decision and documentation
Record:
- Conflict check completion
- Items reviewed
- Decision made
- Waiver obtained (if applicable)
- Who made decision
SRA-Specific Requirements
Paragraph 6.2 Safeguards
Where you act despite potential conflict (with consent), you must have:
- Effective safeguards
- Informed written consent from all clients
Automation can help: Generate consent documents, track consent status, prevent matter work until consent recorded.
Information Barriers
Where conflicts are managed through barriers:
- Physical separation of teams
- IT access restrictions
- Clear protocols on information sharing
Automation role: Enforce access controls. Alert if barrier potentially breached.
COLP Oversight
The Compliance Officer for Legal Practice oversees conflict systems.
Automation role: Provide COLP with oversight dashboards, exception reports, audit trails.
Integration Points
With Practice Management
- Matter opening blocked until conflict check complete
- Conflict status visible on matter dashboard
- Alerts if related matter opened with potential conflict
With Client Onboarding
- Conflict check part of onboarding workflow
- ID verification data feeds conflict system
- Company house data for group structures
With Document Management
- Conflict information stored with matter
- Audit trail of checks and decisions
- Easy retrieval for SRA enquiries
Measuring System Effectiveness
Coverage Metrics
- Matters with completed conflict check: 100%
- Check completion before substantive work: 100%
- Data completeness (all required fields): 95%+
Quality Metrics
- False positives (flagged but not conflicts): Track and tune
- Missed conflicts (found later): Target zero
- Search time per matter
Compliance Metrics
- Waivers documented where required: 100%
- Information barriers in place where needed: 100%
- COLP review of exceptions: Per policy
Common System Failures
Failure 1: Incomplete Data
Historical matters not in system. New clients not fully captured.
Fix: Data migration project for historic matters. Mandatory fields for new entries.
Failure 2: Name Matching Too Strict
"Robert Smith" does not match "Bob Smith" or "R Smith."
Fix: Fuzzy matching, nickname database, phonetic matching.
Failure 3: No Corporate Linkage
Client is subsidiary. Parent company is adverse in separate matter.
Fix: Maintain corporate group data. Match against entire group.
Failure 4: Over-Reliance on System
System says "no conflict" so no further thought.
Fix: System provides information. Solicitor makes decision. Train on using results, not just accepting them.
Failure 5: No Prospective Client Tracking
Consultation did not convert. Information not captured.
Fix: Capture prospective client details even if matter not opened.
The Conflict Check Workflow
Day 0: Enquiry received
- Initial names captured
- Quick search against active matters
- Obvious conflicts identified early
Day 1-2: Full intake
- Complete party information gathered
- Comprehensive search run
- Results reviewed and classified
Day 2-3: Decision
- Conflicts addressed (decline, waiver, barriers)
- Decision documented
- Matter cleared to proceed
Ongoing: Monitoring
- New parties added to matter trigger re-check
- Alerts if potentially conflicting matters opened
- Periodic audit of conflict system integrity
The Bottom Line
Conflict management is fundamental to SRA compliance. Manual systems fail too often.
Automation makes conflict checks faster, more comprehensive, and better documented. But it does not replace solicitor judgment - it supports it.
Build a system that captures complete data, searches intelligently, and creates the audit trail the SRA expects.
Conflict failures are preventable. Proper systems prevent them.
Further reading: Take our free Digitalization Check to find out how digital your firm really is. Read our comprehensive Digital Law Firm 2026 Guide or the Law Firm Software Comparison.