Validation build: the evidence log is live; the pricing example is simulated and places no cover. What that means

Regime packs · one proof, mapped to each rule

What to record, rule by rule

The evidence log proves that a record existed, unaltered, no later than a signed and anchored head. It does not know what the record is. A pack says, for one regime, which fields to put in a record so that the proof answers the question a supervisor will ask, and maps each field to the article it speaks to. The record stays with you; only its salted fingerprint is sent. Fourteen packs, for fourteen laws, are published, as data anyone can use without us.

How it works

A record, its fingerprint, and the bundle you hand over

1. Write the record
A JSON object with the pack's fields, in your own system. Identify people and cases by your own references, never by name: the pack's reference fields refuse anything that looks like a name or an email.
2. Send its fingerprint
Canonicalise it (RFC 8785, with the profile in the specification), hash it with a random salt, and send only the digest and the kind to POST /api/v2/evidence. Optionally sign it with your own key, so the leaf carries your signature too.
3. Keep three things
The record, the salt, and the proof the API gives for the entry. Together they are a bundle: riskrouter-record-bundle|1.
4. Hand over the bundle
Anyone can check it offline with either verifier: the record hashes to the recorded digest, its kind is the recorded kind, the entry is in a tree whose head we signed, and, for a signed leaf, your own signature holds.
# validate a record against its pack, then fingerprint it
node records.mjs validate statement.json
node records.mjs digest statement.json            # prints salt_hex and record_digest; keep both

# after recording: bundle it with the proof, and check it the way a supervisor would
node records.mjs bundle statement.json --salt $SALT --proof proof.json > bundle.json
node records.mjs check bundle.json --key signing-key.json
python3 riskrouter_verify.py bundle.json --key signing-key.json

records.mjs ships with the conformance suite, beside the packs, and in the public verifier repository; the Python verifier is in the kit. The Python client's record_structured() does steps 2 and 3 for you.

What the log proves

What a bundle shows, and what it cannot

It shows
That this exact record, with these field values, existed no later than the head's time and the Bitcoin block its anchor is in, and has not been changed since. With a signed leaf, that you asserted it. A correction is a new record naming the old one in supersedes, and the old one stays: what was there before a correction can always be seen.
It does not show
That the record is true or complete, that an obligation applied to you, or that you met it. Whether a regime applies, what it requires of you, and how long to keep records are for you and your supervisor.
Where the log adds most
Where a rule asks that records cannot be altered or that logs are kept: Delegated Regulation (EU) 2017/565, Article 72(1), and the AI Act's Articles 12, 19 and 26(6). A database row can be edited by whoever administers it; a fingerprint in an anchored tree cannot be changed without the change showing.
EU AI ActAnti-Money Laundering RegulationConsumer Credit DirectiveEU Clinical Trials RegulationCyber Resilience ActDORAGDPR consent and erasureGDPR Article 22Insurance Distribution DirectiveEU Medical Device Regulations (MDR and IVDR)MiFID IINIS2 and data breachesPublic procurementVAT Directive invoices

EU AI Act · pack ai-act version 1

High-risk AI systems: logs, decisions and human oversight

What a provider or deployer of a high-risk AI system records so that its logs, the decisions taken on the system's output, and the human oversight exercised over it can be shown later to be exactly what existed at the time; and what a provider of a high-risk system or of a general-purpose model records of the data sets a model was trained, validated and tested on.

The law
Regulation (EU) 2024/1689 (Artificial Intelligence Act) (CELEX 32024R1689)
Kinds
ai.log-segment log segment sealed
ai.decision decision taken on the system's output
ai.oversight human oversight exercised
ai.model-provenance model, prompt and policy in force
ai.screening-criteria criteria fixed before people are assessed
ai.content-credential generated content and its marking sealed
ai.training-data training, validation or test data set fixed
The file
/packs/ai-act.json, with an example record for every kind
How long to keep it
Articles 19(1) and 26(6) set a minimum of six months for the logs they cover, unless other law provides otherwise; this pack does not decide your period. Whether your system is high-risk, and from when these obligations apply to it, is yours to establish from the Regulation.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Regulation (EU) 2024/1689, Article 12(1)High-risk AI systems must technically allow for the automatic recording of events (logs) over the lifetime of the system.ai.log-segment: system_ref, segment_start, segment_end, event_count, log_digest, previous_segment_record_id
ai.model-provenance: system_ref, effective_from
Regulation (EU) 2024/1689, Article 12(2)Logging must enable recording of events relevant for identifying situations that may result in the system presenting a risk or in a substantial modification, for post-market monitoring (Article 72), and for monitoring the system's operation (Article 26(5)).ai.log-segment: system_version
ai.decision: system_ref, system_version, input_digest, output_digest, decided_at
ai.model-provenance: system_ref, model_version_digest, prompt_template_digest, policy_digest, effective_from, previous_record_id
ai.screening-criteria: criteria_digest, provenance_record_id
Regulation (EU) 2024/1689, Article 14(4)(d)The people overseeing the system must be able to decide, in any particular situation, not to use it or to disregard, override or reverse its output.ai.decision: human_involved
ai.oversight: system_ref, decision_record_id, overseer_ref, action, reason, acted_at
Regulation (EU) 2024/1689, Article 19(1)Providers keep the logs their high-risk AI systems generate automatically, to the extent the logs are under their control, for a period appropriate to the system's intended purpose and of at least six months, unless Union or national law, in particular on personal data, provides otherwise.ai.log-segment: role, log_digest, retain_until
Regulation (EU) 2024/1689, Article 19(2)Providers that are financial institutions subject to internal-governance requirements under Union financial services law keep those logs as part of the documentation kept under that law.ai.log-segment: retain_until
Regulation (EU) 2024/1689, Article 26(6)Deployers keep the logs the system generates automatically, to the extent the logs are under their control, for a period appropriate to the system's intended purpose and of at least six months, unless applicable law provides otherwise.ai.log-segment: role, log_digest, retain_until
Regulation (EU) 2024/1689, Article 86(1)A person affected by a decision a deployer takes on the basis of output from a high-risk AI system listed in Annex III (other than point 2), with legal or similarly significant adverse effects, may obtain clear and meaningful explanations of the role of the AI system in the decision and of the main elements of the decision taken.ai.decision: system_ref, case_ref, output_summary, role_of_system, decision
ai.model-provenance: model_version_digest, prompt_template_digest, policy_digest
ai.screening-criteria: system_ref, round_ref, criteria_digest, fixed_at, opens_at
Regulation (EU) 2024/1689, Article 50(2)Providers of AI systems, including general-purpose AI systems, that generate synthetic audio, image, video or text content ensure that the outputs are marked in a machine-readable format and detectable as artificially generated or manipulated, as far as technically feasible.ai.content-credential: system_ref, content_digest, marking, marking_digest, generated_at
Regulation (EU) 2024/1689, Article 10(2)Training, validation and testing data sets of high-risk AI systems are subject to data governance and management practices appropriate to the intended purpose, concerning in particular the data collection processes and the origin of the data (and, for personal data, the original purpose of the collection) and the data-preparation operations such as annotation, labelling, cleaning, updating, enrichment and aggregation.ai.training-data: dataset_ref, role, use, manifest_digest, item_count, origin_record_digest, preparation_record_digest, fixed_at, previous_record_id
Regulation (EU) 2024/1689, Article 53(1)(a)Providers of general-purpose AI models draw up and keep up to date the technical documentation of the model, including its training and testing process and the results of its evaluation, to provide it on request to the AI Office and the national competent authorities.ai.training-data: dataset_ref, role, manifest_digest, fixed_at
Regulation (EU) 2024/1689, Article 53(1)(c)Providers of general-purpose AI models put in place a policy to comply with Union law on copyright and related rights, in particular to identify and comply with a reservation of rights expressed under Article 4(3) of Directive (EU) 2019/790.ai.training-data: copyright_check_digest
Regulation (EU) 2024/1689, Article 53(1)(d)Providers of general-purpose AI models draw up and make publicly available a sufficiently detailed summary about the content used for training the model, according to a template provided by the AI Office.ai.training-data: public_summary_digest

ai.log-segment · Log segment sealed

When: Each time a segment of the system's automatic log is closed: every hour, every day, or every file rotation.

FieldWhat to put in itTypeMapped to
system_refYour reference for the AI system.your referenceArticle 12(1)
system_versionThe version of the system that produced the log.one lineArticle 12(2)
roleWhether you keep this log as the provider or as a deployer.one of provider, deployerArticle 19(1)
Article 26(6)
segment_startTime of the first event in the segment, UTC.UTC timeArticle 12(1)
segment_endTime of the last event in the segment, UTC.UTC timeArticle 12(1)
event_countHow many events the segment holds, so a shortened log is caught.whole numberArticle 12(1)
log_digestSHA-256 of the segment file exactly as stored.SHA-256Article 12(1)
Article 19(1)
Article 26(6)
log_format (optional)The format of the segment, such as jsonl.one line–
previous_segment_record_id (optional)The record_id of the segment before this one, so a missing segment is caught.your referenceArticle 12(1)
retain_until (optional)The date until which you have decided to keep this segment.dateArticle 19(1)
Article 26(6)
Article 19(2)

ai.decision · Decision taken on the system's output

When: When a decision about a person or a case is taken on the basis of the system's output.

FieldWhat to put in itTypeMapped to
system_refYour reference for the AI system.your referenceArticle 12(2)
Article 86(1)
system_versionThe version of the system that produced the output.one lineArticle 12(2)
case_refYour reference for the case or the person concerned. Never a name.your referenceArticle 86(1)
input_digest (optional)SHA-256 of the input exactly as the system received it.SHA-256Article 12(2)
output_digest (optional)SHA-256 of the output exactly as the system produced it.SHA-256Article 12(2)
output_summaryWhat the system output, in words someone can check against the output.textArticle 86(1)
role_of_systemThe role the system's output played in the decision.textArticle 86(1)
decisionThe decision taken, and its main elements.textArticle 86(1)
human_involvedWhether a person reviewed the output before the decision.true or falseArticle 14(4)(d)
decided_atWhen the decision was taken, UTC.UTC timeArticle 12(2)

