Glossary Updates16 new terms added to the glossaries · 12 November 2026, 21:23 CET
AI TechDocKnowledge
  • English (US)
  • English (UK)
  • Deutsch
All blueprints

Blueprint · Method refinement

The role grammar of technical information: readers, writers and compilers

Four axes that say who does what with a piece of technical information — people and systems alike

A role is what someone does with the information — not who they are.

By
By Saina Veigel · Communications Specialist · Senior Technical Writer
Edition
1
First published
Reviewed

The earlier blueprints on this site speak of the writer, the machine and the reader — in the singular. That is a deliberate simplification. It makes a first model easy to hold: someone builds the structure, something uses it, someone acts on it. For a first look at a documentation project it is enough, and it shows quickly who has an interest in the source.

In practice each of the three is a family. Many people write: the technical writer, the engineer who supplies the values, the translator, the reviewer and the person who releases. Many systems write too. Many people read, and they differ: an operator who was instructed for one task, an operator trained on the machine and a skilled person who may open the control cabinet need different information from the same page. And between them sit systems that pass the information on, compile it into something new — and sometimes write it back.

This blueprint sharpens the simplification without replacing it. It describes a role grammar: four axes that say, for one piece of information, what is done with it, who does it, what they can and may do, and in which situation. The axes are the same for people and systems. The earlier blueprints stay valid; this one says where their singular has to become a plural.

It is written for technical writers, technical project managers and documentation systems developers who have to decide whom a document addresses, who may change what in it, and which system or person a value comes from. The examples take place at the fictional reference system DS-3, the configurable assembly and test cell of the check strategy “Who decides which value counts”.

Why the singular needs a plural

A model in the singular is a lens. It brings one question into focus — what does the writer have to think through, what has to happen in the reader’s mind, what does the machine need — and leaves the rest out of the picture on purpose. The earlier blueprints use it that way, and they gain clarity from it.

The singular becomes a problem only when a decision depends on the difference it leaves out. Whether a warning is enough depends on who reads it. Whether a change is released depends on who may release it. Whether an answer can be trusted depends on whether the function that gave it read the source or compiled a new text from several sources. In these places the singular hides the very thing documentation has to decide.

The role grammar doesn’t add new actors to the earlier models. It adds the axes along which the existing ones differ, so that a singular can be opened into its plural where a decision needs it — and closed again where it doesn’t.

Behind “the writer”, “the machine” and “the reader” of a single warning there are usually:

  • a technical writer and an engineer who supplies the values
  • a reviewer and a person who releases
  • a translator and a translation memory
  • an AI function that drafted a first version
  • a content system that assembles the manual
  • an answer function that composes answers from it
  • an instructed operator, a trained operator and a skilled person
  • a service agent that sets a status after a repair

Each of them does something different with the same sentence.

Documentation doesn’t need to describe all of them every time. It needs to know which difference a decision depends on — and name that one.

The core problem

When roles are named in the singular, the differences that decisions depend on disappear.

  • “The user” is written for, and the instructed operator gets the text written for the skilled person.
  • A qualification is taken for an authority: someone who can do a task is assumed to be allowed to.
  • A job title is taken for a role: “the engineer” both supplies a value and releases it, and nobody notices that the four-eyes principle has gone.
  • An answer function is called a reader, although it writes a text that nobody released.
  • “The machine” is treated as one actor, although its parts read, compile and write in different ways and have different owners.
  • A situation is taken for a person: the novice is planned for the first use, the expert for maintenance — and the expert in an emergency is forgotten.
  • An agent that was meant to read writes back, and nobody had written down that it may.
  • A translation is treated as a copy, although the translator writes a new text in another language.

A role that is named in the singular can’t be checked — and a role that can’t be checked is played by whoever happens to be there.

Blueprints

The four axes and their parts

Five activity families, then the actor, the qualification, the authority, the situation — and the role sentence that joins them

The first five parts are the activity families: what is done with the information. The next four are the axes that say who does it and under which conditions. The tenth part is the role sentence that joins them. Each part answers one test question and leaves a documentation decision behind.

Scroll sideways to see every column.

