Dependency Hunter
ProposesFinds dependencies nobody declared across tasks, documents and risks, and prices each one in days.
- Reads
- Tasks, documents, risks
- Produces
- Links to confirm, with impact
Gantt, board, cards and calendar are views of the same activities, with dependencies, float, the critical path and baselines underneath. Move a date and the platform tells you what it costs.

And what changes when it runs on one model.
Every team keeps its own version and none of them agree.
Nobody can say which slip actually moves the end date.
A planner's Gantt is not how a delivery team wants to work.
A late hand-off surfaces in the next project, weeks later.
Projects, activities and the links between them across the portfolio. Turn on the critical path and everything else dims.

Pick an activity and a delay, and the engine shows the new end date, the items downstream and the people whose assignments stretch.

Delivery teams move cards; the schedule moves with them. Status, owners and dates stay in one place.

The Dependency Hunter reads tasks, documents and risks and finds dependencies nobody declared, with the end-date impact of each.

Every item runs on the same engines the screens use.
Float, lag and dependency maths on every activity.
Frozen baselines with variance and a governed re-baseline.
Gantt, board, cards and calendar on the same activities.
Microsoft Project, Primavera P6, Excel, Jira, Asana and more.
Any slip priced in days before anyone commits.
Undeclared links found and proposed for confirmation.
The advisors and agents that work in this part of the platform. All agents
Finds dependencies nobody declared across tasks, documents and risks, and prices each one in days.
Reads a field report or weekly update and turns it into progress, dates, risks and resource gaps on the plan.
Maps Microsoft Project, Primavera and Excel files onto the model when you bring a plan in.
Builds alternative plans for a goal you set and compares them against the current plan.
No. Lodestar imports Microsoft Project and Primavera P6 files, so schedulers can keep their tools while the portfolio, KPIs and governance run in Lodestar.
Calculated. Dates, float and the critical path come from the scheduling engine, and every view writes to the same activities.
Yes. The delay simulator and What-If Studio run the engine on a copy, and nothing changes until a person applies it.
Send us a slice of your portfolio and we load it before the session, from strategy down to task.