Commercial Management

Commercial Management · Palantir Workflows

June 2026 · Confidential

Session Agenda

Agree which commercial workflows Palantir builds first and confirm the data records needed to begin.

01

Key Objectives

What commercial management needs to solve for

02

Workflow Overview

Six workflows across the commercial lifecycle

03

Workflow Deep-dives

Lifecycle, data sources, and where Palantir adds value

04

Prioritisation

Framework and ranked deployment sequence

05

Next Steps

Scope, records, sprint plan

Commercial Management

Without an owner-side commercial position, scale creates fragmentation and contractors control the default truth.

Own the position	The owner must hold its own view of commitments, cost, and exposure — independent of contractor reporting. On a programme with multiple contracts and contractors, the only accepted position that serves the owner's interests is one the owner computes. Every certified payment, accepted change, and forecast position must originate from owner-controlled data.
Govern exposure	Commercial leakage on a programme almost always originates from changes and claims that were visible but ungoverned at the point of origination. By the time they surface in a contractor's submission or a dispute notice, the window to challenge entitlement has often already closed. Governing at origination — not at submission — is the only way to protect the contingency position.
Drive decisions	EAC, cashflow, and contingency position are the primary inputs to programme governance and executive decisions. If those inputs are compiled from contractor submissions rather than computed from owner-accepted positions, they reflect contractor interests, not programme reality. The owner needs a version it controls — not a version it inherits.
Qualify counterparties	On a multi-contract capital programme, counterparty risk is package-specific: the same supplier may be acceptable for civil groundworks and unacceptable for critical-path electrical scope. Flat company-level qualification misses that distinction. The owner needs package-specific qualification, with sovereignty scoring and continuous monitoring through the delivery lifecycle.

Six Workflows

One data model — a change accepted in W3 flows into the EAC in W4 and the claims evidence in W5 without re-entry.

Workflow	What It Governs	Key Decision
W1 · Vendor Qualification	Package-specific counterparty qualification and monitoring	Is this counterparty safe to commit capital to, for this package, now?
W2 · Obligations & Renewals	Contract obligations extracted, tracked, and linked to programme risks	Does every obligation have a current status and owner before the deadline?
W3 · Change Management	Owner change register reconciled against contractor	What is the owner's accepted position on each change, and is it aligned?
W4 · Forecast & EAC	Owner's accepted cost, contingency drawdown, cashflow	Accept the contractor EAC? What does it mean for programme contingency?
W5 · Claims Management	Immutable claim event ledger: notice, evidence, entitlement	Does the owner have a valid position on every claim before the notice window closes?
W6 · Commercial Close-out	Variation reconciliation, final account, retention, transition	Is the final commercial position agreed and archived before handover?

03

Workflow Deep-dives

Lifecycle, data sources, and where Palantir adds value.

Workflow 1 · Vendor Qualification

Package-specific qualification with continuous monitoring — deployable before any other workflow, with no internal system dependency.

NEED IDENTIFIED

Package or renewal event

OPEN CASE

Supplier, package, criticality

DATA COLLECTION

Financials, certs, sub-tier

SCREEN

Sanctions, CH, distress

PACKAGE RISK

Capacity, lead-time, country

DECISION

Qualified / Conditional / Fail

MONITORING

Continuous alerts and review

What the workflow achieves	In commercial terms
Qualification is per-package, not per-company	A supplier can be approved for civil works and flagged for critical electrical scope simultaneously. The decision is tied to the programme requirement, not a blanket company-level pass.
Compliance screens run on schedule	Sanctions, Companies House, and financial distress checks run when a case opens and on an automated schedule. The team doesn't manage the calendar.
Monitoring continues through contract delivery	A passed qualification doesn't expire at award. Financial distress events, certification lapses, and sanctions changes flag during execution without any manual trigger.
Sovereignty scored per package	Sub-tier provenance, country-of-origin rules, and sanctions screens combine into a sovereignty score at package level. That granularity is what programme governance requires.

Workflow 1 · Vendor Qualification · Data Sources

All compliance screens are API-connected today — the supplier master is available as CSV. No internal system integration is required to begin.

