Skip to content
  • There are no suggestions because the search field is empty.

LCM Reports

Two project-level LCM reports cover portfolio composition (Software Licenses and Contracts) and renewal pressure (Renewals & Lifecycle). Both surface data quality and actionable items.

LCM ships with two project-level reports. Both run on the contract and license data in the current project, both use the same data quality engine to surface action items.

This article covers what’s in each report, how the shared sections work, and how to use them together.

Open the reports

Open Apps, then License and Contracts Manager.

In LCM, open the Reports tab and pick a report.

The two reports at a glance

  • Lens: Software Licenses and Contracts: What do we have, what’s it costing us; Renewals & Lifecycle: What’s coming up, what’s at risk
  • Audience: Software Licenses and Contracts: License managers, finance, executives; Renewals & Lifecycle: Procurement, renewal managers
  • Time view: Software Licenses and Contracts: Snapshot of current state; Renewals & Lifecycle: Forward-looking on renewal calendar
  • Spend view: Software Licenses and Contracts: Total spend by vendor / type / dimension; Renewals & Lifecycle: Renewal spend by month, type, vendor
  • Action items: Software Licenses and Contracts: Yes (shared); Renewals & Lifecycle: Yes (shared)

The two reports complement each other. The first tells you what your portfolio looks like; the second tells you what’s about to change.

Software Licenses and Contracts report

The portfolio composition view. What’s in your contract estate, what’s costing what, who you’re spending with, and where the data quality gaps are.

Top summary tiles

  • Overview: total Number of Contracts and Number of Licenses.
  • Contracts Status: donut split between Active and Expired contracts.
  • License Type: donut split across Perpetual, Subscription, Open-Source, and Freeware (where applicable). Pulls from the license_type field.

Spend visualisations

  • Top 10 Vendors Spend: total spend per vendor, ranked. Pulls from total_value on the contract.
  • Top Spend by License Type: per-vendor spend split across Perpetual / Subscription / Freeware. Tells you the commercial model split per vendor.
  • Top Spend by Contract Type: per-vendor spend split across the contract type categories. Multiple pages of breakdowns may be available depending on the diversity of contract types.
  • Top Spend by Business Unit: spend rolled up by Business Unit.
  • Top Spend by Cost Center: same, for Cost Center.

Tables

  • Licenses table: every license in the project, fully filterable, sortable, and exportable.
  • Contracts table: every contract in the project, same controls.

Both tables include all standard schema columns plus any Settings template columns. Use Hide columns to focus the view, Show Filters to slice, and Download as to export.

Renewals & Lifecycle report

The forward-looking view. What’s coming up for renewal, what’s at financial risk, and what’s already lapsed.

Renewal timeline

Renewal Timeline - Next 12 months plots every upcoming renewal by month, with the number of renewals and the total value at risk above the chart, for example 11 renewals · $2.65M at risk. The timeline is shaded by renewal window, ≤30d, 31–60d, 61–90d, 91–120d and 121d+, and the counts per window sit at the top right. Use it to see at a glance how close each renewal is and how much is riding on it.

Spend forecast

  • Renewal Spend by Type: monthly stacked bar chart of renewal spend, broken down by contract_type. Shows the renewal cliff. Use this to spot months where renewals will require disproportionate procurement effort.
  • Renewal Spend by Vendor: same monthly axis, broken down by vendor. Use this to identify which vendor relationships need attention in any given month.

Tables

  • Upcoming Renewals: every contract approaching renewal, sorted by End Date. Includes Days to End and Renewal Window columns (computed live against today’s date).
  • Expired / Not Renewed: contracts that have passed their end date and haven’t been renewed. Days Expired column is the inverse computed column. This is the “what fell through the cracks” view, useful for both retrospective process improvement and triggering urgent renewal conversations.

Data Completeness, Action Items (shared)

Both reports include a Data Completeness Action Items table. It’s the same data, computed by a shared engine, and surfaces the same recommendations regardless of which report you’re viewing it from. The example above is from the Software Licenses & Contracts report.

The table lists actions like “Add Financial Value”, “Add Business Unit”, “Add Renewal Notice”, with three columns:

  • Affected Contracts: number of contracts where the field is unpopulated.
  • Total Contracts: project total, for context.
  • Coverage (%): percentage of contracts where the field is populated. Higher is better.
  • Severity: see below.

How severity is scored

Severity reflects how important the field is to the value LCM can deliver. The current weighting:

  • High: fields that materially block the platform from functioning as intended. Most notably total_value. Without financial value populated, spend dashboards and value-at-risk calculations are incomplete.
  • Medium: fields that block specific reporting cuts or downstream automation. renewal_notice_days (blocks reminders), Business Unit and Cost Center (block organisational breakdowns).
  • Low: fields that are useful for completeness but don’t block core function. business_owner, Department.

Severity is portfolio-wide, not per-contract. A High-severity row means the field is missing on many or all contracts; it’s not a per-contract priority indicator. For per-contract action priorities, see the Actionable Insights table on the Software Licenses and Contracts report.

Actionable Insights (Software Licenses and Contracts only)

Sits below Data Completeness on the Software Licenses and Contracts report. Where Data Completeness tells you “what type of issues do I have across the portfolio”, Actionable Insights tells you “which specific contracts need attention”.

Each row is a single contract with:

  • Contract Number, Name, Vendor
  • The actions outstanding for that contract (Add Financial Value, Add Renewal Notice, etc.)
  • Action Count
  • Severity (the highest severity across the actions on that contract)
  • Total Value, Currency, End Date, Business Unit

Sorted by severity and end date. Use this as your weekly worklist.

Using the two reports together

A typical workflow:

  1. Monthly portfolio review: open Software Licenses and Contracts. Check overall numbers, spot vendors creeping up the spend ranking, work through the Actionable Insights table.
  2. Weekly renewal triage: open Renewals & Lifecycle. Review Upcoming Renewals, prioritise the ≤30d bucket, check the spend-by-month chart for any approaching cliffs.
  3. Quarterly data quality push: use the shared Data Completeness table on either report to drive a sprint of data enrichment. Focus on High severity items first.
  4. Monthly trend: save a snapshot each month and compare it with the live report to see what changed. Useful for board reporting on portfolio health over time, not just its current state. See Save snapshots and compare them.

Save snapshots and compare them

A report shows your Live data by default, with the date it was last updated. A snapshot saves the report as it is at that moment, so you can come back to it after your contracts and licenses have changed.

Save a snapshot

Open the version menu next to Compare, which shows Live (read only) while you’re on the live report, and click Create snapshot. The snapshot is added to the same menu, numbered and dated, for example v1 (25/06/2026). Pick it from the menu to view the report as it was then.

Compare two versions

Click Compare. The left side shows your current state, the live report for this project. In the menu on the right, Select… what to compare it with:

  • Snapshots: a snapshot saved in this project, to see how it has changed since then.
  • Projects: another project, such as an older one, to compare the two side by side.

Every tile then shows both versions side by side, in the colours named in its legend. The Overview shows each count in its own column, and charts show a bar for each version. To compare two snapshots with each other, pick a snapshot in the left-hand menu too.

In this example, the project has gone from 29 contracts and 24 licenses in the v1 snapshot to 31 contracts and 40 licenses now.

Each tile has its own download button, so you can export a comparison chart on its own.