On this page
Evidence matrix
| Area | Evidence to assemble | Status | Next action |
|---|---|---|---|
| Provenance | Source system, period, and evidence references | Ready / Needs evidence / Out of scope / Not applicable | [action] |
| Structure | Format, units, identifiers, and relationships | Ready / Needs evidence / Out of scope / Not applicable | [action] |
| Labels and metadata | Label definitions, fields, and missingness notes | Ready / Needs evidence / Out of scope / Not applicable | [action] |
| History | Version or time coverage and change notes | Ready / Needs evidence / Out of scope / Not applicable | [action] |
| Rights and scope | Ownership, terms, notice, consent, and exclusions evidence | Ready / Needs evidence / Out of scope / Not applicable | [action] |
| Sample readiness | Redacted sample shape and review instructions | Ready / Needs evidence / Out of scope / Not applicable | [action] |
| Verification environment | Reproducible local checks or source-system notes | Ready / Needs evidence / Out of scope / Not applicable | [action] |
| Privacy handling | Sensitive classes, exclusions, access, and retention | Ready / Needs evidence / Out of scope / Not applicable | [action] |
| Delivery | Format, cadence, deletion, and handoff requirements | Ready / Needs evidence / Out of scope / Not applicable | [action] |
Needs evidence is a useful result. It means the next action is known or can be assigned. Do not sum the statuses into a number without a separately reviewed method.
Technical evidence for code
When the collection is code, the current Repo Check route can provide bounded technical signals about code shape, tests, tooling, CI, history, and disclosure risks. Use the installed tool and its current schema. Do not copy internal thresholds into this general worksheet and do not treat a tool signal as a rights decision.
Buyer-readiness evidence
The current Rightmark buyer flow asks for a data family, specification, volume and unit, license shape, timeline, organization, and work email. A review can also need a sample shape, security requirements, delivery cadence, and deletion terms. Record each item as Ready, Needs evidence, or out of scope. A complete worksheet does not create a buyer, establish demand, or guarantee acceptance.
Safe blank example
Collection: Dataset A
Review purpose: [description]
Rights evidence: Needs evidence
Structure and format: Needs evidence
Sample shape: Not applicable
Privacy handling: Needs evidence
Delivery and deletion: Needs evidence
Next review owner role: [role]The example is synthetic and intentionally incomplete. It contains no data, price, customer, buyer, or relationship.
Boundaries
This worksheet cannot establish ownership, prove absence of prior public exposure or contamination, provide legal clearance, set a price, or forecast demand. It cannot replace a technical evaluation or an appraisal. Health-related material remains research and status only. Do not use this page as health intake or submit a health sample.
General information, not legal advice.
Sources
- Rightmark: Buyers
- Rightmark: Repo Check