Data Evaluation Checklists: Pilot, Match, Governance

High-intent buyer checklists to evaluate data feeds: matched-sample pilots, exclusions, delivery specs, and contract terms. Request the checklist pack.

Repeatable diligence for data procurement

These checklists help legal, privacy, data science, and procurement teams evaluate GSDSI feeds without reinventing questions on every RFP. They mirror the pilot process and are designed to be pasted into internal vendor-comparison memos.

Matched-sample checklist

  • Define match keys and required joins before testing.
  • Set success thresholds by geography, cohort, and channel.
  • Validate refresh cadence, decay behavior, and opt-out propagation.
  • Document delivery path (S3, SFTP, Snowflake, API) and manifest checksums.

Governance checklist

  • Sensitive-category exclusions and permitted-use boundaries.
  • Retention, deletion SLAs, and downstream sharing obligations.
  • Subprocessors review at /trust/sub-processors.
  • Contract alignment with the DPA template and privacy policy.

Delivery checklist

  • Format and schema stability expectations for production pipelines.
  • Region, encryption, and access-control requirements.
  • Change-control process for breaking schema updates.

For measurement-specific workflows see clean room measurement. Federal buyers should pair this page with federal procurement artifacts.

FAQ

What should a matched-sample checklist cover?
Define seed keys, geography and cohort segments, match-rate thresholds, freshness filters (last_seen or event date), opt-out propagation proof, and the delivery path you will use in production. Document pass/fail before expanding volume.
What governance items belong in procurement diligence?
Confirm sensitive-category exclusions, permitted uses, retention and deletion SLAs, downstream sharing rules, subprocessors, and audit rights. Align activation and measurement use cases with the privacy policy before scale.
What delivery checks prevent rework?
Validate format (Parquet, CSV, JSON), partition strategy, manifest checksums, region, refresh SLA, and warehouse compatibility (Snowflake share, S3, SFTP, API). Run a small end-to-end load in the buyer environment before signing production volume.
How does this relate to the GSDSI pilot process?
The checklists mirror the four-step workflow on /pilot-process: scope the endpoint, run a matched sample, confirm delivery and governance, then lock production terms. Use them as an internal memo template during vendor comparison.
Can federal buyers use the same checklists?
Yes. Add GovCloud or Azure Government delivery, CAI-aligned provenance, and socioeconomic verification requirements. Start from /federal-procurement and the federal procurement checklist linked from this page.