Skip to content

Data provenance log template

Use one row per collection or defined source period. Keep the underlying records in controlled storage and reference them by an internal evidence ID. Do not paste customer records, private messages, secrets, health records, or personal contact details into the log.

A provenance log records where a collection came from, what evidence supports the source, what notice or consent record is available, what processing occurred, what was excluded, and who reviewed the entry. It makes missing evidence visible. It does not prove title, prove consent, or provide legal clearance. This log is an editorial aid, not an additional product capability.

  • The Rightmark Buyers page is the public source for the current rights-record and sample-review boundary. Rightmark,

Updated

On this page

Fields

Fields (table)
FieldWhat to enter
record_idA local synthetic or controlled identifier.
collection_nameA neutral collection label, not a person's name.
source_systemThe system or source class.
source_periodThe period or version covered, or unknown.
creator_or_rights_roleA role or rights relationship, not a private person's details.
rights_basisThe evidence category that needs review.
consent_or_notice_refThe evidence reference, or not supplied.
upstream_terms_refThe applicable terms or contract reference, or not supplied.
processing_noteA short description of transformation, filtering, or redaction.
exclusionsRecords or classes left out and why.
evidence_refsInternal references to the supporting records.
verified_by_roleThe role that checked the row.
verified_onThe review date, or not reviewed.
statusNeeds evidence, Review, Recorded, or Out of scope.
notesKnown gaps and the next review action.

CSV starter

record_id,collection_name,source_system,source_period,creator_or_rights_role,rights_basis,consent_or_notice_ref,upstream_terms_ref,processing_note,exclusions,evidence_refs,verified_by_role,verified_on,status,notes
SYN-001,Example collection,Example system,[period],Owner role,[basis],[ref or not supplied],[ref or not supplied],[processing note],[exclusions],[synthetic ref],Reviewer role,[YYYY-MM-DD],Needs evidence,[next action]

Download the blank CSV template

JSON starter

{
  "template": true,
  "record_id": "SYN-001",
  "collection_name": "Example collection",
  "source_system": "Example system",
  "source_period": "[period]",
  "creator_or_rights_role": "Owner role",
  "rights_basis": "[basis]",
  "consent_or_notice_ref": "[ref or not supplied]",
  "upstream_terms_ref": "[ref or not supplied]",
  "processing_note": "[processing note]",
  "exclusions": [
    "[exclusion]"
  ],
  "evidence_refs": [
    "synthetic ref"
  ],
  "verified_by_role": "Reviewer role",
  "verified_on": "[YYYY-MM-DD]",
  "status": "Needs evidence",
  "notes": "[next action]"
}

Download the blank JSON template

Review flow

  1. Give the collection a neutral ID and define its source period.
  2. Link evidence for source, terms, notice, consent, ownership, or an explicit gap.
  3. Record processing and exclusions so a reviewer can see what changed.
  4. Assign a reviewer role and status. Needs evidence is a real outcome, not a failure to fill the row.
  5. Recheck the row when the source, terms, processing, or intended use changes.

If the collection includes health data or another gated category, stop at research and status. Do not submit an intake, sample, or appraisal through this template.

Sources

  1. Rightmark: Buyers

Use the appraisal path only after the evidence is organized for a separate review.

The template is not an appraisal.