Construction scheduling with Claude: check dependencies before the Gantt

Prepare a construction schedule with Claude →

A readable Gantt chart does not guarantee a workable sequence. Before asking Claude for a schedule, collect the tasks, durations, availability and constraints that explain its dates. Dependencies need to be reviewable, not merely illustrated.

Define constraints before drawing bars

Specify the start date, trades, durations, milestones and closures. Identify tasks that require another intervention to finish. Distinguish estimated durations from confirmed lead times and flag unknown supply dates.

The pack includes a generator script and configuration references. It prepares an Excel workbook with Planning chantier, Jalons and Notice & hypothèses. Its cells are static: changing a date in Excel does not automatically recalculate subsequent tasks. Request the configuration file as well to support revisions.

Test a simple dependency

Fictional example: task A starts on Monday 5 October 2026 and lasts two weeks. B takes one week and follows A. Without another constraint, B can start on 19 October. If the site closes for the week of 19 October, the revised scenario places B on 26 October.

Translate this reasoning into configuration dates before regenerating the workbook. The script should not be described as an engine that independently solves every dependency. Week one is the Monday-to-Sunday week containing the start date: inspect the Gantt headers.

Revise without losing assumptions

For each change, request affected tasks, previous and revised dates, and assumptions awaiting confirmation. Compare milestones with bars, then validate availability with participants. Moving a task can affect access or deliveries even when its duration stays unchanged.

Keep each dated version with its configuration. Meeting decisions can be documented in the site minutes. The schedule translates their timing consequences after constraints have been validated.