ai.oversight · Human oversight exercised

When: When a person overseeing the system confirms, overrides, reverses or declines to use its output, or stops it.

FieldWhat to put in itTypeMapped to
system_refYour reference for the AI system.your referenceArticle 14(4)(d)
decision_record_id (optional)The record_id of the ai.decision record concerned, if any.your referenceArticle 14(4)(d)
overseer_refYour reference for the person who acted. Never a name.your referenceArticle 14(4)(d)
actionWhat the person did with the output.one of confirmed, overridden, reversed, not-used, stoppedArticle 14(4)(d)
reasonWhy.textArticle 14(4)(d)
acted_atWhen, UTC.UTC timeArticle 14(4)(d)

ai.model-provenance · Model, prompt and policy in force

When: Each time the model version, the prompt template or the policy a system applies changes: sealed by their digests, so any later decision record can name exactly what was in force.

FieldWhat to put in itTypeMapped to
system_refYour reference for the AI system.your referenceArticle 12(1)
Article 12(2)
model_version_digestSHA-256 of the model identifier and version, or of the model weights, as you define it.SHA-256Article 12(2)
Article 86(1)
prompt_template_digest (optional)SHA-256 of the prompt template or system instructions, exactly as deployed.SHA-256Article 12(2)
Article 86(1)
policy_digest (optional)SHA-256 of the rules or policy the system applies, exactly as deployed.SHA-256Article 12(2)
Article 86(1)
effective_fromFrom when this combination is in force, UTC.UTC timeArticle 12(1)
Article 12(2)
previous_record_id (optional)The record_id of the provenance record this one replaces.your referenceArticle 12(2)

ai.screening-criteria · Criteria fixed before people are assessed

When: Before a round of assessment opens (applications for a job, for credit, for a place): the criteria and their weights are sealed, so they can be shown not to have been changed once the people being assessed were known.

FieldWhat to put in itTypeMapped to
system_refYour reference for the AI system or the assessment process.your referenceArticle 86(1)
round_refYour reference for the round, such as a vacancy.your referenceArticle 86(1)
criteria_digestSHA-256 of the criteria and their weights, exactly as fixed.SHA-256Article 86(1)
Article 12(2)
fixed_atWhen they were fixed, UTC.UTC timeArticle 86(1)
opens_at (optional)When the round opens, UTC.UTC timeArticle 86(1)
provenance_record_id (optional)The record_id of the ai.model-provenance in force.your referenceArticle 12(2)

ai.content-credential · Generated content and its marking sealed

When: When a system generates content and marks it: the digest of the content and of its marking (for example a C2PA manifest) are sealed, so the time it existed is fixed independently and two different versions of it cannot both be presented as the original.

FieldWhat to put in itTypeMapped to
system_refYour reference for the generating system.your referenceArticle 50(2)
content_digestSHA-256 of the generated content exactly as published.SHA-256Article 50(2)
markingHow the output is marked.one of c2pa-manifest, watermark, metadata, otherArticle 50(2)
marking_digest (optional)SHA-256 of the marking itself, such as the C2PA manifest store, where it can be separated.SHA-256Article 50(2)
generated_atWhen it was generated, UTC.UTC timeArticle 50(2)

ai.training-data · Training, validation or test data set fixed

When: Each time a data set used to train, validate or test a model is fixed: sealed by the fingerprint of its manifest (every file and its SHA-256), with the records of where the data came from and how it was prepared, so a later question about which data a model learned from has one answer.

FieldWhat to put in itTypeMapped to
dataset_refYour reference for the data set and its version.your referenceArticle 10(2)
Article 53(1)(a)
roleWhether you keep this as the provider of a high-risk AI system or of a general-purpose AI model.one of high-risk-provider, gpai-providerArticle 10(2)
Article 53(1)(a)
useWhat the data set is used for.one of training, validation, testingArticle 10(2)
manifest_digestSHA-256 of the manifest listing every file of the data set with its own SHA-256, exactly as stored.SHA-256Article 10(2)
Article 53(1)(a)
item_countHow many items the data set holds, so a later, smaller or larger set is caught.whole numberArticle 10(2)
origin_record_digestSHA-256 of your record of the collection processes and the origin of the data.SHA-256Article 10(2)
preparation_record_digest (optional)SHA-256 of your record of the preparation operations: annotation, labelling, cleaning, updating, enrichment, aggregation.SHA-256Article 10(2)
copyright_check_digest (optional)SHA-256 of your record of how reservations of rights were identified and honoured for this data set.SHA-256Article 53(1)(c)
public_summary_digest (optional)SHA-256 of the published summary of training content, exactly as published.SHA-256Article 53(1)(d)
fixed_atWhen the data set was fixed in this form, UTC.UTC timeArticle 10(2)
Article 53(1)(a)
previous_record_id (optional)The record_id of the training-data record for the version this one replaces.your referenceArticle 10(2)

The log itself never leaves you: only the digest of each segment is recorded. A segment produced later can then be shown to be the segment that existed when it was sealed, and event_count and previous_segment_record_id make a shortened or missing segment visible.

Anti-Money Laundering Regulation · pack aml version 1

Anti-money laundering: customer due diligence, sanctions screening and its records

What an obliged entity records so it can show which customer file it approved and when, which version of a targeted financial sanctions list a customer was screened against, and that the screening was repeated. The customer file stays with you; only its digests are sealed.

The law
Regulation (EU) 2024/1624 (Anti-Money Laundering Regulation) (CELEX 32024R1624)
Kinds
aml.onboarding-file customer file approved
aml.list-version sanctions list version held
aml.screening customer screened against a sanctions list
The file
/packs/aml.json, with an example record for every kind
How long to keep it
Article 77 states five years from the end of the business relationship, or from the date of an occasional transaction, and says when that period may be extended. The regulation applies from 10 July 2027. This pack does not decide your period.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Regulation (EU) 2024/1624, Article 20(1)The customer due diligence measures: among them, identifying the customer and the beneficial owners and verifying their identity, and understanding the purpose and intended nature of the business relationship.aml.onboarding-file: customer_ref, approved_at, cdd_level, document_digests, approver_ref
Regulation (EU) 2024/1624, Article 20(1), point (d)Verify whether the customer or the beneficial owners are subject to targeted financial sanctions and, for a legal entity, whether persons subject to them control it or hold more than 50 % of its proprietary rights or a majority interest in it.aml.onboarding-file: screening_record_ids
aml.list-version: list_ref, list_digest
aml.screening: customer_ref, list_record_id, trigger, screened_at, result, reviewer_ref
Regulation (EU) 2024/1624, Article 26Regularly verify again whether the condition in Article 20(1), point (d), is met, as often as the exposure to the risks of non-implementation and evasion of targeted financial sanctions requires; credit and financial institutions also do so upon a new designation.aml.list-version: list_ref, published_at, retrieved_at, list_digest
aml.screening: customer_ref, list_record_id, trigger, screened_at
Regulation (EU) 2024/1624, Article 77(1)Retain, among other things, a copy of the documents and information obtained in performing customer due diligence, the record of the assessment of suspicious transactions, and the supporting evidence and records of transactions.aml.onboarding-file: customer_ref, document_digests

aml.onboarding-file · Customer file approved

When: When a customer's due diligence file is approved: the digest of each document in it is sealed at that moment, so no document can be swapped in later.

FieldWhat to put in itTypeMapped to
customer_refYour reference for the customer, never a name.your referenceArticle 20(1)
Article 77(1)
approved_atWhen the file was approved, UTC.UTC timeArticle 20(1)
cdd_levelThe level of due diligence applied.one of simplified, standard, enhancedArticle 20(1)
document_digestsSHA-256 of each document and data set in the file, exactly as held.list of SHA-256Article 77(1)
Article 20(1)
screening_record_ids (optional)The record_ids of the sanctions screenings done for this file.list of your referenceArticle 20(1), point (d)
approver_refYour reference for the person who approved the file.your referenceArticle 20(1)

aml.list-version · Sanctions list version held

When: Each time you take in a new version of a targeted financial sanctions list: its digest and publication date are sealed, so a screening can later be tied to the list as it stood.

FieldWhat to put in itTypeMapped to
list_refYour reference for the list, such as eu-consolidated or un-sc.your referenceArticle 20(1), point (d)
Article 26
published_atWhen the list version was published by its source, UTC.UTC timeArticle 26
retrieved_atWhen you retrieved it, UTC.UTC timeArticle 26
list_digestSHA-256 of the list file exactly as retrieved.SHA-256Article 20(1), point (d)
Article 26

aml.screening · Customer screened against a sanctions list

When: At onboarding, at each periodic re-check, and upon a new designation.

FieldWhat to put in itTypeMapped to
customer_refYour reference for the customer, never a name.your referenceArticle 20(1), point (d)
Article 26
list_record_idThe record_id of the aml.list-version screened against.your referenceArticle 20(1), point (d)
Article 26
triggerWhy the screening was done.one of onboarding, periodic, new-designation, change-of-customer-dataArticle 20(1), point (d)
Article 26
screened_atWhen, UTC.UTC timeArticle 20(1), point (d)
Article 26
resultThe outcome.one of no-match, potential-match-cleared, potential-match-open, confirmed-matchArticle 20(1), point (d)
reviewer_ref (optional)Your reference for the person who cleared or confirmed a potential match.your referenceArticle 20(1), point (d)

The customer file, the list and the screening detail stay with you; only their digests are sealed. A sealed screening shows which list version was checked and when, not that the check was right.

Consumer Credit Directive · pack ccd version 1

Consumer credit: the creditworthiness assessment and the right to human intervention

What a creditor records so it can show that a thorough creditworthiness assessment was made before the credit agreement, on which data and with which model, and that a consumer who asked for human intervention, an explanation or a review got one.

