Method Tool · Check rules
The check rule grammar
Seven parts that turn a check question into a check rule a team can run, repeat and prove
A question finds the gap. A rule names who closes it, where, and how you can tell.
- By
- By Saina Veigel · Communications Specialist · Senior Technical Writer
- Version
- 1
- First published
- Reviewed
A thinking model helps you design a check method. With a few placeholders — the source, the person, the systems in between — a team sees in minutes where a document can go wrong and which questions a check has to ask. That is what thinking models are for, and it is why they come first.
A question is not yet a check. “Does the manual show the released revision?” can be asked of any manual, and nobody can run it. To run it, a team has to say which system builds the manual, which part of it looks up the revision, which value is meant, what counts as right, what proves it, who answers for the rule and when it is run.
The check rule grammar gives that sentence its parts. It turns the placeholders of a thinking model and the roles of a check strategy into units a rule can name — a system, a subsystem, a function, a subfunction — and joins them with the value, the condition and the evidence into one rule.
It is written for technical writers, technical project managers and documentation systems developers who build their own check processes and check rules: for releases, changes, translations, publishing, answer functions and write-backs.
From placeholder to check rule
The three stages build on each other. None replaces the one before it: the thinking model keeps the method small enough to design, the roles make it precise enough to assign, and the rule makes it concrete enough to run.
- 1
Thinking model
Three placeholders — the source, the person, the systems in between — find the check questions and show where a check method needs to look.
- 2
Check strategy
The placeholders open into roles: who writes, decides, compiles, uses or writes back a value. Each role says what may be done with the value there.
- 3
Check rule
Each role is tied to a unit — system, subsystem, function, subfunction — and to a value, a condition, evidence, an owner and a trigger. Now the check can be run, repeated and shown.
A question that names no unit is checked by whoever happens to look.
The seven parts of a check rule
A check rule is one sentence with seven parts. If one part can’t be filled in, the rule isn’t ready — and that gap is itself a finding.
1 / 7
Unit
Question: Where exactly is the value checked?
The place in the landscape, named from the outside in: system › subsystem › function › subfunction. Go as deep as the rule needs and no deeper — a rule on a release can stop at the function, a rule on a revision lookup needs the subfunction.
ExampleCCMS › publishing subsystem › assembly function › revision lookup
2 / 7
Role
Question: What does the unit do with the value?
One of the roles of the check strategy: source, system of record, master data, integration, derived data, document assembly, exchange package, consuming system, system of engagement, person, acting system. The role sets what the rule may demand — a compiling unit can be asked to name its sources, not to decide the value.
ExampleDocument assembly (compiling)
3 / 7
Value
Question: Which piece of information, and which attribute of it?
The value a decision rests on, with the attribute the rule is about: a part number, its revision, a test interval, a warning text in one language, a status. “The content” is not a value.
ExampleRevision of every assembly listed in the order manual
4 / 7
Condition
Question: What counts as right?
The condition the value has to meet, said against its system of record: equal to, not older than, released for this scope, named with its revision. A condition never allows required or safety-related information to be left out.
ExampleEquals the revision released in the PLM system for the order’s configuration
5 / 7
Evidence
Question: What shows afterwards that the rule held?
The record that proves the check: a build record, a lineage record, a change log, an answer record, a write record. Evidence that only exists in someone’s memory is no evidence.
ExampleThe build record lists the assembly revisions the manual was assembled from
6 / 7
Owner
Question: Who answers for the rule?
The role that answers for the rule and decides when it fails — named as a role, not a job title. The owner of a rule is often not the owner of the value: the content owner answers for the assembly rule, engineering for the revision.
ExampleContent owner of the order manuals
7 / 7
Trigger
Question: When is the rule run?
The event that runs the rule: a release, a change notice, an assembly, a translation package, a publication, an answer, a write-back — or a fixed interval for what changes without an event. A rule without a trigger is checked once and then trusted.
ExampleEvery assembly of an order manual, and every change notice for an assembly in it
Unit, role, value, condition, evidence, owner, trigger — one sentence, and the check can be run by someone who wasn’t in the room.
The levels of a unit
A unit is named from the outside in. The levels use established terms in their usual sense; what is new is only that a check rule names them.
Scroll sideways to see every column.
| Level | What it names | Example at DS-3 | Established term |
|---|---|---|---|
| System | A system that holds or processes the value as a whole, with an owner | The component content management system (CCMS) | System and system element, ISO/IEC/IEEE 15288 |
| Subsystem | A part of the system with a task and an owner of its own | The publishing subsystem of the CCMS | Subsystem, IEC 61508-4; in machinery safety also ISO 13849-1 and IEC 62061 |
| Function | What the unit does with the value | Assembling the order manual from the configured bill of materials | Function, as in functional decomposition in systems engineering |
| Subfunction | The one step of the function that touches the value | Looking up the revision of each assembly | Sub-function, as in IEC 62061, where a safety function is decomposed into sub-functions |
| Value and attribute | The piece of information and the attribute the rule is about | Part number and revision of the interlock switch | Data element and attribute |
In machinery safety, subsystem and sub-function refer to safety-related control systems and their safety functions. A check rule on documentation borrows the structure of the words, not their safety meaning: it never verifies or validates a safety function.
Rule templates per activity family
The five activity families of the role grammar each ask a different kind of rule. Fill in the brackets; keep the sentence.
Scroll sideways to see every column.
| Family | Roles | Rule template | Typical evidence |
|---|---|---|---|
| Writing | Source | [Unit] creates [value]. It is handed on only with status [status] and with its source named. | Release status in the source system |
| Deciding | System of record · Master data | [Unit] is the system of record for [value] in [scope]. Every other unit holds a copy with the revision it took over. | Catalogue of systems of record; revision and release date |
| Compiling | Integration · Derived data · Document assembly · Exchange package · Answer function | [Unit] compiles [value] from [sources]. The result names the source and revision of every value it holds. | Build record or lineage record |
| Using | Consuming system · System of engagement · Person | [Unit] shows or uses [value] only in the revision released for [scope] and learns about a change through [channel]. | Shown revision; change notification log |
| Writing back | Acting system | [Unit] may write [value] into [system] only within [authority], for [scope], after [gate]. | Write record with authority, value before and approver |
An answer function compiles, even when people read its answer: its rule asks for the sources, not for the decision.
A worked example: one change at DS-3
The fictional test cell DS-3 gets a new revision of its door assembly with a successor interlock switch. Five rules cover the chain from the release to the write-back.
Scroll sideways to see every column.
| Rule | Unit | Role | Value | Condition | Evidence | Owner | Trigger |
|---|---|---|---|---|---|---|---|
| R1 | PLM › change management › release function › change notice | Source · System of record | Revision of the door assembly | A released revision carries a change notice with its reason and scope | Change notice | Engineering | Release of a revision |
| R2 | ERP › material master › bill of materials update › planning run | Master data | Revision of the door assembly in the bill of materials | Follows the released revision on the day of release — or the assembly of affected documents is held | Change log of the bill of materials | Data owner for the material | Change notice received |
| R3 | CCMS › publishing subsystem › assembly function › revision lookup | Document assembly | Revision of every assembly in the order manual | Equals the revision released in PLM for the order’s configuration | Build record listing the revisions used | Content owner | Every assembly of an order manual |
| R4 | Service portal › retrieval chat › answer function › source selection | System of engagement (compiling) | Part number and test interval of the interlock switch | Taken from one revision per part, and the revision is named — otherwise the answer refers to the source | Answer record with its sources | Owner of the answer function | Every answer |
| R5 | Service agent › ticket handling › status update › write-back | Acting system | Availability status of a spare part | Written only within the recorded authority, for the scope of the ticket, after approval by the data owner | Write record with authority, value before and approver | Data owner for the material | Every write-back |
DS-3, its systems and its values are fictional. The rules show the structure, not a recommended rule set for a real landscape.
Mistakes when writing check rules
Most rules that can’t be run miss one of the seven parts. The mistakes are easy to spot once the parts have names.
Scroll sideways to see every column.
| Mistake | Looks like | Write instead |
|---|---|---|
| No unit | “The manual shows the current revision.” | Name the unit: CCMS › publishing subsystem › assembly function › revision lookup. |
| A product category for a role | “PLM decides.” | Decide per value: PLM is the system of record for the revision of the door assembly. |
| A placeholder for a role | “The reader must see the warning.” | Name the role and its situation: an instructed operator at the operator panel in routine operation. |
| “Current” for a condition | “Values must be up to date.” | Say against what: equal to the revision released in the system of record for this scope. |
| No evidence | The check is done, but nothing shows it. | Name the record that remains: build record, lineage record, answer record, write record. |
| No trigger | The rule was checked once, at the launch. | Name the event that runs it again: change notice, assembly, translation package, write-back. |
| A condition that leaves information out | “Show only what the role needs.” | Adapt the form, never the required or safety-related information: it stays complete for every role. |
A rule that names its parts can be reviewed by someone else. A rule that doesn’t can only be believed.
Checklist for one rule
Before a rule goes into a check process, it answers yes to every line:
- The unit is named down to the level the rule needs.
- The role says what the unit does with the value — and the rule asks nothing the role can’t do.
- The value names its attribute.
- The condition is said against the system of record, not against “current”.
- The evidence is a record that remains after the check.
- The owner is a role, named once, and knows the rule exists.
- The trigger is an event or an interval, not a good intention.
- No condition leaves out required or safety-related information.
Limits
The check rule grammar structures documentation and data checks. It doesn’t decide which system is the system of record for a value, who owns it or which system may write back: those decisions are made in the company, and the rules only make them visible.
It doesn’t replace the manufacturer’s risk assessment, configuration management, the verification and validation of safety functions, the conformity assessment or the review by the people responsible for the documentation. A rule written with it never makes a document compliant or a machine safe.
About this method tool
This method tool is a working form, 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.
Check rules written with it are documentation and data checks. They do not replace the manufacturer’s risk assessment, the verification and validation of safety functions or the review by the people responsible for the documentation.
How to cite
Saina Veigel (2026). The check rule grammar. Method Tool, Version 1. knowledge.aitechdoc.world. https://knowledge.aitechdoc.world/uk/method-tools/check-rule-grammar