Pre-Decision Conflict Screen¶
Screening gate — instantiates Conflict-of-Interest Mitigation
A hold point before a decision or assignment that matches the participants against disclosed interests and the matter's affected parties, flagging conflicts before the decision proceeds.
The cheapest place to catch a conflict is at the doorway of the decision, before anyone has invested in an outcome. Pre-Decision Conflict Screen is that doorway: a gate that fires when a matter is about to be assigned, evaluated, or decided, matching the people who would participate against the disclosed interests and against the specific parties the matter touches — the applicant, the vendor, the subject — and holding the decision if it finds a hit. Its defining orientation is prospective and outbound: it adjudicates whether a person may participate in a pending decision, scoping that decision's affected parties to know what would even count as a conflict. It is a routine, high-throughput filter, not an adjudicating body — its job is to flag and hold, routing genuine hits onward and letting clean matters pass, so that conflicts are caught before influence rather than discovered afterward.
Example¶
An academic journal is assigning peer reviewers to a submitted manuscript. Before the editor sends invitations, the screen runs. It first scopes the matter's affected parties — the manuscript's five co-authors, their two institutions, and the funder named in the acknowledgments. Then it matches each candidate reviewer against those parties and against the journal's disclosure records: co-authorship in the last three years, shared institution, known rivalry, prior collaboration. One well-qualified candidate is flagged — she co-published with the senior author two years ago — and the screen classifies it as at least a potential conflict and holds the invitation. A second candidate shares a large professional society with an author but has no direct tie; the materiality check finds no meaningful influence path, and that candidate passes. The flagged reviewer is replaced before she ever sees the paper.
The screen's value is that it prevented a compromised review at essentially zero cost, using the disclosed relationships and a defined affected-party map — rather than discovering the conflict after the review had already shaped the decision.
How it works¶
- Scope the matter's affected parties. Enumerate the counterparties, beneficiaries, and linked matters the decision touches, so the screen knows what a conflict would be against.
- Match participants to interests. Compare candidate decision-makers against the disclosed relationships and the affected-party map.
- Classify and size hits. Sort each match into actual/potential/apparent/non-material and check its influence path, so trivial coincidences do not block work while real conflicts are held.
- Hold or release. Genuine hits pause the assignment and route onward; clean matters proceed. An urgent-override path exists but is logged.
Tuning parameters¶
- Match sensitivity — how loosely a candidate is linked to a party before the screen flags. High sensitivity catches more but floods reviewers with false positives; low sensitivity misses real ties.
- Affected-party breadth — how far the map reaches into linked matters and indirect beneficiaries. Broader maps catch downstream conflicts but slow every decision.
- Auto-hold vs. advisory flag — whether a hit blocks the decision or merely warns. Auto-hold is safer but brittle on false positives; advisory relies on human follow-through.
- Override discipline — how easily an urgent matter can bypass the hold, and whether the bypass is logged and reviewed. Loose overrides quietly gut the gate.
When it helps, and when it misleads¶
Its strength is prevention at scale: for a high volume of routine assignments and evaluations, it stops conflicted participation before it can shape anything, at near-zero marginal cost per matter.
Its central failure mode is the false-positive flood: an over-sensitive matcher that flags every shared conference or common surname, so reviewers learn to rubber-stamp releases and stop reading the flags — the base-rate problem that afflicts any high-volume screen.[n1] The mirror failure is late screening, run after assignments are effectively locked, so a hit is ignored to avoid rework. The classic misuse is treating a clean screen as proof of no conflict when the screen only checks disclosed relationships — an undisclosed tie sails straight through. The guarding discipline is to tune sensitivity against real hit rates, to run the screen early enough that a flag can actually change the assignment, and to remember that the screen is only as complete as the register it reads.
How it implements the components¶
conflict_scope_and_affected_party_map— it scopes each pending matter's counterparties, affected parties, and linked decisions so participants can be matched against them.actual_potential_and_apparent_conflict_classification— each match is sorted into the actual/potential/apparent/non-material taxonomy to decide hold vs. release.materiality_and_influence_assessment— it sizes each hit's influence path so trivial coincidences pass and material ties are held.
It does not implement disclosure_trigger_and_update_rule — the screen *reads disclosures but does not collect them; capturing the disclosures it matches against is Gift and Outside-Activity Approval Workflow and the Conflict-of-Interest Disclosure Register. Where the gift workflow gates an incoming benefit, this screen gates an outgoing decision.*
Related¶
- Instantiates: Conflict-of-Interest Mitigation — it is the prospective hold point that keeps conflicted participants out of a decision before influence occurs.
- Consumes: Conflict-of-Interest Disclosure Register — matches participants against the interests the register holds.
- Sibling mechanisms: Gift and Outside-Activity Approval Workflow · Conflict-of-Interest Disclosure Register · Independent Conflict Review Panel · Post-Decision Conflict Audit
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Pre-Decision Conflict Screen operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it a hold point before a decision or assignment that matches the participants against disclosed interests and the matter's affected parties, flagging conflicts before the decision proceeds.
Independent corroboration: The frozen evidence defines Pre-Decision Conflict Screen as 'A hold point before a decision or assignment that matches the participants against disclosed interests and the matter's affected parties, flagging conflicts before the decision proceeds', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Assessment, Review & Assurance — Pre-Decision Conflict Screen includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is a case-specific gate, selection, routing, prioritization, or resource disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Pre-decision disclosure and recusal screening are rooted in legal conflict-of-interest and fiduciary doctrine.
Related originating lineages:
- Accounting & Auditing — Auditing contributes segregation-of-duties and risk-based control checks.
- Organizational & Management Science — Organizational management contributes assignment and committee workflow.
Review resolution: Both blind reviewers agree that law governance is the primary origin. Reconciliation resolves alternate origin disagreement, origin mode disagreement. Formative alternate lineages are retained as accounting_auditing, organizational_management; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The base-rate (or false-positive) problem: when true conflicts are rare, even an accurate matcher generates many more false alarms than real ones, so an over-sensitive screen buries genuine flags in noise and trains reviewers to ignore them. Calibrating sensitivity to the real hit rate is the standard corrective. ↩