Skip to content
Quality, standards & complianceElectronics & SensorsMachinery & Plant EngineeringConveying & IntralogisticsConstruction & Building Services+3

Accident at a customer site: reporting duties and evidence

After an accident you have the evidence secured, reporting duties checked and the notice and customer letter drafted within hours.

Today

When a customer reports an accident or near miss with your machine, the clock is running. Whether the authorities must be informed, by when and with what, only a few people in the company know. The evidence sits in five departments: delivery in the ERP, risk assessment and operating manual in the CE file, service reports in the ticket system, photos in a sales inbox. By the time everything is together, days have passed, and nobody knows for sure whether similar cases happened before.

An example

An office furniture dealer e-mails Tannried Möbelwerk: while lowering an electrically height-adjustable desk from the TI series, 1,800 × 900, an employee trapped his hand between the desk top and a mobile pedestal, suspected broken finger. demi opens the case at 9:12 and finds via the serial number the delivery, the controller with firmware 2.3 and the risk assessment, which handles the crushing hazard through the controller's collision detection. In the service tickets the agent finds two more reports from the past year where collision detection did not trigger, both with firmware 2.3. The product safety officer decides on reporting and a firmware update the same morning; the customer letter and the claim notice to the insurer are ready as drafts.
Fictional company, typical workflow.

Your data, wherever it lives

What counts after an accident is scattered today: the customer's report in a sales inbox, photos in a messenger, delivery and configuration in the ERP, risk assessment and manual as PDFs in the CE file, service reports in the ticket system and old complaints in the quality system. demi reads, understands and links it all per serial number, with your permissions. The AI has the evidence and possible reporting duties together in hours instead of days, and your product safety officer decides whether to report.

Where the data lives today

  • E-mails
  • Tickets
  • Photos, video & audio
  • Chats
  • ERP
  • DMS & archive
  • QM system
  • CRM
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the ticket system, CRM, ERP, CE file and mailboxes. demi replaces nothing and links, per serial number, delivery, configuration and software version, operating manual, risk assessment, declaration of conformity, service reports, modifications and every customer report with photos and videos. The agent finds similar cases by type, component and failure pattern, including in old complaints.

  2. 2 · PermitPermission Layer

    The injured person's name and injuries are visible only to the case team from product safety, quality and legal; service and engineering work with the anonymised case. Secured evidence cannot be changed, only added to. The authority notice, the customer letter and the claim notice to the insurer go out only after an authorised person approves them, and every access is logged.

  3. 3 · ActIntelligence Layer

    The agent reads the report, photos and service records, assigns them to the right machine and checks whether the risk assessment covered the hazard and with which protective measure. It checks possible reporting duties against the criteria you store, such as product type, severity of injury and sales markets, and calculates deadlines from the moment your company knew. A person decides whether to report; the agent shows what speaks for and against it and what is still missing.

How it runs

  1. 1

    A customer reports an accident or near miss by e-mail, phone or service ticket; demi opens the case with the moment your company learned of it.

  2. 2

    Via the serial number the agent gathers delivery, configuration, operating manual, risk assessment, service reports, photos and similar reports and secures their state with a date.

  3. 3

    It checks against your stored criteria which reporting duties may apply and calculates the deadlines.

  4. 4

    It drafts the authority notice, the customer letter and the claim notice to the insurer, every statement with its evidence.

  5. 5

    Your product safety officer decides on reporting and measures, and demi records the decision and its reasons.

What changes

  • All evidence on the accident in one place, secured as of the day it was reported

  • Reporting duties and deadlines checked before a deadline passes

  • Similar cases surface before the next accident happens

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+58 hfreed per year

Assumptions and calculation

demi secures the evidence, checks possible reporting duties and drafts the notice; you decide.

8 h → 5.6 h per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

2 accidents and near misses × 8 h × 30% × 1.0 (manual) × 12 months = 58 h

Value per year, before demi costs

Freed per year+58 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€3,770

gained per year

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

How does demi know the reporting duties for our products?

From the rules you store with your product safety team or legal department: which regulations apply to which products and markets, from which severity a report is due and which deadlines run, for example the accident notification for consumer products under the EU General Product Safety Regulation. The agent applies these rules to the case and shows which rule it applies and why. Whether you report is your decision.

How does demi secure the evidence?

demi records the state of every document in the case with date and version: operating manual and risk assessment as delivered, service reports, e-mails, photos and videos. Later changes to the originals do not alter the secured state. So months later you can still show what was known and when.

What happens to the injured person's data?

Health data is specially protected. Only the case team sees names and injuries; everyone else works with the anonymised case. You set how long the data is kept, and every access is logged.

Does demi also find similar cases from the past?

Yes. The agent searches complaints, service tickets and e-mails for cases with the same type, component or failure pattern, even in years-old records. Each hit shows what matches and what does not. Whether a recall, a retrofit or a revised operating manual follows is your decision.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases