Methodology
Facility identity and institutional roles
How a facility is identified, how owner, operator, parent and contracting authority are kept apart, and when an intervention window is published.
How a facility is identified
Two records are joined only when identity is established. Name resemblance is a question, not an answer.
Every facility has one canonical identity. Before a record is published, a deterministic check flags places where two records could be mistaken for one another: duplicate facility names, an alias that also matches another facility, conflicting alias mappings, a shared street address, an annex or unit relationship, the same name in different states, and harm records whose facility label does not match a canonical entry.
A flag is a question a person answers, not a conclusion. The check never merges, renames, or reassigns anything, and the absence of a flag is not evidence that two records are distinct.
Institutional roles are never collapsed
Different parties can hold each role at the same facility, and the roles change over time.
- Award recipient
- The party holding the federal award.
- Parent
- A parent company of the named entity.
- Owner
- The party owning the property.
- Operator
- The party running day-to-day operations.
- Authority
- The contracting or oversight authority.
- Payer
- The party paying under an award.
- Unresolved
- Where the indexed records do not establish who holds a role, the field says so. A role is never inherited from a similar facility, an older contract, or a company's marketing material.
Relationships are time-bounded and sourced
An operator relationship is published with the period the cited source establishes. A company that operated a facility in one period is not described as its current operator without a record for the current period.
A facility's contract history and its conditions record may appear on the same page. Placing them together is chronology, not a causal claim about the contract.
Which facilities appear, and as of when
The facility list reflects the records currently indexed. It is not a live or complete national inventory, and a facility's absence is not evidence that it does not exist or holds no one.
Each facility record carries its own retrieval and effective dates. A site-wide snapshot date states when records were last read; it does not make any individual source current.
When an intervention window is published
Intervention windows are institutional decision points tied to the case files currently indexed, not a claim of comprehensive coverage.
- Window vs channel
- A window is a concrete decision point with an identifiable controlling office. A standing FOIA portal or IG hotline is a channel, counted separately and never shown as a deadline.
- Date certainty
- Hard means a cited record states the date. Estimated means a source states an expectation. Unknown means no source establishes one — we do not infer a deadline from a contract period or a news report.
- Calendar files
- A downloadable .ics is offered only for a hard, source-supported date. Estimated and unknown dates never produce one.
- Ordering
- Deterministic: verified open first, then deadline proximity, date certainty, and source freshness. Unknown dates never sort as urgent. No impact, outrage, or death-count score is used.
- Closed stays visible
- A window that closes remains published as history with its closure reason. Expired hard dates read as stale / needs review, never as silently closed.
- Coverage
- The ledger is tied to the case files currently indexed. It is not a live or national inventory of every available intervention.
What automation may not do
Contract synchronization can flag a candidate change, but it cannot open, close, extend or publish a window; those records are written for human review only. A source outage never changes a window's status.
Leverage is directed at institutions and documented decision processes. No private individual is named as a target, and no private address or personal contact detail is published.
Where these rules are visible
Every entry in the facility directory carries its own sourced roles and unresolved fields, and the Leverage Room publishes the intervention windows those rules govern.
Rest of the method
This page is one part of the published method. The reader guide summarises all of it, and corrections are recorded on the affected record with the date applied.
Current section: Facilities and roles