CE Software: Who Benefits From What? Four Audiences Compared

For SMEs and machine builders without a CE department

The typical SME has no CE department. It has one person who does CE “on the side”: the head of design or an experienced project engineer, in between quotes, design work and commissioning. Only a few machines are built per year, often months apart. The templates come from the last project, the knowledge sits in one head, and with every new machine the same question starts again from scratch: which standards apply this time, and do the ones from last time still apply at all?

Typical pain points

• No routine: months lie between two CE projects: getting back into the methodology and the legal situation costs days every time.
• Uncertain standards research: whether a standard is harmonised, in its transition period or withdrawn is stated in Official Journal lists. Anyone who does this rarely easily overlooks a change.
• Scattered documents: risk assessment in Excel, declaration in Word, reports on the network drive. When a customer or authority asks, nothing can be found quickly.
• Knowledge tied to one person: if the one colleague who “can do” CE is absent, the topic comes to a standstill.

What the workflow with CE-Copilot looks like

1. Create the project and describe the machine: the standards finder analyses the product description with AI and delivers the relevant standards, each classified as mandatory or recommended, including a check whether the machine falls under Annex IV.
2. With “Assign mandatory standards automatically”, the mandatory standards land in the standards checklist with one click; at the same time, the tracker subscriptions for these standards are created.
3. Risk assessment per EN ISO 12100: AI hazard suggestions per machine type as a starting point, evaluation in the 2D matrix of severity and probability, measures according to the 3-step method. Review, adjust or discard every suggestion: the technical decision remains with you.
4. Generate the declaration of conformity: per Annex II of the Machinery Directive 2006/42/EC, from 20 January 2027 per Annex V of the Machinery Regulation (EU) 2023/1230, with your own logo and letterhead.
5. Complete export as PDF and Word: risk assessment, declaration, checklists and reports as a coherent set of documents for the technical documentation.

Which functions carry weight here

• Standards finder: it replaces the most uncertain phase (“which standards apply at all?”) with a reasoned starting list from a register of 2,300+ harmonised standards.
• Guided risk assessment: the methodology of EN ISO 12100 is built into the tool and does not have to be reconstructed from the standard for every project.
• Standards tracker: e-mail alerts on changes to standards monitor exactly the gap between two projects in which nobody would otherwise look at the Official Journal.
• Complete export: one complete, uniform set of documents instead of scattered files, findable when someone asks.

For series machinery and product lines

You manufacture the same machine type repeatedly, as a true series or as a product line with sizes and option packages. At its core, the CE work arises once per type: standards research, risk assessment and technical documentation refer to the model. But every machine is delivered individually: with its own serial number, its own year of construction, its own declaration of conformity and the requirement that it matches the assessed state exactly.

The legal framework for this: as a rule, the risk assessment applies per type or model and does not have to be rewritten for every single serial number. In return, the conformity assessment procedure (for machinery outside Annex IV usually the internal checks on production per Annex VIII of the Machinery Directive) requires the manufacturer to ensure by suitable measures that every machine produced matches the technical documentation and the requirements. The declaration of conformity can cover a serial-number range. And: if an individual unit deviates in a safety-relevant way (for example through a customer-specific modification), that deviation must be evaluated separately.

Typical pain points

• Copy-and-paste documentation: for every order the Word file is copied and the serial number plus year of construction changed, with all the sources of error: forgotten fields, old standards editions in the new document.
• Variants drift apart: after the fifth size nobody knows for certain which version of the risk assessment belongs to which variant.
• Changes to standards hit the whole product line: if an underlying standard changes, all future deliveries are affected. Anyone who notices late delivers on an outdated basis.
• Evidence per individual machine: that every machine produced matches the assessed state requires production checks that are actually carried out, together with evidence. A folder for the type alone is not enough.

What the workflow with CE-Copilot looks like

1. Build the type project completely: analyse the reference machine with the standards finder, create the checklist and tracker subscriptions in one click via “Assign mandatory standards automatically”, work out the risk assessment per model, store the declaration master data and the test report profile.
2. Start a follow-on order or variant with “Project from template”: the existing project serves as the basis, and the carry-over is selective: machine profile, standards checklist, risk assessment, declaration master data (deliberately without serial number, year of construction and signature) and the test report profile.
3. Check the carried-over risk assessment in a targeted way: carried-over entries are marked “Carried over, to be checked” and their acceptance is reset. For the next size you therefore specifically check the differences (higher drive power? different access points?) instead of rewriting the assessment. In the end, every machine still has a reviewed, accepted risk assessment.
4. Issue the declaration of conformity per delivery or per batch: one declaration can cover a serial-number range, for example a production batch. The master data comes from the project, serial numbers and year of construction are set per declaration; multilingual (DE/EN/FR/IT) for export customers.
5. Document the production checks: the type’s test report profile is completed for every machine produced: the evidence that the individual unit matches the assessed state.
6. Monitor the product line over the years: the standards tracker checks weekly against the 12 OJEU Official Journal lists and reports changes by e-mail; the audit log records who changed what and when on the type state.

Which functions carry weight here

