Term | Definition |
Agreement (Contract) | An individual contract that may be imported into the system (e.g., as a PDF) or created structurally within CLM (auto-generating a PDF). It belongs to one Contract Type and optionally one Contract Entity, and can be defined as an internal agreement. It may act as a main contract for a set of subcontracts. |
Alerts | System-issued notifications regarding various contract activities. |
Contract Amendments | Official changes or modifications made to an existing contract. |
Contract Annexes (Appendices) | Documents that are official parts of the actual contract. They must be added before the contract is signed and cannot be edited, added, or deleted afterward. See also Other contract documents. |
Contract Base | A template used to create a new contract. Templates can be attached to a specific Contract Type, allowing desired Contract Clauses to be inherited automatically. |
Contract Basket (Contract Cart) | A temporary collection point used to gather multiple contracts so that mass changes (editing information, rights, metadata, etc.) can be performed simultaneously. |
Contract Clause | An individual component of the content that makes up a structured contract. Users can create clauses or select them from pre-existing Contract Records or the Phrase Library. |
Contract Documents | A generic term covering both Contract Annexes (appendices) and Other contract documents attached to the contract. |
Contract Entity (Set of Contracts) | An individual entity created to group contracts related to a specific matter. It has its own number and name, can contain one or more main contracts, and its common metadata is inherited by all contained contracts. |
Contract Entity Information Page | The page displaying the metadata (additional information) of a Contract Entity and providing access to the individual contracts it contains. |
Contract File Import | The bulk import of contract documents into the system. Basic information for a desired number of contracts/units is recorded in a quantitative Excel file for system import. |
Contract Folders | Used to group and organise contracts within the system for easier navigation and search. |
Contract Information Page | The comprehensive page for a selected contract, containing all core details, documents, metadata, latest activities, and access to functions enabled by its current status. |
Contract Records | Content created and managed by users (within rights) that consists of reusable Metadata (additional information) or Contract Clauses. |
Contract Status | The different phases of the contract's life cycle. Standard statuses include: Preparing, Active, Terminated, Terminated, and Canceled. |
Contract Supplier | The party chosen as the supplier, and thus a party to the contract. |
Contract Type | A classification label to which an individual contract is linked (one contract to one type). The type defines common Metadata which is inherited by all contracts belonging to it. |
Complaint | The official document delivered to the contract supplier and for the information of users. The person responsible can file it directly or through an approved Complaint Proposal. It always targets a specific contract. |
Complaint Proposal | A suggestion for a complaint that a user can submit to the contract responsible, who can then accept or reject it. It always targets a specific contract. |
Complaint Type | User-defined categories (within rights) used to classify complaints for easier monitoring and searching. |
File Library | A storage location where users (within rights) can create and manage an organisation’s collection of contract appendices and other related documents. |
Metadata (Additional Information) | Identifying and descriptive data created in the contract record to supplement basic information and visible clauses. It does not appear on the contract document itself, but supports searching, application, and monitoring. |
Other Contract Documents | Documents assigned to the contract that are not actual Contract Annexes. They can be added even after the contract is signed. |
Phrase Library | A repository where users (within rights) can create and manage groups of reusable contract sentences for contract creation and editing. |
Reminders | Configurable alerts that can be set for selected contracts or contract entities. Users define the trigger issue, the lead time for the reminder, and who receives the notification. |
Search Function | Used to find specific contracts, folders, or claims. Searches can be refined with keywords or function-specific limits and can be saved for future reuse ("Use saved search"). |
To-do Lists and Tasks | A feature allowing users to set up multiple To-do Lists (e.g., "Project planning") for a contract and create individual Tasks within each list (e.g., "Preparing a plan") for monitoring and control. |
Usage Rights | A general term referring to the combined set of user roles, user groups, and unit relationships that define a user's access and permissions within the system. |
User of the Agreement | A person who needs to access or see the contract (e.g., a customer or invoice inspector) or perform actions based on it (e.g., making purchase orders or complaint proposals). |
Workbench (Desktop) | A system portal where contract management users can publish contracts for viewing by others in the organisation and other contract users. Visibility can be limited by the persons responsible for the agreements. |
Article Ref: 161020251242