The four axes and their parts
PartTest questionDocumentation decision
WritingWho creates or contributes this piece of information?The authors and contributors · the source of every value · the marking of drafted text
DecidingWho may decide that this version counts?Review and release roles · the version that counts · the separation of writing and releasing
CompilingWhat becomes new when this information is passed on, combined or answered from?The compiling roles · what each of them may change · the record of what was compiled from what
UsingWho acts on this information, and what do they need to act safely?The target groups by qualification · the tasks per target group · where a task ends
Writing backWho acts on this information and changes a value while doing so?Write authorities · the gate for each write-back · the record of every change
The actorIs this role played by a person, a rule-based system, an AI function or an AI agent?The actor per role · the review a probable result needs · what an agent may do on its own
QualificationWhat can this person do, and how is it shown?The qualification levels a document uses · the tasks per level · the terms from the applicable standards and laws
AuthorityWhat may this role do here — on this product, today, in this operating mode?Authorities per role · access levels and operating modes · the separation of duties
SituationIn which situation does this role meet the information?The use situations per target group · the information each situation needs · what never depends on the situation
The role sentenceCan the role be written as one sentence with all four axes?A role sentence per decision that depends on a role · the gaps it shows · where the singular is enough

The parts are not a sequence that every piece of information passes through, and not an organisation chart. They are a grammar: a way to say, for one piece of information, who does what with it.

A role is what someone does with the information — not who they are.

One warning, many roles · Reference

The role table

The warning on the door interlock of the fictional cell DS-3, seen through all four axes

The table follows one piece of information — the warning that the door of the test station may only be opened after the cell has stopped and the interlock has released — through the roles it passes. Each row names the activity, the actor, the qualification and the authority, the situation, what the role needs and the documentation decision. The example is fictional.

Scroll sideways to see every column.

The role table
RoleActivity familyActorQualificationAuthoritySituationWhat the role needsDocumentation decision
Technical writerWritingPersonTrained technical writerMay write and change the topic; may not release itChange after a design revisionThe released risk assessment and the design revision the warning rests onName the source of every value in the warning and the revision it belongs to
Design engineerWriting (contributing)PersonSubject-matter expert for the interlockDecides the technical value in engineering; may not edit the topicChange of the interlock designA question that names exactly which value the documentation needsRecord which values the expert supplied and in which revision
Drafting functionWritingAI function—May propose a draft; may not change the sourceFirst draft of a reworked topicThe released source and the rule that safety information is never shortenedMark AI-drafted text until a person has taken it over
Reviewer and releasing personDecidingPerson (two people)Writer for the review; responsible person for the releaseThe releasing person may release; the writer may not release their own textRelease of a new revisionThe changes against the last revision and the evidence they rest onKeep review and release apart and record both
TranslatorCompiling (translating)Person with a translation memoryQualified translator for technical textsMay write the target text; may not change the sourceTranslation of the released revisionThe released source revision and the terminologyTranslate only released revisions and record which one
Answer functionCompiling (answering)AI function—May compose answers from released units; may not shorten safety informationA question at the operator panelReleased units with their validity and the boundary of what it may answerTreat every answer as a new text that refers to released sources, not as a reading
Operator, instructedUsingPersonInstructed personMay stop the cell and acknowledge a fault; may not bypass the interlockRoutine operationOne action and one warning, in the order of the taskWrite the task for the qualification it names, and say where the task ends
Operator, trained on the cellUsingPersonTrained for setup and format changesMay open the door after the interlock has released; may change format partsFault: a part is jammed in the stationThe safe state, how to reach it and how to tell it is reachedGive the fault its own task with the check of the safe state
ElectricianUsingPersonSkilled person (electrically)May work in the control cabinet after lockout/tagoutMaintenance of the interlockThe circuit, the energy sources and the test after the workAddress the skilled person by name of the qualification, not as “qualified staff”
Service agentWriting backAI agent—May propose a status; may set it only after approval by a personAfter a repairThe rule which values it may write and who approvesRecord every write-back with its basis and its approval

Qualification and authority are separate columns on purpose. The same person can be qualified for a task and not authorised to do it on this cell, today, in this operating mode.

One warning, ten roles — and each of them needs something different from it.

Where the singular becomes a plural

The crosswalk to the earlier blueprints

Each earlier blueprint with the simplification it makes, why it helps there, the axis that sharpens it and the card that shows the step

The earlier blueprints stay valid. Each of them simplifies on purpose, because its question is answered more clearly that way. The table names the simplification, why it helps, which part of the role grammar opens it and the context card of the series “Method refinement” that shows the step from before to after.

Scroll sideways to see every column.

