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

Obligations · what the law already asks for

The law already asks for the record. It does not say how you will prove it.

Six EU laws ask a regulated firm to do something, and later to show it did: specify a customer’s needs, explain a recommendation, keep an AI system’s logs, record an incident. Each lets you keep that record in your own systems. None says how you will show, years later, that the record you produce is the one that existed at the time. Every system that stores a record can also edit it, so on the day a record is disputed, that is the question that decides.

This page sets out, for each law, what its articles ask, when the record gets tested, and what a record sealed in the evidence log adds. The summaries are ours and the linked EUR-Lex text is the law. It is orientation, not legal advice: whether an article applies to you, and from when, is yours to establish.

Fourteen laws, one question

LawWhen the record is testedWhat a sealed record adds
Insurance Distribution DirectiveA complaint to the insurer or the ombudsman, a claim refused because the cover did not match the need, a supervisor's inspection.The demands-and-needs note and the recommendation are sealed when they are written, so the note you produce is shown to be the one that existed before the contract, not one written after the complaint.
MiFID IIA client disputes the advice after a loss; the supervisor asks you to reconstitute each stage of it.A correction is a new sealed record that names the record it corrects, and the earlier one stays, so what was changed and what stood before can be ascertained, as Article 72(1) describes.
EU AI ActA person affected by a decision asks for an explanation; a market surveillance authority asks for the logs.Each log segment is sealed as it is written, with its event count and the segment before it, so a shortened, edited or missing segment shows.
GDPR Article 22A person contests an automated decision; the data protection authority asks you to demonstrate compliance.The basis of the decision, and any human review of it, are shown to have been recorded at the time, while the record, which holds personal data, stays with you and erasable.
NIS2 and data breachesA CSIRT or regulator asks what happened and when you knew; a cyber insurer assesses a claim; a customer or a court disputes your account of a breach.Logs sealed segment by segment before the incident cannot be rewritten afterwards without it showing, and each report you sent is shown to be the one you hold, sent when you say.
DORAYour authority reviews a major incident; an auditor compares the report you hold with the report you sent.The incident record and each report are sealed when they are made, so the report you hold today is shown to be the one you held on the day you submitted it.
GDPR consent and erasureA person says they never consented, or that their data was not erased; the data protection authority asks you to demonstrate it.Each consent is sealed with the notice the person saw, and each erasure when it is done, while the personal data stays in your systems and erasable.
Consumer Credit DirectiveA borrower in difficulty says the credit should never have been granted; a consumer asks for a human to review an automated assessment.The assessment is sealed with the digests of its inputs and its model before the agreement, so it can be shown to have come first, and each review is sealed when it is given.
Anti-Money Laundering RegulationA supervisor reviews a customer onboarded years ago, or asks which sanctions list you screened against on a given day.The customer file is sealed by the digests of its documents when it is approved, and each sanctions list and screening when it happens, so no document can be swapped in later and the list version is fixed.
Cyber Resilience ActA market surveillance authority asks for the technical documentation; a CSIRT or a customer asks when you knew of an exploited vulnerability and when you reported it.Each release is sealed with its software bill of materials, and each report when it is sent, so what shipped and when you reported are not your word alone.
VAT Directive invoicesA tax audit questions an invoice years later; a customer or supplier disputes what an invoice said.Each invoice is sealed by its digest when it is issued or received, a business control showing its content has not changed since, without the invoice leaving you.
Public procurementA losing tenderer challenges the award; an auditor asks you to justify the decision at each stage.Each tender is sealed when it arrives and the quality scores before the prices are opened, so neither can be shown to have changed afterwards.
EU Clinical Trials RegulationAn inspection of the trial master file; a question about a safety report, years after the trial; an archive moved to new media or a new owner.Each essential document is sealed when it is filed and each new version names the one it replaces, so any alteration to the file is traceable, as Article 58 asks, and the archive is shown complete by its file list.
EU Medical Device Regulations (MDR and IVDR)A notified body or a competent authority asks for the technical documentation that applied to a device on a given date; an incident report is questioned.Each version of the technical documentation, the declaration and the certificates is sealed when it is released, and each incident report when it is submitted, so the version that applied on a date, and when you reported, are not your word alone.

Insurance Distribution Directive