The law
Directive (EU) 2023/2225 (Consumer Credit Directive) (CELEX 32023L2225)
Kinds
credit.creditworthiness-assessment creditworthiness assessed
credit.human-intervention human intervention, explanation or review given
The file
/packs/ccd.json, with an example record for every kind
How long to keep it
Article 18 does not state how long to keep these records, and this pack does not decide it for you. The directive applies from 20 November 2026 as transposed in each Member State; check your national law.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Directive (EU) 2023/2225, Article 18(1)Before concluding a credit agreement, the creditor carries out a thorough assessment of the consumer's creditworthiness, in the consumer's interest, to prevent irresponsible lending practices and over-indebtedness.credit.creditworthiness-assessment: application_ref, assessed_at, inputs_digest, model_version_digest, outcome, assessor_ref
Directive (EU) 2023/2225, Article 18(8)Where the assessment involves automated processing of personal data, the consumer has the right to request and obtain human intervention on the part of the creditor, an explanation of the assessment, and to express their point of view and request a review of the assessment and of the decision.credit.creditworthiness-assessment: model_version_digest, automated
credit.human-intervention: application_ref, assessment_record_id, requested, requested_at, answered_at, reviewer_ref, decision_changed, explanation_digest

credit.creditworthiness-assessment · Creditworthiness assessed

When: When the assessment is made, before the agreement is concluded: the inputs and the model are sealed by their digests, so the assessment can be shown to have come first.

FieldWhat to put in itTypeMapped to
application_refYour reference for the credit application.your referenceArticle 18(1)
assessed_atWhen the assessment was made, UTC.UTC timeArticle 18(1)
inputs_digestSHA-256 of the data the assessment used, exactly as used (for example, a manifest of the documents and figures).SHA-256Article 18(1)
model_version_digest (optional)SHA-256 of the scoring model or rule set used, if one was.SHA-256Article 18(1)
Article 18(8)
automatedWhether the assessment involved automated processing of personal data.true or falseArticle 18(8)
outcomeThe result of the assessment.one of positive, negative, referredArticle 18(1)
assessor_ref (optional)Your reference for the person who made or approved the assessment, if a person did.your referenceArticle 18(1)

credit.human-intervention · Human intervention, explanation or review given

When: Each time a consumer asks for human intervention, an explanation or a review of an automated assessment, and when it is given.

FieldWhat to put in itTypeMapped to
application_refYour reference for the credit application.your referenceArticle 18(8)
assessment_record_idThe record_id of the assessment concerned.your referenceArticle 18(8)
requestedWhat the consumer asked for.list of human-intervention, explanation, reviewArticle 18(8)
requested_atWhen the consumer asked, UTC.UTC timeArticle 18(8)
answered_atWhen it was given, UTC.UTC timeArticle 18(8)
reviewer_refYour reference for the person who intervened or reviewed.your referenceArticle 18(8)
decision_changedWhether the review changed the decision.true or falseArticle 18(8)
explanation_digest (optional)SHA-256 of the explanation given, exactly as given.SHA-256Article 18(8)

Mortgage credit is outside this directive. Where the assessment uses a high-risk AI system, the AI Act pack covers its logs; where a decision is based solely on automated processing, the GDPR Article 22 pack covers the safeguards that apply.

EU Clinical Trials Regulation · pack clinical-trials version 1

Clinical trials: the trial master file, safety reports and serious breaches

What a sponsor or an investigator records so that the essential documents of a clinical trial, the safety reports exchanged during it and the archive kept after it can be shown later to be exactly what existed at the time, and any alteration to be traceable.

The law
Regulation (EU) No 536/2014 (Clinical Trials Regulation) (CELEX 32014R0536)
Kinds
clinical.tmf-document essential document filed in the trial master file
clinical.tmf-archive trial master file archived
clinical.adverse-event-report adverse event report sent or received
clinical.serious-breach-notification serious breach notified
The file
/packs/clinical-trials.json, with an example record for every kind
How long to keep it
Article 58 sets at least 25 years after the end of the trial for the content of the clinical trial master file, unless other Union law requires longer; subjects' medical files follow national law. This pack does not decide your period.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Regulation (EU) No 536/2014, Article 41(2)The investigator records and documents all adverse events, unless the protocol provides differently, and reports serious adverse events to the sponsor without undue delay and not later than 24 hours after becoming aware of them, unless the protocol provides that no immediate reporting is required, with a follow-up report where relevant.clinical.adverse-event-report: trial_ref, report_ref, role, seriousness, report_type, aware_at, reported_at, report_digest
Regulation (EU) No 536/2014, Article 41(3)The sponsor keeps detailed records of all adverse events reported to it by the investigator.clinical.adverse-event-report: trial_ref, report_ref, role, reported_at, report_digest
Regulation (EU) No 536/2014, Article 52(1)The sponsor notifies the Member States concerned, through the EU portal, of a serious breach of the Regulation or of the protocol version applicable at the time, without undue delay and not later than seven days after becoming aware of it.clinical.serious-breach-notification: trial_ref, breach_ref, aware_at, notified_at, notification_digest
Regulation (EU) No 536/2014, Article 57The sponsor and the investigator each keep a clinical trial master file that at all times contains the essential documents allowing the conduct of the trial and the quality of the data generated to be verified, readily available and directly accessible to the Member States on request.clinical.tmf-document: trial_ref, holder, site_ref, document_type, document_version, document_digest, filed_at
Regulation (EU) No 536/2014, Article 58, first paragraphUnless other Union law requires longer, the sponsor and the investigator archive the content of the clinical trial master file for at least 25 years after the end of the trial; the medical files of subjects are archived in accordance with national law.clinical.tmf-archive: trial_ref, holder, trial_end_date, archived_at, retain_until
Regulation (EU) No 536/2014, Article 58, fifth paragraphThe media used to archive the content of the clinical trial master file keep it complete and legible throughout the archiving period.clinical.tmf-archive: manifest_digest, file_count, reason
Regulation (EU) No 536/2014, Article 58, sixth paragraphAny alteration to the content of the clinical trial master file is traceable.clinical.tmf-document: document_version, document_digest, previous_version_record_id
clinical.tmf-archive: manifest_digest, reason, previous_archive_record_id

clinical.tmf-document · Essential document filed in the trial master file

When: Each time an essential document, or a new version of one, is filed: a protocol version, an informed consent form, a monitoring report, a signed agreement.

FieldWhat to put in itTypeMapped to
trial_refThe trial's EU trial number, or your own reference for the trial.your referenceArticle 57
holderWhose trial master file this is: the sponsor's or an investigator's.one of sponsor, investigatorArticle 57
site_ref (optional)Your reference for the trial site, for an investigator's file.your referenceArticle 57
document_typeWhat the document is, in your own taxonomy, such as protocol or monitoring-report.one lineArticle 57
document_versionThe document's version, as written on it.one lineArticle 57
Article 58, sixth paragraph
document_digestSHA-256 of the document file exactly as filed.SHA-256Article 57
Article 58, sixth paragraph
filed_atWhen it was filed, UTC.UTC timeArticle 57
previous_version_record_id (optional)The record_id of the version this one replaces, so every alteration is traceable and the earlier version stays sealed.your referenceArticle 58, sixth paragraph

clinical.tmf-archive · Trial master file archived

When: When the content of a trial master file is archived after the end of the trial, and again when it is moved to new media or transferred to a new owner.

FieldWhat to put in itTypeMapped to
trial_refThe trial's EU trial number, or your own reference for the trial.your referenceArticle 58, first paragraph
holderWhose trial master file this is: the sponsor's or an investigator's.one of sponsor, investigatorArticle 58, first paragraph
trial_end_dateThe end of the trial, from which the archiving period runs.dateArticle 58, first paragraph
archived_atWhen the archive was closed, UTC.UTC timeArticle 58, first paragraph
manifest_digestSHA-256 of the archive's file list, one line per file with its own SHA-256, such as the list a folder seal produces.SHA-256Article 58, fifth paragraph
Article 58, sixth paragraph
file_countHow many files the archive holds, so a file left out shows.whole numberArticle 58, fifth paragraph
reasonWhy this archive record was made.one of archived, media-migration, ownership-transferArticle 58, fifth paragraph
Article 58, sixth paragraph
previous_archive_record_id (optional)The record_id of the archive record this one follows, after a migration or a transfer.your referenceArticle 58, sixth paragraph
retain_until (optional)The date until which you have decided to keep the archive.dateArticle 58, first paragraph

clinical.adverse-event-report · Adverse event report sent or received

When: Each time an investigator sends, or a sponsor receives, a report of an adverse event: the initial report and each follow-up.

FieldWhat to put in itTypeMapped to
trial_refThe trial's EU trial number, or your own reference for the trial.your referenceArticle 41(2)
Article 41(3)
report_refYour reference for the report; never the subject's name or a direct identifier.your referenceArticle 41(2)
Article 41(3)
roleWhether you sent the report as investigator or received it as sponsor.one of investigator-sent, sponsor-receivedArticle 41(2)
Article 41(3)
seriousnessWhether the event was reported as serious.one of serious, non-seriousArticle 41(2)
report_typeWhether this is the first report or a follow-up.one of initial, follow-upArticle 41(2)
aware_at (optional)When the investigator became aware of the event, UTC; the 24-hour period runs from here.UTC timeArticle 41(2)
reported_atWhen the report was sent or received, UTC.UTC timeArticle 41(2)
Article 41(3)
report_digestSHA-256 of the report exactly as sent or received.SHA-256Article 41(2)
Article 41(3)

clinical.serious-breach-notification · Serious breach notified

When: When the sponsor notifies a serious breach through the EU portal.

FieldWhat to put in itTypeMapped to
trial_refThe trial's EU trial number, or your own reference for the trial.your referenceArticle 52(1)
breach_refYour reference for the breach.your referenceArticle 52(1)
aware_atWhen the sponsor became aware of the breach, UTC; the seven days run from here.UTC timeArticle 52(1)
notified_atWhen the notification was submitted, UTC.UTC timeArticle 52(1)
notification_digestSHA-256 of the notification exactly as submitted.SHA-256Article 52(1)

