Procurement Donor Overlap

Compare caller-supplied requirements and observations for procurement donor overlap.

Description

Procurement-donor overlap compares supplied vendor and donor labels.

Procurement-donor overlap compares supplied vendor and donor labels. Its coverage is the share of unique vendor labels also represented among donors.^[1]

Compare caller-supplied requirements and observations for procurement donor overlap.

When to use Procurement Donor Overlap

Use this tool to compare caller-supplied requirements and observations for procurement donor overlap.

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.

How to use Procurement Donor Overlap and understand its results

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
Enter contractVendorIds, donorEmployerIds using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
contractVendorIds	Contract vendor IDs	list of string	Required
donorEmployerIds	Donor employer IDs	list of string	Required

Supply vendor labels as the required list and donor labels as observations. Enter a nonempty required list and an observed list, which may be empty. Trim and lowercase entries for comparison; blank entries are errors. Deduplicate by normalized key. Return matched/missing required labels, unexpected observed labels, and coverage. Required order is preserved; the last trimmed spelling wins for duplicate keys.

coverage%=100×matchedUnique/requiredUnique

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "contractVendorIds": [
      "vendor-17",
      "vendor-22",
      "vendor-41"
    ],
    "donorEmployerIds": [
      "vendor-22",
      "vendor-90"
    ]
  },
  "output": {
    "coveragePercent": 33.33333333333333,
    "matched": [
      "vendor-22"
    ],
    "missing": [
      "vendor-17",
      "vendor-41"
    ],
    "unexpected": [
      "vendor-90"
    ]
  }
}

Limitations and assumptions

Matching text does not establish a shared legal entity, ownership, improper influence or wrongdoing.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Donor Concentration Analysis: Aggregate contributions by donor and calculate largest-share and Herfindahl concentration measures. For a complementary task, use Beat Holdings Conflict: Find securities holdings that overlap organizations on a reporting beat.

References

Procurement Donor Overlap — tool.io

Similar or alternative tools

Donor Concentration Analysis
Aggregate contributions by donor and calculate largest-share and Herfindahl concentration measures.
Beat Holdings Conflict
Find securities holdings that overlap organizations on a reporting beat.