A lot of Gantt charts are drawn, and the first late delivery breaks them. How to get a linked schedule from one prompt, what to check in the AI's first draft, and how to hand it to a client or a Microsoft Project user.
A lot of Gantt charts are drawn. Someone shaded cells in a spreadsheet, or dragged bars across a slide, and the result looks exactly like a schedule.
Then the furniture supplier says the order will be two weeks late. On a drawn chart you move that one bar. Installing the furniture still sits where it was, and so do the move date and the handover. Somebody has to walk down the chart moving bars by hand, deciding which ones depend on the late order. By the third slip, nobody trusts the chart and the real plan is in the project manager's head.
A modelled schedule behaves differently. Each task knows what it waits for. Push the furniture order out two weeks and every task that depends on it moves too, the finish date updates, and anything that didn't depend on it stays put. The bars are drawn from the links, so they stay true.
So the first test for any "AI Gantt chart maker" is simple. Ask for a chart, move one task, and see what else moves.
You need three terms, and none of them is complicated.
Critical path. Link the tasks together and there is one longest chain from start to finish. Its length is the earliest the project can end. Any delay on that chain delays the finish by the same amount. The method was set out in a 1959 paper by James Kelley and Morgan Walker, "Critical-Path Planning and Scheduling", and the arithmetic hasn't changed since: work forward through the links for the earliest dates, backward from the finish for the latest, and the tasks where the two match are critical.
Float (also called slack). For every task off the critical path, float is how long it can slip before it starts to push the finish date. A task with ten days of float can run a week late and nobody outside the project needs to hear about it. A task with zero float can't move at all.
Baseline. A frozen copy of the plan as agreed. Three weeks in, the schedule shows where things are now. The baseline shows where you said they'd be. The gap between the two is the conversation you have with the client.
The US Government Accountability Office's Schedule Assessment Guide (December 2015) lists ten best practices for a reliable schedule, and three of them are exactly these: confirming that the critical path is valid, ensuring reasonable total float, and maintaining a baseline schedule. It's written for large government programmes, but the checks apply to an office move just as well.
A useful first draft needs four things from you: scope, dependencies, durations and constraints. The AI can guess at scope and order. It has no way of knowing your supplier's lead time or the date your lease ends.
Here is a prompt for a small office move:
Build a project schedule for moving our 20-person office to a new floor. Start Monday 2 November. The old lease ends Friday 18 December and we must be out by then. Tasks: sign the fit-out contractor. Fit-out works, 4 weeks. Data cabling, 1 week, after fit-out framing. Order the internet service, carrier lead time 20 working days. Order furniture, 6-week lead time. Install furniture. Move IT equipment. Removalists, 1 day on a weekend. Staff packing. Make good on the old office, 1 week, after the move. Working days Monday to Friday. Add milestones for "keys to new floor" and "out of old office". Link every task to what it waits for.
Look at what's in it. Each duration that depends on someone else (the carrier, the furniture supplier) is stated, because those are the numbers an AI will otherwise make up. The hard date is stated, so you can check the finish against it. And the last line asks for links, because a schedule without them is the drawn chart again.
Treat the first draft as a junior planner's work, and look in these places first.
| Check | How to spot it | What to do |
|---|---|---|
| Missing links | A task in the middle of the project with nothing before it, or nothing after it except the finish | Ask what it waits for, and add the link. Dangling tasks look like they have huge float. |
| Durations it guessed | Round numbers you never gave it: 5 days, 10 days, 2 weeks | Replace them with your supplier's or contractor's real figure, or mark them as estimates |
| Everything critical | Nearly every bar is on the critical path | Usually a single chain where some work could run side by side. Ask which tasks can overlap. |
| Too much float | One task can slip for months without moving the finish | GAO's guide makes the same point: unreasonably high float usually means logic is missing |
| Non-working time ignored | Tasks running through weekends or a public holiday | Set working days and holiday dates, then re-check the finish |
| Finish vs the hard date | The end date is past the date you gave it | Look at the critical path, not the whole chart. Only tasks on it can bring the finish forward. |
Fix the first two rows before anything else. A missing link makes a task look safe when it isn't, and a guessed lead time makes the whole finish date a guess.
If you want this checking to happen on every schedule without you remembering to do it, write the checks down and have an agent grade the file against them. That mechanism is in how an AI agent knows it's finished.
The point of the model shows up in week three. The carrier emails to say the internet service will be connected eight working days late.
Change that task's duration. In a modelled schedule, the tasks linked behind it move out (in Oppermind's editor, run Respect links), and the question becomes one you can answer from the screen. Is the internet service on the critical path? If it is, the finish moves eight days, and you now know before the removalists are booked that you'll miss the lease date unless something on the critical path gets shorter. If it isn't, check how much float it had. Six days of float and an eight-day slip means it has just become critical, with two days of damage to the finish.
Then compare against the baseline. If you saved one when everyone agreed the plan in October, the agreed dates and the current ones sit on the same row, and "we're eight days behind on the internet and two days behind overall" is something you can show the client on one screen.
Sooner or later the schedule goes to someone else, and the format should match the person.
The client or the boss wants a file they can open and read. A spreadsheet export with one row per task (start, finish, duration, predecessors, resources, per cent complete) opens anywhere and can be filtered and printed.
The project manager who lives in Microsoft Project wants something they can import and keep working on. Microsoft Project can open files in its own XML format, and Oppermind's MS Project XML export writes the tasks, durations, links, milestones, summary tasks, resources, per cent complete and any baseline you saved in that format. It writes a standard Monday to Friday calendar, so holidays and non-standard working days you set in Oppermind don't come across: re-enter them in Project. Then open the file and check it before anyone relies on it, in particular that the links came across as you expect.
A note for anyone searching for an MS Project alternative this month. Microsoft announced in September 2025 that Project Online retires on 30 September 2026, and says the retirement does not affect Project desktop. If what you're losing is Project Online's portfolio features (the Project Web App, shared resource pools, timesheets), that is organisation-wide software, so look at Microsoft's own migration routes first. If what you needed was a schedule for one project at a time, that's a smaller problem, and it's the one this post is about. Oppermind is not affiliated with, endorsed by, or sponsored by Microsoft. Microsoft Project and Project Online are trade marks of Microsoft.
Oppermind is an all-in-one AI workspace, and a project schedule is one of the things it makes from a single prompt. The schedule opens in Oppermind's own Project editor, where every task, date and link can be edited. In the desktop workspace, tasks carry finish-to-start links, and the Critical path button narrows the Gantt to the tasks on the critical path, with its length in days along the bottom. A Respect links command pushes every dependent task out behind a late one, and stops if it finds a circular link. You set working days and holidays under Change working time. Set baseline, under More in the Tools group or from the prompt in the Tracking Gantt view, saves the plan as it stands, and Tracking Gantt then draws each task's baseline as a dashed bar above where the task is now. When it's ready to hand over, export to .xlsx or MS Project XML.
Because the editor is the same workspace as everything else, the brief, the budget sheet and the client update deck can sit beside the schedule. If your schedule is part of a construction job, AI for tradies follows one from the first phone call. If it has to feed an estimating or ERP chain, the estimating post covers when that needs a custom system.
Free with no card, then Starter A$9.95, Pro A$29.99 and Pro Plus A$59.99 a month. Unlimited documents, spreadsheets, decks and designs on every plan.
Whatever you're here to make, make more of it.
Oppermind's editor schedules every link as finish-to-start: the next task begins when the one before it ends. If your plan depends on other link types, such as painting starting two days after plastering starts, split the tasks so the logic becomes finish-to-start, or keep that part of the schedule in a dedicated scheduling tool. Respect links also only pushes tasks later. If a predecessor finishes early, move the tasks behind it forward yourself.
Yes, and the better question is whether the chart is linked. Ask for dependencies in the prompt, then move one task and check that the tasks behind it move too.
Usually a missing link. The task has nothing after it, so the tool thinks it can slip right up to the finish date. Add the task it feeds into.
Export it as MS Project XML and open that file in Project. The export writes links, durations, milestones, resources and any baseline you saved, with a standard Monday to Friday calendar, so check the links after import and re-enter your holidays in Project.
Not for its portfolio features, such as timesheets and shared resource pools. It suits building and running a schedule for one project, and handing it to whoever needs it.
The office move is an illustrative example, not a plan for your project; durations, lead times and dates are yours to confirm with your suppliers. Oppermind platform prices are current as at 24 September 2026, are in Australian dollars, and are subject to the plan terms at checkout.
One prompt for the first draft, a critical path and a baseline to steer by, and an export for whoever gets it next.