The problem: projects run on siloed stacks, not a shared baseline

Projects already run on a stack of siloed systems: Project Information Management Systems (PIMS), planning and scheduling tools, cost and ERP systems, commercial and contract tools, procurement and tendering portals, dashboards, Power BI, spreadsheets, procedures, documents, contracts and of course the emails that glue it all together.

Each system does its specific job inside one organisation. None of them were designed to keep multiple organisations aligned on the same story over time.

The pattern repeats on every major project:

• The Owner’s contract view doesn’t match the Consultant’s or the Contractor’s.
• Change lives in inboxes, minutes of meetings, action/event/decision registers.
• Risks sit in risk registers until they become “realised issues” somewhere else.
• Finance teams sign off valuations they can’t trace back to specific decisions.
• Payments go through 30/60/90 day cycles of re-verification.
• Boards and funders get PRINCE2-style RAG reports, but not an audited explanation of how the project actually got here.

The problem isn’t a lack of tools. It’s the lack of a governed baseline-and-event layer that sits above them and keeps every organisation in sync.

The rationale: a governed protocol above existing tools

Inontime adds that missing layer. It defines a protocol where every scoped, risk, cost, schedule, baseline and funding item can be wrapped in a governed, verifiable envelope and propagated between organisations.

At protocol level:

• Delivery events (progress updates, changes, instructions) are captured as governed envelopes with clear metadata.
• Those envelopes reference shared nodes: organisations, contracts, work packages, SSER items, risks, valuations and evidence.
• When an event is agreed, each organisation replays it into its own workspace, updating its scope/schedule/cost/risk baseline.
• Each step leaves a tamper-evident, hash-anchored audit trail that can be replayed later.

Existing project tools keep doing what they’re good at, drawings, models, workflows, task lists, documents. Inontime makes them all tell the same truth. Instead of reconstructing history at the end of a Project: Owners, Consultants, Contractors and Funders can see, in near real time, what was agreed, when it changed, and why.

This isn’t another project management workflow. It’s the missing protocol that sits above the workflows and systems you already run.

Current status and next steps

Inontime is starting with governed change propagation between two organisations. The current MVP demonstrates that a governed event created in Organisation A can be propagated to Organisation B, independently verified, and used to update each side’s view in a consistent way.

This first slice focuses on:

• Defining the governed event envelope.
• Propagating events between organisational workspaces.
• Proving the integrity and replayability of those events

The same protocol naturally extends to:

• Full baseline versioning and alignment.
• Procurement and package-level change.
• Funding-assurance outputs for owners and lenders.
• Portfolio views and the wider delivery-identity graph.

The immediate next step is to run this initial slice on a real project, using feedback from engineers and delivery teams to shape the baseline engine and integrations that follow.