An AI schedule looks tidy. Did a fixed meeting move?

Mark fixed commitments before asking for a plan. A neat list can still break a deadline, overlap a meeting or omit travel.

Our view: use AI to propose options, then check the constraints you cannot change. A workable plan should say when the request is impossible instead of quietly moving a fixed commitment.

A small example with no room to fit

This invented schedule uses one date and time zone. Meeting A is fixed at 10:00–10:40; meeting C is fixed at 11:00–11:30. Task B takes 30 minutes. Allow 15 minutes to travel between each event. The gap is 20 minutes, but B plus both trips needs 60. It cannot fit between A and C.

A visible correction, rather than a hidden trade

Putting B at 10:30–11:00 overlaps A by 10 minutes even before travel. One feasible option is A at 10:00–10:40, C at 11:00–11:30, then B at 11:45–12:15. A-to-C has 20 minutes and C-to-B has 15. The fixed meetings stay fixed.

Specify what may change

Give the date, time zone, fixed events, task durations and travel requirements. Our suggested request is: preserve every fixed event, list any conflict first, and explain each moved flexible task. If there is no feasible option, ask which constraint I can relax.

What research can and cannot tell you

PlanBench, published at NeurIPS in 2023, separates planning into tasks that can be evaluated systematically. We cite it for the need to check a plan’s conditions, not as a score for today’s assistants. The time arithmetic above is our own example, independently checked.

Published October 13, 2026. Editorial opinion with a fictional schedule and verified interval arithmetic. We did not ask an AI service to generate the example or test a current model’s planning accuracy.

Sources: NeurIPS 2023 · PlanBench.