LADX
Start free
← Products

Planner

Available now

Every project on one timeline.

A Gantt chart over every project at once, seeded from the deliverables each job actually owes. Drag a bar to move it, drag its edge to change how long it takes, and let a dependency stop a task starting before the one it waits on has finished.

Open Planner
The plan, as bars against real datesMARAPRMAYJUNURSFDSSoftwareFATSATTODAYDrag a bar to move it. A task that depends on another cannot start before it ends.
Bars against real dates, with the dependency drawn because the chart enforces it, and a rule for today.

In short

Is there a Gantt chart that knows what an automation project actually owes?

LADX Planner draws every project on one timeline, seeded from the deliverables each job owes rather than from a blank page. Drag a bar to reschedule it, drag an edge to change its duration, and a dependency stops a task starting before the one it waits on has finished. Dates are stored as dates, so a plan drafted in London reads the same in Chennai.

The problem

The plan lives in a spreadsheet that nobody updates, or in a scheduling tool that knows nothing about the job. Both drift from the work within a fortnight, and the first anybody notices is when a date is missed.

What it does

  • Seeded from the scope, not from a blank page

    The tasks come from the deliverables the project owes. Change the scope from programming only to a full lifecycle and the plan grows to match, without disturbing work already under way.

  • A chart you can actually edit

    Drag a bar to reschedule it, drag either end to change its duration, and zoom between days, weeks and months. Weekends are shaded, today is marked, and dates are stored as dates rather than instants so a plan drafted in London reads the same in Chennai.

  • Dependencies that mean something

    A task can wait on another. The chart draws the link, refuses a circular one, and flags a task scheduled to start before the thing it depends on has finished, rather than letting the two quietly disagree.

  • Scheduling for the undated

    A new project has a plan and no dates. One action lays every undated task end to end across working days, which is a starting point to argue with rather than a blank column to fill in by hand.

  • In and out as CSV

    Export the plan and open it in anything. Import one back, with quoted fields and real date validation, so a plan built in a spreadsheet can come in rather than being retyped.

  • Across every client at once

    Filter by client or by project, or look at all of them together, which is the view that answers the question a small integrator actually has: what is happening in March.

What it doesn't do

Listed because you would find out anyway, and finding out later is worse.

  • No resource levelling and no critical path. It shows what is planned and what depends on what, not who is over-committed.
  • Duration is in working days, and the working calendar is Monday to Friday. Public holidays are not modelled.
  • It plans deliverables. Whether a deliverable is any good is still a person's job.

Questions

How is this different from a general project planner?
The tasks come from the deliverables the project owes, which the system already knows. Widen the scope from programming only to a full lifecycle and the plan grows to match, without disturbing work already under way. A general planner starts empty and stays whatever somebody last typed.
Can I import and export the plan?
Both, as CSV, with quoted fields and real date validation. A plan built in a spreadsheet can come in rather than being retyped, and the plan can go out to anyone who wants it in Excel.
Does it do resource levelling or critical path?
No. It shows what is planned and what depends on what. Resource levelling and critical path are not implemented and the page says so rather than implying otherwise.