Home
Method

The method

A programme is built by decisions, not by luck.

The method runs from the first conversation to the last review. It is written for committees and company teams that need a shared picture of the work, not a long list of activities.

Strategic planning

What is this gathering for, and who must be in the room?

Write the purpose in one sentence that a busy committee member can repeat. Name the audience, the outcome and the constraint that cannot move. If the group cannot agree on the sentence, the programme is not ready to be designed.

Watch for

A purpose that describes the event format rather than the change it should produce.

Output

A one page programme brief with audience, outcome and fixed constraints.

Where it connects

The format desk sets the scope this phase must support.

Budget

What are we committing to, and what is still unknown?

Build the budget from the programme, not from last year's spreadsheet. Separate committed costs, probable costs and open items. Put the venue, production, catering, travel and contingency on the same page so the committee can see the shape of the whole commitment.

Watch for

A contingency line that exists only in conversation.

Output

A live budget with named owners and a visible list of unknowns.

Where it connects

The format desk sets the scope this phase must support.

Marketing

Why would this person give us a day of their attention?

The invitation should lead with the reason to attend and the work the visitor will leave with. Channels matter less than clarity. Agree the message, the proof you can honestly offer and the point at which registration opens.

Watch for

Copy that describes the organisation before it describes the visitor.

Output

A message frame, a launch sequence and a registration route.

Where it connects

The brief builder records the decisions as you make them.

Logistics

How do people, equipment and information move through the day?

Map arrival, registration, session changeovers, catering, press access, accessibility needs and departure. Every route should be walked by someone who has not designed it. The aim is not a perfect plan but a plan with fewer surprises.

Watch for

A registration desk that sits on the only route into the room.

Output

A movement plan, a supplier schedule and a site walk note.

Where it connects

The brief builder records the decisions as you make them.

Execution

Who is doing what, at what time, and how will we know?

The run of show is a working document, not a ceremonial one. It should be readable by the venue, the production team and the chair. Include the cues, the owners and the decision point for each segment. Rehearse the moments that cannot be recovered if they fail.

Watch for

A schedule that only the event manager can interpret.

Output

A single run of show with cues, owners and escalation contacts.

Where it connects

The brief builder records the decisions as you make them.

Networking

Where will strangers have a reason to speak to each other?

Networking is a design decision. It needs a place, a prompt and a time. A reception after a long day is not the same as a structured exchange between sessions. Give people something to do together, not only somewhere to stand.

Watch for

A room full of people holding a drink and looking for the exit.

Output

A networking plan with hosts, prompts and room layouts.

Where it connects

The room setup note explains how layout shapes contact.

Crisis readiness

What happens if the plan stops working?

Agree the escalation path before the event. Who can close a room, move a session or cancel a segment? Where does the team gather? Who speaks to the venue, the speakers and the audience? A short, tested protocol is worth more than a long document nobody has read.

Watch for

No named decision maker once the event has started.

Output

A one page response protocol with roles and contact routes.

Where it connects

The brief builder records the decisions as you make them.

Post event review

What did we learn that the next team should not have to relearn?

Collect the decisions, not just the ratings. Review the programme against the brief, the budget against the commitments and the room against the behaviour it produced. Record the changes you will make and give each one an owner.

Watch for

A review that produces a file but no change.

Output

A short decision record with named owners for the next edition.

Where it connects

The review note expands this step.

Using the method with a committee

A committee does not need to see every document. It needs to see the decisions that belong to it. Present the phase, the open question and the consequence of leaving it open. Ask for a decision, not for a review of the whole plan.

For a small gathering, several phases may sit in one meeting. For a large conference, each phase may need its own owner. The order stays the same either way. Skipping a phase does not remove the decision. It only moves it later, usually into the week of the event.

What to bring to each review

The current brief and the outcome it names
The budget with committed, probable and open items
The run of show, even if it is still a draft
A short list of decisions required from the room

If the committee is new to the work, start with the format desk. The format sets the scope that the method has to carry.

Industry desk

Reference shelf for programme planning

Associations, standards bodies and trade publications that inform the method. Each source is independent of Event Solutions.

These independent sources are listed for orientation. They are not clients, partners or endorsements.

PCMAAssociation Meeting Professionals InternationalAssociation IAEEExhibitions CventTechnology MeetingsNetPublication Event MarketerPublication Events Industry CouncilStandards Skift MeetingsPublication EventbriteTechnology Event Industry NewsPublication BizBashPublication Exhibition WorldPublication