See the whole job, and exactly what's at risk of slipping.
A Gantt with real critical-path math underneath. Link the tasks, and Vinclo computes float and the critical path, compares them to your baseline and tells the PM when the job slips.
Sample data. Projects, people and vendors shown on this page are illustrative.
Float is computed, not guessed.
The critical path method runs on every change. It finds the critical path, the chain of tasks that drives your finish date, and gives every task its float to the deadline and its free float.
Built the way schedulers think.
Dependencies between tasks, date constraints, milestones, and WBS parents that roll their children up. Enough structure for a real job, without a scheduling department.
- WBS parent
- 3 · Roadworks
- Start
- Jul 27, 2026
- Duration
- 18 d
Dependencies
- Storm sewer & catch basins
- Finish to start
- Watermain & services
- Finish to start
Constraint
- Start no earlier than
- Jul 27, 2026
A baseline to measure against.
Set the baseline when the plan is agreed, and every task shows its variance from then on. Accepted change orders move the contractual end by the days they carry.
Told when it slips, on your own calendar.
When project float goes negative, the PM gets a schedule-slipped notification and the project appears in Portfolio. Durations run on your company work calendar: the weekdays you work and the days you do not. Ontario statutory holidays come seeded, and the list is yours to edit.
Where it stands today
- One baseline per schedule. Setting a new baseline overwrites the old one, and no baseline history is kept.
Works with
Find the critical path before it finds you.
We'll build a schedule for a job like yours and break it on purpose.
Request a demo