Only digests are sent; the documents, the reports and anything about a subject stay with you. A new version is a new record that names the one it replaces, and the earlier one stays sealed, so an alteration shows as a chain of records rather than an overwrite. A record evidences what existed and when; whether a document is an essential document, and whether a deadline was met, is for the sponsor and the investigator to establish.

Cyber Resilience Act · pack cra version 1

Cyber Resilience Act: what shipped, its components, and when a vulnerability was reported

What a manufacturer of a product with digital elements records so it can show what it released, with which components, and that each report about an actively exploited vulnerability was sent within its deadline. The release and the reports stay with you; only their digests are sealed.

The law
Regulation (EU) 2024/2847 (Cyber Resilience Act) (CELEX 32024R2847)
Kinds
cra.release release made available
cra.vulnerability-report report on an actively exploited vulnerability sent
The file
/packs/cra.json, with an example record for every kind
How long to keep it
The regulation requires the technical documentation to be kept for at least ten years after the product is placed on the market, or for the support period if that is longer. Article 14 has applied since 11 September 2026; most other obligations apply from 11 December 2027. This pack does not decide your period.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Regulation (EU) 2024/2847, Article 13Manufacturers place products with digital elements on the market only if they meet the essential cybersecurity requirements of Annex I, whose Part II includes identifying and documenting the product's vulnerabilities and components, among other things by drawing up a software bill of materials.cra.release: product_ref, sbom_digest, sbom_format, support_period_end
Regulation (EU) 2024/2847, Article 31The technical documentation, with the contents Annex VII sets out, is drawn up before the product is placed on the market and kept up to date.cra.release: product_ref, version, released_at, artefact_digest, sbom_digest
Regulation (EU) 2024/2847, Article 14(1)Notify any actively exploited vulnerability in the product that the manufacturer becomes aware of, simultaneously to the CSIRT designated as coordinator and to ENISA, via the single reporting platform.cra.vulnerability-report: product_ref, vulnerability_ref, aware_at, submitted_at, report_digest
Regulation (EU) 2024/2847, Article 14(2)An early warning within 24 hours of becoming aware, a vulnerability notification within 72 hours, and a final report no later than 14 days after a corrective or mitigating measure is available.cra.vulnerability-report: vulnerability_ref, stage, aware_at, corrective_measure_at, submitted_at, report_digest

cra.release · Release made available

When: Each time a version is released: the artefact and its software bill of materials are sealed by their digests at that moment. A SCITT Signed Statement (POST /api/v2/evidence/statement) does the same for a supply chain that already speaks SCITT.

FieldWhat to put in itTypeMapped to
product_refYour reference for the product.your referenceArticle 13
Article 31
versionThe version released.one lineArticle 31
released_atWhen it was made available, UTC.UTC timeArticle 31
artefact_digestSHA-256 of the released artefact exactly as shipped.SHA-256Article 31
sbom_digestSHA-256 of the software bill of materials for this release.SHA-256Article 13
Article 31
sbom_format (optional)The format of the bill of materials.one of cyclonedx, spdx, otherArticle 13
support_period_end (optional)The end of the support period you declared for this product.dateArticle 13

cra.vulnerability-report · Report on an actively exploited vulnerability sent

When: Each time something is sent: the early warning, the vulnerability notification, the final report. The deadlines run from aware_at, and for the final report from the corrective measure.

FieldWhat to put in itTypeMapped to
product_refYour reference for the product.your referenceArticle 14(1)
vulnerability_refYour reference for the vulnerability, or its CVE identifier.your referenceArticle 14(1)
Article 14(2)
stageWhat was sent.one of early-warning, vulnerability-notification, final-reportArticle 14(2)
aware_atWhen you became aware of the active exploitation, UTC.UTC timeArticle 14(1)
Article 14(2)
corrective_measure_at (optional)When a corrective or mitigating measure became available, UTC; the final report's deadline runs from here.UTC timeArticle 14(2)
submitted_atWhen it was sent, UTC.UTC timeArticle 14(1)
Article 14(2)
report_digestSHA-256 of what was sent, exactly as sent.SHA-256Article 14(1)
Article 14(2)

Whether a product is in scope, and in which class, is for the manufacturer to establish from the regulation. `node tools/deadline.mjs` checks the times of sealed reports against the 24-hour, 72-hour and 14-day deadlines.

DORA · pack dora version 1

ICT incidents, incident reports and the register of information

What a financial entity records so that its incident log, the reports it sent to its competent authority and its register of ICT third-party arrangements can be shown later to be exactly what existed at each date.

The law
Regulation (EU) 2022/2554 (Digital Operational Resilience Act) (CELEX 32022R2554)
Kinds
dora.incident incident recorded at a stage
dora.incident-report report submitted to the competent authority
dora.register-snapshot register of information at a date
The file
/packs/dora.json, with an example record for every kind
How long to keep it
This pack does not state how long to keep these records. Check the period with your competent authority.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Regulation (EU) 2022/2554, Article 17(1)Define, establish and implement an ICT-related incident management process to detect, manage and notify ICT-related incidents.dora.incident: stage, detected_at, stage_at
Regulation (EU) 2022/2554, Article 17(2)Record all ICT-related incidents and significant cyber threats, with procedures for consistent monitoring, handling and follow-up so root causes are identified, documented and addressed.dora.incident: incident_ref, category, description, root_cause, actions
Regulation (EU) 2022/2554, Article 18Classify ICT-related incidents and determine their impact against the criteria the article sets.dora.incident: classification, services_affected
Regulation (EU) 2022/2554, Article 19(4)For a major ICT-related incident, submit to the competent authority an initial notification, an intermediate report and a final report.dora.incident-report: incident_ref, report_type, authority, report_digest, submission_ref, submitted_at
Regulation (EU) 2022/2554, Article 28(3)Maintain and update a register of information on all contractual arrangements for ICT services provided by ICT third-party service providers.dora.register-snapshot: as_of, register_digest, arrangements, purpose

dora.incident · Incident recorded at a stage

When: At each stage of an ICT-related incident or significant cyber threat: detected, classified, resolved, closed.

FieldWhat to put in itTypeMapped to
incident_refYour reference for the incident.your referenceArticle 17(2)
stageThe stage this record captures.one of detected, classified, resolved, closedArticle 17(1)
categoryWhether it is an incident or a significant cyber threat.one of ict-related-incident, significant-cyber-threatArticle 17(2)
classificationYour classification under Article 18 at this stage.one of major, not-major, not-yet-classifiedArticle 18
services_affected (optional)Your references for the services affected.list of your referenceArticle 18
descriptionWhat happened, as known at this stage.textArticle 17(2)
root_cause (optional)The root cause, once identified.textArticle 17(2)
actions (optional)What was done, and what will be done to prevent recurrence.textArticle 17(2)
detected_atWhen the incident was detected, UTC.UTC timeArticle 17(1)
stage_atWhen this stage was reached, UTC.UTC timeArticle 17(1)

dora.incident-report · Report submitted to the competent authority

When: When an initial notification, an intermediate report or a final report is submitted.

FieldWhat to put in itTypeMapped to
incident_refYour reference for the incident.your referenceArticle 19(4)
report_typeWhich report.one of initial-notification, intermediate-report, final-reportArticle 19(4)
authorityThe competent authority it went to.one lineArticle 19(4)
report_digestSHA-256 of the report exactly as submitted.SHA-256Article 19(4)
submission_ref (optional)The authority's acknowledgement reference, if any.your referenceArticle 19(4)
submitted_atWhen it was submitted, UTC.UTC timeArticle 19(4)

dora.register-snapshot · Register of information at a date

When: Each time the register is updated, and when it is submitted.

FieldWhat to put in itTypeMapped to
as_ofThe date the register describes.dateArticle 28(3)
register_digestSHA-256 of the register file exactly as kept or submitted.SHA-256Article 28(3)
arrangementsHow many contractual arrangements it lists.whole numberArticle 28(3)
file_format (optional)The format of the file, as your authority names it.one line–
purposeWhether this is an internal update or the version submitted.one of update, submissionArticle 28(3)

The reports themselves go to your authority by its own channel; the log never sends anything to anyone. What the log adds is that the report you hold today can be shown to be the one you held on the day you submitted it.

GDPR consent and erasure · pack gdpr-accountability version 1

GDPR accountability: consent given and withdrawn, and erasure carried out

What a controller records so it can show that a person consented, to which notice and for which purpose, that a withdrawal was honoured, and that a record it had to erase was erased on time. The records hold no personal data beyond your own references, and the personal data they refer to stays erasable in your systems.

The law
Regulation (EU) 2016/679 (General Data Protection Regulation) (CELEX 32016R0679)
Kinds
gdpr.consent consent given or withdrawn
gdpr.erasure erasure carried out
The file
/packs/gdpr-accountability.json, with an example record for every kind
How long to keep it
The GDPR states no fixed period for these records: keep them as long as you may need to demonstrate the consent or the erasure, and no longer. This pack does not decide it for you.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Regulation (EU) 2016/679, Article 5(2)The controller is responsible for, and must be able to demonstrate, compliance with the principles in Article 5(1).gdpr.consent: subject_ref, notice_digest
gdpr.erasure: subject_ref, erased_at, erased_record_digests, systems
Regulation (EU) 2016/679, Article 7(1)Where processing is based on consent, the controller must be able to demonstrate that the person consented to the processing of their personal data.gdpr.consent: subject_ref, event, purposes, notice_digest, notice_version, channel, at
Regulation (EU) 2016/679, Article 7(3)The person may withdraw consent at any time, withdrawing must be as easy as giving consent, and the person is informed of this before giving it.gdpr.consent: event, channel, at
Regulation (EU) 2016/679, Article 17(1)The person has the right to obtain the erasure of personal data concerning them without undue delay, and the controller must erase it without undue delay, where one of the grounds the article lists applies.gdpr.erasure: subject_ref, ground, requested_at, erased_at, systems

gdpr.consent · Consent given or withdrawn

