Services

Requirement patterns

Your project is new. The pattern behind it usually isn’t.

Eight patterns that recur in regulated industries. Each one describes what triggers it, how to recognise it, what lies behind it, what it takes, what you have at the end and where my work ends.

A pattern looks the same in medical technology as it does in rail or machine building. That is why I know where to look first, and why I go straight to the point where your case departs from it.

Eight patterns

I hear the sentences under ‘How you recognise it’ again and again in projects. If you recognise yourself in one of them, the matching service is at the end of the card.

M1

Deadline under regulation

Trigger
A submission, an audit, a certification or a phase gate is fixed. The documentation is not.
How you recognise it
  • ‘The content is all there, it just needs writing up.’
  • ‘Approvals always take longer than planned.’
What lies behind it
The bottleneck is rarely the writing. It is review loops, unclear responsibilities and documents that depend on each other and are therefore produced in the wrong order.
What it takes
An inventory by criticality, a delivery sequence by dependency, fixed interim states and parallel reviews instead of review chains.
Result
A delivery plan, finished documents and templates your team can carry on with alone.
Limit
Conformity assessment stays with the manufacturer and the notified bodies.

M2

A change of regulation

Trigger
One regulation replaces another, such as the MDD giving way to the MDR or the Machinery Directive to the Machinery Regulation (EU) 2023/1230, or a new target market comes with its own authority.
How you recognise it
  • ‘Our documents were always fine — so what exactly is different now?’
What lies behind it
Existing documents are adjusted paragraph by paragraph instead of first establishing the differences. The result is a lot of work in the wrong place.
What it takes
A gap analysis of the old against the new regulation, a prioritisation, and then the rebuilding of the templates. Only after that are the individual documents adjusted.
Result
A gap list, revised templates and converted documents per product.
Limit
Legal advice is not part of it.

M3

The boundary shifts

Trigger
Single machines or subsystems are joined into a line, or a supplied part becomes part of a larger system.
How you recognise it
  • ‘Every station has its manual, but nobody describes the transfer.’
  • ‘Who is actually responsible for the shared emergency stop?’
What lies behind it
The interfaces have no owner, neither in the risk assessment nor in the user information.
What it takes
An integration analysis (interfaces, signals, operating modes, variants, safety functions), followed by a document structure for the whole installation above the individual manuals.
Result
An interface description, a system manual and input for the risk assessment of the assembly as a whole.
Limit
Safety functions are not designed or calculated.

Case example: in the case note ‘Five open doors’, the gap lies between a train’s automatic protection and operation once that protection is isolated.

M4

Two truths

Trigger
The risk assessment and the manual are produced separately: by different people, at different times, sometimes in different companies.
How you recognise it
  • ‘We took the warnings over from the previous model.’
  • ‘The residual risk is in the assessment, but where is it in the manual?’
What lies behind it
There is no traceable link from the hazard via the measure to the user information.
What it takes
A context table that links every hazard to its place in the manual. It makes gaps, duplicates and contradictions visible.
Result
An alignment, cleaned-up safety chapters and a template for every further product.
Limit
The risk assessment stays with the manufacturer’s experts.

Case example: the case note ‘The watertight door’ follows a hazard from its identification to the behaviour on board and shows where the chain breaks.

M5

Third-party input has to fit

Trigger
Supplier documentation, test records or incoming data arrive in varying quality and have to go into your own system.
How you recognise it
  • ‘We check the supplier documentation when there’s time.’
  • ‘Every supplier delivers a different format.’
What lies behind it
There are no fixed checking criteria. Everyone checks differently, and errors surface late.
What it takes
Checking criteria and checklists and, if you wish, an AI-assisted pre-check under one rule: the machine suggests, a person decides, safety statements are left untouched.
Result
A checking procedure, templates and, if you wish, a configured checking assistant using the tools your IT has approved.
Limit
Release stays with a person.

M6

The evidence has to hold

Trigger
Requirements, risks, tests and documents sit in different systems, and an audit asks how they connect.
How you recognise it
  • ‘We do the traceability in Excel at the end.’
  • ‘Which version was actually released?’
What lies behind it
The chain of evidence is reconstructed afterwards instead of being kept as the work goes on.
What it takes
Clarifying which system holds which truth, defining linking rules and adapting templates, for example for the design history file, phase gates or batch review.
Result
An evidence structure, adapted templates and audit-ready documentation.
Limit
The existing tool is not replaced, and no new one is introduced.

Simulated example: the film ‘Evidence and traceability’ in the section How I work.

M7

Content moves house

Trigger
A system change (from desktop publishing to XML or a component content management system), a spin-off, a merger or a growing number of variants.
How you recognise it
  • ‘We maintain the same thing in five places.’
  • ‘After the migration everything looks the same as before, only slower.’
What lies behind it
Content is moved one to one without first settling the content model: modules, metadata, variants, terminology.
What it takes
The model first, then the move: a structure check, a clean-up and migration rules.
Result
An assessment with priorities, a content model and a terminology base.
Limit
System programming is not part of it.

Simulated examples: the films ‘Content pooling concepts’ and ‘Variant management’ in the section How I work.

M8

Knowledge lives in heads

Trigger
New requirements, staff turnover, new team members or a complex system that operators or service staff need to understand.
How you recognise it
  • ‘Only our colleague knows that.’
  • ‘The training was good, but two weeks later it’s all forgotten.’
What lies behind it
Knowledge is passed on as a lecture, not where the work happens.
What it takes
Short learning units with exercises from your own documentation, and troubleshooting that follows the way technicians think.
Result
Microlearnings or learning videos, knowledge checks and revised troubleshooting guides. Everything belongs to you afterwards.
Limit
I do not run a learning management system.

Examples: the microlearning ‘Power off does not mean energy-free’ and the microlearning series ‘Five open doors’.

Where your case departs

A pattern is a starting point, not a template. In a first conversation we work out which pattern applies to you and where your case departs from it. That is usually where the real work lies.

The linked case notes retell public investigation reports in my own words; they are not client projects. The sample assignments in the films are simulated.