Milestones and dependencies
Milestones per stage with blocking and informing dependencies.
CONTINUITY · Trovensa Progress
DesignedOne connected view of the program.
Designed, not yet available. Status as of 2026-09-15.
Intended forProgram leads, development teams and manufacturing specialists.
PillarCONTINUITY · Work with continuity
Capabilities
Progress is being designed to show one development program as a connected picture: milestones by stage, the dependencies between them, open items, and approval requests with their decisions and signatures. It supports parallel activities and repeated experiments and links each milestone to the evidence behind it.
Each capability below is a design target for Trovensa Progress.
Milestones per stage with blocking and informing dependencies.
Outstanding questions and responsibilities linked to the records they concern, including the ones agents propose from a thread.
Approval requests for plans, protocols, reports, hypotheses and milestones, with the decision and rationale recorded and, for protocols and reports, a decision signature.
A Progress agent would read milestones, dependencies, open items and recent checks and propose open items or milestone changes. It holds no tool to request an approval, decide one or sign.
Roadmap On the roadmap, not yet available. Status as of 2026-09-15.
In the console
How Trovensa Progress is used from the console: one ask, the plan, the proposals an agent may make, and the decision that stays with a person.
Roadmap On the roadmap, not yet available. Status as of 2026-09-15.
“What is blocking the toxicology milestone?”
Read milestones, dependencies, open items and recent checks; show the blocking view; propose open items.
Requesting or deciding an approval; signing.
The program lead approves the open items and declines the rest with a reason, then chooses whether to share the thread with the program.
Milestones · Dependencies · Open items · Approvals
Stages served
Read on