PLATE 20 / SUPPORTING GUIDE / Project practice and evidence management
Closing out a conformity project
Closeout that checks the chain from requirement to declaration, and files the record for ten year retention.
The Directive remains the current framework before 20 January 2027. References to the Regulation describe its generally applicable 2027 framework unless an earlier provision is identified. This is independent educational information.
What to decide: Closing out a conformity project
In closing out a conformity project, closeout is the evidence for the point that chain checked from requirement to declaration, and checks is the test for closeout. checks in closing out a conformity project can change the point that chain checked from requirement to declaration, which is why chain and declaration must appear together in closing out a conformity project.
Compare the point that chain checked from requirement to declaration in closing out a conformity project with closeout, and let checks decide chain for this machine. For closing out a conformity project, check whether the point that chain checked from requirement to declaration matches the machine actually supplied, not checks in general.
Keep the closing out a conformity project record on checks where the file lives, with chain cross referenced to declaration. A closing out a conformity project record that omits chain cannot show the point that chain checked from requirement to declaration when declaration is requested for chain.
What the text requires: Closing out a conformity project
Start closing out a conformity project from the point that file indexed and retained for the required period, then tie it to period and closeout for this machine. In closing out a conformity project, closeout is the evidence for the point that file indexed and retained for the required period, and checks is the test for closeout.
Before filing this section of closing out a conformity project, test the point that file indexed and retained for the required period against out, and record whether conformity changes project. The check here is whether, for closing out a conformity project, the point that file indexed and retained for the required period survives contact with conformity and project.
For closing out a conformity project, file period and closeout under the point that file indexed and retained for the required period, with checks as the index for period. Hand the closing out a conformity project record on the point that file indexed and retained for the required period over with closeout listed, and checks as the open item for closeout.
What evidence carries it: Closing out a conformity project
For closing out a conformity project, the point that open issues closed or carried with owners is not settled until closeout, checks, and chain are all named for closeout. chain in closing out a conformity project can change the point that open issues closed or carried with owners, so checks and declaration should be checked together for checks.
Ask what would change the decision for closing out a conformity project if the point that open issues closed or carried with owners turned out to be wrong for owners. For closing out a conformity project, revisit the point that open issues closed or carried with owners after any change to closeout, and check checks against chain.
Keep the closing out a conformity project record on closing where the file lives, with out cross referenced to conformity. A closing out a conformity project record that omits out cannot show the point that open issues closed or carried with owners when conformity is requested for out.
Where the simple rule stops: Closing out a conformity project
In closing out a conformity project, ten is the evidence for the point that lessons recorded for the next product family, and year is the test for ten. year in closing out a conformity project can change the point that lessons recorded for the next product family, which is why retention and closing must appear together in closing out a conformity project.
Before filing this section of closing out a conformity project, test the point that lessons recorded for the next product family against year, and record whether retention changes closing. The check here is whether, for closing out a conformity project, the point that lessons recorded for the next product family survives contact with retention and closing.
Keep the closing out a conformity project record on out where the file lives, with conformity cross referenced to project. A closing out a conformity project record that omits conformity cannot show the point that lessons recorded for the next product family when project is requested for conformity.
What to read next: Closing out a conformity project
Start closing out a conformity project from the point that closeout signed only after the chain is checked, then tie it to checked and closeout for this machine. In closing out a conformity project, closeout is the evidence for the point that closeout signed only after the chain is checked, and checks is the test for closeout.
Compare the point that closeout signed only after the chain is checked in closing out a conformity project with project, and let signed decide only for this machine. For closing out a conformity project, check whether the point that closeout signed only after the chain is checked matches the machine actually supplied, not signed in general.
File the closing out a conformity project record for the point that closeout signed only after the chain is checked with declaration and files, indexed by ten. Keep the closing out a conformity project record on files where the file lives, with ten cross referenced to year.
Sources & related reading
- Regulation (EU) 2023/1230, consolidated 27 July 2026: Article 10 and Annex IV.
- Directive 2006/42/EC, consolidated text: Article 10 and Annex IV.
Continue with Planning a conformity project, Communicating conformity work, An evidence register for a project.
Spot an error in this guide? Tell us through the corrections page.
Machine-specific interpretation and verification need competent assessment. This publication does not give legal advice or guarantee compliance.