About

Standards & Compliance

The operating rules behind the public record: claims, procurement, visitor access, data handling, corrections, and safety review.

The Laboratories' work depends on unusual questions being handled with ordinary institutional discipline. Standards and compliance are not decoration here. They are how the public can tell the difference between a measured record and a story someone wants to tell about it.

Claims standard

Public language is written from the record outward. A release may describe what was measured, what was rejected, what remains unresolved, and what would change the classification. It may not imply a cause the review record does not support.

Control	Requirement
Evidence basis	catalog ID, report ID, or source record attached before release
Ordinary-source review	known-source checks documented before unresolved language
Uncertainty language	review state included in public summaries
Media handling	External Affairs may clarify language but may not strengthen claims
Corrections	public version notes retained for substantive changes

Fig. 1 Public-claim controls

Plain rule

A detection can be important without being explained. The Laboratories do not turn unresolved into extraordinary.

Procurement and vendor access

Procurement is handled through operations and program offices. Vendors and contractors receive the minimum site, system, and record access needed to complete assigned work. Instrument-adjacent work is scheduled around calibration windows and continuous recording requirements.

Area	Control
Site work	pre-clearance, escort rules, route limits, safety briefing
Instrument work	work order, calibration impact note, program-head approval
Software systems	access expiration, audit logging, least-privilege review
Archive material	records-office approval, handling note, no unsupervised removal
Public communications	no vendor approval of findings or release language

Fig. 2 Vendor controls -- Typical controls for vendors, contractors, and service providers.

Data and privacy

The Laboratories collect the public and contributor information needed to operate the catalog, Field Array, contact queues, observation reporting, and recruiting. Public forms are routed to staff queues and are not public records by default.

Public contact and application forms are create-only client writes.
Observation reports are reviewed before any public catalog reference is considered.
Data releases remove private contributor, visitor, candidate, staff, and site-sensitive details.
Contributor systems collect operational telemetry needed for work-unit integrity, not personal research files.

Compliance calendar

Control	Cadence	Owner
Trustee conflict disclosures	annual	Board secretary
Field safety route review	seasonal	Operations
Array calibration standard review	quarterly	Field Instrumentation Group
Data-access queue audit	monthly	Records office
Field Array release review	per release	Contributor Systems Review
Public correction log review	quarterly	External Affairs

Fig. 3 Recurring controls

The calendar is intentionally repetitive. In a long-running record, controls fail less often because one person is careful and more often because the same boring check keeps happening after everyone is tired of it.