Embargo Coordination

Audit embargo coordination confirmations across required recipients.

Description

Embargo coordination can track whether required participant labels are present in a supplied acknowledgment list.

Embargo coordination can track whether required participant labels are present in a supplied acknowledgment list. Coverage helps locate missing records.^[1]

Audit embargo coordination confirmations across required recipients.

When to use Embargo Coordination

Use this tool to audit embargo coordination confirmations across required recipients.

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 Embargo Coordination 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 requiredRecipients, confirmedRecipients 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
requiredRecipients	Required embargo recipients	list of string	Required
confirmedRecipients	Confirmed recipients	list of string	Required

Supply required and observed coordination labels. 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": {
    "requiredRecipients": [
      "alpha",
      "beta",
      "gamma"
    ],
    "confirmedRecipients": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No email is sent and no embargo terms, actual acknowledgment or compliance is verified.

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 Records Request SLA: Measure a records-request response against a caller-supplied SLA. For a complementary task, use Media Policy Coverage: Audit newsroom media-policy coverage.

References

Embargo Coordination — tool.io

Similar or alternative tools

Records Request SLA
Measure a records-request response against a caller-supplied SLA.
Media Policy Coverage
Audit newsroom media-policy coverage.