Make the acceptance decision before relying on the CE mark

The decision job is practical: when an OEM or importer claims CE for a service robot, identify what is present, missing or inadequate in the Annex IV technical documentation before accepting the machine. The mark belongs at the end of a compliance process, not at the beginning of a buyer’s investigation. The European Commission’s CE-marking guidance explains that manufacturers are responsible for assessing conformity, setting up the technical file, issuing the declaration and affixing the mark where the applicable rules require it.

The timing also matters. The Commission’s machinery overview distinguishes the current Machinery Directive from Regulation (EU) 2023/1230 and notes the corrected application timetable. The consolidated Regulation applies from 20 January 2027, subject to provisions with different dates. A procurement file should state which legal regime applies when the product is first placed on the market or put into service. It should not mix a 2006/42/EC declaration with 2023/1230 document labels as if the transition were merely cosmetic.

For hotel management, the acceptance outcome should be one of four states. Evidence may be accepted for the agreed review scope, accepted subject to named close-out items, or held pending material evidence. Rejection is appropriate when the product identity, conformity route or safety case cannot be reconciled. That classification is more useful than a binary “CE received” checkbox. It also preserves a record of what management knew before payment and deployment.

Separate the duties of manufacturer, importer and hotel

Article 10 of the consolidated Machinery Regulation requires the manufacturer to design and construct machinery or a related product against Annex III. Before market placement or first use, the manufacturer must also draw up the Annex IV Part A technical documentation and complete the relevant Article 25 conformity-assessment procedure. The same article requires retention of the documentation and EU declaration of conformity for at least ten years. Where necessary for an authority’s compliance check, source code or programming logic may have to be made available on a reasoned request.

An authorised representative can hold documents and cooperate with authorities under a written mandate, but Article 12 does not allow the manufacturer’s core duties to be delegated away. Article 13 gives an importer a separate gatekeeping role. Before placing machinery from outside the Union on the market, the importer must ensure the appropriate procedure was completed and the manufacturer drew up the Annex IV Part A file. The importer must also check the required marking and accompanying documents, retain the declaration, and ensure the technical documentation can be made available to authorities.

A Greek hotel that buys from an EU distributor is not automatically the importer. A hotel that buys directly from a non-EU OEM may become the importer, depending on the transaction and market-placement facts. A hotel can also become the manufacturer for regulatory purposes if it manufactures for its own use or makes a substantial modification within the Regulation’s rules. These roles must be established from contracts, invoices, customs records, product labels and the actual modification scope, not from the supplier’s sales terminology.

The hotel remains an employer and operator with workplace, installation, maintenance and safe-use duties even when it is not the product manufacturer. Ergasa’s Machinery Regulation readiness guide for Greek hotels places the technical file within that broader deployment decision. A clean manufacturer file does not replace site-specific route testing, staff controls, lift integration review or emergency arrangements.

Check the Annex IV Part A contents against the exact robot

Annex IV Part A is not a request for every engineering record ever produced. It specifies enough documentation to demonstrate conformity and enable authorities to assess the machine. The file begins with a complete description of the machinery or related product and its intended use. It should identify the model, type, serial or configuration boundaries and explain foreseeable misuse. For a mobile hotel robot, the description should match the delivered sensors, batteries, payload modules, chargers, software version and optional lift or door integrations.

The file then needs overall and detailed drawings and the schemes, calculations, test results, certificates and explanations required to understand operation and verify conformity. The risk-assessment documentation must show the procedure followed: the applicable essential health and safety requirements, identified hazards, protective measures, residual risks and the outcome of design choices. A generic corporate risk-policy PDF is not the same thing as the product’s risk assessment.

The documentation must identify the specifications applied. These may include harmonised standards, common specifications or other technical specifications, with the essential requirements covered. The Commission’s machinery standards page is the correct place to verify published references for the current machinery regime. Under Regulation (EU) 1025/2012, European standardisation operates within a formal legal framework; a supplier’s standards list still has to identify editions, amendments and the requirements actually addressed.

Annex IV also calls for reports giving results of tests performed by the manufacturer or by a body selected by it. It requires a copy of the instructions for use and the EU declaration of conformity, plus evidence for series production where applicable. If partly completed machinery is incorporated, the relevant declarations of incorporation and assembly instructions belong in the evidence chain. The file may also need the EU declarations for incorporated products governed by other Union harmonisation legislation.

Test traceability, software and change control

A file can contain every expected heading and still be inadequate. The decisive quality is traceability: each applicable Annex III requirement should connect to a hazard or design issue, a protective measure, a specification or engineering rationale, and verification evidence. Test reports should identify the tested unit or representative sample, configuration, software version, method, acceptance criteria, date and result. If the test laboratory is external, its scope and report identity should be checked rather than inferred from a logo.

For connected and software-driven robots, the review should establish which software affects safety functions, who controls updates and how changes are assessed. Annex IV expressly contemplates source code or programming logic needed to understand conformity, while Articles 10 and 13 permit competent authorities to request relevant code or logic where necessary for checking Annex III compliance. A hotel does not need unrestricted source-code ownership to ask for a credible safety-software configuration record, update policy and authority-access arrangement.