• “Project from template”: reuse without blind copying: the selective carry-over plus the review marker on the risk assessment entries is the middle way between “everything from scratch” and risky copy-and-paste.
• Serial-number ranges in the declaration of conformity: represent batches and individual deliveries without building a document by hand for every machine.
• Test reports: make the internal checks on production verifiable per unit: the missing link between type documentation and individual machine.
• Standards tracker: with series, a change to a standard does not affect one project but all future deliveries. The alert arrives before the next machine leaves the factory on an outdated basis.
• Audit log: documents changes to the type state over the entire life of the series; relevant when, years later, someone asks which state applied to serial number X.

For special-purpose machinery and one-off systems

In special-purpose machinery building, every system is a one-off built to a requirements specification. The CE work runs in parallel with design, assembly and commissioning and regularly collides with the delivery date at the end of the project, because acceptance by the customer (and often a payment milestone) depends on complete documentation. Unlike the series manufacturer, there is no identical predecessor from which the risk assessment could be derived, but there are recurring subsystems.

Typical pain points

• No identical predecessor: there is no ready-made template for the risk assessment: every project starts conceptually from zero.
• CE at the end of the project: under deadline pressure, the documentation is produced retrospectively instead of alongside the design. Gaps only show up at acceptance.
• The customer demands the package: declaration of conformity, risk assessment and technical documentation as a complete, consistent handover package.

What the workflow with CE-Copilot looks like

1. Create the project, put the system description into the standards finder: the AI analysis delivers the standards classified as mandatory or recommended and checks whether the system falls under Annex IV, which does happen with special-purpose machinery depending on its function.
2. “Generate risk assessment draft automatically”: hazards, preliminary evaluation and measure proposals are produced in one pass. The result is expressly a draft: the project engineer checks every point against the concrete system concept, discards and adds.
3. Refine alongside the design: document measures according to the 3-step method; for recurring hazard groups (for example ten similar crushing points along a conveyor line), bulk measures save typing the same thing ten times.
4. Use recurring subsystems: even one-offs consist of known building blocks. Via “Project from template” you selectively carry over, for example, the standards checklist or the test report profile from a similar previous project; carried-over risk assessment entries remain marked “Carried over, to be checked”.
5. For acceptance: complete export as PDF and Word, the CE documentation as a consistent package for the customer and your own records. The technical documentation follows the structure of Annex VII of the Machinery Directive, from 2027 Annex IV of the Machinery Regulation.

Which functions carry weight here

• “Generate risk assessment draft automatically”: the quick starting point where no template can exist, with clear draft labelling instead of a pretence of completion.
• Bulk measures: assign measures to many similar hazards in one step: for large systems the difference between hours and days of documentation work.
• Technical documentation: the documents grow alongside the project in the structure of Annex VII of the Directive or Annex IV of the Regulation, instead of improvising a folder at the end.
• Complete export PDF & Word: the acceptance package in one step, complete and internally consistent, when the payment milestone depends on it.

For external CE service providers and consultants

As an external CE coordinator or consultant, you look after several clients in parallel with different machine types. You deliver assessments and documents. In the legal sense, however, the manufacturer remains your customer: the declaration of conformity is issued in its name and must be signed by its authorised person. Your capital is methodology, speed in familiarising yourself with a new machine and the traceability of your work towards the client.

Typical pain points

• Constant context switching: several engagements, several machine types, several document states: keeping an overview alone costs billable time.
• Consistency of methodology: every engagement should be assessed against the same grid. That is hard to maintain across Excel templates of different generations.
• Traceability: the client, and in the event of a dispute third parties, want to know who assessed and changed what and when.
• Handover without lock-in: after the end of the project the customer must be able to maintain the documentation itself, not in a format that chains it to you.

What the workflow with CE-Copilot looks like

1. One project per engagement: create the machine profile, put the product description into the standards finder. The AI analysis with mandatory/recommended per standard serves as a well-founded initial assessment for the quote and kick-off.
2. Uniform methodology across all engagements: risk assessment per EN ISO 12100 with the same 2D matrix of severity and probability. Results are comparable between projects and explainable to the client.
3. Documents in the manufacturer’s branding: declaration of conformity with the client’s logo and letterhead, multilingual (DE/EN/FR/IT) for exporting customers, issued in the manufacturer’s name and signed by its authorised person.
4. Make your work verifiable: the audit log documents who changed which assessment and when; via training records you record briefings you have carried out at the client’s site.
5. Hand over cleanly or keep supporting: the complete export as Word lets the client maintain the documents itself. If the project stays with you, the standards tracker reports changes to standards by e-mail: a basis for actively informing existing customers.

Which functions carry weight here

• Multilingual declaration of conformity with logo/letterhead: documents appear in the manufacturer’s branding, legally correctly issued in the client’s name.
• Audit log: evidences your work towards the client and creates clarity when several people work on the same project.
• Word export: handover in a format that every client can continue editing without special software.
• Standards finder: shortens familiarisation with a new machine type to a reasoned starting list that you check professionally.
• Standards tracker: the basis for an ongoing support model beyond the individual project.