Why definitions in the contract text are not enough
Definitions written into the clauses of the contract grow over time and are hard to update. A definitions annex can be replaced without an amendment to the whole contract, and it can also be used in requests and orders. It has one more advantage: a technician can read it without searching through the clauses on settlements.
The basic rule: one term, one definition, one number or one observable condition. A definition that cannot be checked is an opinion.
Practice 1: define acceptance through an artifact
Implementation takes 3 months in three stages, and each stage ends with the acceptance of a specific artifact: a working training module, an accepted test permit, production launch. In the glossary, record acceptance as an event: checking a named artifact by a specified person and signing the protocol. Exclude general formulas that do not state what was checked.
Permitted outage in a 30-day month at different availability levels
Practice 2: describe the SLA with event types
The SLA has three event types: a strategic failure (response in 12 hours, repair in 8 hours from the start of service), a failure that hinders work (response by the next business day, repair within 1 business day) and support and planned works (up to 7 days). The availability of the server part of the instance is 99.5% in the calendar month.
In the definition, record the moment the time starts running: the report in the service desk system, not a phone call. Also state clearly that repair time counts from the start of service, because this element most often causes disputes.
Practice 3: record the SLA parameters and how they are measured
The SLA parameters (availability, response and repair times) are set in the maintenance agreement, for example availability of 99.5% in the month. The glossary does not repeat the settlement mechanisms of a specific contract, only defines the terms the contract refers to: 'type A failure', 'response time', 'repair time', 'availability'.
For each definition, name the source of measurement, for example a report from the service desk system, and one numerical example: with availability of 99.5% in a 30-day month, the permitted outage is 3.6 hours (example calculation).
Practice 4: decide who is a user
The license covers the plant's users and the coordinators of external companies who register their employees. Employees of external companies and guests are not counted. The Inviter role does not take up an active user license and has access only to the module for external companies and guests. The system has no counter of active users, so the counting takes place outside the system.
This last point must be written into the glossary: who counts active users, how often, and on the basis of which report. Without this, the parties will discover after a year that each of them counts differently.
Practice 5: version the glossary and attach it to orders
The glossary should carry a version number and a date, and each implementation order should state which version it applies. If the glossary is changed, the change applies to new orders, while existing ones keep the earlier meaning. This simple rule prevents retroactive disputes.
Checklist
Video
Frequently asked questions
Must the glossary be written into the clauses of the contract?
No. A definitions annex allows the definitions to be replaced without an amendment to the whole contract, and they can also be used in requests and orders.
Where are the SLA parameters set?
In the maintenance agreement: availability, response and repair times, for example availability of 99.5% in the month. The glossary only defines the terms used.
Who counts the active users?
The system has no counter of active users, so the counting takes place outside the system. The glossary should name the person and the frequency.
See the model of a definitions annex
We will show the structure of a glossary of terms that the lawyer can adapt to the plant's contract. It will save rounds of agreement after signing.
Let's talk