When: Each time a person gives consent, and each time they withdraw it: one record per event, the notice they saw sealed by its digest.

FieldWhat to put in itTypeMapped to
subject_refYour own reference for the person, never their name or email.your referenceArticle 5(2)
Article 7(1)
eventWhether consent was given or withdrawn.one of given, withdrawnArticle 7(1)
Article 7(3)
purposesThe purposes consented to, as your own short codes.list of one lineArticle 7(1)
notice_digestSHA-256 of the notice exactly as the person saw it, so the wording they agreed to can be shown later.SHA-256Article 7(1)
Article 5(2)
notice_version (optional)Your version label for that notice.one lineArticle 7(1)
channelWhere the consent was given or withdrawn.one of web, app, email, paper, phone, in-person, otherArticle 7(1)
Article 7(3)
atWhen, UTC.UTC timeArticle 7(1)
Article 7(3)

gdpr.erasure · Erasure carried out

When: When personal data is erased on request or because its period has run out. The record that was erased can be referred to by its record_digest: the digest stays, the data goes.

FieldWhat to put in itTypeMapped to
subject_refYour own reference for the person, never their name or email.your referenceArticle 5(2)
Article 17(1)
groundWhy the data was erased.one of request, consent-withdrawn, objection, no-longer-necessary, unlawful, legal-obligation, retention-expiredArticle 17(1)
requested_at (optional)When the person asked, UTC, if they did.UTC timeArticle 17(1)
erased_atWhen the erasure was completed, UTC.UTC timeArticle 17(1)
Article 5(2)
erased_record_digests (optional)The record_digests of sealed records whose underlying data was erased. Each seal stays and now proves only that a record existed.list of SHA-256Article 5(2)
systemsYour references for the systems the data was erased from.list of your referenceArticle 5(2)
Article 17(1)

The records name people only by your own references; the personal data stays in your systems and erasable there. Recording a consent does not make it valid: whether consent was freely given, specific, informed and unambiguous is decided by the facts, not by the seal.

GDPR Article 22 · pack gdpr-art22 version 1

Automated individual decisions: basis, information and human intervention

What a controller records to show, for a decision based solely on automated processing, which exception it relied on, what the person was told, and what happened when they asked for a human to look again.

The law
Regulation (EU) 2016/679 (General Data Protection Regulation) (CELEX 32016R0679)
Kinds
gdpr.automated-decision automated decision taken
gdpr.human-intervention human intervention requested and handled
The file
/packs/gdpr-art22.json, with an example record for every kind
How long to keep it
This pack does not state how long to keep these records. The records are yours and hold personal data under your control: keep them no longer than your purposes need, and they stay erasable because they never leave you. Only a salted digest is in the log, and without the record and its salt nobody, including us, can link it to anyone.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Regulation (EU) 2016/679, Article 5(2)The controller is responsible for, and must be able to demonstrate, compliance with the principles in Article 5(1).gdpr.automated-decision: basis_ref, outcome, decided_at
gdpr.human-intervention: reasons
Regulation (EU) 2016/679, Article 13(2)(f) and Article 14(2)(g)Inform the person of the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4), and at least in those cases give meaningful information about the logic involved and the significance and envisaged consequences.gdpr.automated-decision: information_digest
Regulation (EU) 2016/679, Article 22(1)A person has the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning them or similarly significantly affects them.gdpr.automated-decision: subject_ref, decision_ref, solely_automated, significant_effect
Regulation (EU) 2016/679, Article 22(2)That does not apply where the decision is necessary for entering into or performing a contract, is authorised by Union or Member State law with suitable safeguards, or is based on the person's explicit consent.gdpr.automated-decision: exception, basis_ref
Regulation (EU) 2016/679, Article 22(3)Where the contract or explicit-consent exception applies, the controller implements suitable measures, at least the right to obtain human intervention, to express one's point of view and to contest the decision.gdpr.automated-decision: safeguards_offered
gdpr.human-intervention: subject_ref, decision_record_id, request, requested_at, reviewer_ref, result, reasons, concluded_at

gdpr.automated-decision · Automated decision taken

When: When a decision falling within Article 22(1) is taken, or when you conclude a decision does not fall within it.

FieldWhat to put in itTypeMapped to
subject_refYour pseudonymous reference for the person. Never a name, an email or a national number.your referenceArticle 22(1)
decision_refYour reference for the decision.your referenceArticle 22(1)
solely_automatedWhether the decision was based solely on automated processing.true or falseArticle 22(1)
significant_effectWhether it produces legal effects concerning the person or similarly significantly affects them.true or falseArticle 22(1)
exceptionThe Article 22(2) exception relied on, or that the decision is outside Article 22(1).one of contract, union-or-member-state-law, explicit-consent, not-within-article-22Article 22(2)
basis_ref (optional)Your reference for the contract, the legal provision or the consent record relied on.your referenceArticle 22(2)
Article 5(2)
information_digest (optional)SHA-256 of the notice given to the person about the automated decision, as given.SHA-256Article 13(2)(f) and Article 14(2)(g)
safeguards_offeredThe safeguards offered with the decision.list of human-intervention, express-point-of-view, contest-decisionArticle 22(3)
outcomeThe decision, in a short phrase.one lineArticle 5(2)
decided_atWhen the decision was taken, UTC.UTC timeArticle 5(2)

gdpr.human-intervention · Human intervention requested and handled

When: When the person asks for human intervention, expresses a point of view or contests the decision, and again when that request is concluded.

FieldWhat to put in itTypeMapped to
subject_refYour pseudonymous reference for the person. Never a name.your referenceArticle 22(3)
decision_record_idThe record_id of the gdpr.automated-decision record concerned.your referenceArticle 22(3)
requestWhat the person asked for.one of human-intervention, express-point-of-view, contest-decisionArticle 22(3)
requested_atWhen the request arrived, UTC.UTC timeArticle 22(3)
reviewer_ref (optional)Your reference for the person who reviewed. Never a name.your referenceArticle 22(3)
resultWhere the request stands, or how it ended.one of pending, upheld, changed, reversedArticle 22(3)
reasons (optional)Why the decision was upheld, changed or reversed.textArticle 22(3)
Article 5(2)
concluded_at (optional)When the review concluded, UTC.UTC timeArticle 22(3)

Recording that a decision was outside Article 22(1) is as useful as recording one inside it: it shows the question was asked at the time.

Insurance Distribution Directive · pack idd version 1

Insurance distribution: demands and needs, advice and product information

What an insurance distributor records to show, later, what the customer needed, what was proposed and why, and what information the customer received before the contract.

The law
Directive (EU) 2016/97 (Insurance Distribution Directive) (CELEX 32016L0097)
Kinds
idd.demands-needs demands and needs
idd.recommendation personalised recommendation
idd.ipid-provided product information document handed over
idd.pre-contract-disclosure pre-contract information provided
idd.product-version product version approved
The file
/packs/idd.json, with an example record for every kind
How long to keep it
This pack does not state how long to keep these records. Check the period that applies to you with your supervisor or your professional federation. In Belgium the directive is transposed by the Act of 4 April 2014 on insurance, and the FSMA supervises its conduct rules.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Directive (EU) 2016/97, Article 20(1), first subparagraphBefore a contract is concluded, specify the customer's demands and needs on the basis of information obtained from the customer, and give objective information about the product in a comprehensible form.idd.demands-needs: customer_ref, product_class, information_obtained, demands_and_needs, specified_at
Directive (EU) 2016/97, Article 20(1), second subparagraphAny contract proposed must be consistent with the customer's insurance demands and needs.idd.demands-needs: proposed_product_ref, consistency_note
Directive (EU) 2016/97, Article 20(1), third subparagraphWhere advice is given before a specific contract is concluded, give the customer a personalised recommendation explaining why a particular product would best meet their demands and needs.idd.demands-needs: advice_given
idd.recommendation: customer_ref, demands_needs_record_id, recommended_product_ref, reasons, document_digest, given_at
Directive (EU) 2016/97, Article 20, paragraphs 4 to 9For non-life products, give the product information by way of the standardised insurance product information document (IPID).idd.ipid-provided: customer_ref, product_ref, ipid_version, ipid_digest, provided_at
idd.pre-contract-disclosure: contract_ref, documents, provided_at
Directive (EU) 2016/97, Article 23How information reaches the customer: on paper, or on another durable medium or a website where the conditions for that are met.idd.recommendation: document_digest, medium
idd.ipid-provided: medium
idd.pre-contract-disclosure: customer_ref, contract_ref, documents, medium, provided_at, product_version_record_id
Directive (EU) 2016/97, Article 25(1)Insurance undertakings, and intermediaries that manufacture insurance products, maintain, operate and review a process for the approval of each insurance product, or significant adaptation of an existing one, before it is marketed or distributed to customers.idd.product-version: product_ref, version, terms_digest, target_market_digest, approved_at, effective_from

idd.demands-needs · Demands and needs

When: Once the customer's demands and needs are specified, before any contract is concluded.

FieldWhat to put in itTypeMapped to
customer_refYour own reference for the customer. Never a name.your referenceArticle 20(1), first subparagraph
product_classThe class of cover discussed, in your own terms, such as motor or home.one lineArticle 20(1), first subparagraph
information_obtainedWhat the customer told you, and how you obtained it.textArticle 20(1), first subparagraph
demands_and_needsThe demands and needs you specified from that information.textArticle 20(1), first subparagraph
proposed_product_ref (optional)Your reference for the product you proposed, if any.your referenceArticle 20(1), second subparagraph
consistency_note (optional)Why the proposed contract is consistent with those demands and needs.textArticle 20(1), second subparagraph
advice_givenWhether you gave advice. If true, an idd.recommendation record follows.true or falseArticle 20(1), third subparagraph
adviser_ref (optional)Your reference for the person who handled the customer. Never a name.your reference–
specified_atWhen the demands and needs were specified, UTC.UTC timeArticle 20(1), first subparagraph

idd.recommendation · Personalised recommendation

When: When advice is given, once the recommendation is handed to the customer.