The crosswalk to the earlier blueprints
BlueprintWhat it simplifiesWhy it helps thereWhat sharpens itMethod refinement card
Thinking models for technical writersOne writer who structures complexityThe thinking before writing is one person’s workWriting · Deciding · QualificationOne writer, many writers
Cognitive psychology for technical communicationOne reader; situation and prior knowledge in one rowWhat happens in a mind is described for one mindUsing · Qualification · SituationThree operators, one warning
AI-enabled information systems for technical writersJob groups as perspectives; one reader, one AI agent; the machine as one actorThe grid shows quickly who has an interest in the sourceThe actor · Compiling · Writing backFrom job groups to roles · The machine is a network
AI systems and the machine: levels and boundariesLevels by who decides, not by what is done with the informationThe scope question is answered level by levelThe actor · CompilingThe machine is a network
The content lifecycle under AIReader and user as one; the answer function in the answering stageThe stages and their gates stay in viewCompiling · UsingThe answer function compiles
Who decides which value countsThree placeholders as one lens on everyone with a stake in a valueA check method can be designed before a single system is namedThe five activity families · Qualification · AuthorityFrom three readers to check roles
The cow modelAn idealized reader as the test of the textThe test question needs one reader to imagineUsing — only where several readers are meantNone — the singular is the method

The blueprints in the intranet (the evidence space, the MedTech evidence chain) already name several roles of their own; the MedTech evidence chain names the reviewer as a reader of its own.

The singular is a lens. The role grammar says when to change it.

Confusions · Reference

Where the axes get mixed up

Each confusion with the axes it merges, an example, what it costs and how to keep them apart

Most mistakes with roles are not missing roles but merged axes. Each row names a confusion, the axes it merges, an example at the fictional cell DS-3, what it costs and how to keep the axes apart.

Scroll sideways to see every column.

Where the axes get mixed up
ConfusionAxes mergedExampleWhat it costsKeep apart by
Qualification taken for authorityQualification · AuthorityA skilled person from another site opens the control cabinet of DS-3 without being authorised thereThe operator’s control over who works on the cellName the required authority in the task, next to the qualification
Situation taken for qualificationSituation · QualificationThe jam-clearing task is written for “experienced users”, but a jam happens on every shiftThe instructed operator meets a task written for someone elsePlan each situation for every target group that meets it
Job title taken for roleActivity · Actor“The engineer” supplies the interlock value and releases the topicThe second view that the release was meant to giveName supplying and releasing as two roles, also if one team holds them
Actor taken for activityThe actor · Compiling“It’s AI, so it reads the manual”The answer is treated as the manual, although nobody released itName the activity first: an answer function compiles
The machine taken for one actorThe actor · Levels“The machine got it wrong”Nobody can say which part to correctName the part — index, retrieval, model, agent — and its owner
Reader taken for writerUsing · Writing backThe service agent sets a part status that the next export spreadsA value that nobody released becomes the current oneGive every role that writes back a scope, a gate and a record
Translation taken for copyCompiling · WritingThe translation of revision B is kept after revision C was releasedA language version with an old warningTranslate released revisions only and record which one

The column “Keep apart by” names documentation decisions, not organisational rules. Who is qualified and who is authorised is decided by the manufacturer and the operator.

Two axes that are kept apart can be checked one by one.

The parts of the role grammar

Each entry explains one part: its test question, what it covers, where it ends and what documentation has to decide about it. The first five are the activity families, the next four the axes, the last the role sentence.

  1. Writing
  2. Deciding
  3. Compiling
  4. Using
  5. Writing back
  6. The actor
  7. Qualification
  8. Authority
  9. Situation
  10. The role sentence

1. Writing

Core question: Who creates or contributes this piece of information?

Writing creates a piece of information or contributes to it: the technical writer who writes the topic, the engineer who supplies the value, the system that generates a parameter list, the function that drafts a first version.

Questions to ask in this family:

  • Who wrote this text, and who supplied the values in it?
  • Which parts were drafted by a function and taken over by a person?
  • Who would have to be asked if a value turns out to be wrong?

The writer of the earlier blueprints is the technical writer who structures complexity before writing. In practice the text has several writers. The subject-matter expert contributes knowledge that the writer turns into a usable unit; an engineering system contributes values; a drafting function contributes a proposal. Each of them writes, and each of them is a different source of error.

For documentation, writing is the family where questions go. A text that names only one author sends every question about a value to the person who formulated it, not to the one who decided it.

  • Formulated is not supplied.
  • A draft is not a text until someone takes it over.

Every piece of information has more writers than its byline shows.

Documentation decision

  • The authors and contributors
  • the source of every value
  • the marking of drafted text

2. Deciding

Core question: Who may decide that this version counts?

