Loading...
Loading...
Flagship conference and summit websites
Give attendees one place for the programme, speakers, venue, sponsors and ticket link. Your team keeps the changing information current.
Three routes
The date decides. Most events with sponsors and a full programme take the standalone route. Take the smaller route if the event is a section of your organisation site, not a brand of its own. Take the largest one if this event runs every year.
Your organisation site is fine. Add the event pages, the programme and the ticket link inside it. Archive them after the day. This is the smallest of the three routes.
Scoped in writing after the inventory.
The event needs its own address, its own look and its own pages. It is scoped around the promotion date, and it stays up afterwards as the record. Most events with sponsors and a full programme need this route.
Scoped in writing after the inventory.
You run this event repeatedly. Each year reuses the approved structure, while its content and support receive a new written scope.
Scoped in writing after the inventory.
Who does the work
Scope
The process
After the inventory, the written scope names the content owners, approval points, support coverage and expected effort.
I list the programme, speakers, sponsors, documents, deadlines and the ticket tool. We agree the pages, approver, change process and any support coverage included in the written scope.
Output: A written scope, approval rules and any agreed support coverage, plus a content map and the list of gaps.
I set up the pages and the programme, speaker and sponsor blocks on a private preview site. I load the content you approve. I then check the dates, links, documents and accessibility of each page.
Output: A complete preview site, your sign-off on the sponsor tiers, and an acceptance checklist.
I publish after your named approver releases the pages, check the live site and hand over the accounts. We agree what happens to the pages after the event.
Output: A live site, an editor guide and a written archive plan.
Safeguards
Programmes change every week, and sometimes the date changes too. Most of the risk sits in the last fortnight. Here is what holds it down.
Questions
No. Registration, payments, discount codes, refunds, badges and check-in belong to a ticket tool. Keep the one you have. The site sends people to it, or embeds it, and the money never touches me.
I look at what you have first. Then you get the expected effort, the risks and the decision points in writing. You approve that scope before any work starts, and you can stop there. I do not put a number on a web page for work I have not seen. A number like that is wrong in both directions.
If you run one track with one ticket type, yes. A template builder with built-in tickets does that job well. Spend the difference on the event. Come to me when the programme, the sponsors and the archive outgrow a template.
Send the date first. I will tell you what fits in the time and what drops. The name, the dates, the venue and a ticket link go live first. The programme follows as your content lands. A web page cannot promise dates for content that still sits in someone's inbox.
Yes. Your named editors change speakers, sessions, rooms and times without me. We agree that list in the first step. One approver signs off changes in the last fortnight. The site then shows what the room shows.
The written scope names the async incident channel, coverage hours and fallback developer. Your editors handle routine programme changes.
Your editor publishes the approved postponement or cancellation notice. Any additional work is agreed in writing before it starts.
You do. The domain goes in your organisation's name, in an account you control. The content, the code and the accounts are yours, and I hand them over before launch. There is no lock-in and no subscription to me.
Your advisor decides which consent controls and notices apply to the chosen analytics and ticket tools. I build what they approve.
Your advisor names the accessibility duty and statement requirements. The written scope names my checks; an independent audit is separate.
We agree that before launch. Pages stay live at an address with the year in it, so this year's build never breaks last year's links. Media, speakers and sponsors keep their links. We redirect only where we must.
Send the programme outline, venue and ticket-page address. I return the smallest suitable route, the content risks and the scope questions.
Send me the event date