FORKCAST BOOKING GUIDE
How to check a London tech event before you book
An event can suit your interests and still leave practical questions unanswered. Before booking, check five things separately: how you get in, what happens when, which sessions matter to you, when you can meet people, and what food is actually promised. Keep the organiser's page open as you work through the checklist.
Sources checked:
Check the ticket and your booking status
Look for an explicit admission price for the ticket you can use. Read any eligibility restrictions, approval requirement and ticket conditions. If no price is visible, record entry as unconfirmed rather than assuming it is free. Food and admission are separate checks.
After registering, read the status carefully. On Luma, an application awaiting approval or a waitlist place is not a confirmed spot. Check for confirmation before treating the event as a firm plan. Luma registration guidance
Read the timetable before planning your journey
Check the date, London location and displayed timezone. Separate doors opening from the first session. Find the finish time in the agenda and compare it with the event summary. If they differ, keep the finish marked unresolved until the organiser clarifies it; do not choose whichever time makes the event sound better.
Check whether the venue is public or disclosed after acceptance. A neighbourhood is not an exact address. Reopen the original listing before travelling to catch changes to location, schedule or access.
Choose talks by the question you want answered
Write down what you hope to learn. Then look for a session whose description addresses that question. Check whether it is a talk, panel, demonstration or workshop, whether a level or prerequisite is stated, and whether there is time for questions.
A named speaker and a specific topic make relevance easier to judge. They do not prove that a session will be useful to you. If the agenda or speakers are still unannounced, say so in your own plan instead of filling the gap with the event's broad theme. With parallel tracks, check that the sessions you want do not overlap.
Count only the networking time the programme identifies
Find intervals explicitly set aside for meeting people. Use published start and end times; a following session can provide an endpoint. If no endpoint is available, the duration is unconfirmed. Do not subtract talks from the whole event and call the remainder networking: that remainder may include queues, breaks and travel between rooms.
Treat a block combining food, drinks and networking as shared time. It gives you a scheduled opportunity, not a promise of uninterrupted conversation. An agenda alone cannot establish how much actual networking you will do.
Look for an explicit food statement
Find wording that identifies what is provided and when. Keep pizza, snacks and a full meal distinct. Drinks or unspecified refreshments leave food unconfirmed; a lunch break may simply leave time to find lunch. Check whether catering is included in your ticket, restricted to a separate session or subject to additional conditions.
If dietary suitability matters, look for explicit provision rather than inferring it from the menu name or a registration question. Where the information is missing, record that uncertainty and plan accordingly. An organiser's promise before the event is different from an attendee's report afterwards.
A real listing can answer one question and leave another open
The London AI Hub / AI for Growth listing for (now past), checked on , names pizza and requires host approval. Its time summary finishes at 20:00, while its agenda closes at 20:30. Those facts can coexist: food is announced, admission still depends on acceptance, and networking duration remains unresolved. The checked page does not explicitly confirm free entry or whether pizza is included at no extra cost. The event has taken place, so the listing is a worked example only and its current wording may differ. Official listing
Your final check
- Entry: price, eligibility and registration status understood.
- Agenda: date, location, timezone and conflicting times checked.
- Talks: a session matches your question; unknowns remain visible.
- Networking: an explicit interval identified, with uncertainty retained.
- Food: provision, cost and dietary details checked separately.
Use Forkcast to find an event, then open its original source to confirm the details that affect your decision. Browse events · How Forkcast verifies events