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

Pathway card

One writer, many writers

Who writes a technical text — and why does it matter that it isn’t one person?

A pathway card shows where a practice starts, where it can get to, what does not change on the way, and the steps from one to the other. The path from before to after

By knowledge.aitechdoc.world

Reviewed

Review log and changes

The short answer

A technical text has several writers: the technical writer who formulates it, the subject-matter expert who supplies the values, the translator, the reviewer, the person who releases it, and systems or AI functions that generate or draft parts of it. Naming them apart shows where a question about a value has to go and where a second view is required.

For: Technical writers, technical project managers and documentation systems developers

Key points

  • The writer’s stack is one person’s thinking — the text has more writers.
  • Formulated is not supplied: the expert decides the value, the writer the wording.
  • Reviewing and releasing are two roles where safety information is concerned.
  • Drafted text is marked until a person has taken it over.

Before and after

Before

One writer

  • The technical writer is named as the author.
  • Values from engineering arrive as “input”.
  • Review and release are done by whoever has time.

After

Many writers, named by role

  • Each value names who supplied it and in which revision.
  • Review and release are two named roles for safety information.
  • Drafted and translated text names its writer.

Side by side

Each row names how far the control is as of the review date.

AspectBeforeAfterMaturity
AuthorOne bylineWriter, contributors and their rolesBuilding block available

Metadata in content systems

Supplied valuesCopied from e-mail or meetingsLinked to the source and its revisionBuilding block available

Common in CCMS and PLM links

Review and releaseOne person, one stepTwo roles, both recordedBuilding block available

Release workflows

AI draftsNot distinguishableMarked until taken over by a personProduct-specific

Varies by tool

The path from before to after

Each step names who does it and what it leaves as evidence.

  1. Name the writers

    List who writes, supplies, translates, reviews and releases for one document type.
    Who
    Technical writer
    Evidence
    Role list
  2. Record supplied values

    Link every value to the person or system that supplied it.
    Who
    Technical writer with the experts
    Evidence
    Source links per value
  3. Separate review and release

    Decide where a second view is required and give the two roles to two people.
    Who
    Documentation owner
    Evidence
    Release workflow
  4. Mark drafted text

    Mark text drafted by a function until a person takes it over.
    Who
    Documentation systems developers
    Evidence
    Draft marking rule

Limits and residual risk

Naming roles doesn’t create competence or replace the review. Small teams may hold several roles; the role grammar only asks for them to be named.

The context

The simplification

The blueprint “Thinking models for technical writers” describes how a technical writer structures complexity before writing. That is one person’s work, and it is right to describe it in the singular.

Where it becomes too coarse

The finished text has more writers. A subject-matter expert supplies the interlock value; a translator writes the target text with a translation memory; a drafting function proposes a first version; a reviewer checks; a releasing person takes the release decision. When a value turns out to be wrong, the question has to go to the one who supplied it — not to the one who formulated it.

The role grammar

The family writing names creating and contributing apart; the family deciding names reviewing and releasing apart, following the idea of segregation of duties. The record of who supplied what is part of the content provenance.

Questions readers ask next

Does every text need four people?
No. A small team can hold several roles. The role grammar asks for them to be named apart where a check depends on a second view — safety information, values a release rests on.
Is an AI drafting function a writer?
It writes a proposal. Until a person has taken it over, the text is marked as drafted; the function never releases.

Review log and changes

Every context card is checked against its sources before it is published, and again whenever it changes; the date under the byline is the last review. Corrections (something was wrong) and additions (something was missing) are logged below with date and time (Berlin time). Typos, formatting and link fixes are not listed.

Reviewed

No corrections or additions since publication.