How to plan a conference timeline on a Gantt chart
Plan a conference timeline as a Gantt chart: the venue contract, an open call for speakers, programme, sponsors, a registration period, operations and follow-up, and how to test a fixed date against your lead times.
A conference is planned around commitments that take weeks to close and cannot be hurried. This guide shows how to put them on a Gantt chart, join them at the programme and test a fixed conference date against your real lead times.
The short version
- Date nothing until the venue contract is signed, and plan the contract as a task with its own length.
- Plan open windows, such as a call for speakers or a registration period, as tasks of that length.
- Link the committee review and the final numbers to the end of the window with finish-to-finish.
- Join the streams at the programme and expect a late programme to move everything after it.
- Pin the conference days to the real date, and compare the finish date with the date you need.
Plan the long commitments first
Conference planning goes wrong at the front, not the back. The venue contract takes longer than expected, the call for speakers is opened before the date is confirmed, and sponsors are approached with a programme that does not exist yet. By the time the on-site tasks are due, the margin was spent months ago and nobody can say when.
Start with the commitments that have a length of their own: the venue contract, the call for speakers, the sponsor process and the registration period. Give each a duration in working days, and record what it waits for. Then look for the milestone where the streams meet. In most conferences that is the programme: registration, travel, orders and promotion all depend on it, so a late programme moves the whole back half of the plan.
Some tasks are windows, not work. A call for speakers is open for a set time and a registration period runs until it closes. Plan them as tasks of that length and link the tasks that depend on their end, such as the committee review or the final numbers, to the end of the window rather than to the start. A finish-to-finish link with a lag does that: the review can begin while submissions come in and finish a few days after the call closes.
The example below builds the conference template in stages. For the template with notes on each group, see /templates/conference-gantt-chart. For a single-day event, see /templates/event-planning-gantt-chart. Trade shows follow the same shape; the last stage describes the changes.
A conference plan, built in stages
Nineteen tasks in five groups. Durations are illustrative; set your own. Open the spreadsheet panel to see the rows behind each stage.
The venue gates everything
"Set concept, budget and date range" (5 working days), "Shortlist and visit venues" (8) and "Negotiate and sign venue contract" (10) follow one another, and the "Date and venue confirmed" milestone follows. That is 23 working days before anything else can be dated.
A call for speakers and a finish-to-finish review
"Open call for speakers" is 20 working days. "Programme committee reviews submissions" (10) is finish-to-finish with it, with a lag of 3, so it starts during the call and ends three days after it closes. "Invite keynote speakers" (6) runs beside them, and "Programme agreed" waits for both.
Sponsors and registration
"Sponsor prospectus and outreach" (25) and "Build registration site" (8) start at the venue milestone. "Registration period" (30) waits for "Programme agreed" and the site. "Promotion and partner emails" (30) starts two working days after registration opens.
Operations, the days and the follow-up
"AV, catering and accommodation orders" (10) follow the programme, and "Final numbers to venue and caterer" (2) wait for registration. "Run-of-show and staff briefing" (5) waits for the speakers' travel, the orders and the numbers. "Conference days" (3) also waits for the sponsor outreach, then come "Attendee survey and sponsor reports" (6) and "Close accounts and lessons learned" (4).
How it works
List the commitments with the longest lead times
Start with the venue, the call for speakers, sponsors and registration. Give each a duration in working days that reflects how long it takes you in practice, not how long you hope it takes.
Make the venue a milestone
Add a task of length 0 that follows the contract and make the call for speakers, the sponsor process and the registration site depend on it. Nothing downstream has a date until it is reached.
Plan windows as tasks and link to their end
Set the length of the call and of the registration period. Make the review finish-to-finish with the call, for example 5FF+3, and the final numbers depend on the end of registration.
Join the streams at the programme
Link registration, travel and the venue orders to the programme milestone. Switch on View, Critical path to see which chain sets the finish date.
Test the fixed date
Set a fixed Start on the conference days. If the work before it needs more time, the task is flagged with the earliest date its dependencies allow; if there is spare time, a gap shows. Compare the finish date with the date you need and shorten or overlap tasks on the critical path.
Add owners, share and export
Put the responsible person in People, share the chart with the committee, and export a PDF for sponsors or the venue.
Mistakes to avoid
Using short durations for a long contract
A venue or sponsor deal can take far longer than the example's. Use your own history; the template's lengths are illustrations.
Linking the review to the start of the call
A finish-to-start link makes the review wait until the call has closed. A finish-to-finish link with a lag lets it start earlier and still end after the last submission.
Forgetting that dates are calculated forward
The chart plans from the start of the project. A fixed date is a check on that plan: compare the finish date with the date you need.
Leaving out the follow-up
The survey, sponsor reports and closing the accounts are tasks with lengths. Keep them in the chart so the project is not finished on the last day of the event.
Open the conference Gantt chart
Open the conference template, change the lead times to yours and test your conference date against the plan.
Related guides
Frequently asked questions
How do I plan a trade show with the same method?
Keep the venue, registration and follow-up shape. Replace the call for speakers and the programme with stand design, shipping with its lead time and staffing, and make the final tasks depend on them.
How do I show a call for speakers that is open for weeks?
As a task with that length. Link the committee review to the end of the call with a finish-to-finish dependency and a lag, so the review can begin while submissions arrive.
Can I track registrations and sponsor payments in the chart?
No. QueryChart schedules the tasks and records progress as a percentage. Keep the registration numbers and sponsor payments in the systems you use for them and refer to them in task notes.
Can the chart tell me the latest date for each task?
It shows the earliest dates the dependencies allow and the critical path. Pin the conference days to the real date to see whether the plan fits, and use the critical path to see which tasks have no room.
