A
Secure the deadline
“The date is fixed. The documentation is not.”
- You tell me the date and where things stand.
- I tell you openly whether the date can be met.
- You receive a delivery plan and the finished documents.
E-learning samples
Saina Veigel
I make sure product information in regulated industries is correct, ready on time and backed by evidence.
Four services for projects under deadline and evidence pressure, plus twelve services around the user manual. You work with me directly, not with a team.
In short
A
“The date is fixed. The documentation is not.”
B
“The risk assessment and the manual do not match.”
C
“The same content is maintained in many places.”
D
“Supplier documents arrive in every quality. Knowledge sits in a few heads.”
U1 – U12
“The operating manual has to be written from scratch or revised.”
DITA
“Our DITA team needs extra capacity.”
Billed at an hourly rate · Estimate after reviewing your documents · You work with me directly.
When a deadline moves closer, a regulation is replaced, single machines become a line or content moves to a new system, the course of events is remarkably similar in almost every industry. Problems appear in the same places: at interfaces nobody owns, in evidence that is pieced together at the very end, and in knowledge that lives in one person’s head.
I work with these patterns. I don’t need to learn your problem from scratch to know where to look first. What I need to find is the point where your case departs from the pattern, because that is usually where the real work lies.
A · B · C · D
Each service starts with a small, clearly defined first step. After that, you decide whether and how to continue.
For submissions, audits, certifications and phase gates with a fixed date, including when a regulation changes at the same time.
“The content is all there, it just needs writing up.” The sentence is well meant and almost always wrong. The bottleneck is rarely the writing. It is the dependencies: the instructions for use wait for the risk analysis, the risk analysis waits for a design decision, and every approval needs several signatures.
First I separate what is critical for the deadline from what is merely desirable. Then I set the order in which the documents have to be produced so that nobody waits for anybody, with parallel reviews instead of review chains. When a regulation changes, I first establish what has actually changed, so that the work happens there and not everywhere.
After that I work with your team, not next to it: drafting documents and templates, preparing reviews and following them up. I know the common authoring, document control and requirements management systems.
Responsibility for conformity stays with you and the notified or competent bodies. My job is to keep the documentation from becoming the obstacle. Legal advice is not part of it.
First step: tell me the date and where you stand. In a short conversation I tell you whether the deadline is achievable and what it takes. If it isn’t achievable, I tell you that too.
For lines and installations built from single machines or purchased modules, and for manuals that have to match the risk assessment.
Every machine in a line has its manual and its risk assessment. Yet what happens at the transfer between two stations, who describes the shared emergency stop and how the line restarts after a zone stop is often written down nowhere. The interfaces belong to nobody. On top of that, the risk assessment and the manual are produced separately. Then a residual risk appears in the assessment but not in the manual, or a warning in the manual has no reason in the assessment.
The Machinery Regulation (EU) 2023/1230 applies from January 20, 2027. These relationships are not new, but they will be examined more closely.
First, the information on the assembly as a whole is brought together: interfaces, signals, operating modes, variants and safety functions. I coordinate the information and the analyses your own experts provide, and advise where my competence allows. Second, a context table that links every hazard to the place in the user information where it is addressed. Gaps, duplicates and contradictions become visible before someone else finds them.
Your safety engineers still decide what is safe. I make sure their decisions appear in the manual exactly as made, and are understood. I do not design or calculate safety functions; the risk assessment stays with the manufacturer’s experts.
First step: an alignment on one machine or one line. Afterwards you know where you stand and have a template for all the others.
For documentation teams that maintain the same content in several places, before or after a system change, and before an AI assistant is meant to answer from that content.
An authoring system is introduced or replaced, the content moves, but the model behind it is never settled: which modules, which metadata, how variants are controlled, which term applies. A few years later the same component has three names in three manuals, one change triggers a search through twenty documents, and the released version is recorded in a spreadsheet. An AI assistant finds exactly what the structure contains, including the draft from five years ago.
A structure check over a fixed period, with the effort estimated in advance. I review your content model, your terminology, your variants and your release and evidence paths, and I talk to the people who work with them every day.
Many teams implement the assessment themselves. It also works as a paper to justify internally why time or budget is needed. You can see beforehand how I think about terminology, cross-references and structure in my blueprints on AI TechDoc Knowledge.
I don’t replace your tool or introduce a new one. System programming and the technical implementation of ontologies or knowledge graphs are not part of my scope.
First step: the structure check, fixed period, billed by the hour.
For companies with a lot of third-party documentation, and for knowledge that a few people have and many people need.
Suppliers deliver in every quality and every format, checking depends on who happens to have time, and errors surface only once the document is already in use. At the same time, knowledge is passed on as a lecture and forgotten two weeks later.
Checking starts with fixed criteria, not with AI. Only once it is clear what is checked can an assistant take over the pre-check: missing information, inconsistent terms, deviating safety statements. The rule: the machine suggests, a person decides, and safety statements are left untouched. The assistant is set up with the tools your IT has already approved.
For handing over knowledge, I develop short learning units where the work happens: with exercises drawn from your own documentation and troubleshooting that follows the path technicians actually think through. Concept, script and production stay in one hand; a short explainer film can be part of it.
My e-learning samples show what such learning units look like.
Release stays with a person. I do not run a learning management system.
First step: one checking step or one learning topic that is pressing for you right now. Within a few weeks you see whether it saves time or prevents errors, and you have a concrete result to report.
Eight patterns that recur in regulated industries: how to recognize them, what lies behind them, what they take and where my work ends.
Twelve services around the manual: writing it from scratch, checking, revising, setting up Word properly, writing in two languages and keeping it current.
Work in your DITA project, in your editorial team and with your XML tools: extra capacity, moving to DITA, a structure check and safety messages linked to the risk assessment.
Terms & contact
The services are open to organizations in every country, freelance and project-based. You work with me directly, not with a team.
Estimate after reviewing your documents
I bill at an hourly rate, which I tell you in our first conversation. Before you commit, I review your documents and give you an estimate of the effort and a date. We exchange documents once your non-disclosure agreement is signed.
Employment preferred
For organizations in Switzerland, I prefer to work in fixed-term or permanent employment. Project-based freelance work is possible as well.
Based in the Rhine Valley — close to St. Gallen, Vorarlberg and Lake Constance.
Available now until Christmas 2026 for short projects, and from January 2027 for medium- and long-term projects.