Delivery as living objects,
not documents.
A project plan is a snapshot of what someone believed on the day they typed it. RAiDAR keeps the object itself true — an agent reconciles the plan against the signals delivery already produces, recomputes the date it can actually defend, and surfaces only the calls that change the outcome.
Signals in. A defensible date out.
Nothing here asks a human to re-type what the organisation already knows. Every input is something delivery emits anyway — the engine is what turns it into a position.
How it stays true without a status meeting.
- 1AskThe agent asks the one person who knows — 60 seconds, in Teams.
- 2ReconcileThe answer lands against the plan, the spend and the tickets.
- 3RecomputeLockDate and confidence move. Nobody re-types a status.
- 4SurfaceOnly the calls that change the outcome reach a human.
Three depths, one object.
The same record, read at the altitude you need. Nothing is re-keyed between them — drill down far enough and you reach the signal that moved the date.
Every programme, one screen. Colour is derived, never typed — you are reading the engine's verdict, not someone's optimism.
The gauge, the tiles, and the gap between the date that was promised and the LockDate the evidence supports.
A real WBS with predecessors, float and baselines — because senior PMs will not give that up. Guardrails flag what the data disputes.
Everyone gets a different product.
Switching persona with the picker in the top bar changes the whole toolkit — the navigation, the landing screen and what is worth your attention. Pick a role below to see exactly what it can do and how to work it.
Owns delivery of specific programmes end to end — the plan, the crew, the vendors and the date.
- 1Create a programme on the Planning Canvas — the wizard builds a WBS from the org model and the vendor's published basis; you adjust the last 20%, and every override is kept on the record.
- 2Inside a programme, the tabs are the whole book: Plan, Artifacts, Meetings, Resources, Sourcing, Data Trail.
- 3The Project Plan tab is a real WBS — predecessors, float, baselines, CSV out. The Rails column flags what the data disputes; you can override with a reason.
- 4Stop chasing status. The agent asks; you read what came back in Agent Comms and act on what it surfaced.
The ceremonies existed to close an information gap.
Standups, status reports and steering committees are all mechanisms for discovering what is actually happening. When that is continuously known, the mechanism is the part you can retire — not the governance.
Everything in this demo runs on seeded data — the integrations are simulated, the engine is not.