The highest-privilege role in the platform. Admins have full access to all modules — they manage organisation settings, users, departments, governance, connectors, and all contract operations.

An automatic routing process where contracts created by Super Users are sent to the relevant Department Admin for approval. The contract status changes to "Approval Pending" until the Dept Admin approves or rejects it.

A tamper-proof chronological record of every action performed in the platform — creates, updates, deletes, logins, and configuration changes. Used for compliance, security, and accountability.

The ability to create multiple records at once by uploading a CSV file. Supported for Contracts, Customers, Suppliers, and Departments.

A contract where your organisation is the buyer/consumer. The contract is linked to a Supplier. Buy-side contracts track what you are purchasing from external parties.

A configuration area within the Organisation module for defining dropdown values used across the platform — Regions, Contract Types, Governance Approvers, KPI Types, and other reference data.

A formal request to modify an existing contract — value changes, date extensions, scope modifications, or party changes. CCRs go through an approval process before the contract is updated.

An item, service, or asset tracked for billing purposes. Defined in Cost Center and selected in Customer Billing. Examples: "Managed Print Service", "Cloud Storage", "Office Supplies".

A configured link to an external system. Data Connectors pull metrics from databases or APIs for KPI/SLA evaluation. Email Connectors monitor mailboxes for automated document processing.

A document generation tool that merges form data into a Word template to produce a standardised contract document. Can optionally send the document for DocuSign signature.

An AI-powered module that extracts contract data from uploaded PDF documents using OCR and natural language processing. Extracted fields are presented for human review before saving.

A Word document (.docx) with placeholder merge fields that the Contract Builder uses to generate contract documents. Templates ensure consistency across contracts of the same type.

A configuration module defining three dimensions of cost tracking: Commodities (what), Locations (where), and Users to Bill (who). These items are used in Customer Billing.

A reporting module that displays actual usage costs for sell-side contracts — broken down by commodity, location, and user. Data comes from Customer Billing configurations.

An external party that your organisation provides services to. Customers are linked to sell-side contracts. The Customer module includes contact details, invoice profiles, and a billing configuration tab.

The landing page showing a visual summary of the contract portfolio — contract counts, RAG distribution, upcoming expiries, financial summaries. DB1 is the main dashboard; DB2 is the Contract Builder dashboard.

Interactive graphical views of the contract ecosystem — hierarchy graphs (Organisation → Supplier → Contract → SLA → KPI), side-by-side comparisons, and portfolio performance summaries.

An organisational unit that owns contracts. Departments have a Department Admin who approves contracts. Every contract must belong to a department.

A role scoped to a specific department. Dept Admins approve or reject contracts submitted by Super Users within their department.

A tracking module that lists all documents sent for electronic signature — showing status (Sent, Completed, Expired), automatic reminders, and download links for original and signed documents.

The third-party electronic signature platform integrated with Contract intELIEgence. Used for signing contract documents, supplier MOUs, and customer NDAs. Configured in the Connectors module.

A role with view-only access to contracts and data within assigned departments. End Users cannot create, edit, or approve records.

A compliance mechanism that assigns structured oversight to contracts based on value bands and date ranges. Each scheme specifies an approver. Governance records who approved what — it is not an automated approval workflow.

A contract status indicating that required fields are not fully filled in. Incomplete contracts display a GREY RAG indicator because performance cannot be evaluated with missing data.

A contact record within the Customer module representing a billing/invoice recipient. Invoice Profiles can have NDAs generated and sent for signature.

A measurable metric that quantifies contract performance. Each KPI maps a field from a Data Connector to a target value. KPIs are the building blocks of SLAs — they provide the raw measurements that SLA rules evaluate.

A placeholder in a Word template (e.g. {{CompanyName}}, {{ContractValue}}) that the Contract Builder replaces with actual contract data during document generation.

A formal document establishing a relationship with a Supplier. Generated from Organisation → Templates and sent for electronic signature via DocuSign.

The platform supports multiple organisations (tenants) in a single deployment. Each organisation's data is isolated — users in one organisation cannot see or access another organisation's records.

A confidentiality agreement generated for Customer Invoice Profile contacts. Created from Organisation → Templates and sent for DocuSign signature.

Automated email alerts triggered by platform events — contract expiry, SLA breaches, approval requests, signature reminders, and status changes. Configured via SMTP settings and templates.

A monitoring module that charts KPI metrics over time with trend lines, target lines, and variance analysis. Unlike SLAs (which show current status), trackers show historical performance trajectory.

A colour-coded health indicator for contracts driven by SLA evaluation. Green = target met, Amber = at risk / approaching threshold, Red = breach / target missed, Grey = Incomplete (data missing).

A reference data value configured in Organisation → Catalogs (Type = Region). Regions are used in Cost Center items and can be used for geographic segmentation of data.

Predefined standard reports and a custom ad-hoc report builder. Ad-hoc reports allow selecting up to 10 fields, 3 selection criteria, 3 sort criteria, and 3 summary fields.

A time-based configuration that determines how often the platform runs an automated process — SLA evaluation, data collection, cost calculation. Supports daily, weekly, monthly, and custom CRON expressions.

A contract where your organisation is the seller/provider. The contract is linked to a Customer. Sell-side contracts support billing configuration and cost tracking.

A grouping module that bundles related contracts into logical services. Aggregates RAG statuses and SLA metrics from individual contracts into a single service-level health view.

A performance rule that evaluates KPI metrics against defined targets using a compute method (Sum, Average, Count, Min, Max) and produces a RAG (Red/Amber/Green) health indicator. Runs on a configurable schedule.

A broad-access role that can create and edit contracts, configure tracking, and manage operational modules. Cannot manage users or organisation settings. Contracts created by Super Users require Department Admin approval.

An external party that your organisation purchases from. Suppliers are linked to buy-side contracts. The Supplier module supports MOU generation and electronic signature.

A consolidated calendar view that aggregates all key dates from across the platform — contract start/end dates, review dates, SLA evaluation dates, and service milestones.

A Cost Center item representing the individual or account that billing should be attributed to. Used in Customer Billing to assign cost responsibility.