Machine learning, remote diagnostics and cloud services should not be treated as one undifferentiated “AI” feature. The file should state which functions influence movement, speed, stopping, obstacle detection, payload stability, access control or other safety outcomes. It should distinguish fixed automation from behaviour that changes after deployment. The applicable conformity route is a separate decision, and the Commission’s NANDO system can be used to verify whether a named notified body is actually notified for the relevant legislation and conformity tasks.

Change control matters because the delivered robot may not be the version that was originally tested. Review the chain from design baseline to serial production: component substitutions, battery changes, sensor revisions, safety-parameter changes, firmware releases and integration scripts. The file should explain how the manufacturer decides whether a change requires new risk assessment, testing, documentation or conformity action. A version mismatch is not automatically non-compliance, but an unexplained mismatch is a procurement hold.

Review the machinery technical file with an evidence matrix

Start with a controlled index rather than an email attachment folder. Record document title, owner, version, date, language, product identifier, applicable requirement, confidentiality restrictions and review result. Mark each item present, missing, inconsistent, insufficient or not applicable with a reason. “Confidential” should trigger an access arrangement, not an automatic pass. The Regulation requires the file to be available to competent authorities, while commercial review can use secure rooms, redacted copies or specialist attestations where full disclosure to the hotel is not proportionate.

The 2022 Blue Guide is useful for the horizontal concepts behind EU product rules, including economic operators, conformity assessment, technical documentation and market surveillance. It should be read with the machinery-specific Regulation rather than used to overwrite it. The legal hierarchy also matters: a standard can support a presumption for requirements within its scope, but it does not replace the manufacturer’s responsibility to identify all applicable requirements and address uncovered risks.

Do not ask a supplier to “send the technical file” without defining the acceptance test. A better machinery technical file request asks for the controlled Annex IV index, product-identity matrix, risk-assessment map, applied-specification register, verification plan and reports, declarations, instructions, software baseline and production-change process. It also states the review language, secure-access method, response deadline and people authorised to resolve gaps.

Decision checklist before final payment

• Confirm whether the delivered unit is complete machinery, a related product or partly completed machinery.
• Record the manufacturer, importer, authorised representative and distributor from primary documents.
• Match model, serial number, modules, charger, battery, sensors and software baseline across the file.
• Map Annex III requirements to hazards, measures, specifications and verification evidence.
• Check test scope, sample identity, methods, acceptance criteria, dates and unresolved failures.
• Reconcile instructions, declarations, labels and technical documentation in the required languages.
• Verify any notified body and its notified scope directly in NANDO.
• Log every gap with an owner, evidence required, due date and effect on acceptance.
• Keep final payment and deployment conditional on closure of material safety or identity gaps.
• Archive the reviewed baseline and define notification rules for later hardware or software changes.

Classify gaps by decision impact and closing work

Not every missing page has the same consequence. An administrative gap may be a correctable identifier, translation or signature issue. A traceability gap arises when a report, certificate or drawing cannot be tied to the exact product. A technical gap exists when a hazard, requirement, protective measure or test is absent or inadequately supported. A conformity-route gap appears when the chosen assessment procedure or notified-body involvement cannot be justified. A role gap exists when the manufacturer or importer identity is uncertain.

Closing work should be described without inventing a price or completion date. It may require document correction, engineering analysis, a model-specific risk assessment, testing, translation, software-baseline evidence, production-control records or an independent conformity-assessment review. The buyer should obtain a scoped proposal from a competent provider. A spreadsheet estimate is not proof that the machine can be brought into conformity.

The enforcement context is real. Regulation (EU) 2019/1020 establishes the Union framework for market surveillance and product-compliance controls, while Regulation (EC) 765/2008 provides rules on accreditation and market surveillance. The common product-marketing framework in Decision 768/2008/EC helps explain why traceable economic operators and reliable declarations recur across EU harmonisation laws. These instruments do not let a hotel declare a robot compliant; they show why a weak file can become an operational and commercial problem after import.

There is also a cash decision. Technical-file access and gap closure should be included in the purchase terms before the hotel loses leverage. Milestones can tie deposits, shipment, customs release, site acceptance and final payment to named evidence. The financial model should include specialist review and retesting as contingent costs rather than assert that every robot will incur them. For a wider capex view, Ergasa’s hotel-robot funding and cash-timing analysis shows why eligibility and reimbursement assumptions must remain separate from compliance evidence.

Set a defensible next step

Before accepting a hotel service robot, request a controlled Annex IV Part A index and build the evidence matrix against the exact delivered configuration. Resolve identity, role and conformity-route questions first; they determine what the rest of the file must prove. Escalate material safety, software and verification gaps to competent engineering or conformity-assessment specialists. Keep the review conclusion narrow: it records procurement evidence and unresolved questions at a date. It is not the manufacturer’s declaration, a notified-body certificate or legal advice.

Uncertainty must remain visible. The Regulation’s classification and conformity procedures can turn on product-specific facts that a sales brochure does not disclose. Harmonised-standard references and notified-body scopes can change. Software updates can alter the assessed baseline. The only defensible acceptance record is therefore one that names its assumptions, identifies the reviewed configuration, dates every source and keeps open items attached to an owner and decision.