Record	Current Source	Final Source
Sanctions lists (OFAC, OFSI, EU)Consolidated watchlist screening data used to identify sanctioned entities, individuals, and jurisdictions across procurement packages	Third-party screening (ad hoc)	Third-party screening API
Companies House / corporate registryCorporate filing data used to verify legal entity status, ownership structure, financial health, and insolvency risk	Public API	Public API
Supplier master / long-lead package listActive and prospective supplier records with package assignments, commercial status, and criticality flags	Procurement spreadsheets	Procurement system
Contract qualification obligationsContract requirements specifying the qualification standards, evidence thresholds, and periodic review obligations for each supplier	CLM	CLM
Package criticality thresholdsOwner-defined scoring parameters determining the qualification risk tier, evidence depth, and monitoring frequency per package type	Not formally held	Owner-authored in Palantir

Workflow 2 · Obligations & Renewals

Every active obligation is extracted from the contract on execution, tracked to a confirmed outcome, and linked to the programme risk register without manual transfer.

EXECUTE

Contract live in CLM

EXTRACT

AIP reads obligations

VALIDATE

User reviews, edits

TRACK

Dashboard live

NOTIFY

90/60/30 day alerts

CONFIRM

Fulfilled / waived / overdue

AUDIT

Immutable outcome log

What the workflow achieves	In commercial terms
Obligations extracted on execution	An AI agent reads every contract on execution and surfaces obligation type, value, due dates, and assignee. Nothing is manually transcribed from a contract document.
Renewal windows triggered proactively	Configurable alerts fire at 90, 60, and 30 days before expiry. Each stakeholder — procurement, legal, finance, contract owner — gets the right notice at the right stage.
RAID items created automatically	Contracts approaching expiry, high-value obligations nearing due date, and overdue obligations raise risks and issues in the programme RAID register without manual transfer.
Immutable audit trail per obligation	Every status change — fulfilled, extended, waived, or overdue — is timestamped with the user and captured. The log supports compliance review and dispute resolution.

Workflow 2 · Obligations & Renewals · Data Sources

CLM is the only integration needed to begin — RAID linkage from week 4 extends reach into the programme risk register.

Record	Current Source	Final Source
Contract documentsExecuted contract documents from which obligation type, value, due dates, and assignee are extracted by AIP	CLM	CLM
Obligation registerOwner-validated list of obligation instances with type, value, due date, assignee, and current fulfilment status	Not held	Owner-authored in Palantir
Contract register (expiry dates)Contract identifiers, parties, values, execution dates, and expiry milestones used to trigger renewal workflows	CLM	CLM
RAID registerProgramme risk, action, issue, and decision register into which contract expiry risks and overdue obligations are automatically created	RAID system (manual entry)	RAID system (automated via Palantir)
Stakeholder contact directoryContact records for contract owners, procurement, legal, and finance used to route obligation notifications at 90, 60, and 30 days	Procurement spreadsheets	Procurement system

Workflow 3 · Change Management

The owner's change register exists in parallel with the contractor's — reconciliation runs automatically when each extract arrives.

ORIGINATE

Event identified and logged

RECORD

Owner register opened

SUBSTANTIATE

Rates, hours, fragnet

REVIEW

Adequacy checked at intake

RECONCILE

Owner vs. contractor compared

ACCEPT / DISPUTE

Decision recorded

REPORT

Open / closed register

What the workflow achieves	In commercial terms
Owner register maintained in parallel	The owner holds its own change position, independent of the contractor's. On every reconciliation, the owner's version is the reference position.
Reconciliation runs at extract arrival	Each contractor extract is matched line by line on arrival. Gaps appear as numbered exceptions before the review meeting, not during it.
Substantiation tested before review	A change pack without rates, hours, or fragnet is returned at intake. Adequacy is established before the commercial meeting, not argued through it.
Accepted changes feed W4 directly	Changes cleared through authority thresholds update the W4 EAC without re-entry. Positions stay aligned across workflow boundaries.

Workflow 3 · Change Management · Data Sources

Contract terms from CLM and contractor change extracts via CSV are both available from day one — P6 fragnet adds programme linkage from weeks 10–12.