Deciding reviews a piece of information, releases it or keeps it as the version that counts: the reviewer, the person responsible for the release, the system of record that holds the released revision.

Questions to ask in this family:

  • Who reviews, and who releases — are they two people?
  • Which system holds the version that counts?
  • How does a released version become visible to everyone after it?

Writing and deciding are often done by the same person, and that is not wrong in itself. It becomes a risk where a check depends on a second view: safety information, values that a release rests on, changes that reach many documents at once. There, the role grammar asks for the two roles to be named apart, even if a small team has to give them to two people who otherwise do the same work.

Systems decide too. A system of record decides which revision counts for one object; a content system decides which topic version is released. The check strategy “Who decides which value counts” describes these roles from source to answer.

  • Reviewed is not released.
  • Holding a value is not deciding it.

A version that nobody decided is decided by whoever saves last.

Documentation decision

  • Review and release roles
  • the version that counts
  • the separation of writing and releasing

3. Compiling

Core question: What becomes new when this information is passed on, combined or answered from?

Compiling takes information that exists and makes something from it: an interface passes it on, a report derives a figure, a content system assembles a manual, a package bundles it, a translator writes it in another language, an answer function composes an answer.

Questions to ask in this family:

  • Is the result a copy, a derivation, an assembly, a translation or a new text?
  • Which released sources and revisions went into it?
  • What may the compiling role change — order, wording, scope, nothing?

Compiling is the family that the singular hides most. In the chain writer — machine — reader, everything in the middle looks like transport. But a translation is a new text, an assembled manual is a new combination, and an answer is a text that nobody released. The answer function reads and writes in one act; it is a compiler, not a reader.

For documentation, compiling decides what can be traced. A result that records what it was compiled from can be corrected when a source changes. A result that doesn’t is a new source that nobody owns.

  • An answer is not a reading.
  • A translation is not a copy.

Everything that is compiled is new — and needs to say what it was made from.

Documentation decision

  • The compiling roles
  • what each of them may change
  • the record of what was compiled from what

4. Using

Core question: Who acts on this information, and what do they need to act safely?

Using reads a piece of information, looks at it or acts on it: the operator at the panel, the service technician, the electrician, the auditor who checks the documentation, the system that takes a value over without changing it.

Questions to ask in this family:

  • Who reads this — with which qualification and in which situation?
  • What does each of them have to do, and what must they not do?
  • Who reads to check rather than to act — an auditor, a notified body, a buyer?

The reader of the earlier blueprints is the person in whose mind documentation has to work. That person is rarely one person. The same page is read by someone who was instructed for one task, someone trained on the machine and a skilled person who may do more — and by people who don’t act on the product at all but check what the documentation says about it.

Target audience analysis, as IEC/IEEE 82079-1 describes it, already asks for the users’ skills and qualifications. The role grammar keeps that answer visible in every task: whom the task addresses, and where it ends for the others.

  • The user is not one person.
  • Reading to check is not reading to act.

A task that doesn’t name its reader is written for the one who needs it least.

Documentation decision

  • The target groups by qualification
  • the tasks per target group
  • where a task ends

5. Writing back

Core question: Who acts on this information and changes a value while doing so?

Writing back is using that changes something: a technician who sets a status after a repair, a function that corrects a value, an agent that opens a ticket or updates a record. Whoever writes back has become a writer.

Questions to ask in this family:

  • Which values may this role change, and in which system?
  • Which changes need a person’s approval before they take effect?
  • What is recorded about each change — the value before, the basis, the authority?

Writing back closes the circle between the user and the writer. It is where feedback becomes data, and where an agent that was built to read becomes a source. The family exists so that this moment is seen: a reader that writes needs what every writer needs — a scope, an owner and a gate.

For documentation, a role that writes back is an author that nobody invited. Its change can alter a value that a document rests on, and the next synchronization copies it as if it had been released.

  • A reader that writes is a writer.
  • Delegated is not authorised unless it is recorded.

Every write-back needs a gate — or the documentation has a writer that nobody knows.

Documentation decision

  • Write authorities
  • the gate for each write-back
  • the record of every change

6. The actor

Core question: Is this role played by a person, a rule-based system, an AI function or an AI agent?

The actor axis says who plays a role: a person, a deterministic system that follows fixed rules, an AI function that does one task with a probable result, or an AI agent that takes several steps with tools of its own.

Questions to ask on this axis:

  • Does the same input always give the same result here?
  • Who reviews a result that is only probable?
  • Which steps does an agent take without a person — and which never?

