Contracts
A contract is the formal agreement covering one or more of the solutions a third party provides. Registering it turns the vendor relationship from a technical fact into a governed one: you can answer when the agreement ends, how much notice a termination needs, which law governs it, and what it costs each year — questions that are asked during a renewal or an incident, and that nobody can answer from a solutions list alone.
Where to find it
Section titled “Where to find it”Contracts have no top-level sidebar entry. They live where they belong: on an entity’s page under the Contracts tab, and on a solution’s page listing the agreements that cover it. Use Add contract from the entity to create one.
What a contract holds
Section titled “What a contract holds”Parties and coverage
Section titled “Parties and coverage”Provider entity is the third party supplying under the agreement. Beneficiary entity is who receives it — leave it empty and it defaults to your own main organisation, which is what you want for an ordinary supplier contract and what you would change for an intra-group arrangement. Solutions lists the services the contract actually covers, which is the link that lets a service question become a commercial one.
Owner is the actor accountable on your side, and Evidences carries the signed document and anything else that substantiates the terms.
Lifecycle
Section titled “Lifecycle”Status moves through Draft, Active, Expired and Terminated. Start date and End date bound the agreement, and Termination reason records why a terminated contract ended. Prefer moving a contract to Expired or Terminated over deleting it — a deleted contract takes the history of the relationship with it.
Commercial and legal terms
Section titled “Commercial and legal terms”| Field | Notes |
|---|---|
| Reference ID | The contract number as the counterparty knows it |
| Currency and Annual expense | What the agreement costs each year |
| Governing law country | Whose law applies |
| Notice period for entity | Days of notice your organisation must give |
| Notice period for provider | Days of notice the provider must give |
| Is intra-group | Marks an agreement inside your own group of companies |
| Contract type | The contractual-arrangement classification used in regulatory reporting |
| Overarching contract | The parent agreement, when this is a subordinate arrangement |
The two notice periods are the fields most often needed under pressure. A renewal decision taken a week after the notice window closed is a renewal you did not choose.
Hierarchy
Section titled “Hierarchy”Overarching contract points at a parent agreement, so a master services agreement with several statements of work under it is modelled as one overarching contract and several subordinates. The parent lists its subordinates in return, which keeps the commercial structure legible without duplicating the terms on every child.
Fitting contracts into the rest of the section
Section titled “Fitting contracts into the rest of the section”The natural chain is entity, then solutions, then a contract covering those solutions, then assessments reviewing the relationship. Each step narrows the previous one:
- The entity says who you depend on.
- The solutions say what for.
- The contract says on what terms, for how long, and at what cost.
- The entity assessment says whether that is acceptable.
Related
Section titled “Related”- Entities — where contracts are created and listed.
- Solutions — what a contract covers.
- Evidences — attaching the signed document.
- Feature flags — enabling the module.