Who it concerns
Insurance distributors: brokers, agents, and insurers selling directly. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A complaint to the insurer or the ombudsman, a claim refused because the cover did not match the need, a supervisor's inspection.
What a sealed record adds
The demands-and-needs note and the recommendation are sealed when they are written, so the note you produce is shown to be the one that existed before the contract, not one written after the complaint.
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 to record
The Insurance Distribution Directive pack: idd.demands-needs, idd.recommendation, idd.ipid-provided, idd.pre-contract-disclosure, idd.product-version
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
Directive (EU) 2016/97, Article 20(1), second subparagraphAny contract proposed must be consistent with the customer's insurance demands and needs.
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.
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).
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.
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.

MiFID II

Who it concerns
Investment firms that give investment advice or manage portfolios. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A client disputes the advice after a loss; the supervisor asks you to reconstitute each stage of it.
What a sealed record adds
A correction is a new sealed record that names the record it corrects, and the earlier one stays, so what was changed and what stood before can be ascertained, as Article 72(1) describes.
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 to record
The MiFID II pack: mifid.suitability, mifid.suitability-statement, mifid.call-recording, mifid.sustainability-reasons
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
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.
Commission Delegated Regulation (EU) 2017/565, Article 54How the suitability assessment is carried out, and what the suitability report must contain.
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.
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.
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.

EU AI Act

Who it concerns
Providers and deployers of high-risk AI systems, which include risk assessment and pricing for natural persons in life and health insurance, and assessing the creditworthiness of natural persons (Annex III, point 5). Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A person affected by a decision asks for an explanation; a market surveillance authority asks for the logs.
What a sealed record adds
Each log segment is sealed as it is written, with its event count and the segment before it, so a shortened, edited or missing segment shows.
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 to record
The EU AI Act pack: ai.log-segment, ai.decision, ai.oversight, ai.model-provenance, ai.screening-criteria, ai.content-credential, ai.training-data
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
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)).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.

GDPR Article 22

Who it concerns
Any controller whose decisions about people are made, wholly or partly, by automated processing. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A person contests an automated decision; the data protection authority asks you to demonstrate compliance.
What a sealed record adds
The basis of the decision, and any human review of it, are shown to have been recorded at the time, while the record, which holds personal data, stays with you and erasable.
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 to record
The GDPR Article 22 pack: gdpr.automated-decision, gdpr.human-intervention
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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).
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.
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.
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.
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.

NIS2 and data breaches

Who it concerns
Essential and important entities under NIS2: medium-sized and large organisations in the sectors of its Annexes I and II, and some others whatever their size (Article 2); for personal-data breaches, every controller under the GDPR. Financial entities report ICT incidents under DORA instead. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A CSIRT or regulator asks what happened and when you knew; a cyber insurer assesses a claim; a customer or a court disputes your account of a breach.
What a sealed record adds
Logs sealed segment by segment before the incident cannot be rewritten afterwards without it showing, and each report you sent is shown to be the one you hold, sent when you say.
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 to record
The NIS2 and data breaches pack: security.log-segment, security.incident, security.notification
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
Directive (EU) 2022/2555, Article 21(2)(b)Those measures include incident handling.
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.
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.
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.
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.
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.

DORA

Who it concerns
Financial entities within DORA's scope, including insurers and insurance intermediaries, other than intermediaries that are micro, small or medium-sized enterprises (Article 2(3)). Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
Your authority reviews a major incident; an auditor compares the report you hold with the report you sent.
What a sealed record adds
The incident record and each report are sealed when they are made, so the report you hold today is shown to be the one you held on the day you submitted it.
How long to keep it
This pack does not state how long to keep these records. Check the period with your competent authority.
What to record
The DORA pack: dora.incident, dora.incident-report, dora.register-snapshot
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
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.
Regulation (EU) 2022/2554, Article 18Classify ICT-related incidents and determine their impact against the criteria the article sets.
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.
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.

GDPR consent and erasure

Who it concerns
Any controller that relies on consent, or that erases personal data on request or when its period runs out. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A person says they never consented, or that their data was not erased; the data protection authority asks you to demonstrate it.
What a sealed record adds
Each consent is sealed with the notice the person saw, and each erasure when it is done, while the personal data stays in your systems and erasable.
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 to record
The GDPR consent and erasure pack: gdpr.consent, gdpr.erasure
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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).
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.
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.
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.

Consumer Credit Directive

Who it concerns
Creditors granting consumer credit within the directive's scope, from 20 November 2026 as transposed in each Member State. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A borrower in difficulty says the credit should never have been granted; a consumer asks for a human to review an automated assessment.
What a sealed record adds
The assessment is sealed with the digests of its inputs and its model before the agreement, so it can be shown to have come first, and each review is sealed when it is given.
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 to record
The Consumer Credit Directive pack: credit.creditworthiness-assessment, credit.human-intervention
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
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.

