Commissioning to Contract Management

Where this usually breaks down

Three places the picture usually gets lost.

None of these are about one bad tool. They're about how much depends on someone remembering.

The reasoning behind funding decisions isn't written down

A Board or executive decides what gets funded each commissioning round. Once the meeting ends, that reasoning usually isn't captured anywhere. Ask again in a year and the answer depends on who remembers being in the room.

A tender portal solves procurement, not what comes after

A dedicated tender platform handles publishing, vendor questions, even structured evaluation scoring, entirely inside its own portal. The moment a provider is chosen, that's the end of its job. Everything from signing the contract onward starts from zero.

Contracts run in parallel, each on its own clock

Different program areas, different KPI cadences, different renewal dates. Knowing which of 20 or 50 contracts needs attention this month usually means checking each one by hand.

What this looks like today

The information exists. It's just scattered across whoever's handling it.

Right now

A funding decision gets made in a meeting. The reasoning lives in whoever attended, not in a record.

A provider is chosen through a separate tender process, evaluated inside that portal.

Once the contract is signed, tracking KPIs, chasing overdue reports, and approving payments all happen by hand, spreadsheet by spreadsheet.

What changes

Every funding decision becomes a record, with the reasoning attached, not just the outcome.

Once a provider is selected, the contract, its approvals, and its onboarding checklist all live in one place.

KPIs are checked automatically against target, and payment approval is tied to whether they were actually met.

How it works

Four stages, from a funding decision to a contract that manages itself.

Each stage maps to configuration already available on the platform, not custom development. The tender itself, whichever portal a PHN already uses for that, sits between stages one and two.

Capture & prioritise the need

Needs get logged from any source and reviewed together each round, with the reasoning behind what gets funded captured alongside the decision.

FormsDecision Tables

Bring the contract to life

Approval scales with contract value, from a manager's sign-off to full executive review, then an onboarding checklist before service commencement.

Approval ChainsRecord Updates

Track performance automatically

Every contract's KPI reports come in on their own cadence, checked against target on arrival, with overdue reports chased without anyone keeping a mental list.

Record QueriesNotifications

Review, renew, and pay

Quarterly reviews arrive with the data ready, renewals get flagged months out, and payment approval ties to whether KPIs were actually met that period.

Workflow ActionsEmail Automation

Beyond the dashboard

Your own AI can already ask the questions, directly against this data.

Every record above, needs, contracts, KPI results, invoices, sits on a platform that exposes an MCP interface. A PHN's own AI assistant can query it directly. No export, no dashboard to build, no separate integration.

"Which contracts are behind on this quarter's reporting?" "Show me every contract renewing in the next 90 days." "Which providers missed their KPI target last cycle, and by how much?"

These aren't hypothetical prompts. They're the kind of question an AI assistant can answer straight from the underlying records, the moment it's connected, in language a contract manager already thinks in.

What's proven, what's a concept

Worth being precise about which is which.

Already proven

Form Studio, Flow Designer, Rule Engine: live platform capabilities, in production today
Working inside a PHN environment: an existing PHN customer runs supplier document handling through a governed, multi-stage workflow with a full audit trail on this same platform
ISO 27001 certified, built on Microsoft Azure: the governance layer underneath any configuration

These aren't specific to commissioning or contracts. They're the same building blocks used across every industry this platform serves.

This document

Commissioning to Contract Management as a named configuration of those building blocks
A solution concept, shaped around how this workflow actually runs, not yet a named deployment
A starting point for a conversation about what your team's version of this would need

Shown here to make the fit concrete, not to claim it's already running for a specific PHN.

Contract Portfolio Dashboard: Business Process Automate platform

How this fits your process

Built to work with your procurement process, however you run it.

Decisions stay decisions, not automated away. A Board still decides what gets funded, a contract manager still decides how to handle an underperforming provider. The system prepares the information and keeps the record, it doesn't make the call.

BPA works with your procurement process, not around it. Whether a PHN keeps using its existing tender platform, or wants a fully customised procurement workflow built on this same system, this covers what happens before, during, and after. Every organisation's procurement journey looks a little different, and this is built to fit that, not force a single path.

Payment approval tied to performance, only where that's wanted. Some PHNs will want KPI results gating that approval automatically, others won't, that's a configuration choice, not a default. Either way, this stores the decision and its audit trail. The transfer itself still runs through whatever finance system a PHN already uses.

Knowing whether one of your contracts is underperforming still means opening a different spreadsheet for each one.