Standards Style Manual, Part 2
Rules for the structure and drafting of SQLBL deliverables: document elements, clause numbering, verbal forms, references and annexes.
- 9th, 2025-09-08
- 8th edition
- Technical Management Board
- All deliverable types
Application
Part 2 applies to every deliverable registered in the corpus, including composite profiles and control documents. Where a committee requires a departure, the departure shall be recorded in the foreword and approved by the editorial panel before publication.
Document elements
| Element | Status | Content |
|---|---|---|
| Title page | Required | Reference number, edition, title, stage code, ICS field, price group. |
| Foreword | Required | Committee responsible, edition history, relationship to previous editions. |
| Introduction | Optional | Non-normative background; shall contain no requirements. |
| 1 Scope | Required | Subject and aspects covered; states what is excluded. No requirements. |
| 2 Normative references | Required | Documents indispensable for application; undated references admit the latest edition. |
| 3 Terms and definitions | Required | Defined terms in systematic order; each entry numbered. |
| 4 Symbols and abbreviated terms | Optional | Used only where the deliverable relies on them. |
| 5 … n Requirements | Required | Normative clauses expressed with the verbal forms of Clause 7. |
| Annex A … (normative) | Conditional | Requirements that would disturb the flow of the main clauses. |
| Annex Z (informative) | Optional | Explanatory material, checklists, worked examples. |
| Bibliography | Optional | Documents cited informatively. |
Drafting rules
- Clause numbering
- Clauses are numbered from 1 in a single sequence. Subdivision beyond the fifth level is not permitted. A clause shall not be subdivided into a single subclause.
- Verbal forms
- Requirements use shall; recommendations use should; permission uses may; possibility uses can. The forms must, has to, and it is necessary that shall not be used to express requirements.
- Deprecated wording
- Do not use where possible, as appropriate, adequate, or sufficient in a requirement: such wording cannot be verified in assessment.
- Numbers and units
- The decimal sign is a full stop. Digit grouping uses a thin space, never a comma. Quantities are stated with their unit at first occurrence in each clause.
- Cross-references
- Refer to clauses by number, never by page. Undated references to other SQLBL deliverables admit all later editions; dated references do not.
- Notes and examples
- Notes and examples are informative and shall contain no requirements, permissions, or recommendations.
- Header apparatus
- Since the amendment of 2026-06-19, every published deliverable carries its current stage code, ICS field, price group and responsible committee in the document header.
Verbal forms are defined normatively on the conformance page; stage progression under Part 1 is tabulated in the stage codes table.