Record	Current Source	Final Source
Contractor change registerChange ID, originator, description, contract reference, status, impact on contract value, programme and substantiation reference	Contractor (ad hoc)	Contractor CSV / workflow export
Contract terms and clausesContract document providing the instruction basis, change valuation rules, and authority thresholds governing the change process	CLM	CLM
Substantiation packsContractor-supplied rates, hours, productivity impact, and fragnet supporting each change submission	SharePoint	ACC (from week 10)
Delegated authority thresholdsInternal governance parameters defining which change values require escalation above commercial team level	Not formally held	Owner-authored in Palantir
Programme fragnet / P6 activitiesSchedule impact evidence attached to change packs showing affected P6 activities and programme delay	Not integrated	Primavera P6 via XER

Workflow 4 · Forecast & EAC

The owner's accepted EAC is computed independently — the gap between the owner and contractor positions becomes the structured challenge agenda.

SUBMIT

Contractor submits EAC + CTC

INTAKE CHECK

Cost codes validated

RECONCILE

Owner EAC compared

CHALLENGE

Variance flagged automatically

ACCEPT

Drawdown position updated

UPDATE CASHFLOW

Forward schedule updated

REPORT

Exec pack generated

What the workflow achieves	In commercial terms
Owner EAC computed independently	The owner calculates its own EAC from validated cost-code data, independent of the contractor's submission. The gap between the two positions becomes the structured challenge agenda.
Contingency tracked automatically	Each accepted EAC adjusts the programme contingency position. Threshold breaches surface before executive review, not inside it.
Payment schedule updated at acceptance	The accepted EAC feeds directly into the forward payment schedule, aligned to milestones and treasury cut-off. No manual assembly between acceptance and reporting.
Submissions gated at intake	A contractor EAC without cost-code alignment or movement narrative is returned before the review meeting opens. The challenge is structured from the first interaction.

Workflow 4 · Forecast & EAC · Data Sources

Core records are available as CSV extracts from day one — programme schedule linkage adds cashflow fidelity from weeks 10–12.

Record	Current Source	Final Source
Contractor EAC / cost-to-completeWBS / cost code, budget, actuals to date, committed cost, forecast to complete, EAC, variance, movement narrative	Contractor ERP (ad hoc)	Contractor ERP structured CSV
Certified payments to dateCumulative and current-period certified amounts by contract, reconciled to the payment run	Finance team extract	SAP / Coupa
Contract reference dataContract identifiers, package names, and counterparty details required to code EAC submissions against the owner's commercial register	Google Sheets	CLM
Cost codesOwner WBS and cost coding structure used to validate and align contractor EAC submissions	Google Sheets	Owner-authored in Palantir
Contingency registerOwner-maintained position tracking contingency allocation, drawdown decisions, and remaining balance by contract	Not held	Owner-authored in Palantir
Programme schedule / cashflowMilestone dates and forward cashflow phasing used to align certified payment projections to treasury cut-off	Not integrated	Primavera P6 via XER

Workflow 5 · Claims Management

Claims are won on notice compliance and the quality of the chronology — both are built into the system from day one.

EVENT

Delay or disruption logged

NOTICE ASSESS

Clause and deadline flagged

EVIDENCE

Transmittals, diaries, costs

ENTITLEMENT

Clause mapping, causation

QUANTUM

Time and money impact

NEGOTIATE

Without-prejudice discussion

ESCALATE

Formal dispute package

What the workflow achieves	In commercial terms
Notice obligations flagged at event	When a claim event is logged, the clause, required notice form, and deadline appear immediately. The team has the answer before the first call, not after a contract search.
Immutable audit trail	Each event is timestamped at creation. The notice compliance record cannot be altered retrospectively, which matters when the dispute reaches adjudication or litigation.
Evidence assembled before pressure	Transmittals, RFI references, and cost actuals attach to the event as they become available. The evidence pack builds over time, not in a rush under dispute pressure.
Live exposure in the risk position	Total live claim exposure rolls into the recognised risk register at programme level, visible to the executive before any contractor submission arrives.

Workflow 5 · Claims Management · Data Sources

Contract clauses from CLM and CDE transmittals connect today — P6 schedule integration adds critical-path linkage from weeks 10–12.