FieldWhat to put in itTypeMapped to
customer_refYour own reference for the customer. Never a name.your referenceArticle 20(1), third subparagraph
demands_needs_record_idThe record_id of the idd.demands-needs record this recommendation answers.your referenceArticle 20(1), third subparagraph
recommended_product_refYour reference for the product recommended.your referenceArticle 20(1), third subparagraph
reasonsWhy this product would best meet the customer's demands and needs.textArticle 20(1), third subparagraph
document_digest (optional)SHA-256 of the recommendation document exactly as the customer received it.SHA-256Article 20(1), third subparagraph
Article 23
mediumHow the recommendation reached the customer.one of paper, durable-medium, websiteArticle 23
given_atWhen the recommendation was given, UTC.UTC timeArticle 20(1), third subparagraph

idd.ipid-provided · Product information document handed over

When: For a non-life product, when the IPID is given to the customer.

FieldWhat to put in itTypeMapped to
customer_refYour own reference for the customer. Never a name.your referenceArticle 20, paragraphs 4 to 9
product_refYour reference for the product.your referenceArticle 20, paragraphs 4 to 9
ipid_versionThe version of the IPID, as the manufacturer labels it.one lineArticle 20, paragraphs 4 to 9
ipid_digestSHA-256 of the IPID file exactly as handed over.SHA-256Article 20, paragraphs 4 to 9
mediumHow the IPID reached the customer.one of paper, durable-medium, websiteArticle 23
provided_atWhen it was provided, UTC.UTC timeArticle 20, paragraphs 4 to 9

idd.pre-contract-disclosure · Pre-contract information provided

When: When the pre-contract documents reach the customer: each is sealed by its digest, and the customer can be given the receipt too, so both sides hold the same evidence of what was provided.

FieldWhat to put in itTypeMapped to
customer_refYour reference for the customer, never a name.your referenceArticle 23
contract_refYour reference for the proposed contract.your referenceArticle 23
Article 20, paragraphs 4 to 9
documentsSHA-256 of each document provided, exactly as provided (the IPID, the terms, the demands-and-needs statement).list of SHA-256Article 23
Article 20, paragraphs 4 to 9
mediumHow the documents were provided.one of paper, durable-medium, websiteArticle 23
provided_atWhen they were provided, UTC.UTC timeArticle 23
Article 20, paragraphs 4 to 9
product_version_record_id (optional)The record_id of the idd.product-version in force.your referenceArticle 23

idd.product-version · Product version approved

When: Each time a product, or a significant adaptation of it, is approved: its terms and target market are sealed by their digests, so which terms applied on a given day can be shown.

FieldWhat to put in itTypeMapped to
product_refYour reference for the product.your referenceArticle 25(1)
versionYour version label.one lineArticle 25(1)
terms_digestSHA-256 of the terms and conditions exactly as approved.SHA-256Article 25(1)
target_market_digest (optional)SHA-256 of the target market definition as approved.SHA-256Article 25(1)
approved_atWhen the product version was approved, UTC.UTC timeArticle 25(1)
effective_fromFrom when it may be distributed.dateArticle 25(1)

The Worker's own quote ledger (v1) can record what was proposed and priced; this pack covers what stays with you.

EU Medical Device Regulations (MDR and IVDR) · pack medical-devices version 1

Medical devices: technical documentation and incident reports

What a manufacturer of a medical device or an in vitro diagnostic records so that each version of its technical documentation, its declaration of conformity and its certificates, and each serious incident or field safety corrective action report, can be shown later to be exactly what existed at the time.

The law
Regulation (EU) 2017/745 (Medical Device Regulation) (CELEX 32017R0745)
Regulation (EU) 2017/746 (In Vitro Diagnostic Medical Devices Regulation) (CELEX 32017R0746)
Kinds
device.technical-documentation technical documentation, declaration or certificate version released
device.incident-report serious incident or field safety corrective action reported
The file
/packs/medical-devices.json, with an example record for every kind
How long to keep it
Article 10(8) of the MDR sets at least 10 years after the last device covered by the declaration of conformity has been placed on the market, and at least 15 years for implantable devices; Article 10(7) of the IVDR sets at least 10 years. This pack does not decide your period.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Regulation (EU) 2017/745, Article 10(4)Manufacturers of devices other than custom-made devices draw up and keep up to date technical documentation that allows the conformity of the device to be assessed, including the elements set out in Annexes II and III.device.technical-documentation: device_ref, document_type, document_version, document_digest, released_at, previous_version_record_id
Regulation (EU) 2017/745, Article 10(8)Manufacturers keep the technical documentation, the EU declaration of conformity and any relevant certificate, including amendments and supplements, available to the competent authorities for at least 10 years after the last device covered by the declaration has been placed on the market, and for implantable devices at least 15 years.device.technical-documentation: regulation, document_type, document_digest, implantable, retain_until
Regulation (EU) 2017/745, Article 87(1)Manufacturers report serious incidents and field safety corrective actions concerning devices made available on the Union market to the competent authorities, through the electronic system referred to in Article 92.device.incident-report: device_ref, regulation, report_ref, subject, submitted_at, report_digest
Regulation (EU) 2017/745, Article 87(3)A serious incident is reported immediately after the manufacturer has established, or finds reasonably possible, a causal relationship with its device, and not later than 15 days after becoming aware of it.device.incident-report: aware_at, submitted_at
Regulation (EU) 2017/745, Article 87(6)Where necessary to report in time, the manufacturer may submit an initial report that is incomplete, followed by a complete report.device.incident-report: report_type
Regulation (EU) 2017/746, Article 10(4)Manufacturers draw up and keep up to date technical documentation that allows the conformity of the device to be assessed, including the elements set out in Annexes II and III.device.technical-documentation: device_ref, document_type, document_version, document_digest, released_at, previous_version_record_id
Regulation (EU) 2017/746, Article 10(7)Manufacturers keep the technical documentation, the EU declaration of conformity and any relevant certificate, including amendments and supplements, available to the competent authorities for at least 10 years after the last device covered by the declaration has been placed on the market.device.technical-documentation: regulation, document_type, document_digest, retain_until
Regulation (EU) 2017/746, Article 82(1)Manufacturers report serious incidents and field safety corrective actions concerning devices made available on the Union market to the competent authorities, through the electronic system referred to in Article 87.device.incident-report: device_ref, regulation, report_ref, subject, submitted_at, report_digest
Regulation (EU) 2017/746, Article 82(3)A serious incident is reported immediately after the manufacturer has established, or finds reasonably possible, a causal relationship with its device, and not later than 15 days after becoming aware of it.device.incident-report: aware_at, submitted_at

device.technical-documentation · Technical documentation, declaration or certificate version released

When: Each time a version of the technical documentation, the EU declaration of conformity or a certificate, or an amendment or supplement to one, is released.

FieldWhat to put in itTypeMapped to
device_refYour reference for the device, or its Basic UDI-DI.your referenceArticle 10(4)
Article 10(4)
regulationWhich regulation the device falls under.one of mdr, ivdrArticle 10(8)
Article 10(7)
document_typeWhat was released.one of technical-documentation, declaration-of-conformity, certificateArticle 10(4)
Article 10(8)
Article 10(4)
Article 10(7)
document_versionThe version, as written on it.one lineArticle 10(4)
Article 10(4)
document_digestSHA-256 of the file exactly as released, or of the file list of a documentation folder, one line per file with its own SHA-256.SHA-256Article 10(4)
Article 10(8)
Article 10(4)
Article 10(7)
released_atWhen it was released, UTC.UTC timeArticle 10(4)
Article 10(4)
implantable (optional)Whether the device is implantable, for which the MDR's period is at least 15 years.true or falseArticle 10(8)
previous_version_record_id (optional)The record_id of the version this one replaces; the earlier version stays sealed.your referenceArticle 10(4)
Article 10(4)
retain_until (optional)The date until which you have decided to keep it.dateArticle 10(8)
Article 10(7)

device.incident-report · Serious incident or field safety corrective action reported

When: Each time a report is submitted to the competent authority: the initial report, each follow-up and the final report.

FieldWhat to put in itTypeMapped to
device_refYour reference for the device, or its Basic UDI-DI.your referenceArticle 87(1)
Article 82(1)
regulationWhich regulation the device falls under.one of mdr, ivdrArticle 87(1)
Article 82(1)
report_refYour reference for the report; never a patient's name or a direct identifier.your referenceArticle 87(1)
Article 82(1)
subjectWhat is reported.one of serious-incident, field-safety-corrective-actionArticle 87(1)
Article 82(1)
report_typeWhich report this is.one of initial, follow-up, finalArticle 87(6)
aware_atWhen you became aware of the incident, UTC; the reporting periods run from here.UTC timeArticle 87(3)
Article 82(3)
submitted_atWhen the report was submitted, UTC.UTC timeArticle 87(1)
Article 87(3)
Article 82(1)
Article 82(3)
report_digestSHA-256 of the report exactly as submitted.SHA-256Article 87(1)
Article 82(1)

Only digests are sent; the documentation and the reports stay with you, as does anything about a patient. A new version is a new record that names the one it replaces, and the earlier one stays sealed. Whether a device is in scope, in which class, and whether software that is a medical device is also a high-risk AI system under Article 6(1) of the AI Act, is for the manufacturer to establish; for such a system's logs, use the ai-act pack beside this one.

MiFID II · pack mifid2 version 1

Investment advice: the suitability assessment and the statement on suitability

What an investment firm records to show what it knew about the client when it advised, what it advised, and that the statement on suitability existed, unaltered, before the transaction.

