All rules

A party named by its role instead of the name the contract gave it

party-role-nameon by default (info)Japanese / English

A party given a short name ("the Supplier") and later called something else

Example

Flagged
# Services Agreement This agreement is between Harbour Works Ltd (the "Supplier") and North Trading Inc (the "Customer"). 1. The Customer pays the Vendor within thirty days of each invoice.
What chaff prints
5:26 "Vendor" is not a name this contract gave a party (Supplier, Customer)
Fixed
# Services Agreement This agreement is between Harbour Works Ltd (the "Supplier") and North Trading Inc (the "Customer"). 1. The Customer pays the Supplier within thirty days of each invoice.
What chaff prints
no finding
chaff.yaml used for this example
genre: legal/contract

How to fix

Use the name the contract gave the party. If someone else is meant, define them first.

Why it matters

Once a contract says "Harbour Works Ltd (the "Supplier")", writing "the Vendor" later makes the reader check whether the Supplier is meant or someone else, such as a subcontractor. It happens when clauses from another template are pasted in with that template's names. In a document that gives its parties short names in brackets, chaff points at each later role word (the Vendor, the Recipient, the Company, 受託者, 売主) that the document did not define. The words are in each language's word list.

What it does not flag

Uses before the parties are named, a role word the document defines itself ("Recipient" means), a role word inside a defined term (Receiving Party) or a longer word, a lower-case role word (the vendor, an ordinary noun), and a plural with no article at the head of a sentence (Customers who register …, the ordinary noun capitalised by its place) are not reported. A party is read from a short name in brackets that is a party word (we) or a role word itself, or that follows a company name (Ltd, Inc.). The legal genres run this rule, except statutes, which name people by their role and define no parties.

Turning it off or relaxing it

Silence this one spot (in the document)
<!-- stet: party-role-name — reason -->
Relax it for the team (the reason is kept as a comment in chaff.yaml)
npx chaffjs relax party-role-name --why "reason"
Turn it off for the team (chaff.yaml)
rules: party-role-name: 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

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).

strictwarning
normalinfo
relaxedinfo

This rule has no limit to count to. A level sets how a finding is marked: relaxed keeps the finding and marks it a step lower.

By genre

Runs by default in
legal/contract, legal/judgment, legal/patent
Turned off by the genre in
legal/statute, 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

"{role}" is not a name this contract gave a party ({names})

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/party-role-name.yaml