The Late-Stage Compliance Risk Checklist: Can Your Team Show the Evidence?
A practical project review for hardware teams approaching launch: find missing decisions, outdated tests, and evidence gaps before they become release blockers.
Where could compliance still derail our launch?
Run an evidence-based readiness review and turn the gaps into owned recovery work.
“The testing is done.”
It is a comforting sentence. It is also incomplete. Testing of which configuration? Against which requirements? Before or after the supplier changed the motor?
Imagine a machine approaching launch. Its test reports are neatly filed, its risk spreadsheet is mostly green, and the declaration has been drafted. Then someone compares the tested prototype with the production bill of materials. The drive is different. The firmware is newer. Nobody has recorded whether either change affects the conclusions.
That is an illustrative scenario, not a reported customer case. It captures the problem this checklist is designed to find: reassuring status that cannot be connected to current evidence.
Use it to review your project before making a release commitment. It is a management tool, not a complete conformity assessment or permission to ship. For the underlying process, read the EU conformity assessment guide.
How to run the review
Bring the product lead, the relevant engineering owners, and whoever maintains the conformity documentation. Open the actual records. Work through one defined product configuration and its intended markets.
For each question, record one of three states:
- Evidence available: the team can show a reviewed record that applies to the intended release.
- Gap identified: the team knows what is missing and has assigned the work.
- Unknown: the team cannot yet determine whether the question is satisfied.
Record the evidence link, owner, next action, and date. These states are visibility markers; a green-looking sheet does not establish conformity. An unknown on a safety-critical matter requires investigation, not an optimistic colour change.
Ten questions that expose launch risk
1. Can we explain which rules apply to this product?
Show: a scope decision describing the product, intended use, market, relevant EU legislation, and assessment procedure, with unresolved classification questions called out.
Look for: a list copied from an earlier product, an assumption that a supplier's certificate covers your assembly, or disagreement about what your company is supplying.
Act: resolve the boundary and applicability before deciding whether existing evidence is sufficient. For machinery, the Machinery Directive article explains the scope and procedure decisions.
2. Does the risk assessment describe the current design and real tasks?
Show: the assessment revision, its product baseline, and coverage of relevant tasks across the lifecycle, including foreseeable misuse.
Look for: normal operation assessed carefully while cleaning, jam clearing, installation, or maintenance receives a single generic line. Also check whether design changes made since the assessment have been reviewed.
Act: reopen affected scenarios with the people who understand the work. A change in how the operator reaches a mechanism can matter as much as a change in the mechanism itself. The ISO 12100 guide explains the iteration.
3. Can we trace each significant risk to a completed measure?
Show: the connection from the hazardous situation to the design or protective measure, its implementation, and the assessment of remaining risk.
Look for: “guard added” with no drawing revision, “software fix” with no release version, or a warning used as the answer to an unresolved design problem.
Act: verify what was implemented and whether the risk reduction is adequate. For machinery, the order of safer design, protective measures, and residual-risk information comes from Annex I, section 1.1.2 of the Machinery Directive.
4. Are applicable essential requirements connected to evidence?
Show: for each applicable requirement, the engineering response and the evidence supporting it. Keep the rationale for non-applicability too.
Look for: a requirements list marked complete because a standard has been selected, even though its requirements have not been implemented or verified.
Act: distinguish choosing an approach from demonstrating that it works. Essential Requirements in Practice shows how to build that connection.
5. Do we know what our standards cover and what they leave open?
Show: relevant editions, applicability, citation status under the correct legislation, any restrictions, and identified gaps.
Look for: a standard number with no edition, a citation assumed from a catalogue search, or an unusual operating mode omitted because the standard does not discuss it.
Act: verify the official references and address uncovered requirements. Harmonised standards confer presumption only for the requirements they cover, under the conditions of the applicable legislation. The Commission's harmonised standards guidance explains their role.
6. Do test reports cover the configuration we plan to release?
Show: sample identification, hardware and software versions, operating conditions, test scope, acceptance criteria, results, and the treatment of deviations.
Look for: a report covering one variant while sales offers three, a prototype with different protective components, or a pass reported without the conditions attached to it.
Act: make the coverage explicit. A difference does not automatically invalidate a report, but it needs a competent impact review. Record why the result remains applicable or define the additional verification needed.
7. Have we settled required external assessment work?
Show: the chosen procedure and, where it requires notified-body involvement, the relevant scope, deliverables, and completed assessment outputs.
Look for: treating a lab booking as completion of the conformity procedure, or discovering that an external reviewer still needs a technical file that nobody has assembled.
Act: confirm the actual remaining work with the external partner. Identify inputs, review cycles, and dependencies. Put those dates in the same plan as the engineering work.
8. Do instructions match the machine and its remaining risks?
Show: reviewed instructions for the release configuration, required languages, safe operating and maintenance information, and treatment of residual risks.
Look for: illustrations from an earlier enclosure, a cleaning procedure that requires bypassing a safeguard, or translated text that has not followed the final design changes.
Act: review the instructions alongside the risk assessment and the physical product. For machinery, instruction requirements are specified in Annex I, section 1.7.4.
9. Could we assemble the technical file without relying on one person's memory?
Show: an index, controlled evidence links, access permissions, retention arrangements, and an identified person able to compile the documentation.
Look for: decisive evidence in an engineer's private folder, missing supplier documentation, or filenames that do not identify which product revision they cover.
Act: test retrieval now. Ask a colleague to follow the index and find the evidence for one significant requirement. Under the Machinery Directive, Annex VII specifies the technical file and its availability obligations.
10. Is there a controlled path from reviewed evidence to release?
Show: the release baseline, open issues, review responsibilities, declaration and marking checks, and a way to review changes after approval.
Look for: a signed declaration followed by an unreviewed component substitution, or release authorised on the promise that a missing safety test will probably pass.
Act: settle unresolved requirements before release and assess later changes before applying the previous conclusion to the new configuration. Machinery placed on the market or put into service from 20 January 2027 also needs a transition review against the new regulation. See what changes in 2027.
Turn findings into a recovery plan
Do not average the answers into a compliance score. Nine available records do not compensate for one unresolved serious hazard.
Instead, group the findings by what has to happen next: resolve applicability, change the design, validate a measure, obtain an external assessment, or recover missing documentation. Identify dependencies before promising dates.
Use a working table like this:
| Finding | Next action | Owner | Closure evidence | Release dependency |
|---|---|---|---|---|
| Production drive differs from tested prototype | Review effects on safety functions and affected tests | Controls lead | Recorded impact review and additional results where needed | Set before release decision |
| Cleaning task missing from assessment | Observe task and assess hazards | Mechanical lead | Updated assessment, measures, and validation | May affect enclosure and instructions |
| Supplier document missing | Obtain and check relevant document | Project lead | Reviewed document linked to component revision | Needed for file review |
These are examples, not judgements about a particular design. Your competent engineering review determines the consequences.
A useful review ends with a more precise schedule. It might reveal that the launch is on track. It might reveal work that changes the date. Either outcome gives the product lead something better than reassurance: a decision grounded in evidence.
Keep the next review smaller
If this exercise turns into a document hunt, the immediate task is recovering visibility. The lasting improvement is to capture the connections as the product changes.
Start with the minimum conformity assessment workflow. It describes the records, ownership, and review rhythm that let a small team find these problems during development, while there is still time to act.
Sources and scope
This checklist was reviewed on 8 October 2026. It uses machinery examples; other hardware needs assessment against its own applicable legislation. The review method and sample recovery table are practical recommendations.
- Machinery Directive 2006/42/EC, consolidated text — Articles 5 and 12; Annexes I and VII.
- European Commission: Harmonised standards — role and official references.
- European Commission: Machinery — current legislation and transition.