The law
Directive 2014/65/EU (MiFID II) (CELEX 32014L0065)
Commission Delegated Regulation (EU) 2017/565 (CELEX 32017R0565)
Kinds
mifid.suitability suitability assessment
mifid.suitability-statement statement on suitability
mifid.call-recording conversation recorded
mifid.sustainability-reasons sustainability preferences not met
The file
/packs/mifid2.json, with an example record for every kind
How long to keep it
Article 16(7) states five years for the recordings and communications it covers, and up to seven years where the competent authority requests it. For the other records this pack covers, check the period with your competent authority; in Belgium the FSMA supervises these conduct rules.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Directive 2014/65/EU, Article 25(2)When providing investment advice or portfolio management, obtain the information needed on the client's knowledge and experience in the relevant investment field, financial situation including ability to bear losses, and investment objectives including risk tolerance, so as to recommend what is suitable.mifid.suitability: client_ref, service, knowledge_and_experience, financial_situation, ability_to_bear_losses, investment_objectives, risk_tolerance, assessed_at
Directive 2014/65/EU, Article 25(6)When providing investment advice, before the transaction is made, give the retail client a statement on suitability in a durable medium, specifying the advice given and how it meets the client's preferences, objectives and other characteristics.mifid.suitability-statement: client_ref, assessment_record_id, instruments, advice, how_it_meets_the_client, statement_digest, provided_at
Commission Delegated Regulation (EU) 2017/565, Article 54How the suitability assessment is carried out, and what the suitability report must contain.mifid.suitability: knowledge_and_experience, financial_situation, investment_objectives, other_preferences, method_ref
mifid.suitability-statement: how_it_meets_the_client
Commission Delegated Regulation (EU) 2017/565, Article 54(10), second and third subparagraphsA firm does not recommend or trade financial instruments as meeting a client's sustainability preferences when they do not meet them; it explains the reasons to the client and keeps records of those reasons. Where no financial instrument meets the client's sustainability preferences and the client decides to adapt them, the firm keeps records of the client's decision, including the reasons for it.mifid.sustainability-reasons: client_ref, assessment_record_id, situation, reasons, preferences_stated, preferences_adapted, recorded_at
Commission Delegated Regulation (EU) 2017/565, Article 72(1)Records are kept so the competent authority can access them readily and reconstitute each key stage, so any corrections or amendments and the contents before them can be easily ascertained, and so they cannot otherwise be manipulated or altered.mifid.suitability: assessed_at
mifid.suitability-statement: assessment_record_id, transaction_ref
mifid.call-recording: recording_digest
Directive 2014/65/EU, Article 16(7)Records include the recording of telephone conversations and electronic communications relating at least to transactions concluded when dealing on own account and to client order services, including those that do not result in a transaction; they are provided to the client on request and kept for five years and, where the competent authority requests it, up to seven years.mifid.call-recording: client_ref, channel, relates_to, started_at, ended_at, recording_digest, recording_format, order_refs

mifid.suitability · Suitability assessment

When: When the information for the suitability assessment has been obtained and assessed, before advice is given.

FieldWhat to put in itTypeMapped to
client_refYour own reference for the client. Never a name.your referenceArticle 25(2)
serviceThe service the assessment is for.one of investment-advice, portfolio-managementArticle 25(2)
knowledge_and_experienceThe client's knowledge and experience in the investment field relevant to the product or service.textArticle 25(2)
Article 54
financial_situationThe client's financial situation, as obtained.textArticle 25(2)
Article 54
ability_to_bear_lossesYour assessment of the client's ability to bear losses.one lineArticle 25(2)
investment_objectivesThe client's investment objectives.textArticle 25(2)
Article 54
risk_toleranceThe client's risk tolerance, in your own scale.one lineArticle 25(2)
other_preferences (optional)Any other preference your assessment method records.textArticle 54
method_ref (optional)Your reference for the questionnaire or method version used.your referenceArticle 54
adviser_ref (optional)Your reference for the adviser. Never a name.your reference–
assessed_atWhen the assessment was completed, UTC.UTC timeArticle 25(2)
Article 72(1)

mifid.suitability-statement · Statement on suitability

When: When the statement on suitability is given to the retail client, before the transaction is made.

FieldWhat to put in itTypeMapped to
client_refYour own reference for the client. Never a name.your referenceArticle 25(6)
assessment_record_idThe record_id of the mifid.suitability record the advice rests on.your referenceArticle 25(6)
Article 72(1)
instrumentsThe instruments advised, by identifier such as ISIN.list of your referenceArticle 25(6)
adviceThe advice given.textArticle 25(6)
how_it_meets_the_clientHow the advice meets the client's preferences, objectives and other characteristics.textArticle 25(6)
Article 54
statement_digestSHA-256 of the statement exactly as the client received it.SHA-256Article 25(6)
provided_atWhen the statement was provided, UTC. The log's own time bounds it from above.UTC timeArticle 25(6)
transaction_ref (optional)Your reference for the transaction that followed, if any.your referenceArticle 72(1)

mifid.call-recording · Conversation recorded

When: When a recorded telephone conversation or electronic communication ends: the recording is sealed by its digest at once, so it can be shown to be unedited whenever the client or the supervisor asks for it.

FieldWhat to put in itTypeMapped to
client_refYour reference for the client, never a name.your referenceArticle 16(7)
channelThe kind of communication.one of telephone, video, chat, email, otherArticle 16(7)
relates_toWhat the communication relates to.one of own-account-dealing, reception-transmission, execution, advice, otherArticle 16(7)
started_atWhen it started, UTC.UTC timeArticle 16(7)
ended_atWhen it ended, UTC.UTC timeArticle 16(7)
recording_digestSHA-256 of the recording file exactly as stored.SHA-256Article 16(7)
Article 72(1)
recording_format (optional)The file format, such as wav or opus.one lineArticle 16(7)
order_refs (optional)Your references for the orders or transactions it concerns.list of your referenceArticle 16(7)

mifid.sustainability-reasons · Sustainability preferences not met

When: When no financial instrument meets the sustainability preferences the client stated: when you explain why you do not recommend one as meeting them, or when the client decides to adapt them.

FieldWhat to put in itTypeMapped to
client_refYour own reference for the client. Never a name.your referenceArticle 54(10), second and third subparagraphs
assessment_record_idThe record_id of the mifid.suitability record in which the preferences were stated.your referenceArticle 54(10), second and third subparagraphs
situationWhich record this is: the reasons for not recommending an instrument as meeting the client's sustainability preferences, or the client's decision to adapt them.one of not-recommended-as-meeting, client-adapted-preferencesArticle 54(10), second and third subparagraphs
reasonsThe reasons explained to the client, or the reasons for the client's decision.textArticle 54(10), second and third subparagraphs
preferences_stated (optional)The sustainability preferences as the client stated them.textArticle 54(10), second and third subparagraphs
preferences_adapted (optional)The preferences as the client adapted them, when they did.textArticle 54(10), second and third subparagraphs
adviser_ref (optional)Your reference for the adviser. Never a name.your reference–
recorded_atWhen the explanation or the client's decision was recorded, UTC.UTC timeArticle 54(10), second and third subparagraphs

A correction is a new record whose supersedes field names the record it corrects; the earlier record stays in the log. That is how Article 72(1)'s requirement that corrections and earlier contents can be ascertained shows up in the evidence.

NIS2 and data breaches · pack nis2 version 1

Security incidents and logs: NIS2 incident handling and reporting, and personal-data breaches

What an organisation records so that, after a security incident, it can show which logs existed before the incident, what it knew and when, what it did, and what it reported to whom.

The law
Directive (EU) 2022/2555 (NIS2 Directive) (CELEX 32022L2555)
Regulation (EU) 2016/679 (General Data Protection Regulation) (CELEX 32016R0679)
Kinds
security.log-segment log segment sealed
security.incident incident recorded at a stage
security.notification report or notification sent
The file
/packs/nis2.json, with an example record for every kind
How long to keep it
Neither NIS2 nor GDPR Article 33(5) states how long to keep these records, and this pack does not decide it for you. Check the period with your competent authority or supervisory authority.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Directive (EU) 2022/2555, Article 21(1)Essential and important entities take appropriate and proportionate technical, operational and organisational measures to manage the risks posed to the security of the network and information systems they use.security.log-segment: source_ref, log_digest
Directive (EU) 2022/2555, Article 21(2)(b)Those measures include incident handling.security.log-segment: source_ref, segment_index, segment_start, segment_end, line_count, log_digest, previous_segment_record_id
security.incident: incident_ref, stage, description, actions, stage_at, log_segment_record_ids
Directive (EU) 2022/2555, Article 23(1)Notify the CSIRT or, where applicable, the competent authority without undue delay of any significant incident, and where appropriate the recipients of the services concerned.security.incident: significant
security.notification: recipient
Directive (EU) 2022/2555, Article 23(4)For a significant incident: an early warning within 24 hours of becoming aware of it, an incident notification within 72 hours, an intermediate report on request, and a final report within one month of the incident notification.security.incident: aware_at
security.notification: incident_ref, stage, aware_at, submitted_at, report_digest
Regulation (EU) 2016/679, Article 33(1)Notify a personal data breach to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to people's rights and freedoms; a later notification gives the reasons for the delay.security.incident: aware_at
security.notification: incident_ref, stage, recipient, aware_at, submitted_at, report_digest, delay_reason
Regulation (EU) 2016/679, Article 33(5)Document every personal data breach, comprising the facts relating to it, its effects and the remedial action taken, so the supervisory authority can verify compliance with the article.security.log-segment: segment_start, segment_end, log_digest
security.incident: incident_ref, personal_data_breach, description, effects, actions, log_segment_record_ids
security.notification: report_digest
Regulation (EU) 2016/679, Article 34(1)When a breach is likely to result in a high risk to people's rights and freedoms, communicate it to the people concerned without undue delay.security.notification: stage, recipient

security.log-segment · Log segment sealed

When: Each time a segment of a system's log is closed: after a number of lines, a number of seconds, or a file rotation. The logseal tool in the recorder kit does this for you.

