Manual Contract Creation

Flow Guide — Create a contract by filling in all fields directly
🎯 Purpose

Create a contract by manually entering all details — parties, dates, values, terms, and optional SLA/governance assignments. This flow gives you full control over every field and is ideal when no template exists, when contract terms are unique, or when migrating legacy contracts into the platform.

Benefits
  • Complete flexibility — every field is directly editable, supporting non-standard or complex contract structures.
  • Supports both Buy-side (Supplier) and Sell-side (Customer) contracts from a single form.
  • Allows optional attachment of SLAs, KPIs, governance schemes, and performance trackers at creation time.
  • Enables bulk import via CSV for migrating large volumes of existing contracts quickly.
  • Triggers department-based approval workflows automatically when created by a Super User.
📥 What You Need
  • Contract direction — Buy-side (with Supplier) or Sell-side (with Customer).
  • An existing Supplier or Customer record in the platform.
  • Contract details — name, description, type, value, start/end dates, owning department.
  • Optional: Governance scheme selection and approver assignment.
  • Optional: SLA and KPI configurations for performance monitoring.
  • Optional: CSV file for bulk contract import.
🏁 Outcome

A fully registered contract record in the Contract Hub with all metadata, linked to its Supplier or Customer, assigned to a department, and optionally monitored by SLAs and governed by approval rules. The contract appears in the contract listing, on the Dashboard, in the System Calendar, and in Reports. If created by a Super User, it enters the department approval workflow automatically.

Manual Creation Flow

Select PartyFill DetailsAssign SLASelect GovernanceSave Contract
Prerequisites
  • Platform setup completed (Organisation, Users, Departments)
  • At least one Supplier (for buy-side) or Customer (for sell-side) already created
  • Contract details: value, dates, type, owning department
Buy-side vs Sell-side: Buy-side contracts are with Suppliers (your organisation is purchasing). Sell-side contracts are with Customers (your organisation is providing services). The contract form adjusts based on direction — buy-side shows Supplier fields, sell-side shows Customer fields with billing configuration.

Creation Steps

1
For buy-side: create a Supplier record with company details, contacts, and SIC code. For sell-side: create a Customer record with company details, invoice profile, and billing contacts. The supplier/customer must exist before you can link a contract to them.
Business Value:The Contract Hub is the central module for all contract records. Starting here ensures you are creating a new contract rather than editing an existing one.
Depends On:Platform Setup flow must be complete — Organisation, Users, Departments, and optionally Governance are prerequisites.
Enables:The contract form (Step 2) opens with Organisation and Department pre-filtered based on your user role.
2
Navigate to Contract Listing and click Create. Fill in the contract form: select direction (buy/sell), choose the supplier or customer, set contract type, enter value, start and end dates, owning department, and description. Attach any supporting documents.
Business Value:Contract direction (Buy-side/Sell-side) determines the form layout and which party field appears. Buy-side links to a Supplier (you are purchasing); Sell-side links to a Customer (you are providing services). This choice affects billing, cost tracking, and signature flows downstream.
Depends On:Supplier or Customer records must already exist — they are selected from dropdowns populated by the Supplier and Customer modules.
Enables:The selected party is permanently linked to the contract. Sell-side contracts unlock Customer Billing and Cost Tracking. Buy-side contracts link to Supplier MOUs.
3
If SLAs have been created, assign them to the contract's RAG block. Each SLA computes a Red/Amber/Green indicator that shows on the contract listing. You can assign multiple SLAs to track different performance aspects.
Business Value:Contract metadata — name, type, value, dates, department — drives everything downstream: governance eligibility, calendar entries, dashboard metrics, report filtering, and approval routing.
Depends On:Department (from Platform Setup) — selected here for ownership and approval routing. Governance Schemes filter based on the value and dates entered.
Enables:Dashboard shows contract counts and values. Calendar shows start/end dates. Reports include these fields. Governance evaluates value against scheme bands.
4
If governance rules are configured, submitting the contract triggers the approval workflow automatically. The contract moves to Pending Approval status and the designated approvers receive notification emails.
Business Value:Assigning SLAs at creation time means performance monitoring begins immediately. Selecting a Governance Scheme ensures compliance oversight is recorded from day one rather than retrofitted later.
Depends On:SLA module — SLAs must be pre-configured with KPIs and connectors. Governance module — schemes must exist with valid date/value ranges.
Enables:SLA assignment activates RAG indicators on the contract. Governance selection records the approver for compliance. Both appear in the contract detail view.
5
Once active, monitor the contract from the Contract Listing. View RAG indicators, track SLA performance, check cost tracking, and manage renewals or change requests as needed throughout the contract lifecycle.
Business Value:Saving creates the contract record and triggers the department approval workflow (if created by a Super User). The contract enters the system and becomes visible in listings, dashboards, calendars, and reports.
Depends On:All previous steps — contract details, party, SLAs, and governance are bundled into the record.
Enables:Department Admin receives an approval notification. Dashboard updates. Calendar entries are created. The contract is now available for Service Manager grouping, Cost Tracking, and Performance Tracking.
Result

A fully configured contract record linked to a supplier or customer, with optional SLA tracking and governance approval. The contract appears in the Contract Listing with its RAG status and is available for tracking, reporting, and service aggregation.