01Area
Write it Safe
Make safety usable.
Safety information, user manuals and instructions that people can find, understand and follow.
The situation
The risk assessment is finished, but the manual does not yet say what it means at the machine. Warnings are generic, operating modes run into each other, residual risks are missing or buried.
The service
User manuals written or revised, safety chapters and warnings built as a standard, risk assessment and information for use brought into line, support in DITA XML.
The result
Information for use that matches the machine and its risk assessment, in editable files that belong to the client.
A manual never replaces a protective measure. The risk assessment stays with the manufacturer.
01Newsletter section
Issues in this area
Information for use is where safety reaches the people who operate, clean, maintain and service a machine or a device. This section collects the issues on the elements that carry this information: emergency stop and HMI, interlocks, hazard points, safety messages and their readability. The common measure is whether the information is found, understood and acted on in the situation in which it is needed.
-
Safety Information Readability and Usability
Risk management often fails where nobody transfers the safety logic into information that people can actually work with. The issue describes what makes safety information in internal technical documentation readable and usable for R&D, Safety, Regulatory and Quality, without inventing a second risk-assessment language.
-
Material handling machines: systemic risks and recurring failure patterns
The hazards of material handling machines arise from continuous interactions: constant motion, limited visibility, narrow spaces, unclear responsibilities and routine behavior. The issue describes evidence-based methods, such as incident and near-miss data, fault logs and observation at transfer points, that reveal recurring failure patterns traditional assessments often miss.
-
Hazard points and machine motion
Safeguarding does not start with the choice of a guard but with what moves, how it moves, where people can reach it and which energy is present. The issue explains how injury mechanisms such as entanglement, crushing, shearing or drawing-in define a hazard point and why the name of a machine says little about its risk.
-
Operational user focus of interlocks
Operators do not experience an interlock as PLC logic but as a condition such as “Guard closed” or “Safe to start.” The issue shows how a user manual translates the safety intent of an interlock into operational meaning: what the visible condition allows or prohibits at the machine.
-
Manuals, SOPs, and SIMOPS: why document type is a safety boundary
Procedures often fail because the wrong kind of document was published, such as a generic guide where a behavioral standard was needed. The issue sets out what manuals, SOPs and SIMOPS rules are each responsible for and treats documentation as a management instrument for parallel work, shift handovers and contractor interventions.
-
Lubrication data is a safety control
Lubrication and media documentation defines operating limits, compatibility and the isolation steps that prevent hazardous releases, and is therefore part of the safety architecture. The issue looks at it from the safety, compliance and documentation side, separates manufacturer and operator duties using a linked paper-industry line and an offshore plant, and shows how media belong in the risk assessment.
-
ISO 12100 is everyone’s business
ISO 12100 is the shared risk language that connects design, purchasing, operation and documentation, not a topic for the CE team alone. The issue describes how to keep working with it while it is not yet harmonized under the Machinery Regulation (EU) 2023/1230 and why the system definition belongs in chapter 1 of the operating instructions.
-
Documentation and HMI: the place where concepts either stay sharp — or get blurred
Operating instructions often leave out safety functions such as presence-sensing devices, on the assumption that operators do not interact with them. The issue explains why the purpose, coverage and limits of these devices, the difference between stop and power isolation, and the conditions for reset and restart belong in the manual and the HMI, also with a view to the Machinery Regulation (EU) 2023/1230.
-
Writing emergency stops right: why documentation shapes E‑Stop versus Power‑Off understanding
Emergency stop concepts in interconnected lines are often engineered with care, yet manuals, HMI texts and LOTO instructions blur Emergency Stop and Emergency Power-Off. Using hotforming lines as an example, the issue shows how stop functions, zones, energy domains and reset discipline have to be described so that people expect what the machine actually does.
Articles in the blog “Read the Signs”
-
Penguins
No profile does not mean no obligation
For many OT components there is no product profile under EN 50770 yet. The Cyber Resilience Act applies all the same. The gap is not in the standard. It lies between the decision, the information and its evidence.
01Write it Safe
Services in this area
Each service in short: the situation it fits and what results. The full description, with approach and limit, is on sainaveigel.com.
-
Writing or revising a manual
- The situation
- A new machine needs its manual, or an existing manual is older than the Machinery Regulation (EU) 2023/1230, which applies from January 20, 2027.
- The result
- A manual that fits the machine, in Word or in the client’s system, revised where it is needed rather than page by page.
Full description on sainaveigel.com: Writing or revising a manual ↗
-
One safety chapter for all products
- The situation
- Every manual has its own safety chapter, and each one is a little different.
- The result
- One standard with fixed modules for warnings, residual risks and intended use. After that, only the differences are maintained.
Full description on sainaveigel.com: One safety chapter for all products ↗
-
Having a manual checked
- The situation
- A manual has grown over the years or was written fully or partly with AI, and nobody knows how well it still holds.
- The result
- A written report on completeness, safety and clarity with every finding in its place, ranked by weight, and an estimate of the effort a revision would take.
Full description on sainaveigel.com: Having a manual checked ↗
-
Bringing the manual and the risk assessment into line
- The situation
- A residual risk appears in the risk assessment but not in the manual, or a line built from several machines has interfaces that nobody describes.
- The result
- A context table that links every hazard to its place in the user information, cleaned-up safety chapters and, for lines, a system manual above the individual manuals.
Full description on sainaveigel.com: Bringing the manual and the risk assessment into line ↗
-
Working in DITA XML in the client’s editorial team
- The situation
- The editorial team already works in DITA and needs an experienced person for a delivery, a change in a standard or a vacant position.
- The result
- Topics and maps written and revised following the client’s style guide, with any XML tool in the client’s environment.
Full description on sainaveigel.com: Working in DITA XML in the client’s editorial team ↗
A manual never replaces a protective measure. The risk assessment stays with the manufacturer.
Billed at an hourly rate, with an estimate after reviewing your documents. You work directly with Saina Veigel.
The other areas
-
02
Prove it Safe
Evidence: lifecycle documentation, traceability and AI in the chain of safety evidence.
-
03
Keep it Safe
When rules, systems and signals change: safety and security, interfaces, semantic drift and new deadlines.
New issues on the third Friday of every month on LinkedIn.
Subscribe on LinkedIn