Instructed by Nera Capital · Prepared for Barings Law
Getting Started
Wolf AI Labs has been instructed by Nera Capital to onboard Barings Law onto the ClaimPassports platform. This report sets out how the platform works and what Barings Law needs to provide to get started.
Prepared by
Wolf AI Labs
ClaimPassports · Matt, CEO
ClaimPassports Recipient
Barings Law
Borrowing Client: Barings Law
Discover.
Understand.
Build.
OCC asking
Answers auto-save
0 / 25 answered
Part One · Wolf AI Labs to Barings Law
How Do You Currently Operate?
A complete set of questions for Barings Law to work through and respond to. Wolf AI Labs will use these responses to configure ClaimPassports for Barings Law. All answers save automatically. One button sends everything directly to OCC when complete.
STAGE A
Lead Generation and First Contact
Q1 · Lead Sources
Where does your client volume come from? Social media, paid advertising, lead generators, referrals, or a mix? Which channels produce the most volume right now?
Tap to expand and answer
Why we ask thisClaimPassports can connect directly to lead generation sources and auto-ingest records at point of capture. Knowing your lead sources tells us where the intake pipeline starts and whether we can eliminate the manual transfer step entirely.
Barings Law's answer Saved
Q2 · Lead Quality and Screening
When a lead comes in, is there any initial screening or qualification before it becomes a live client record? Who does that screening and what does it involve?
Tap to expand and answer
Why we ask thisIf there is a manual screening step between lead capture and file creation, that is a candidate for automation. We need to understand the screening logic so ClaimPassports can replicate or replace it.
Barings Law's answer Saved
Q3 · First Client Contact
Who makes first contact with a new client and through what channel? Is that a telesales team, a lead gen team, an automated message, or something else?
Tap to expand and answer
Why we ask thisFirst contact handling is a key handoff point in the intake process. We need to know whether first contact is human-led, automated, or a combination, and what information is captured at that stage.
Barings Law's answer Saved
Q4 · Client Data Capture at Intake
What information do you collect from a client at the point of first contact? Name, address, vehicle details, finance agreement details? How is it captured and by whom?
Tap to expand and answer
Why we ask thisThe completeness of data at intake directly affects how quickly ClaimPassports can score and process a claim. Knowing exactly what is captured at first contact tells us what the validation layer needs to check for.
Barings Law's answer Saved
STAGE B
File Opening and CRM
Q5 · File Opening Process
How does a new client go from lead to open file? What steps does that involve, how long does it typically take, and which team members are involved?
Tap to expand and answer
Why we ask thisFile opening is often where the first significant delays occur. Understanding the steps and time involved tells us how much ClaimPassports can compress this stage through automated intake and instant validation.
Barings Law's answer Saved
Q6 · CRM and Case Management
What system or software does your team use to record and manage client files and claims? Is that a single system, or multiple systems used by different teams?
Tap to expand and answer
Why we ask thisWe need to know the current technology stack before we architect the ClaimPassports integration. If multiple systems exist, ClaimPassports needs to consolidate that into a single view rather than add another layer.
Barings Law's answer Saved
Q7 · Data Completeness and Record Quality
Across your existing 1.5 million client records, how complete is the data on average? Are there known gaps, and if so, what are they typically missing?
Tap to expand and answer
Why we ask thisClaimPassports has a validation layer that identifies missing fields at record level. We need to understand the known gaps in the existing book so the validation rules are calibrated to your data reality, not a theoretical perfect record.
Barings Law's answer Saved
Q8 · Volume and Team Size
How many new client records are being opened per day or per week right now, and how many staff are involved in processing across all roles?
Tap to expand and answer
Why we ask thisCurrent volume and headcount tells us the baseline throughput we are building from. We need to size the Barings Law instance correctly from day one against both current volume and the anticipated surge under PS26/3.
Barings Law's answer Saved
STAGE C
Claim Eligibility and Assessment
Q9 · Eligibility Checking
How do you currently determine whether a client has a viable claim? Is there a defined checklist, a solicitor review, an automated check, or a combination?
Tap to expand and answer
Why we ask thisEligibility assessment is one of the highest-value steps ClaimPassports automates through its ESP scoring engine. Understanding how you currently do this tells us what logic the scoring model needs to replicate and where it can go further than your current manual process.
Barings Law's answer Saved
Q10 · Claim Strength Prioritisation
Once a claim is assessed as eligible, do you currently rank or prioritise claims in any way? Or does every claim move forward at the same pace regardless of expected value?
Tap to expand and answer
Why we ask thisClaimPassports produces a Passport Intelligence Score for every claim combining strength and expected return. If all claims currently move at the same pace, introducing scoring will immediately change how the team allocates effort and which claims move fastest.
Barings Law's answer Saved
Q11 · Rejected or Ineligible Claims
What happens when a client is assessed as ineligible? Is there a defined process for communicating that, and what does the client communication look like?
Tap to expand and answer
Why we ask thisClaimPassports flags ineligible records at the scoring stage and can generate standardised client communications automatically. We need to understand the current rejection workflow so the automated output matches your regulatory obligations and communication standards.
Barings Law's answer Saved
STAGE D
Claim Processing and Lender Submission
Q12 · Document Production
How are letters of authority, complaint letters, and claim submission documents currently produced? Is that a template system, manual drafting, or something else?
Tap to expand and answer
Why we ask thisDocument generation is one of the highest-volume manual tasks ClaimPassports removes. We need to see exactly what documents Barings Law produces, in what format, and to which lenders, so the generation engine produces output that matches your existing standards without any manual rework.
Barings Law's answer Saved
Q13 · Lender Submission Process
How are claims submitted to lenders? Post, email, online portal, or a mix depending on the lender? Which lenders account for the majority of your current motor finance book?
Tap to expand and answer
Why we ask thisClaimPassports manages lender submission as part of the claim output. Knowing submission channels and the lender mix tells us which submission formats to build into the platform and where bulk submission will replace the highest volume of manual work.
Barings Law's answer Saved
Q14 · Submission Tracking
Once a claim is submitted to a lender, how do you track its status? Logged in your CRM, tracked manually, or monitored through a separate system?
Tap to expand and answer
Why we ask thisPost-submission tracking is a significant source of manual overhead at volume. ClaimPassports monitors submission status and flags response timeframes automatically. Understanding your current tracking method tells us what the platform replaces.
Barings Law's answer Saved
STAGE E
Lender Responses
Q15 · Handling Lender Responses
When a lender responds to a claim, who receives it, how is it logged, and what happens next? Walk us through what a typical lender response looks like in your operation today.
Tap to expand and answer
Why we ask thisLender response handling is the most operationally variable stage in the claim lifecycle. ClaimPassports can receive, categorise, and route responses automatically. We need to understand your current response workflow in detail to configure the routing logic correctly for every response type.
Barings Law's answer Saved
Q16 · Accepting or Declining Offers
When a lender makes a redress offer, who decides whether to accept, negotiate, or decline? Is that a solicitor decision, a team leader decision, or does it go to the client immediately?
Tap to expand and answer
Why we ask thisOffer assessment sits at the intersection of legal judgment and commercial decision-making. ClaimPassports flags offers against the expected return score for each claim. We need to understand who currently owns this decision so we configure the right alert and escalation logic.
Barings Law's answer Saved
Q17 · Rejected or Disputed Lender Responses
When you reject a lender offer or dispute a lender decision, what does that process look like? Who handles it and what documentation is produced?
Tap to expand and answer
Why we ask thisRejected offer handling is one of the most document-intensive steps in the claim lifecycle. ClaimPassports can automate the generation of dispute letters and escalation documents. We need to know what those documents look like in the Barings Law context.
Barings Law's answer Saved
STAGE F
Client Communication Throughout
Q18 · Client Updates and Progress
How do you keep clients informed throughout the life of their claim? Automated updates, outbound calls, client-initiated contact, or a combination?
Tap to expand and answer
Why we ask thisClient communication is one of the highest-volume operational tasks at scale. ClaimPassports can automate status updates at every stage of the claim journey. Understanding your current model tells us what automated touchpoints to build and where human contact remains essential.
Barings Law's answer Saved
Q19 · Chasing Clients for Documents or Information
When you need something from a client, how is that request made? Post, email, SMS, phone call? Who handles the chasing and how many times is a client typically contacted?
Tap to expand and answer
Why we ask thisClient chasing is typically the single biggest source of manual overhead in a high-volume claims operation. ClaimPassports automates outbound client requests and tracks response rates. We need to know your current chasing volume and channels to configure the automation correctly.
Barings Law's answer Saved
Q20 · Inbound Client Queries
How do clients contact Barings Law with questions or to check on their claim? Who handles inbound client contact and how is it logged?
Tap to expand and answer
Why we ask thisInbound query volume scales directly with claim volume. At 1.5 million claimants, unmanaged inbound contact creates significant overhead. ClaimPassports reduces inbound query volume by keeping clients informed automatically. We need to understand your current inbound load to size the impact correctly.
Barings Law's answer Saved
Q21 · Who Handles Client Contact
Is client communication handled by your legal or operations team, or by a separate telesales or lead gen team? Is there a clear handoff point between who communicates with a client at different stages?
Tap to expand and answer
Why we ask thisUnderstanding who owns client communication at each stage is critical to configuring ClaimPassports correctly. If different teams own different communication stages, the platform needs to route automated messages from the right sender and flag exceptions to the right team.
Barings Law's answer Saved
STAGE G
FOS Referral and Litigation
Q22 · FOS Referral Decision
At what point do you decide to refer a claim to the Financial Ombudsman Service? Who makes that decision and what does the referral process currently look like operationally?
Tap to expand and answer
Why we ask thisFOS referral is a one-way, binding decision. Once a claim is referred to FOS, the firm accepts the FOS determination as final. It is therefore a track chosen in place of litigation, not a step before it. ClaimPassports needs to identify FOS-track cases early so the correct case file and correspondence trail is built before referral. FOS integration is a native capability and will be high-volume under PS26/3.
Barings Law's answer Saved
Q23 · FOS Submission Documents
What documents are currently produced for a FOS submission? How are those prepared and who prepares them?
Tap to expand and answer
Why we ask thisClaimPassports generates FOS-ready documentation automatically as part of the claim output. Knowing what Barings Law currently produces for FOS submissions tells us exactly what the document generation engine needs to replicate and what format the output should take.
Barings Law's answer Saved
Q24 · Litigation Track
For claims that do not go to FOS, at what point does Barings Law decide to pursue litigation directly? Who makes that decision, what criteria trigger it, and what does the operational process look like when a case goes to court?
Tap to expand and answer
Why we ask thisLitigation and FOS are separate, parallel tracks, not sequential steps. Once a claim is referred to FOS, the FOS determination is binding and the case cannot subsequently be taken to court. Litigation is therefore a route chosen instead of FOS at the point of escalation. ClaimPassports needs to identify which track each claim is on early so the correct document set and case file structure is built from the outset. A litigation-track case requires a different data structure and export format.
Barings Law's answer Saved
Q25 · Bottlenecks Across the Full Process
Looking at the full journey from lead to settlement, where are the three or four points where your operation slows down or creates the most manual work for your team right now?
Tap to expand and answer
Why we ask thisThis is the most important question we ask. The answer tells us where ClaimPassports needs to deliver the most value for Barings Law from day one. Every bottleneck you identify becomes a configuration priority in the bespoke build.
Barings Law's answer Saved
Barings Law responses sent directly and securely to Wolf AI Labs
Barings Law responding
Tap for the answer
Part Two · How ClaimPassports Works
How Does ClaimPassports Work?
How ClaimPassports works for Barings Law as the claims solicitor firm being onboarded to ClaimPassports by Wolf AI Labs. Tap each question to read the answer.
Consumer Claim Passport Platform
What does a backend client account look like within the platform?
Tap for the answer
Every client onboarded to ClaimPassports receives their own dedicated AI account.
ImportantThe Consumer Claim Passport platform is a stand-alone, separate platform that does not require integration with any other platforms. If you do have a case management system, we will review and configure ClaimPassports to work alongside it. If you do not have one, ClaimPassports becomes your primary system. The technical requirement on your side is providing client data in an agreed format. We handle everything else.
This is not a case file. It is a fully functional client account within the platform, accessed and managed by the Barings Law back office team. Each account contains a structured suite of tools, all configured and templated to Barings Law's operational style.
01
Credit Files — Full credit file access and management within the client account.
02
Open Banking — Direct open banking integration within the account for transaction visibility and verification.
03
eSign Documentation — Template-driven eSign document generation, structured and pre-configured to Barings Law's operational requirements.
04
Additional Tools — A full suite of further back office functions, all templated and configured to suit Barings Law's workflow and operational style.
White Label
The entire platform can be white labelled to Barings Law's branding, colours, and identity. Every screen, document template, and client-facing output carries the Barings Law brand, not Wolf AI Labs'.
Intake
What actually happens when a client record enters the platform?
Tap for the answer
The moment a record enters ClaimPassports it is automatically validated against our required data fields. Any gaps are flagged immediately with specific missing fields listed, so your team knows exactly what to chase. Records that pass validation move straight to claim assessment with no human needed to route them.
Claim Assessment
How does the platform assess whether a claim is strong or weak?
Tap for the answer
ClaimPassports runs each claim through our ESP and EPR scoring engines. ESP assesses claim strength based on the financial product, the lender, and the commission structure. EPR assesses expected return. Together they produce a Passport Intelligence Score for each client. Your team sees a scored, ranked claim book rather than a flat list of files.
ClaimPassports · Claim Journey
1
Automatic
Client Record Enters
Zero-touch intake. Data captured and ingested automatically.
No staff needed
2
Automatic
Validation Layer
Record checked against required fields. Gaps flagged with specific items listed.
No staff needed
3
Automatic
ESP / EPR Scoring
Claim strength and expected return calculated. Passport Intelligence Score produced.
No staff needed
4
Automatic
Document Generation
Letters of authority, FOS submissions, and claim documents generated automatically.
No staff needed
5
Your Team
Exception Handling
Staff review only flagged records and exception cases. Not every file.
Staff review
→
Output
FOS-Ready Claim
Scored, documented, and ready for submission at bulk volume.
Bulk processing live
FOS Integration
We submit large volumes to FOS. Does the platform handle that?
Tap for the answer
Yes. FOS integration is a native capability. The platform generates FOS-ready documentation as part of the standard claim output. Bulk submission workflows are built in. For a firm with 1.5 million motor finance claimants this is one of the highest-impact areas where the platform removes manual overhead.
Integration
What do we need to do technically to get this connected to our existing systems?
Tap for the answer
The Consumer Claim Passport platform is a stand-alone, separate platform that does not require integration with any other platforms. If you do have a case management system, we will review and configure ClaimPassports to work alongside it. If you do not have one, ClaimPassports becomes your primary system. The technical requirement on your side is providing client data in an agreed format. We handle everything else.
Scale
Can the platform handle our full client book, not just the first tranche?
Tap for the answer
Yes. The platform is currently running at 1.4 million claims per month and growing at 7% per month. The 100,000 client opening tranche is a starting point, not a ceiling. The platform scales to your full book of 1.5 million motor finance claimants and beyond as your other claim types grow.
Barings Law responding
Part Three · Barings Law Team
What Does My Team Need to Do?
A clear picture of what the Barings Law team needs to do and what ClaimPassports handles automatically on their behalf.
The core shift for Barings Law: your team stops processing every record and starts managing the process. ClaimPassports handles the volume. Your team handles the judgment calls.
What the Barings Law Team Currently Does
What ClaimPassports Handles Automatically
Manually enters or checks new client records
Platform ingests records automatically. Team only reviews flagged exceptions.
Chases missing client information across every file
Platform flags specific missing fields per record. Team chases targeted items only.
Manually produces letters of authority and claim documents
Documents generated automatically. No manual drafting.
Decides which claims to prioritise from a flat list
Platform scores every claim. Team works from a ranked list showing strength and expected return.
Manually prepares FOS submissions
FOS-ready documents produced automatically. Bulk submission workflows built in.
Reviews all claims at every stage
Reviews exception cases only. Strong, clean claims move through without manual intervention.
Training
What training does my team need before they can use this?
Tap for the answer
We run a 90-minute platform walkthrough with your operations team at week 7 of the build programme covering daily workflow, exception handling, the scoring dashboard, and FOS output. No technical background needed. In addition to the walkthrough, two to three designated Barings Law staff will be enrolled on the Wolf AI Labs AI Apprenticeships programme across nine competencies. This runs alongside the build and continues post go-live. It is an operational milestone, not a payment trigger.
Support
Who do I call if something is not working?
Tap for the answer
You have direct access to Matt for the duration of the implementation phase, as well as a named technical contact for platform configuration questions. There is no ticketing system between you and a decision maker during the build and go-live period.
Headcount
Does this mean we need fewer staff?
Tap for the answer
The platform increases what the existing team can handle, not a signal to reduce headcount. With 1.5 million claimants moving toward a June 2026 FCA redress window, your team's capacity needs to go up, not down. ClaimPassports is how you scale without proportionally scaling headcount.
Part Four · Delivery Timeline for Barings Law
What Happens and When
A full bespoke build for Barings Law, delivered by Wolf AI Labs. Four milestones from MSA signing to full go-live across a 12 to 16 week build programme.
Full Programme at a Glance
RRP
MSA
M1
M2
M3
GO
NOW
Scoping
WK 2-4
Build Starts
+4 WKS
Arch Done
+8 WKS
Build Done
+10 WKS
UAT
12–16 WKS
Go-Live
RRP
Now · Scoping Phase
NO BUILD YET · RESOURCE RESERVED · ARCHITECTURE ONLY
The RRP secures Wolf AI Labs' dedicated resources for the Barings Law ClaimPassports build. This phase covers discovery of the Barings Law operation, scoping of the ClaimPassports instance, and backend hardware build.
NOW
Discovery Report Issued
Wolf AI Labs will accrue the necessary data to understand the Barings Law operation end-to-end. Data format, bottlenecks, team structure, and existing technology confirmed. Forms the input to the architecture document. Full discussions and summary conclusions around the FCA redress issues, from which a Structured Plan of Action is shaped, assessed, and agreed.
Owner: Matt · Wolf AI Labs + Barings Law
WK 1-2
Architecture Document Produced
OCC produces the full bespoke architecture specification for Barings Law covering claim types, intake design, data schema, ESP and EPR scoring model, FOS integration, and document generation logic.
Owner: OCC Technical
WK 2-4
Architecture Review and MSA Execution
Operations Director and Matt review and sign off the architecture document. Any amendments confirmed. MSA executed. Build clock starts.
Owner: Matt · Wolf AI Labs + Barings Law + Gerard
M1
MSA + 4 Weeks · Architecture
BUILD COMMENCED · ARCHITECTURE SIGNED OFF
Build is underway. The detailed technical architecture for the bespoke Barings Law instance is finalised and locked. This is the foundation every subsequent build sprint works from.
M+W1
Bespoke Build Commences
Wolf AI Labs technical team begins building the Barings Law instance. Zero-touch intake, validation layer, ESP and EPR scoring engines, document generation, and FOS integration all built to the agreed specification.
Owner: OCC Technical
M+W2
Data Schema Delivered to Barings Law
Wolf AI Labs provides the exact data format specification. Operations Director's team begins preparing the client data extract in parallel with the build. No time lost waiting.
Owner: Wolf AI Labs delivers · Barings Law prepares data
M+W4
Architecture Milestone Review
Matt and Operations Director review build progress against the architecture document. Core infrastructure, intake pipeline, and scoring engine confirmed. Any deviation from spec addressed before the build continues.
Owner: Matt · Wolf AI Labs + Barings Law + OCC Technical
M2
MSA + 8 Weeks · Build Complete
FULL BESPOKE BUILD DELIVERED · READY FOR TESTING
The full bespoke ClaimPassports instance for Barings Law is built. All claim types, scoring engines, document generation, and FOS integration are complete. Handed to Barings Law for UAT.
M+W7
Staff Walkthrough and Training Programme
90-minute platform walkthrough for the Barings Law team before UAT begins. Daily workflow, exception handling, scoring dashboard, and FOS output reviewed. Team prepared before they test. In addition, the Wolf AI Labs AI Apprenticeships programme begins for two to three designated staff across nine competencies. This runs alongside the platform build and continues post go-live. Operational milestone, not a payment trigger.
Owner: Wolf AI Labs leads · Barings Law organises attendees
M+W8
Build Complete · Handover to UAT
Full bespoke build formally handed over. OCC provides UAT test scripts covering all Barings Law claim types. Barings Law's team begins structured testing against real scenarios.
Owner: Wolf AI Labs Technical + Barings Law
M3
MSA + 10 Weeks · UAT
USER ACCEPTANCE TESTING · COURMACS LED
Barings Law team tests the platform against real claim scenarios. OCC resolves any issues identified. UAT sign-off by Operations Director triggers go-live.
M+W9
UAT Testing Period
Barings Law team runs structured test scenarios across motor finance, housing disrepair, and business energy claim types. Intake, scoring, document generation, and FOS output all tested.
Owner: Barings Law · Wolf AI Labs on standby
M+W10
UAT Sign-Off
Any issues resolved by OCC. Barings Law signs off UAT completion. Go-live confirmed and scheduled. First tranche data extract finalised and ready for upload.
Owner: Matt · Wolf AI Labs + Barings Law
GO LIVE
MSA + 12–16 Weeks · Full Go-Live
ALL CLAIM TYPES LIVE · FULL PLATFORM ACTIVE
Full bespoke ClaimPassports platform live for Barings Law across all claim types. First tranche processing begins. FOS-ready documents in production at bulk volume.
M+W12
Full Platform Go-Live
ClaimPassports live for all Barings Law claim types. First tranche upload initiated. Zero-touch intake, ESP and EPR scoring, document generation, and FOS integration all active at live volume.
Owner: Wolf AI Labs Technical + Barings Law
+10D
First Live Throughput Review
Matt and Operations Director review first 10 days of live processing. Throughput rate, exception volume, FOS document output, and staff workflow confirmed against expected performance.
Owner: Matt · Wolf AI Labs + Barings Law
+30D
30-Day Operational Review
Full operational review. Staff time impact, claim throughput, FOS output volume confirmed. Tranche 2 scope agreed ahead of FCA PS26/3 deadline.
Owner: Matt · Wolf AI Labs + Barings Law + Darren
FCA Redress Scheme · Key Dates
Scheme 2 · Loans from 1 April 2014
30 JUN 26
Implementation period ends. Platform must be live and processing before this date.
30 SEP 26
Lenders must notify consumers whether compensation is owed and the amount.
NOV 26
Redress must be paid. End of Scheme 2 active payment window.
Scheme 1 · Loans from 6 April 2007
31 AUG 26
Implementation period ends for pre-2014 loans.
28 FEB 27
Deadline for firms to have contacted all eligible consumers who have not complained.
31 AUG 27
Final date for consumers to opt-in to Scheme 1.
JAN 28
FCA expects the vast majority of all claims across both schemes to be resolved.
Why This Matters for Go-Live
Barings Law's motor finance claimants motor finance claimants span both schemes. The Scheme 2 implementation period ends 30 June 2026. ClaimPassports must be fully live and processing before that date.