Standards catalog · 2026 August release

SQLBL 1028:2026

PublishedEdition 1

Verified Consequence Metrics — Reporting Requirements for Claimed Results

Specifies a controlled term for measurable results and the verification metadata that shall accompany each reported result.

Status
Published · stage 60.60
Edition
1 (2026-07)
Publication date
2026-07-15
Technical committee
SQLBL/TC 7 Candidate Materials
Secretariat
SQLBL Central Secretariat
ICS
03.100.30 — Company organization and management — Personnel
Pages
20
Price group
D
Language
English (reference language)
Work item
SQLBL/TC 7/WG 1 N1448
Category
Candidate Materials
Document type
Standard
Cite this document

1Scope§

This document specifies requirements for verified consequence metrics in professional and quasi-professional written communication.

It applies to claimed results in candidate materials and performance narratives.

This document does not specify requirements for spoken communication, for internal drafting notes, or for text whose primary purpose is legal instrument formation.

2Normative references§

The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document.

  • SQLBL 1000, Structured language — Vocabulary and verbal forms
  • For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document applies.

    3Terms and definitions§

    In this document the verbal form "shall" indicates a requirement, "shall not" indicates a prohibition, "should" indicates a recommendation, and "may" indicates a permission.

    Terms and definitions given in SQLBL 1000 and the following apply.

    3.1 verified consequence metric — measurable outcome attributable to the described action and confirmed by a party other than the author

    3.2 attribution window — period within which the outcome is attributed to the action

    4General principles§

    Candidate materials are read comparatively. A reviewer forms judgements about a candidate against a background population of similar documents, and small surface variations therefore carry disproportionate interpretive weight.

    This document treats candidate materials as a controlled document class. Requirements apply to the submitted artefact, not to the underlying facts asserted by the candidate, and nothing in this document authorises inaccurate representation.

    Conformance is assessed per artefact. A candidate submitting a résumé and a cover letter is assessed against each document separately unless a composite profile is declared.

    5Requirements§

    5.1 Measurable results shall be described as "verified consequence metrics".

    5.2 Each metric shall state a baseline, a resulting value, and an attribution window.

    5.3 A metric that cannot be confirmed by a second party shall be described as self-reported.

    5.4 Percentages shall not be reported without the underlying absolute values.

    6Conformance§

    A document conforms to SQLBL 1028:2026 where every requirement expressed with the verbal form "shall" in Clause 5 is satisfied and no requirement expressed as "shall not" is violated.

    Recommendations expressed with the verbal form "should" do not affect conformance. Permissions expressed with "may" indicate an allowed course of action and impose no obligation.

    Conformance claims shall take the form: "This document conforms to SQLBL 1028:2026, Edition 1." Partial conformance shall be declared by clause number, for example "conforms to SQLBL 1028:2026 Clauses 5.1 and 5.2 only."

    Conformance may be assessed manually or by an automated checker. Where an automated checker is used, the assessment record shall identify the checker and the catalog release of SQLBL-1028 against which it was run.

    7Implementation guidance§

    The term is intentionally heavy. Its cost discourages attaching it to unverified figures.

    Where confirmation is unavailable due to confidentiality, the constraint should be stated rather than the metric inflated.

    Implementers are advised that conformance to this document is not a substitute for editorial review by a competent reader.

    8Examples§

    EXAMPLE 1 — Conforming. Verified consequence metric: settlement exceptions fell from 1,240 to 310 per month over two quarters, confirmed by operations reporting.

    EXAMPLE 1 — Non-conforming. Reduced settlement exceptions by 75% and dramatically improved operational efficiency.

    Annex AAssessment checklist§

    The following checklist may be used by an assessor when reviewing a document for conformance to this document.

  • Baseline and result stated.
  • Attribution window stated.
  • Confirmation source identified.
  • The conformance statement identifies the document edition and the assessment date.
  • Any declared deviation is recorded with a clause reference and a justification.
  • BibliographyBibliography§

  • SQLBL 1000, Structured language — Vocabulary and verbal forms
  • SQLBL 9001, Corpus construction — Principles and traceability
  • SQLBL 9004, Conformance assessment — Guidance for assessors
  • SQLBL/TR 938, Technical report on observed usage in candidate materials
  • Life cycle

    PositionStageDescription
    Previous30.99Committee draft approved for enquiry, 2025
    Current60.60International deliverable published
    Next90.20Systematic review scheduled 2029

    Stage codes follow the harmonized stage matrix used for deliverable tracking. Dates are indicative and subject to committee resolution.

    Revision history

    EditionDateSummary
    12026-07-15First edition. Published following technical committee ballot.

    Citation

    Recommended citation

    SQLBL (2026). SQLBL 1028:2026, Verified Consequence Metrics — Reporting Requirements for Claimed Results. Edition 1. SQLBL/TC 7 Candidate Materials. Experimental standards corpus.

    SQLBL documents are fictional research artefacts. They should be cited as corpus material and not as normative authority.