Before you book the ticket, work out whether this conference is worth going to.

A conference programme is written to sell tickets, but read the way an editor would, it also tells you who is actually being invited to speak and why. Session titles that name a specific problem and a specific method, "How we cut deployment time from six hours to forty minutes", usually mean someone with hands-on experience wrote the abstract themselves. Titles built from marketing nouns are the clearer sign that whoever wrote the session did not go through the call for papers (CFP), the open process by which organisers invite and select talks. They wrote a sponsorship deliverable instead.

What a speaker bio does and does not tell you

A full bio names the speaker's actual role, the organisation they hold it at, and something concrete they have done. A bio limited to a job title and a company name, with no project and no specific claim attached, is often filler: someone the organiser needed to put against a slot. Check whether several speakers list the same employer across unrelated sessions. One or two is ordinary sponsorship. Five or six on a programme of thirty suggests the track was built around who paid.

What the track structure reveals

A programme with a clearly labelled sponsor track or partner session is being straightforward about which content is paid placement, and that is not automatically a problem provided you can tell which sessions those are before you plan your day. A programme where every track looks identical in format, and only the fine print of a sponsor prospectus reveals which slots were sold, is not built for you to make that judgement. Some conferences also depend on a corridor track: unscheduled conversation that happens because delegates are in the same building at the same time. A multi-track programme packed with no gaps between sessions is usually a sign the organiser has not planned for that time to exist.

The ratio worth checking

Look at the proportion of sessions that are clearly a vendor demonstrating its own product against sessions built around a problem, a method or independent research. There is no fixed threshold that makes a programme worth attending, but a programme where more than a third of sessions read as product pitches is telling you where the organiser's revenue actually comes from, and it is not solely your ticket. For how organisers build a programme from the other side of that decision, see Designing a Conference Programme, and for how speakers are actually selected rather than sold a slot, see Finding, Choosing and Looking After Speakers.

The ticket price is usually the smallest number in the calculation. A conference that costs £400 to attend can easily cost two or three times that once you add travel, a hotel room if the event runs more than a day, and meals away from your normal routine, so the figure worth working from is the total.

The days out of the office are a cost too

Two or three days away from your desk is not free time the conference has given you. It is time that would otherwise have gone on the work in front of you, and someone, either you or a colleague, absorbs that gap while you are away. Weigh this properly: what would those days have produced if spent on the thing you are currently behind on, and does the conference content justify displacing it?

Ignore what you have already paid

Once a ticket is booked, there is a pull to attend regardless of whether the programme still looks worthwhile, because pulling out feels like wasting the money already spent. That money is spent either way. The only question worth asking on the morning you are deciding whether to go is whether the next two days are the best use of your time now.

Compare against the realistic alternative

The honest comparison is not conference versus doing nothing. It is conference versus the specific piece of work, meeting, or project time that would otherwise fill those days, and whether the sessions on offer are likely to teach you something that work would not. If the programme is thin on substance, a point covered in Is This Conference Worth Going To?, the comparison tips quickly toward staying at your desk.

If your employer is paying, the same arithmetic still applies, because their money and your time are both being spent, and a case built on the total cost is a stronger one to put to a manager. See How to Get Your Employer to Pay for a Conference for how to frame that request, and How to Actually Get Value From a Conference for what to do once you have decided the trade-off is worth it.

The sessions on stage are the part of a conference you can judge before you arrive: read the programme, check who is speaking, work out whether the content is curated or paid for. The part you cannot judge the same way is what happens in the gaps between sessions, over lunch, and in the queue for coffee. That is where a problem gets solved by finding the person who has already solved it, where a supplier relationship starts, and where you pick up something nobody put on a slide. Organisers call this the corridor track: the unscheduled conversation that happens because a room full of relevant people is in the same building for a day. It has no speaker and no agenda, and for a lot of attendees it is the reason the ticket was worth the money.

How a programme either makes room for this or squeezes it out

A conference built around the corridor track leaves long enough breaks, usually 30 to 45 minutes between sessions, and puts catering somewhere people have to walk through and can stand around in. Lunch is served at fixed tables or in one shared space. Check the published timings before you book: back-to-back 45-minute sessions with 10-minute changeovers all day is a schedule built to maximise the number of slots sold.

Signals the corridor has been squeezed out

• Breaks under 15 minutes between sessions, all day
• Catering served at desks or in a room away from the main circulation space
• Lunch split into several sittings with no shared window
• A single track with no gaps, so the only choice on offer is which talk to sit through

None of these on its own ruins a conference, but together they describe an event built around filling a room for a set number of hours.

What to do with this before you register

Ask for the detailed timetable before you commit the ticket price and the days out of the office. If the organiser cannot or will not give you break lengths and catering arrangements, treat that as an answer in itself. For weighing the full cost of attending against what you are likely to get from the day, including this part of it, see How to Actually Get Value From a Conference. If you are the one drawing up the schedule, the same trade-off runs the other way: see Designing a Conference Programme for how break length and catering layout get weighed against session count.