Anti-Money Laundering Regulation

Who it concerns
Obliged entities under the Anti-Money Laundering Regulation, from 10 July 2027: credit and financial institutions, crypto-asset service providers, and the other entities it lists. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A supervisor reviews a customer onboarded years ago, or asks which sanctions list you screened against on a given day.
What a sealed record adds
The customer file is sealed by the digests of its documents when it is approved, and each sanctions list and screening when it happens, so no document can be swapped in later and the list version is fixed.
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 to record
The Anti-Money Laundering Regulation pack: aml.onboarding-file, aml.list-version, aml.screening
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
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.
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.
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.

Cyber Resilience Act

Who it concerns
Manufacturers of products with digital elements made available in the EU: reporting since 11 September 2026, most other obligations from 11 December 2027. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A market surveillance authority asks for the technical documentation; a CSIRT or a customer asks when you knew of an exploited vulnerability and when you reported it.
What a sealed record adds
Each release is sealed with its software bill of materials, and each report when it is sent, so what shipped and when you reported are not your word alone.
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 to record
The Cyber Resilience Act pack: cra.release, cra.vulnerability-report
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
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.
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.
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.

VAT Directive invoices

Who it concerns
Every taxable person that issues or receives invoices. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A tax audit questions an invoice years later; a customer or supplier disputes what an invoice said.
What a sealed record adds
Each invoice is sealed by its digest when it is issued or received, a business control showing its content has not changed since, without the invoice leaving you.
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 to record
The VAT Directive invoices pack: invoice.issued, invoice.received
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
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.

Public procurement

Who it concerns
Contracting authorities awarding public contracts under Directive 2014/24/EU. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A losing tenderer challenges the award; an auditor asks you to justify the decision at each stage.
What a sealed record adds
Each tender is sealed when it arrives and the quality scores before the prices are opened, so neither can be shown to have changed afterwards.
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 to record
The Public procurement pack: procurement.tender-received, procurement.evaluation-freeze
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
Directive 2014/24/EU, Article 67(1)Contracting authorities base the award of public contracts on the most economically advantageous tender.
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.

EU Clinical Trials Regulation

Who it concerns
Sponsors and investigators of clinical trials on medicinal products under Regulation (EU) No 536/2014, and the software that keeps their trial master files. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
An inspection of the trial master file; a question about a safety report, years after the trial; an archive moved to new media or a new owner.
What a sealed record adds
Each essential document is sealed when it is filed and each new version names the one it replaces, so any alteration to the file is traceable, as Article 58 asks, and the archive is shown complete by its file list.
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 to record
The EU Clinical Trials Regulation pack: clinical.tmf-document, clinical.tmf-archive, clinical.adverse-event-report, clinical.serious-breach-notification
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
Regulation (EU) No 536/2014, Article 41(3)The sponsor keeps detailed records of all adverse events reported to it by the investigator.
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.
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.
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.
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.
Regulation (EU) No 536/2014, Article 58, sixth paragraphAny alteration to the content of the clinical trial master file is traceable.

EU Medical Device Regulations (MDR and IVDR)

Who it concerns
Manufacturers of medical devices and in vitro diagnostics, including software that is itself a device. Whether it applies to you, and from when, is yours to establish from the text.
When it is tested
A notified body or a competent authority asks for the technical documentation that applied to a device on a given date; an incident report is questioned.
What a sealed record adds
Each version of the technical documentation, the declaration and the certificates is sealed when it is released, and each incident report when it is submitted, so the version that applied on a date, and when you reported, are not your word alone.
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 to record
The EU Medical Device Regulations (MDR and IVDR) pack: device.technical-documentation, device.incident-report
Article (links to the text on EUR-Lex)What it asks (our summary; the linked text is the law)
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.
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.
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.
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.
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.
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.
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.
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.
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.

What no law requires, and what the log does not do

No law names a product
None of these laws requires RiskRouter or any other product. You can meet every duty on this page without us. What we offer is a way to show you met it that does not depend on anyone’s word, including ours.
It proves when, not whether
A sealed record is shown to have existed, unchanged, no later than a signed and anchored head. The log does not know what the record says, so it cannot make a record correct, complete or sufficient, and recording something does not make anyone compliant.
The record stays with you
Only a salted fingerprint of each record is sent. The record, and any personal data in it, never reach us, so it stays yours to keep and to erase. Data protection
It outlives us
Every proof checks offline with the open-source verifier, against keys and anchors that are published. Continuity

To start, take a sandbox key and record a fingerprint in a few minutes, or read what to record, rule by rule.