Record	Current Source	Final Source
Contract clauses and notice requirementsContract provisions defining claim entitlement, notice obligations, timescales, and the response process	CLM	CLM
CDE transmittals and document historySite instruction records, drawing issues, and formal transmittals forming the primary factual chronology for claims	SharePoint	ACC (from week 10)
Cost actuals (quantum estimation)Cost code, description, labour hours, rates, material quantities, subcontractor reference, period actuals and cumulative	Procurement spreadsheets	Finance system CSV
RFI / TQ chronologyRequest for information and technical query log evidencing information-flow failures and delays that form the factual basis of a claim	Google Sheet / email	ACC RFI module
Programme schedule — critical pathCurrent and contemporaneous schedule used to demonstrate programme impact, delay causation, and critical path disruption	Not integrated	Primavera P6 via XER

Workflow 6 · Commercial Close-out

The W3 change register means the owner's variation position is already in the system when practical completion is issued.

TRIGGER

Practical completion issued

VARIATION RECON

W3 register vs. contractor

FINAL ACCOUNT

Owner position prepared

RECONCILIATION

Gaps resolved or referred

RETENTION & BONDS

Release schedule checked

FINAL CERTIF.

Final certificate issued

OPS TRANSITION

Warranty objects transferred

What the workflow achieves	In commercial terms
Owner final account prepared first	The owner's close-out position is built from the W3 change register and certified payment ledger before any negotiation begins. The contractor receives a structured comparison.
Variation register feeds close-out directly	The W3 change register flows into the close-out reconciliation without re-entry. Gaps appear as numbered exceptions, not a spreadsheet cross-reference under time pressure.
Retention and bonds tracked with alerts	Release dates and bond expiry windows carry automated alerts. Missed calls and lapsed bonds are caught by the system, not by whoever remembers to check.
Settlement record retained for benchmarks	Close-out produces a structured commercial settlement record with variance analysis. That intelligence is retained as programme benchmark data, not filed in a PDF archive.

Workflow 6 · Commercial Close-out · Data Sources

Close-out draws on records built throughout delivery: the W3 register, certified payment ledger, and owner-authored retention register.

Record	Current Source	Final Source
Contract register and variation logChange ID, originator, description, contract reference, status, impact on contract value, programme and substantiation reference	W3 register (Palantir)	W3 register (Palantir)
Contract terms and close-out schedulesContract provisions governing final account procedures, retention release, defects liability, and close-out certification	CLM	CLM
Certified payment ledgerCumulative and current-period certified amounts by contract, reconciled to the payment run	Finance team extract	SAP / Coupa
Retention / bond registerBond reference, type, value, expiry, renewal terms, and retention balance by contract and milestone trigger	Not held	Owner-authored in Palantir
P6 milestone linkagePractical completion and sectional handover milestones used to trigger close-out procedures and retention release events	Not integrated	Primavera P6 via XER

04

Prioritisation

Where to build first

Workflows ranked by programme impact and the data records available to hydrate them today.

Data Readiness

W1, W2, and the W5 event log can run with data available today — the remaining workflows are gated on records being shared.

Data Pipeline Ready Now

⠿

W1 · Vendor Qualification

All compliance APIs connect today with no internal system dependency. Supplier master available as CSV. Cases can open immediately.

⠿

W2 · Obligations & Renewals

CLM integration available from day one. AI extracts obligations from executed contracts automatically. RAID linkage adds from week 4.

⠿

W5 · Claims — event log tier

The immutable event ledger and time-bar alerting need only contract clauses loaded from CLM. No integration required.

Workflow can be hydrated with interim arrangements

⠿

W3 · Change Management

Owner register deployable with CDE connector and MDR API. Contractor CSV extract available. P6 fragnet adds programme linkage from weeks 10–12.

⠿

W4 · Forecast & EAC

Core records available via CSV pathways today. P6 cashflow linkage adds richness from weeks 10–12.

⠿

W5 · Claims — full evidence + schedule

CDE transmittals live. Full evidence packaging enriched as P6 integrates.

Workflow needs to wait for data

⠿

W6 · Commercial Close-out

Structure and design the register now — including retention, bond, and obligation objects. Active use follows practical completion milestones.

Workflow Prioritisation

W1, W2, and W3 rank highest on both programme impact and data readiness — all three can begin now.

	Workflow	Programme Impact	Data Readiness	Priority
☰	W1 · Vendor Qualification
☰	W2 · Obligations & Renewals
☰	W3 · Change Management
☰	W4 · Forecast & EAC
☰	W5 · Claims Management
☰	W6 · Commercial Close-out