AI-governed PPM: what it means and why it matters

The phrase, unpacked

"AI-governed PPM" is doing two jobs in the same compound noun. The first job is the obvious one — AI is part of the platform. The second, and the more important one, is that AI itself is governed. It does not sit outside the platform's audit envelope. It is not a black box you glue on after the fact. Every recommendation it produces, every action it executes, every state change it touches carries the same provenance, the same audit trail, and the same human-in-the-loop gates that any other privileged actor in the platform carries.

The reason this matters: an AI plane that operates outside governance is just another vendor lock-in disguised as productivity. You cannot roll back what you cannot trace. You cannot explain to an auditor what you cannot reconstruct. And in a portfolio context — where the decisions in question are about which projects get funded, which people get reassigned, and which forecasts go to the board — the cost of a wrong AI suggestion is not "we have to redo the prompt." It is "we have to explain to the executive team why the budget moved."

The wedge against the incumbents

The major incumbents — Planview, Clarity, Smartsheet-Enterprise, Asana-Enterprise — built their cores in an era before LLMs. Their AI features are bolt-ons. They are bolt-ons in the literal architectural sense (a separate service, a separate identity, an asynchronous hand-off) and in the more telling provenance sense (an AI-originated change does not carry the same actor metadata as a human-originated change). When a CFO asks "who approved this re-baseline?", the answer should not depend on whether the answer was generated by a model.

IntelliPPM's bet is the opposite axiom. AI is a first-class actor in the platform from day one. The audit envelope on every state change includes actor.type, which can be human or ai. When it is ai, the envelope also includes the recommendation id that produced the change, the model id and version that generated the recommendation, the feature freshness at the moment of inference, and a reversibility window during which the action can be rolled back with a single click.

This is not a feature. This is a substrate.

What governance looks like in practice

In an AI-governed PPM platform there are three autonomy levels per AI head per portfolio:

• auto — the head executes without human review. Available for

read-only heads (a Status Summarizer is the canonical example), and available for read-write heads only with explicit per-tenant approval at the portfolio level.

• recommend — the head produces ranked suggestions, with confidence

and counterfactuals, in a human-in-the-loop inbox. A human approves each one before any state change is committed.

• require_human — the head produces drafts only. Even after approval,

every action runs through a human review step, with the human's reasoning captured back into the feedback loop.

The defaults are conservative on purpose. A Resource Optimizer head that automatically reassigns people would be a career-impact nightmare; it ships on recommend and never auto. A Prioritizer head that automatically re-ranks a portfolio would be a strategy-impact nightmare; it ships on recommend and never auto. A Planner head that drafts WBS structures ships on require_human because the cost of a wrong WBS compounds across the project lifecycle.

These defaults do not get the way of velocity. They are how velocity becomes safe at portfolio scale.

The recommendation contract

A recommendation under AI-governed PPM carries:

• The suggestion (what the head thinks should happen)
• A confidence score, calibrated against historical eval data
• The drivers — the features that pushed the recommendation in this

direction

• A counterfactual — what would change if the most influential driver

flipped

• The rationale, expressed in plain language with citations to the

events that supported the conclusion

• The proposed actions, expressed as references to pre-declared,

idempotent action templates (not free-form code)

• The model identity (model id, version, signature)
• The feature freshness — how stale the inputs were at inference
• The residency region the inference ran in

Every field is auditable. Every field is queryable. None of it is generated post-hoc to placate a regulator. The contract is the artifact.

The reversibility window

Auto-executed AI actions carry a default 7-day reversibility window. During that window the action can be reversed with a single click, which generates a compensating event and rolls the state forward with the reversal recorded as a peer fact in the event log. Reversals are never in-place mutations. The original action and the reversal are both first-class events.

This matters less for the cases where you reverse and more for the fact that it is possible at all. A platform that cannot reverse an AI action is a platform that cannot trust an AI action. And a platform that cannot trust an AI action is one where the AI plane stays a demo, not a workflow.

Where this leads

The end state is straightforward. AI Brain is the decision layer. The canonical event bus is the substrate. The HITL inbox is the surface. The reversibility window is the safety net. And the governance defaults are calibrated such that a portfolio leader can say yes to running AI on real work without saying yes to handing control to a model.

That is what AI-governed PPM means.

Talk to founder

If you run a portfolio that lives across Microsoft Project, Jira, an ERP general ledger, and twenty spreadsheets — and you want an AI plane that meets your audit standards, not the other way around — the contact form on the pricing page reaches the founder directly.