FlowGenius: generate, review, apply

The left column is a form, and it saves as you go

You do not have to leave the page to change what FlowGenius is reading. Expected guests, the two vibe sliders, wide dynamic range, the call-to-action type and the ask in your own words, and the must-have chips all edit in place. A small “Saving…” turns into “✓ Saved” at the top of the card as each change lands. If a save fails, the field goes back to its last saved value and tells you what happened rather than pretending it stuck.

Must-haves are not limited to the presets. Click “+ Add” and type your own, and it becomes a chip you can toggle like the rest.

A few things are shown but not edited here: the event title, its type, its date and window, and the venue. Those belong to the event itself, so the card links straight to the event form to change them. Your speakers and your immovable times appear underneath as a read-only summary, because FlowGenius reads both and you should be able to see what it has.

When something essential is missing, it asks in place

Three inputs FlowGenius will not guess: the event’s start and end times, the expected number of guests, and, when your event has a conversion goal, the ask in your own words. Each missing one raises a short amber note next to the field it belongs to. Leave out the guest count and it says it will not guess the room size. Leave out the times and it says so and gives you a link to set them.

The Generate button stays unavailable while any of those are open, and it lists what is still needed underneath, so you are never left clicking a button that quietly does nothing.

What comes back

The header line above the draft describes what Apply would write right now: how many blocks, the total running time, the start time, and the time the draft was made. It moves as you review, so it can never disagree with the schedule underneath it.

Under that sits a projected energy strip, then the outlook band, then any warnings, then two cards about what FlowGenius assumed, then the show itself, section by section.

The outlook band

Every draft gets an outlook: WEAK, FAIR, STRONG, or PRIME. It’s a call-to-action outlook if your event has a conversion goal, and a show outlook otherwise. Alongside the band you get the top reasons in plain English and the one or two highest-impact fixes. It’s a band, not a percentage, on purpose: we don’t show precision the data hasn’t earned.

It recalculates live. Skip a block and the outlook and the projected energy arc update instantly, restore it and they update again, and retiming a block moves both as you type. None of that costs anything or counts against any limit.

Labeled assumptions, in two cards

The first is headed “How your event’s days were read.” An event stores one start and one end, so anything beyond “one day, exactly as you entered it” is FlowGenius reading those two times rather than hours you set. That reading decides which day every section lands on, so it is shown rather than buried, and each line links to the event dates.

The second is headed “Assumptions FlowGenius made.” When an optional input is missing it proceeds and names what it assumed, each with a link to set the real value. You will never have to wonder which parts of a draft rest on facts you gave it and which rest on a reasonable guess.

Apply and Skip, block by block

This is the mental model worth having: you are reviewing a proposal one block at a time, not accepting or rejecting a document.

Every block row carries its clock time, its title, who is speaking, the one-line reason it is there, its type, and its energy. A CREW tag means guests would never see it. On the right it says “✓ Will apply,” because every block starts in the set. Click Skip and the row dims, its clock is replaced by the word “skipped,” and everything after it on that day pulls up to fill the space. The button turns into Apply so you can put it back.

Section headers keep up with you. A section whose blocks you all skipped reads “ALL SKIPPED” with no times at all rather than a zero-length range, and a section that has moved because of what you did earlier is tagged with how far it moved and in which direction.

Days do not move. A section that opens a later day keeps the start time you reviewed, whatever you did to the day before it. If the blocks you kept on the previous day now run past the next day’s start, the panel says so in plain words and asks you to trim before applying rather than quietly sliding the second day later.

Adjust: retitle and retime before you apply

Every block has an Adjust button. It opens a card underneath with the block’s full reasoning, what it is trying to achieve, its energy, whether it is guest-visible or crew-only, and the speaker. Two fields there are yours: the block title, and its length in minutes.

Retiming a block moves everything after it, and the clock, the energy arc, and the outlook all update as you type. If you change your mind, “Reset to FlowGenius” puts the block back exactly as it was drafted. You can also skip or re-include the block from inside the card.

A block you changed swaps its AI badge for “YOUR EDIT,” and that is not decoration. It is applied as yours: the AI attribution is dropped so a block cannot wear a badge it no longer deserves, and both your change and FlowGenius’s original wording are kept in the block’s note.

Warnings tell you, they don’t stop you

If a draft bends a rule, FlowGenius flags it and lets you decide. A hard immovable time with no break, meal, or transition within ten minutes of it. Two low-energy blocks back to back. A single speaker talking for more than forty-five minutes without a beat. A show that ends on an admin block instead of a designed moment. Awards sitting in the half hour before the ask on a conversion show. Each of those is a sentence at the top of the draft naming the blocks involved, and then it gets out of your way. You’re the operator.

There is one case where it does stop. If a day carries more than double the hours you set for it, FlowGenius says it misread how long the day is and asks you to generate again or widen the times first, because trimming will not rescue a plan that far off.

Applying

The Apply button says what it will do: “Apply all 14,” or “Apply 11 of 14” once you have skipped some. Applying creates a new run-of-show version containing the blocks you kept, with your edits. Every previous version is kept, untouched. There is no code path where a draft replaces something you built.

A draft applies once. If you want a different set of blocks after that, generate again and review the new draft, which leaves the version you just applied exactly where it is.

What we record, and the beta cap

When you apply, we record which blocks you kept, which you skipped, and both sides of every edit you made, so “FlowGenius said twenty minutes and the planner said thirty-five” is stored as a pair. We use it to learn which suggestions planners reject and why the drafts are wrong when they are wrong. We would rather tell you that than collect it quietly.

During beta, each organization can generate up to 25 drafts per day, and the counter resets at midnight UTC. It’s a safety cap. Reviewing, skipping, restoring, adjusting, and every recalculation of the arc and the outlook are free and never count toward it. Only a fresh generation does, including one you start with the Regenerate button.