Every party on every project, in one governed record, not in someone's inbox.
Infrastructure portfolios run on counterparty relationships. Delivery partners, SPV co-shareholders, subcontractors, consultants, authority representatives, funders and insurers; every project touches a different mix, and every action lands with one of them. Tracked in spreadsheets and Outlook contacts, that web disappears the moment someone leaves. Origin Zero structures the counterparty layer per project, links every action to the party that owns it, and gives delivery partners a portal to act directly, so the relationships stay contactable, accountable and governed.
Sound familiar?
Relationship questions that should have structural answers.
“Who's the current contract manager for the delivery partner on Northfield Schools?”
When the answer requires opening a contract document, asking a colleague, or guessing from a 2024 email, your counterparty data isn't a system; it's tribal knowledge.
“Send the delivery partner the open actions for Kingsbridge Courts.”
Manually copying actions out of your platform, formatting them into a spreadsheet, and emailing them is how accountability degrades.
“Did the consultant respond on that close-out evidence yet?”
Without an external portal for counterparties to update actions themselves, you become the bottleneck.
Counterparty capabilities
Six features that bring your supply chain into the audit trail.
Eight structured organisation types
FM Provider, SPV, Subcontractor, Consultant, Authority, Funder, Insurer, Other. Every party fits a category, and every category fits the workflows that need it.
Per-project contact directory
Named individuals linked to their organisation, their role, and the specific project. Contact changes get logged in the audit trail. No more orphaned email addresses or stale numbers.
External Actions Portal
Sandboxed write-access for delivery partners and other counterparties. They see only what's assigned to them, update progress, upload evidence, submit for close-out, without ever entering your platform proper.
Action–counterparty linkage
Every action raised in an audit is assignable to a specific counterparty contact, not just a generic role. Accountability is named, not implied.
Notification on external updates
When a delivery partner updates or submits an action for close-out, the assigned Asset Manager is notified. You retain approval authority while delegating the data entry to the responsible party.
Counterparty role across the lifecycle
The same counterparty record flows through actions, MOS records (parties involved), narratives, and reporting. One counterparty entity, one governance trail.
What changes
When your supply chain is part of the audit trail.
Counterparty knowledge is institutional, not individual.
When the Asset Manager who owned a project moves on, the next person inherits a complete counterparty map, not a list of people to "ask Sarah about".
External work is visible the moment it happens.
Delivery partners updating their own actions creates real-time visibility into the work. The Asset Manager relay bottleneck disappears.
Audit trail extends across the supply chain.
Every counterparty interaction (action assignment, progress update, evidence upload, close-out) is logged. External governance becomes auditable.
Close-out timelines compress.
When the delivery partner doesn't have to wait for an email from you to update an action, remediation moves at the speed of the work.
Bring your supply chain into the audit trail.
Book a walkthrough and we'll show you the Asset Manager to delivery partner workflow, including the External Actions Portal, on a sample portfolio.