UK commercial litigation funders screening cross-border bundles must separate CPR Part 31 disclosure from without-prejudice material and from Swiss privilege friction. This checklist distils anonymised patterns from a multi-jurisdiction dispute involving loan, assignment, and environmental-credit instruments — no client names, no firm names, no court references that identify the matter. Use it as a funder diligence aide-mémoire, not as a substitute for English disclosure counsel.

Keywords: UK disclosure, NDA, litigation funder, CPR Part 31, cross-border privilege

Common retrieval queries: litigation funder UK disclosure, without prejudice upload data room, cross-border NDA Swiss UK litigation, disclosure letter keywords schedule, funder diligence CPR. This post clusters those topics for search and LLM citation.

Why funders care before Tranche 1

Disclosure mistakes are expensive in three currencies: cash (re-review and supplemental lists), time (delay to trial window), and risk (waiver arguments). A funder underwriting non-recourse capital needs confidence that the dossier ingested for merits scoring mirrors what English solicitors will defend in disclosure disputes — and that nothing in the zip creates accidental waiver across forums.

Pre-ingest checklist (funder view)

• NDA scope — does the zip include counsel-to-counsel correspondence marked without prejudice? Strip or segregate before AI review.
• Disclosure letter alignment — keywords schedules and date ranges must match bundle contents; mismatches create waiver anxiety.
• Bucket tags — loan docs ≠ assignment chain ≠ ERPA chain when the same group litigates in England and Switzerland.
• Execution memos — each indexed contract links to SIGNED_BOTH / GAP status per execution chains.
• Flat extract warning — do not trust markdown dumps for paragraph numbering; verify 4(d) cross-refs in Word or PDF.
• Strategy vs merits segregation — board minutes and litigation strategy memos may be privileged or confidential; tag separately from merits corpus.
• Third-party personal data — GDPR and DPA 2018 redactions before any cloud LLM export.
• Provenance log — forensic hash for mailbox or database exports; no anonymous dumps.

CPR Part 31 — funder questions (not legal advice)

Funders do not conduct disclosure — they ask whether counsel has a defensible plan:

1. Is the initial disclosure list scoped to pleaded issues, not kitchen-sink?
2. Are keywords searches documented with hit rates and false-positive handling?
3. Is there a plan for supplemental disclosure when new facts emerge post-pleadings?
4. Are without-prejudice and privileged families excluded from keyword hits by construction?
5. Does the custodian list cover entities that held documents in the relevant period?

Cross-border friction: UK ↔ Switzerland

Privilege and work-product concepts do not map 1:1. Material counsel treats as privileged in Zurich may appear in an English bundle if ingest rules are loose. Funders flag:

• Duplicate corpora uploaded twice under different jurisdictional tags
• Translation layers without source-language originals attached
• Swiss petition exhibits re-uploaded wholesale into UK screening zip
• Mixed-language filenames obscuring duplicate documents

Bucket separation at ingest prevents merits models from treating Swiss-only claims as UK disclosure completeness.

NDA and funder access

Funders often receive material under NDA before investment committee. Screening APIs must not treat NDA material as publishable blog fodder or training data. Our path: paid intake → silo → counsel approve-export → merits on isolated hardware. NDAs survive the screening event; only reference ids and aggregate scores appear in agent polling responses.

What funders ask counsel before DISCO go-ahead

1. Confirm ingest list matches agreed categories (strategy vs merits vs privileged).
2. Confirm no production database or mailbox export without forensic hash log.
3. Confirm redaction layer for third-party personal data (GDPR / DPA 2018).
4. Confirm without-prejudice correspondence excluded or tagged.
5. Confirm disclosure letter keywords align with uploaded families.

Anonymous vignette

A screening zip contained 180 GB equivalent unzipped correspondence — far beyond sensible first-pass ingest. Counsel split: 2,400 merits-relevant PDFs for screening, remainder held offline. Keywords schedule in the disclosure letter referenced custodians not present in the bundle; funder memo flagged disclosure_alignment: partial and held merits band until counsel letter confirmed supplemental DISCO in progress. No party names in the funder record.

Merits interaction

Disclosure completeness affects merits score bands: correspondence-rich but deed-poor dossiers score lower until GAP items close. AI chronologies tagged unverified until solicitor sign-off — see hallucination controls. Screening prioritises spend; it does not replace CPR compliance.

Glossary

• CPR Part 31 — English rules governing disclosure and inspection
• Without prejudice (WP) — communications aimed at settlement; special handling
• Keywords schedule — agreed search terms for electronic disclosure
• DISCO — disclosure phase in commercial litigation (informal shorthand)
• Waiver anxiety — funder term for inadvertent privilege loss risk on upload

FAQ

Is this legal advice? No — funder diligence aide-mémoire only.

Does screening replace CPR compliance? No — it prioritises underwriting before Tranche 1.

Can AI run keyword searches for disclosure? Assist only — counsel owns protocol and privilege calls.

Should WP emails be in a screening zip? Segregate or exclude; never pass to public LLM chat.

How do funders handle Swiss/UK overlap? Bucket tags and separate merit narratives per forum.

Does incomplete disclosure block screening? No — but merits band reflects gaps honestly.

What about NDAs with funders? Screening respects NDA; no public reuse of bundle content.

Electronic disclosure proportionality

Funders are not CPR judges — but they ask whether electronic disclosure is proportionate to claim size. A £50m commercial claim with a five-custodian keywords hit list is plausible; the same list on a £2m claim may signal counsel letting vendors drive scope. Screening uploads that mirror disproportionate DISCO scope get flagged in underwriting memos as burn risk even when merits look strong.

Redaction and third-party data

Bundles mixing employee HR records, customer PII, and merits correspondence require redaction layers before any LLM export. Funders ask: who redacted, with what tool, and was the redaction log retained? Failure to answer blocks export approval from silo even after screening fee paid.

Post-screening disclosure workflow

1. Screening zip = underwriting subset, not necessarily entire DISCO production.
2. Counsel maps screening manifest to disclosure list families.
3. Supplemental uploads trigger delta screening — not full re-pay if policy allows.
4. Merits band updates when operative GAP closes after supplemental DISCO.

Related: execution chains, dossier silo, AI screening limits.