Categories

Contract categories

Classify agreements in a category tree, for example energy, telecom sites, procurement or corporate. Each category has its own document types, lifecycle and fields.

How it works

Agreement categories are managed in the Agreement Studio. A tree can group power purchase and grid connection under Energy, and site leases under Telecom sites.

Each category defines the document types it expects, its lifecycle, for example a fixed term without renewal, and the fields shown on the summary sheet. Settings can be inherited from a parent category, and a lifecycle override can limit extraction to the effective and expiration dates.

The category also drives import options, such as whether new agreements go straight into the repository or wait for review.

What you get

  • Category tree with subcategories
  • Document types per category
  • Lifecycle settings per category
  • Summary fields per category

Why teams use it

Your own classification

Categories follow how your teams work, not a generic list.

The right fields for each contract

A PPA and an NDA do not show the same data.

Settings that cascade

Subcategories inherit what their parent defines.

Adjusted without code

Administrators change categories directly in the platform.

More in Repository & import

See all →

Central contract repository

Every agreement, with its amendments and annexes, in one list.

Learn more →

Bulk upload

Upload hundreds of files or whole folders at once.

Learn more →

Inbox with document triage

Imported documents are triaged: accepted, uncertain or out of scope.

Learn more →

Searchable scans (OCR)

Scanned PDFs become searchable, analysable text.

Learn more →