What does AI-powered project management look like in TransformRadar?

Every prompt TransformRadar sends to a model carries the structured data that licenses every factual claim in the answer, and instructs the model to mention nothing outside that data. The output is validated against a schema before anyone sees it; raw model text is never rendered. A banned-phrase list catches the hedging and the filler. And every AI-produced artefact is a draft that a named person edits and approves — nothing is circulated automatically, and nothing is written to the record without an explicit confirmation.

The consequence is that the AI is exactly as good as the record. That is deliberate. A steering pack drafted from a live plan, a maintained governance log and a scored health assessment is worth reading. One drafted from a model’s general sense of how programmes go is not.

If the AI provider is slow or unavailable, each feature degrades to a deterministic summary or an empty state. A broken page is not an acceptable failure mode for a status report.

Each workspace has one AI job, and it always ends in a draft the owner of that workspace reviews.

Blip is the assistant inside every project workspace and on My work. It answers from the live record — what is overdue, what changed in delivery, which risks are open without an owner — and reads exactly the data the screens show, nothing else.

Blip can also prepare a change: log a risk, create a task or a delivery item, update a status draft. The change appears as a confirmation card showing what will be written and what it looked like before. You approve, or you do not. Blip never commits a change on its own, and it acts strictly as you, inside your own permissions on the project.

TransformRadar is a Model Context Protocol server. An organisation can allow Claude, ChatGPT, Cursor, Google Gemini or Mistral Vibe to connect; the agent then acts as the signed-in user, with that user’s project roles, through the same governed actions the buttons in the product use. Reads come with access, writes are switched on separately in tiers, and every write is a preview the user confirms. The MCP access page explains how to connect.

Inference runs on Mistral La Plateforme in Paris. Hosting, the database, file storage, email and AI are all European providers, and none of them trains on customer data. Every AI call is logged with who triggered it and which artefact it relates to; the prompt and completion are retained for thirty days for review and then removed, while the metadata is kept for cost analysis.

The one sanctioned exception is MCP: when you connect your own agent, that agent’s provider handles the conversation, which is why an Org Admin has to acknowledge the egress before switching external access on.

A new project starts with a plan and a weekly status, and the AI drafts from those two from the first week. Governance, Programme Health, value realisation, steering and the agile delivery backlog are switched on per project when a project needs them, and each one becomes another input the AI can draft from. Nothing about the AI layer assumes a large programme.

TransformRadar’s AI today is synthesis and preparation: it reads, drafts and proposes. It does not chase task owners, it does not watch the record continuously and raise anomalies on its own, and it does not negotiate with other systems’ agents. Those are the next steps, and the blog sets out the direction. What will not change is the rule at the top of this page: it reframes your data, it never invents, and a person confirms.