All rules

A defined term used in another form

defined-term-formon by default (info)Japanese / English

A defined term later written in another form: quoted, lower case, or lengthened

Example

Flagged
# Terms 1. We provide a room booking service (the "Services"). 2. You may use the Services for business only. The Services are provided as is. 3. You must not resell the services.
What chaff prints
7:28 "Services" is defined with a capital on line 3, but written in lower case here
Fixed
# Terms 1. We provide a room booking service (the "Services"). 2. You may use the Services for business only. The Services are provided as is. 3. You must not resell the Services.
What chaff prints
no finding
chaff.yaml used for this example
genre: legal/contract

How to fix

Use the defined term without quotes and, in English, with its capital as defined. If the ordinary sense is meant, use another word.

Why it matters

A contract uses each defined term exactly as defined. Quoting a term again after its definition ("the "Services"") leaves the reader asking whether it is being defined anew. Writing "services" where "Services" is defined splits the defined sense from the ordinary one, which is where disputes start. In Japanese, 本件業務 written where 本業務 is defined reads as another task. "the Application" written where the Pinecone Notes application is defined as the "App" leaves the reader asking whether it is the same thing. chaff points at a term set in quotes again after its definition, at a capitalised term written in lower case (when the capitalised uses are more, "records officer" for "Records Officer" too), at a Japanese term written with its other prefix (本 for 本件 or the other way round) unless that form is defined too, and at a term made longer with a word of its own definition (Application for App, 文書管理責任者 for 管理責任者). Statutes and regulations use their defined terms as defined, too.

What it does not flag

The definitions themselves ("Services" means, (the "Services")), uses before the definition (use-before-definition reads those), capitals at the start of a sentence, and terms written in lower case more than {limit} times or more often than capitalised (taken as the ordinary word used on purpose) are not reported, nor is a use inside the defining sentence ("Customer" means the party named "Customer"). A statute or a regulation (a document read with the statute profile) quotes a term to talk about the term itself ("controller" has the same meaning as in Part 3), so a quoted term is not reported there. A lower-case phrase that starts with an adjective, or that an adjective, a possessive or a noun comes before (its own confidential information, additional terms of service, a common parent, a limited liability company), one followed by "of" and a bare noun (certificates of deposit), and one inside another defined term (certificate of merger where Certificate of Merger is defined) is the ordinary phrase and is not reported; after a pointing word (the other party, such company) it is. Nor is a quoted term that the words before it name as a term (the definition of "Material Adverse Effect", the term "Affiliate"). Nor is a quoted Japanese term that quotes the wording of a provision or a document (憲法一九条にいう「良心の自由」, 「謝罪」の文言). A term with its other prefix (本件業務 for 本業務) is not reported when that form is defined too, or inside a longer word (見本物品). A longer word is not reported when only a pointing word comes before the term (当該管理責任者), when the term has two characters or fewer (提供, 登録), when the definition itself writes the longer word (東京都(以下「都」という。)), when the longer word is defined too, or when it is a plural (Boxes).

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: defined-term-form — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax defined-term-form --why "reason"
Turn it off for the team (chaff.yaml)
rules: defined-term-form: off
Technical details
Layer
L3
Status
stable
Severity
info
Languages
Japanese and English
Suited to
legal, docs, academic, literature, speech
Reads from the document
structure, pos

Levels

Set a level for this rule under rules in chaff.yaml. With nothing set, it runs at the level its genre gives it (see By genre below).

strictlower-case uses reported when they are 3 or fewer and fewer than the capitalised ones
normallower-case uses reported when they are 2 or fewer and fewer than the capitalised ones
relaxedlower-case uses reported when they are 1 or fewer and fewer than the capitalised ones

By genre

Runs by default in
legal/contract, legal/statute, legal/judgment, legal/patent
Turned off by the genre in
docs/manual, docs/faq, docs/glossary, academic/paper, literature/fiction, literature/essay, literature/poetry, literature/play, speech/address, speech/transcript
Not suited to, and not run in
technical/spec, technical/readme, blog/tech, blog/essay, blog/owned-media, business/proposal, business/report, business/email, business/press-release, business/meeting-notes

Genres

Message

"{term}" is used in another form than defined

"{term}" is defined on line {line}; after that it is used without quotes

"{term}" is defined with a capital on line {line}, but written in lower case here

"{term}" is defined on line {line}, but written "{written}" here

"{term}" is defined on line {line}, but written "{written}" here, longer with a word of its definition

Rewrite depth (chaff fix-plan --depth): light — words and sentences; the structure and the voice stay

This page is built from the rule's definition file:packages/chaff/rules/defined-term-form.yaml