FieldWhat to put in itTypeMapped to
source_refYour reference for the system or log source, such as fw-edge-1 or auth-server.your referenceArticle 21(1)
Article 21(2)(b)
segment_indexThe position of this segment in its source's sequence, from 0, so a missing segment is caught.whole numberArticle 21(2)(b)
segment_startWhen the segment was opened, UTC.UTC timeArticle 21(2)(b)
Article 33(5)
segment_endWhen the segment was closed, UTC.UTC timeArticle 21(2)(b)
Article 33(5)
line_countHow many lines the segment holds, so a shortened segment is caught.whole numberArticle 21(2)(b)
log_digestSHA-256 of the segment exactly as archived.SHA-256Article 21(1)
Article 21(2)(b)
Article 33(5)
log_format (optional)The format of the lines, such as syslog, journald-json or cloudtrail-json.one line–
previous_segment_record_id (optional)The record_id of the segment before this one, so a removed segment is caught.your referenceArticle 21(2)(b)

security.incident · Incident recorded at a stage

When: At each stage of a security incident: detected, assessed, contained, resolved, closed.

FieldWhat to put in itTypeMapped to
incident_refYour reference for the incident.your referenceArticle 21(2)(b)
Article 33(5)
stageThe stage this record captures.one of detected, assessed, contained, resolved, closedArticle 21(2)(b)
significantWhether you consider it a significant incident under NIS2 at this stage.one of yes, no, not-yet-assessedArticle 23(1)
personal_data_breachWhether it is a personal data breach, as known at this stage.one of yes, no, not-yet-knownArticle 33(5)
descriptionThe facts, as known at this stage. Refer to people by your own references, never by name.textArticle 21(2)(b)
Article 33(5)
effects (optional)Its effects, as known at this stage.textArticle 33(5)
actions (optional)The remedial action taken, and what will be done to prevent recurrence.textArticle 21(2)(b)
Article 33(5)
aware_atWhen you became aware of the incident, UTC: the reporting deadlines run from here.UTC timeArticle 23(4)
Article 33(1)
stage_atWhen this stage was reached, UTC.UTC timeArticle 21(2)(b)
log_segment_record_ids (optional)The record_ids of the sealed log segments that cover the incident.list of your referenceArticle 21(2)(b)
Article 33(5)

security.notification · Report or notification sent

When: Each time something is sent about an incident: an early warning, a notification, an intermediate or final report, a breach notification, a communication to the people concerned.

FieldWhat to put in itTypeMapped to
incident_refYour reference for the incident.your referenceArticle 23(4)
Article 33(1)
stageWhat was sent.one of early-warning, incident-notification, intermediate-report, final-report, breach-notification, data-subject-communicationArticle 23(4)
Article 33(1)
Article 34(1)
recipientTo whom it was sent.one of csirt, competent-authority, supervisory-authority, service-recipients, data-subjectsArticle 23(1)
Article 33(1)
Article 34(1)
aware_atWhen you became aware of the incident, UTC, as stated in what was sent.UTC timeArticle 23(4)
Article 33(1)
submitted_atWhen it was sent, UTC.UTC timeArticle 23(4)
Article 33(1)
report_digestSHA-256 of what was sent, exactly as sent, so the copy you keep can be shown to be the one you sent.SHA-256Article 23(4)
Article 33(1)
Article 33(5)
delay_reason (optional)Why it was sent after the deadline, if it was.textArticle 33(1)

The logs never leave you: the logseal tool in the recorder kit archives each segment on your own storage and sends only the digest of its record. A segment sealed before an intruder controlled the machine that writes it cannot be changed afterwards without it showing; what that machine writes once it is controlled can be forged at the source, and no seal changes that. Financial entities under DORA report ICT incidents under DORA, whose own pack covers them.

Public procurement · pack procurement version 1

Public procurement: tenders received and evaluations fixed before prices are opened

What a contracting authority records so it can show which tenders it received and when, and that the quality scores were fixed before the prices were opened: the documentation that has to justify each decision in a procedure.

The law
Directive 2014/24/EU (public procurement) (CELEX 32014L0024)
Kinds
procurement.tender-received tender received
procurement.evaluation-freeze evaluation fixed at a stage
The file
/packs/procurement.json, with an example record for every kind
How long to keep it
Article 84(2) states at least three years from the date of award of the contract. Your national law or funding rules may set a longer period; this pack does not decide it for you.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Directive 2014/24/EU, Article 67(1)Contracting authorities base the award of public contracts on the most economically advantageous tender.procurement.evaluation-freeze: stage, criteria_digest
Directive 2014/24/EU, Article 84(2)Contracting authorities document the progress of all procurement procedures and keep sufficient documentation to justify decisions taken at all stages, such as on communications with economic operators, internal deliberations, selection and award; the documentation is kept for at least three years from the date of award.procurement.tender-received: procedure_ref, lot_ref, tenderer_ref, received_at, tender_digest
procurement.evaluation-freeze: procedure_ref, lot_ref, stage, frozen_at, criteria_digest, scores_digest, committee_refs

procurement.tender-received · Tender received

When: When each tender arrives, before anything is opened: its digest is sealed, so a tender cannot be swapped or backdated.

FieldWhat to put in itTypeMapped to
procedure_refYour reference for the procedure.your referenceArticle 84(2)
lot_ref (optional)The lot, if the procedure has lots.your referenceArticle 84(2)
tenderer_refYour reference for the tenderer.your referenceArticle 84(2)
received_atWhen it was received, UTC.UTC timeArticle 84(2)
tender_digestSHA-256 of the tender exactly as received (the archive the platform gives you).SHA-256Article 84(2)

procurement.evaluation-freeze · Evaluation fixed at a stage

When: When the committee fixes its scores at a stage, before the next stage begins: in particular, the quality scores before the price envelopes are opened.

FieldWhat to put in itTypeMapped to
procedure_refYour reference for the procedure.your referenceArticle 84(2)
lot_ref (optional)The lot, if the procedure has lots.your referenceArticle 84(2)
stageThe stage the scores belong to.one of selection, quality-before-price, awardArticle 84(2)
Article 67(1)
frozen_atWhen the scores were fixed, UTC.UTC timeArticle 84(2)
criteria_digestSHA-256 of the award criteria and weightings as published.SHA-256Article 67(1)
Article 84(2)
scores_digestSHA-256 of the score sheet exactly as fixed.SHA-256Article 84(2)
committee_refsYour references for the committee members who fixed it.list of your referenceArticle 84(2)

The tenders and the score sheets stay with you; only their digests are sealed. Utilities procurement under Directive 2014/25/EU and concessions under Directive 2014/23/EU have their own documentation articles, not mapped here.

VAT Directive invoices · pack vat-invoice version 1

Invoices: authenticity of origin and integrity of content from issue to the end of storage

What a business records so it can show that an invoice it issued or received has not been altered since the day it was issued, without sending the invoice anywhere. One business control among those the directive leaves to the taxable person.

The law
Council Directive 2006/112/EC (VAT Directive) (CELEX 32006L0112)
Kinds
invoice.issued invoice issued
invoice.received invoice received
The file
/packs/vat-invoice.json, with an example record for every kind
How long to keep it
Article 247(1) leaves the storage period to each Member State. This pack does not decide it for you; check the period where the supply takes place.

What each article asks, in our words, and where a record answers it

ArticleWhat it asks (our summary; the linked text is the law)Recorded in
Council Directive 2006/112/EC, Article 233(1)The authenticity of the origin, the integrity of the content and the legibility of an invoice, on paper or electronic, are ensured from the point in time of issue until the end of the period for storage; each taxable person determines how, for example by business controls that create a reliable audit trail between an invoice and a supply.invoice.issued: invoice_ref, issued_on, invoice_digest, invoice_format, supply_ref
invoice.received: supplier_ref, invoice_digest, invoice_format
Council Directive 2006/112/EC, Article 244Every taxable person ensures that copies of the invoices issued by it, by its customer or by a third party on its behalf, and all the invoices it has received, are stored.invoice.issued: invoice_ref, invoice_digest, customer_ref
invoice.received: invoice_ref, supplier_ref, received_at, invoice_digest

invoice.issued · Invoice issued

When: When the invoice is issued, before it is sent: the file exactly as issued is sealed by its digest.

FieldWhat to put in itTypeMapped to
invoice_refThe invoice number.your referenceArticle 233(1)
Article 244
issued_onThe date of issue on the invoice.dateArticle 233(1)
invoice_digestSHA-256 of the invoice file exactly as issued (the XML of an e-invoice, or the PDF).SHA-256Article 233(1)
Article 244
invoice_formatThe form of the invoice.one of peppol-bis-billing-3, en16931-ubl, en16931-cii, pdf, paper-scan, otherArticle 233(1)
customer_ref (optional)Your reference for the customer.your referenceArticle 244
supply_ref (optional)Your reference for the supply invoiced (an order or a delivery), the link in the audit trail.your referenceArticle 233(1)

invoice.received · Invoice received

When: When an invoice is received, before it is processed.

FieldWhat to put in itTypeMapped to
invoice_refThe supplier's invoice number.your referenceArticle 244
supplier_refYour reference for the supplier.your referenceArticle 244
Article 233(1)
received_atWhen it was received, UTC.UTC timeArticle 244
invoice_digestSHA-256 of the invoice file exactly as received.SHA-256Article 233(1)
Article 244
invoice_formatThe form of the invoice.one of peppol-bis-billing-3, en16931-ubl, en16931-cii, pdf, paper-scan, otherArticle 233(1)

The invoice never leaves you: only its digest is sealed. A seal shows the invoice has not changed since it was sealed; it does not show the invoice is correct or that VAT is due. Directive (EU) 2025/516 (ViDA) amends the invoicing rules from dates it sets; check the consolidated text.

Read this before using a pack

What a pack is not

A pack is a data format and a reading of the law, not legal advice, and using one does not make a firm meet any obligation. The summaries of articles are ours, written for orientation; the text on EUR-Lex, linked from each pack, is the law, and national rules and supervisory guidance add to it. We do not decide whether a regime applies to you. We never see your records, handle your customers, or report to your supervisor on your behalf.

The log accepts any kind, packed or not: a pack is a convention you may adopt, never a condition of using the API. The packs, like the specification, are published so that another implementation can read the same records without us. Something wrong in a summary or a mapping? Tell us, and the correction goes in the changelog.