The actor doesn’t change the activity. An answer function compiles, an interface passes on, an operator uses — whoever or whatever does it. But the actor changes what the role needs: a deterministic system needs its rules checked once, a probable result needs a review each time it matters, an agent needs boundaries before it starts.

“The machine” of the earlier blueprints is not one actor. It is a web of actors that play different roles: an index that holds, a retrieval that selects, a model that composes, an agent that acts. The blueprint “AI systems and the machine: levels and boundaries” describes where the company decides about them; the actor axis describes what each of them does with the information.

  • The machine is not one actor.
  • Probable is not wrong — but it needs a review.

Name the actor, and the review it needs follows.

Documentation decision

  • The actor per role
  • the review a probable result needs
  • what an agent may do on its own

7. Qualification

Core question: What can this person do, and how is it shown?

The qualification axis says what a person is able to do because of their education, training and experience. It applies to readers and writers alike.

Questions to ask on this axis:

  • Which qualification does this task require, and which standard or law names it?
  • Is the person instructed for this task, trained on this product, or a skilled person in the field?
  • Which qualification does the writer need to write this unit — and the reviewer to review it?

Established terms exist for this axis, and the role grammar uses them instead of inventing its own. IEC 60050-826 distinguishes the ordinary person, the instructed person and the skilled person for electrical risks; occupational safety knows the qualified and the competent person; the MDR defines the lay person. Between instruction and skill, many manufacturers name a trained level — trained on this product for setup, format changes or troubleshooting. Which levels a document uses is decided once and then applied in every task.

Writers have qualifications too. A unit on safety parameterization needs a writer who understands it and a reviewer who can check it. The axis makes this visible without turning it into a ranking: a subject-matter expert is not a better writer, and a skilled reader is not a better reader — they need different things.

  • Qualified is not authorised.
  • Instructed for one task is not trained on the product.

A qualification that a document names can be checked. “Qualified staff” can’t.

Documentation decision

  • The qualification levels a document uses
  • the tasks per level
  • the terms from the applicable standards and laws

8. Authority

Core question: What may this role do here — on this product, today, in this operating mode?

The authority axis says what a role may do: the permission granted by the operator of the product, the access level on the panel, the operating mode, the release right in a content system, the write right of an agent.

Questions to ask on this axis:

  • Who grants this authority, and where is it recorded?
  • Does it depend on the operating mode, the access level or the shift?
  • Which duties must stay with different roles?

Authority and qualification are often confused, because they often go together. They don’t always. A skilled person may not be authorised on this machine; an instructed operator may be authorised to stop the cell but not to bypass the interlock. Who grants the authority is the operator’s decision, not the manufacturer’s — documentation can only say which authority a task requires.

Systems have authority too: access rights, release rights, write rights. For AI functions and agents the authority axis is where boundaries are written down — what an agent may change on its own, what it may only propose, and what it may never touch.

  • Can is not may.
  • An access level is not a qualification.

A task that names its authority tells everyone else where to stop.

Documentation decision

  • Authorities per role
  • access levels and operating modes
  • the separation of duties

9. Situation

Core question: In which situation does this role meet the information?

The situation axis says when a role meets the information: first use, routine operation, a task done rarely, a fault, an emergency, maintenance — and for writers a first version, a change or a correction.

Questions to ask on this axis:

  • Which situations does each target group meet the information in?
  • What changes in a fault or under time pressure — attention, prior knowledge, the error that is likely?
  • Which information must stay the same in every situation?

The use-situation grid of the blueprint “Cognitive psychology for technical communication” describes how the same reader needs different information in the first hour, in routine operation and after a fault. The role grammar keeps situation and qualification on two axes, because they cross: a skilled person in an emergency is under the same time pressure as anyone else, and an instructed operator also meets a rare task.

Situation never reduces what is required. A short form for routine operation never leaves out the safety information that the situation of a fault or an emergency needs.

  • A situation is not a person.
  • The expert also has emergencies.

Qualification says what someone can do. The situation says what they can do right now.

Documentation decision

  • The use situations per target group
  • the information each situation needs
  • what never depends on the situation

10. The role sentence

Core question: Can the role be written as one sentence with all four axes?

The role sentence joins the axes for one piece of information: who — with which qualification and authority — does what with it, in which situation.

Questions to ask with the sentence:

  • Which part of the sentence can’t be filled in yet?
  • Does the decision at hand depend on that part?
  • Where is the singular enough, because nothing depends on the difference?

