Skip to content

Intelligence

Better context before the next decision.

Intelligence needs a reliable foundation: connected requirements, decisions and evidence. The Delivery Graph is that direction — assistance should point to its context, not replace accountable judgement.

Available today · subject to enabled add-ons and access

Workspace assistance

A metadata-focused assistant helps find permitted project information. It is not an autonomous delivery manager.

Requirement suggestions

Opt-in extraction from authorised RFQ/Requirements documents returns suggestions for review, not automatic changes to the shared register.

Tender award advice

An advisory summary and scoring simulation support review. Reviewer-entered scores remain authoritative; the adviser does not award a tender.

Planned concepts · illustrative examples

Five ways connected context could help.

Impact EnginePlanned conceptIf this requirement changes, what should we review?

Scenario

A cooling-duty requirement is revised after design review.

A proposed impact view would identify linked deliverables, obligations, test criteria and milestones for human review.

Today, teams record changes and their impacts. Automatic cross-project impact analysis is not implemented.

Decision LedgerPlanned conceptWhy did we choose this approach?

Scenario

A team accepts a different material specification following a clarification.

A proposed unified decision view would gather the rationale, source requirement, participants and evidence without losing the original context.

Decision registers and activity history exist today. A unified graph-backed Decision Ledger is planned.

AI Project ControlPlanned conceptWhich connected issues deserve attention?

Scenario

A late deliverable and an unresolved interface affect the same work package.

A proposed advisory briefing would surface related records and suggest review priorities with references.

Project control registers and a metadata workspace assistant exist. Autonomous project control or schedule prediction is not implemented.

Readiness EnginePlanned conceptWhat is missing before acceptance?

Scenario

A package is due for handover, but one test has no accepted evidence.

A proposed readiness view would compare linked acceptance commitments, verification and handover records, highlighting evidence gaps.

Verification and handover records exist. Automatic end-to-end readiness certification is not implemented.

Risk IntelligencePlanned conceptCould these changes create a wider risk?

Scenario

A supplier change, design deviation and delivery delay share a requirement.

A proposed advisory view would connect these signals for an accountable person to assess.

Qualitative risk registers exist. Predictive risk scoring and automatic risk discovery are not implemented.

These planned concepts describe a product direction, not active engines or a delivery-date commitment. Examples are hypothetical. No new project engines are introduced by these public pages.

Your next project

Keep the agreement connected to the delivery.

Let’s talk about your project