%20--%3e%3cpath%20d='M59.1,199.2c1.4,12.4,17,19.5,35.9,19.5s25.9-1.8,37.8-5.5l6.6,35.7c-15.9,6.2-34.7,8.6-52.6,8.6-49.8,0-77.8-28.1-77.8-75.4s24.3-80.1,73.5-80.1,64.7,31.6,64.7,75.4-.9,17.9-1.8,21.8H59.1ZM99.2,163.4c0-10.5-3.6-26.3-19.2-26.3s-20.6,15.7-21.2,26.3h40.5Z'%20fill='%23231f20'/%3e%3cpath%20d='M203.7,105l13.8,62.4c2.8,12.8,4.8,25,6.7,38.1h.9c1.8-13.6,3.7-24.8,6.3-38.1l13-62.4h54.2l-50.2,149.7h-51.7l-49.8-149.7h56.8Z'%20fill='%23231f20'/%3e%3cpath%20d='M347,199.2c1.4,12.4,17,19.5,35.9,19.5s25.9-1.8,37.8-5.5l6.6,35.7c-15.9,6.2-34.7,8.6-52.6,8.6-49.8,0-77.8-28.1-77.8-75.4s24.3-80.1,73.5-80.1,64.7,31.6,64.7,75.4-.9,17.9-1.8,21.8h-86.2ZM387,163.4c0-10.5-3.6-26.3-19.2-26.3s-20.6,15.7-21.2,26.3h40.5Z'%20fill='%23231f20'/%3e%3cpath%20d='M451.4,155c0-18.7-.6-35.8-1.2-50h45.3l2.4,18.5h.9c6.3-9,20.3-21.6,42.6-21.6,33.9,0,50.2,24.4,50.2,62.8v90h-52.6v-84.8c0-15.1-5-25.2-17-25.2s-13.6,6.1-16.2,11.9c-1.2,2.7-1.8,7.3-1.8,11.9v86.3h-52.6v-99.7Z'%20fill='%23231f20'/%3e%3cpath%20d='M672.2,63.1v41.9h30.6v38h-30.6v48c0,17.4,5.1,23.7,16.7,23.7s9.1-.5,12.4-1.1v40.2c-6.2,2-17.7,3.7-31.1,3.7s-27.7-4.8-35.7-12.5c-9.1-8.9-14-22.8-14-46.2v-55.9h-18.1v-38h18.1v-30.3l51.6-11.6Z'%20fill='%23231f20'/%3e%3cpath%20d='M773.7,49.6v205.1h-52.6V49.6h52.6Z'%20fill='%23231f20'/%3e%3cpath%20d='M964.1,291.7c-26.4-8.6-48.4-18.3-74.1-30.2-4.7-2.3-9.5-3.4-13.5-3.8-44.5-2.4-82.8-38.1-82.8-104.6s33.3-106.6,93.1-106.6,89.2,53,89.2,102.5-17.4,77.6-39.6,89.2v1.4c13.4,4.8,28.7,8.4,43.5,12.3l-15.8,39.8ZM920.6,151.3c0-36.6-12.7-62.1-35.5-62.1s-36.2,25.8-36,62.5c-.3,38.6,13.4,63.3,36,63.3s35.5-24.7,35.5-63.8Z'%20fill='%23231f20'/%3e%3c/svg%3e)
Türkçe
EnglishFeatures / Program, speakers & content
Build the program once. Keep every surface honest.
Sessions, speakers, submissions, and agenda changes live on one event record—so registration, the app, and the floor follow the program you actually approved.
How it works
Collect. Decide. Place. Prep. Publish.
Programs break when submissions, decisions, rooms, and speaker prep live in different files. This workflow keeps one program record through the five moments that decide whether the floor still matches what you approved.
Collect — Bring submissions and invited speakers into one place
Capture calls for content, invited speakers, and imported session lists without rebuilding the same spreadsheet every week. Submissions and invitations · Speaker and session basics · One inbox for what might run.
Decide — Accept, decline, or hold with a clear status
Review what came in and mark what runs — so the committee’s call is visible on the same record the schedule will use. Accept / decline / hold · Clear ownership of decisions · Status the team can trust.
Place — Put sessions into tracks, rooms, and times
Build the multi-track agenda the event will actually run: tracks, rooms, capacity, and speaker assignments on the program — not a PDF that drifts from the app. Tracks and rooms · Session placement · Capacity you can see.
Prep — Keep speaker profiles, materials, and tasks moving
Speakers need bios, materials, and open tasks without chasing five threads. Profiles on sessions · Materials and tasks · What they still owe before doors open.
Publish — Push the approved program to every surface
When something moves, registration choices, the mobile agenda, and onsite access should follow the same program — not a Hall C copy-paste. Live program on the event · App and registration stay aligned · Floor follows what you approved.
Who it serves
Program teams build. Speakers stay ready. Attendees find the truth.
Same program record. Different jobs. One source so nobody rebuilds Hall C in a spreadsheet the night before.
What you run
Submissions, sessions, moves, and publish
Four jobs on one program record — without turning this page into a site builder or a broadcast studio.
Program ops
Spreadsheet stack, or one program record?
Most teams don’t lack a list of sessions. They lack a single place where submissions, decisions, rooms, and speaker prep still mean the same program attendees open.
Spreadsheets + email + a separate schedule tool
Sheets, inboxes, and a PDF agenda.
- Source of truth: Sheets, inboxes, and a PDF agenda
- Before publish: Status buried in threads
- When something moves: Hall C updated in three places — maybe
- After doors open: “Which version is the floor using?”
One program record from submission to published agenda
One event program record.
- Source of truth: One event program record
- Before publish: Accept, place, and prep on the same spine
- When something moves: Registration, app, and onsite follow
- After doors open: “Does the floor match what we approved?” — karar zekâsı
Experience Engine
Program truth on the same journey the attendee already lived
Program, speakers & content sits inside eventIQ’s Experience Engine — beside registration, the mobile app, onsite, engagement, and insights. The agenda is not a bolted-on PDF after the fact; it reads the event you already run. Event Marketing owns sites and campaigns that promote the program. Web Studio owns branded live broadcast rooms. Data & insights owns session performance karar after the fact.
Experience Engine
The tools that shape every attendee’s journey
Registration, the mobile app, and insights share the same event this program runs on.
Walk collect → place → publish with your team
Tell us how you gather speakers today, where schedule changes break, and what still lives in spreadsheets. We’ll show how program, speakers, and content run as one record in eventIQ.