Contract Lifecycle Management — Overview & module guide

Module: Contract Lifecycle Management v1.5.0

End-to-end contract lifecycle tracking, stages, and governance for BIXCRM

Screen-by-screen guides (each tab explained)

Click a menu item below for step-by-step instructions on that Contract Lifecycle Management screen:

How to use in BIXCRM (daily operations)

  1. Sign in to the admin area with a role that includes Contract Lifecycle Management permissions.
  2. Open Contract Lifecycle Management (sidebar) or search for Contract Lifecycle Management in the admin menu.
  3. Start on the Dashboard (if available) to see open tasks, pending approvals, and KPIs.
  4. Review Settings after upgrades — new options may need defaults for your company.
  5. Create or import master data first; most modules block transactions until masters exist.
  6. Run the main business flow (create → submit → approve → post/complete) using the screens listed in Admin menu below.
  7. Use Reports / Analytics screens to reconcile stock, finance, compliance, or SLA metrics.
  8. For integrations (API, EDI, gateways, tax), confirm credentials in Settings and monitor logs or webhook delivery screens.
  9. Train staff with role-based access — give approvers approve permissions only, operators create/edit on their area.
  10. If something fails overnight, check BIXCRM cron ran and open the module log / failed queue screen if present.

Admin menu — where to work

Open the Contract Lifecycle Management section in the admin sidebar. Screens your staff may use (depending on role):

  • Amendments
  • Approvals
  • CLM
  • CLM Dashboard
  • Contracts
  • Lifecycle Stages
  • Milestones
  • Renewals
  • Reports
  • Settings

Detailed guide — features, workflows, API & FAQ

Features (Complete — Phases 1–6)

  • Lifecycle Stages — Draft, Review, Negotiation, Approval, Active, Renewal Due, Expired, Terminated
  • Contract Registry — Full CRUD with client, project, value, dates, and contract types
  • Core Contract Sync — Optional auto-link to BIXCRM core contracts via hooks
  • Stage Transitions — Full audit trail with notes and staff tracking
  • Milestones & Obligations — Delivery, payment, review, renewal notice tracking per contract
  • Amendments & Version Control — Contract changes with diff view, attachments, core sync
  • Renewals — Renewal proposals, approval workflow, decision tracking, RR sync
  • Approval Workflows — Multi-level sign-off, configurable rules, stage gates, email alerts
  • Reports — Expiry register, stage pipeline, value by client/type, milestone tracker, RR links
  • REST API — Token-authenticated read access to contracts and related data
  • Webhooks — Outbound events for stage changes, expiring contracts, and renewals
  • CSV Export — Export any report with applied filters
  • Automation — Cron for milestones, expiry alerts, auto-expire, renewal stage moves
  • Dashboard — KPI cards, stage chart, pending approvals, expiring contracts
  • Permissions — Granular staff capabilities per feature

REST API

Base URL: {your-crm}/contract_lifecycle_management/clm_api

Authentication: X-CLM-API-Key: {token} or Authorization: Bearer {token}

Enable under Settings → Enable REST API, then generate keys under API Keys.

Webhooks

Configure subscribers under Settings → Webhooks. Events:

  • contract.stage_changed
  • contract.expiring
  • renewal.approved

Payloads are JSON with HMAC-SHA256 signature in X-CLM-Signature.

Database Tables

TablePurpose
----------------
clm_lifecycle_stagesStage definitions
clm_contractsLifecycle contract records
clm_stage_transitionsStage change audit trail
clm_milestonesContract milestones & obligations
clm_amendmentsContract amendment versions
clm_amendment_attachmentsAmendment file attachments
clm_renewalsRenewal proposals & decisions
clm_approval_rulesConfigurable approval workflow rules
clm_approvalsApproval requests & decisions
clm_api_keysREST API token hashes
clm_webhooksOutbound webhook subscribers
clm_webhook_deliveriesWebhook delivery log
clm_logsGeneral activity log

Features

End-to-end contract lifecycle tracking, stages, and governance for BIXCRM

  • **Lifecycle Stages** — Draft, Review, Negotiation, Approval, Active, Renewal Due, Expired, Terminated
  • **Contract Registry** — Full CRUD with client, project, value, dates, and contract types
  • **Core Contract Sync** — Optional auto-link to BIXCRM core contracts via hooks
  • **Stage Transitions** — Full audit trail with notes and staff tracking
  • **Milestones & Obligations** — Delivery, payment, review, renewal notice tracking per contract
  • **Amendments & Version Control** — Contract changes with diff view, attachments, core sync
  • **Renewals** — Renewal proposals, approval workflow, decision tracking, RR sync
  • **Approval Workflows** — Multi-level sign-off, configurable rules, stage gates, email alerts
  • **Reports** — Expiry register, stage pipeline, value by client/type, milestone tracker, RR links
  • **REST API** — Token-authenticated read access to contracts and related data
  • **Webhooks** — Outbound events for stage changes, expiring contracts, and renewals
  • **CSV Export** — Export any report with applied filters
  • **Automation** — Cron for milestones, expiry alerts, auto-expire, renewal stage moves
  • **Dashboard** — KPI cards, stage chart, pending approvals, expiring contracts
  • **Permissions** — Granular staff capabilities per feature

Permissions

Granular staff capabilities are registered on activation. Assign them under Setup → Staff → Roles for the Contract Lifecycle Management capability group.

Typical capabilities include view, create, edit, delete, plus module-specific actions (approve, export, settings, API access).

Cron Jobs

Background tasks (if enabled) run through BIXCRM's main cron. Example crontab (every 5 minutes):

* * * * * php /path/to/bixcrm/index.php cron/index > /dev/null 2>&1

Check module settings for scheduled jobs (alerts, sync, reports, retention).

After activation — configuration checklist

  1. Go to Setup → Modules and activate Contract Lifecycle Management.
  2. If prompted, click Upgrade Database or reload admin — migrations run automatically.
  3. Assign permissions under Setup → Staff → Roles.
  4. Open the module menu and configure settings.
  5. BIXCRM 3.0+
  6. PHP 7.4+ (8.1+ recommended)
  7. MySQL 5.7+ / MariaDB 10.3+ (InnoDB)
  8. PHP extensions: mysqli, json, mbstring, curl, fileinfo

Staff permissions (from module)

Assign under Setup → Staff → Roles. Each feature can expose different actions:

FeatureActions
CLM Dashboard
clm_dashboard
view
Contracts
clm_contracts
view, create, edit, delete, transition
Lifecycle Stages
clm_stages
view, create, edit, delete
Milestones
clm_milestones
view, create, edit, delete
Amendments
clm_amendments
view, create, edit, delete, approve
Renewals
clm_renewals
view, create, edit, delete, approve
Approvals
clm_approvals
view, create, edit, delete, approve
Reports
clm_reports
view, export
Settings
clm_settings
view, edit

One-time setup (first time only)

  1. Setup → Modules → activate Contract Lifecycle Management.
  2. Setup → Staff → Roles → assign Contract Lifecycle Management permissions (view, create, edit, delete, approve, export, settings as needed).
  3. Open Contract Lifecycle Management → Settings and complete company defaults, prefixes, integrations, and notification options.
  4. Create master data (warehouses, products, templates, accounts, routes, etc.) before processing live transactions.
  5. Enable BIXCRM cron (php /path/to/bixcrm/index.php cron/index) for sync, retries, alerts, and scheduled jobs.
  6. Optionally enable REST API / webhooks in module settings if you integrate external systems.

BIXCRM Knowledge Base — usage guide generated from module README and documentation.

Did you find this article useful?