For the block that decides the registration
Guests scan the agenda to work out whether an hour is worth their evening. Here is how to write chapters with durations and a takeaway each, so the block answers them in one pass.
The first pass is a judgement of length and shape: is this an hour of someone talking, or does something happen? The second is a search for the part that concerns the reader personally, which is why a vague chapter wastes the only block a visitor genuinely studies. An agenda answers the question the description raises, and a good one makes the title credible in a way the biography cannot.
The product builds an agenda as chapters, each with its own duration and its own takeaways. That structure is not decoration: a chapter is a promise with a number of minutes against it, which is exactly what a registrant is trying to assess. Write them that way and the block reads like a plan rather than a list of subjects.
One session, laid out with durations and a takeaway line against each chapter.
Where a night rota actually breaks. The two handover points that cause most of the arguments on a ward, named by the time of day they happen.
The last nine months, honestly. What Marek Novák changed on his own rotas, what the staff noticed first, and the one change he would undo.
Building next month on screen. A live pass through the ward template, from the unfilled Friday column to the published version, with the checks in between.
Your rotas, your questions. Bring one you are arguing about; the takeaway is a shape you can copy for the next cycle.
A thing, not a category. Building next month beats a word like overview, and a reader scanning four lines should be able to picture each one. Nouns and verbs survive a skim; abstractions do not.
The number you can actually hold on the night. Rounds of five minutes read as planned; twenty-three minutes reads as guessed. Sum them and the total should equal the length you promised in the description, or the page contradicts itself.
One line saying what the reader has afterwards rather than what they watched. Named handover points, a shape they can copy, the checks in order. This is also the honest place to put what the session will let them do, since that sentence is not rendered anywhere else on the page.
An agenda overpromises in two ways and both cost registrations later. First, the chapter that cannot survive being cut: every plan has an hour's worth of material in it and forty-five minutes' worth of things that could go, so mark the chapter you would drop if you ran long. Second, the chapter describing a tool you do not have. A discussion block is fine because that is what happens on your own session; a line promising a poll, a live question board or notes published afterwards is a promise the page cannot keep.
The good news about getting it wrong is that it is cheap to fix. The block stays editable while the address holds, so a chapter you cut on the night never needs reprinting, and a session that ran long can be described accurately before the next one is announced.
How it works
Decide the one thing a registrant should do or take away, then work backwards. The last chapter is that thing, and everything before it exists to get them there.
Rough durations against each. If it splits into two long blocks, you have an outline rather than an agenda; split again until each has a single takeaway.
What the reader has afterwards. Cut the sentence that only describes what they will watch, and check the minutes total to the length in your description.
Publish the agenda before the invitations go out, mark your cut-down chapter, and run the session against it rather than against memory.
Questions
Yes, and that is the point of the block. The chapters sit on the registration page with their durations and takeaways, so the decision about whether the hour is worth their evening is made with the plan in front of them rather than after it.
Four is the shape most hour-long sessions take, with the last one held for discussion. Three reads thin for a promised hour; six stops being a plan and starts being a list, which is the opposite of what a scanning reader is looking for.
You can edit the page and the link stays the same, so the next person to open it reads the current version. Registrants are told the joining details by email; if a change is significant enough to matter to them, say so in the reminder you send rather than letting the page do the work.
If two or more people present, yes — a chapter that says whose it is makes both biographies useful and stops the room wondering whether the handover was a mistake. With one speaker it is noise, and the speaker section already covers it.
The confirmation is for the time and the way in, and it carries a calendar file with it. Put the agenda on the page, where people weigh it before registering, and send them back to the link in your reminders if the running order is the reason they came.
Get Started
An agenda is the block that answers whether the hour has a shape. Write it in promises a stranger can scan and the registration takes care of itself.