The role sentence is the test of the grammar. “A trained operator uses the jam-clearing task in a fault and may open the door after the interlock has released.” “The answer function compiles an answer from released units at the operator panel and may not shorten the safety information.” Where a part stays empty — nobody knows who releases, or which qualification the task needs — the documentation has found a decision it hasn’t taken yet.

The sentence is also the way back to the singular. Not every decision depends on all four axes. Where it doesn’t, the earlier blueprints’ writer, machine and reader are enough, and the role grammar stays in the drawer.

  • An empty part is an open decision.
  • The singular is a choice, not a mistake.

Write the sentence where a decision depends on it — and only there.

Documentation decision

  • A role sentence per decision that depends on a role
  • the gaps it shows
  • where the singular is enough

Why this matters for documentation

The role grammar turns “the writer”, “the machine” and “the reader” into roles that can be checked:

  • every task names the qualification and the authority it requires
  • target groups are defined once and used in every task
  • writing, reviewing and releasing are named apart where a check depends on it
  • every value names the person or system that supplied it
  • translations and answers are treated as new texts that refer to released sources
  • AI functions and agents are named by what they do, not by what they are
  • every role that writes back has a scope, an owner and a gate
  • situation and qualification are planned on two axes, not one

A role that is named can be addressed, checked and corrected.

Distinctions to keep

The role grammar depends on a few distinctions that everyday language blurs. Each of them keeps two axes or two families apart.

  • A role is not a job title.
  • A role is not a person.
  • Qualified is not authorised.
  • Instructed is not trained, and trained is not skilled.
  • A situation is not a qualification.
  • Formulated is not supplied.
  • Reviewed is not released.
  • An answer is not a reading.
  • A translation is not a copy.
  • The machine is not one actor.
  • A reader that writes back is a writer.
  • The singular is a choice, not a mistake.

Each distinction names two roles that a singular would have merged.

Tools and AI

Tools already hold much of the role grammar: user rights and access levels in content systems and on the panel, release workflows, translation management, target-group metadata, role-based access control, approval gates for agents. What they rarely hold is the connection — that this task addresses this qualification, under this authority, in this situation.

AI functions can help to find where a role sentence is incomplete: tasks without a named target group, warnings without a qualification, write rights without a gate. They can’t decide the roles. Who is qualified, who is authorised and which situations a product creates are decided by the manufacturer, the operator and the people responsible for the documentation.

A tool supports the role grammar when it can:

  • store the target group and the required qualification with every task
  • keep the authority a task requires apart from the qualification
  • record who wrote, who supplied, who reviewed and who released each unit
  • mark text that a function drafted until a person takes it over
  • show which released sources an answer or a translation was compiled from
  • give every role that writes back a scope, an approval step and a record

Tools hold the rights. The role grammar says which right a decision depends on.

The core principle

The core principle is short: a role is what someone does with the information — not who they are.

The earlier blueprints speak of the writer, the machine and the reader, and they are right to: a lens in the singular brings one question into focus. The role grammar opens the singular where a decision depends on the difference it hides — between writers, between readers, between the systems that compile in between — and closes it again where nothing depends on it.

The role grammar supports documentation decisions. It never replaces the target audience analysis, the risk assessment, the operator’s decisions about qualification and authority, the safety information required for a product or the review by the people responsible for the documentation. No qualification level ever justifies leaving out safety-related information, and naming a role never implies compliance.

Cut complexity — create clarity

Explained in context

Context cards explain the general, checkable background of some of the questions this blueprint raises. They are written by knowledge.aitechdoc.world and are not part of the blueprint.

Reference updates

The glossary references, the terms under “Related established methods” and the context cards are attached to this blueprint, not part of it. They are checked and updated on their own, without a new edition.

The references haven’t been updated since the first edition.

How to cite

Saina Veigel (2026). The role grammar of technical information: readers, writers and compilers. Blueprint, edition 1. knowledge.aitechdoc.world. https://knowledge.aitechdoc.world/uk/blueprints/role-grammar-of-technical-information

Edition and changes

Edition 1 · Reviewed

Corrections (something was wrong) and additions (something was missing) since the first edition.

No corrections or additions since the first edition.

About this blueprint

This Check Strategy leads from a thinking model to a check method. It is not a standard, a certified method or a compliance framework. Naming a standard, a law or an established method does not mean that a product, a system or its documentation conforms to it.

The check rules a team builds with it are documentation and data checks. They do not replace the manufacturer’s risk assessment, configuration management, the verification and validation of safety functions or the review by the people responsible for the documentation.

Copyright © 2026 Saina Veigel. All rights reserved. Copyright notice