When FlowGenius gets a time wrong

Fix it in the draft, in about five seconds

Click Adjust on the block and change the minutes. Everything after it moves, and the clock, the energy arc, and the outlook update while you type. You can rename the block in the same card. “Reset to FlowGenius” puts it back if you decide the original was right after all.

If the block shouldn’t be there at all, Skip removes it from the set and the rest of that day pulls up to fill the time it was taking.

The end time you set is checked, and the check is loud

If a day’s programme runs past the end time on the event, a warning above the draft names the day and how many minutes over it goes, and asks you to shorten or skip blocks before applying.

If a section was drafted outside the hours you set, the rule engine moves it to the first time that fits and tells you it did. The warning names the block, how far it moved, and its new time. A move of two hours or more gets its own “MAJOR CHANGE” warning naming the before and after clock times, because a move that size is a different plan rather than a tidy-up and it deserves a closer read.

Set the start and end times on the event form. FlowGenius will not generate at all without both of them, so there is no version of this where it has to guess how long your day is.

Gaps are left alone on purpose

Unprogrammed time inside your own hours is reported and never closed. Open dancing between dinner and the last dance looks exactly like a hole to a machine, and closing it would haul the last dance back into the middle of the meal.

So a long gap gets a sentence naming what it sits between and how long it is, and then it stays where it is. Add a block or change the times yourself if it wasn’t intended.

Immovable times are the strongest lever you have

Add them on the event form and mark each one HARD or FLEX. Hard is a wall. A section sitting on a hard timed anchor is never moved by the rule engine, even when it falls outside the hours you set, because a venue-contracted noon lunch outranks anything we derived.

If a hard anchor ends up with no break, meal, or transition within ten minutes of it, you get a warning naming that anchor so you can look at the layout around that time.

Your immovable times are listed on the event’s Overview tab with a HARD or FLEX badge on each, and again in the left column of the FlowGenius panel, so you can check what it is working with before you generate.

Multi-day events, and the one thing worth knowing

An event stores one start time and one end time. Everything past “one day, exactly as you entered it” is FlowGenius reading those two times, and that reading decides which day every section lands on. The panel shows it in a card headed “How your event’s days were read,” with a link to the event dates on every line.

When the hours for later days are inferred that way rather than set by you, FlowGenius will not throw a generation away over its own reading. It shows you the draft, says the hours are its reading, and tells you not to apply that day without re-timing it yourself.

A day that opens later than the last one keeps its own start time. Nothing you skip or retime on day one can drag day two earlier.

Give it more to work with

The draft is only as good as what it is reading. The inputs that change the timing most are your speakers and their energy ratings, the expected size of the room, your must-haves, and the ask in your own words when the event has one. A beta user told us that adding more speakers improved the timing she got back, which is the plainest version of this we have.

See “Speakers and crew detail” for what to add and where.

After you have applied

Change a block’s duration in the run-of-show builder and everything after it shifts with it. Drag blocks between sections and the schedule recalculates as they land. Or generate again with tighter inputs, and the version you already applied stays exactly where it is.

One honest note for early beta users: a show applied in the first weeks of the beta was written with every section fixed to an absolute time, so editing one block’s length in it moves nothing after it. Generating and applying a fresh draft writes the show the new way, and the cascade works from then on.

If you think it’s a bug

Tell us. Beta users’ reports are the reason most of the timing work above exists. Every bug a beta user has reported, and where each one currently stands, is listed in public at planetevents.io/roadmap, and you can write to us from planetevents.io/contact. A screenshot of the draft with the times in it is worth more than a paragraph.