Create a Gantt chart from your tasks, dates and dependencies. Provide the scheduling facts you want represented and check overlaps before using the result to plan work.
State the schedule assumptions
Name each task, its start and end, and any predecessor. Explain whether durations mean calendar days or working days. If a person cannot work on two tasks at once, include that constraint. A chart cannot infer holidays, team availability or actual effort from task names.
In the example, implementation overlaps design deliberately. Without that explanation, overlapping bars could imply work starts before it has the input it needs.
Distinguish dependencies from proximity
Two adjacent bars do not necessarily have a dependency. Label the relationship that requires one task to wait for another. If a milestone slips, review the tasks that depend on it rather than moving every bar by the same amount.
Use a timeline when you only need the headline milestones. Use a swimlane when ownership and handoffs are the central question.
Treat the result as a reviewed plan
Read each task’s dates against the supplied schedule. Check that shortened bars represent changed durations, not just a layout adjustment. Ask the responsible people to confirm effort and dependencies before using the plan for a commitment.
The drawing does not synchronize a task tracker, calculate real resource availability or report live completion status.
Make it about your work
Edit this starting prompt, then send it when you are ready.