writeitsafe.comServices
Services at a glance
The three areas of writeitsafe.com and the services behind them, for manufacturers and their editorial teams, freelance and project-based. Each service is described in one situation and one result, without codes or jargon.
Choose the area
Usable information, traceable evidence or controlled change.
Recognize the situation
Each service starts with the situation it fits and ends with what results.
Read the details
The full description, with approach, limit and first step, is on sainaveigel.com.
01Write it Safe
Make safety usable.
Safety information, user manuals and instructions that people can find, understand and follow.
-
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.
02Prove it Safe
Make safety traceable.
Evidence chains that connect requirements, risks, measures, tests and the released product information.
-
Securing a deadline that requires evidence
- The situation
- A submission, an audit, a certification or a phase gate has a fixed date, sometimes while a regulation changes at the same time.
- The result
- A delivery plan with interim states that can be shown every week, the finished documents and templates that make the next deadline calmer.
Full description on sainaveigel.com: Securing a deadline that requires evidence ↗
-
Evidence chains that hold in an audit
- The situation
- Requirements, risks, tests and documents sit in different systems, and the traceability is put together in a spreadsheet at the end.
- The result
- An evidence structure with clear linking rules and adapted templates, from the requirement to the released information version, in the tools the client already uses.
Full description on sainaveigel.com: Evidence chains that hold in an audit ↗
-
Safety messages that show where they come from
- The situation
- Safety messages come from the risk assessment, and it has to stay traceable why each one is there.
- The result
- Reusable safety messages in DITA, structured in line with IEC/IEEE 82079-1 and each linked to its hazard, so that a change in the risk assessment reaches every output.
Full description on sainaveigel.com: Safety messages that show where they come from ↗
Testing, certification and the declaration of conformity stay with the manufacturer and the responsible bodies.
03Keep it Safe
Keep safety intact through change.
Controlled content, variants, terminology and change paths, so that safety information stays valid when the product, the rules or the system change.
-
Maintaining content once instead of in many places
- The situation
- The same component has three names in three manuals, and one change triggers a search through twenty documents, before or after a system change.
- The result
- A written assessment of content model, terminology, variants and release paths, with measures ranked by effect and effort for the system already in use.
Full description on sainaveigel.com: Maintaining content once instead of in many places ↗
-
Keeping variants under control
- The situation
- Product and document variants multiply, and copies drift apart.
- The result
- A model for product and document variants, so that shared content is maintained once and differences are controlled deliberately.
Full description on sainaveigel.com: Keeping variants under control ↗
-
Controlling which version applies
- The situation
- Nobody can say quickly which version of a document applies, for whom and since when.
- The result
- A concept for the control of documents and records, from identification, versions, review and release to distribution, change and retention.
Full description on sainaveigel.com: Controlling which version applies ↗
-
Keeping manuals up to date
- The situation
- The machine keeps evolving, and the manual does not.
- The result
- Changes worked in every quarter and every delivered version frozen, so that the manual matches every machine that has shipped.
Full description on sainaveigel.com: Keeping manuals up to date ↗
-
Checking third-party documentation and passing on knowledge
- The situation
- Suppliers deliver in every quality and format, and knowledge that a few people have is passed on as a lecture and forgotten.
- The result
- Checking criteria and a checking procedure, plus short learning units built from the client’s own documentation. Release stays with a person.
Full description on sainaveigel.com: Checking third-party documentation and passing on knowledge ↗
-
Moving to DITA
- The situation
- The editorial team is moving to DITA from Word, FrameMaker or another system.
- The result
- A content model with topic types, metadata and reuse rules, and one manual migrated as a pilot.
Content and release stay with the manufacturer, and the quality management system remains theirs.
Support on the information behind safety
Billed at an hourly rate, with an estimate after reviewing your documents. You work directly with Saina Veigel.
Send an email Request a callback All services on sainaveigel.com