Programme and schedule files
PDFs, spreadsheets, agenda notes and session descriptions that can populate programme and schedule pages.
Event Growth Studio
Turn event collateral into structured, usable content
Event content intake is the preparation layer inside Event Growth Studio, not the full parent workflow or a publishing step. It converts programmes, biographies, venue documents, FAQs, partner materials and media into trusted source material for a complete digital event guide.
Structured for discovery. Assisted by AI. Approved by your team.
Conceptual workflow
Synthetic collateral intake — no customer documents.
Conceptual workflow
Conceptual workflow using synthetic Harbour Lights Festival materials only.
Source material teams can intake
Events rarely start with a perfect CMS record. Intake brings scattered material into the guide content workflow.
Biographies and profiles
Speaker, performer, host, exhibitor and partner details that can support structured pages.
Venue and visitor information
Travel notes, accessibility guidance, arrival instructions, food information, FAQs and practical audience details.
Campaign and partner assets
Launch copy, sponsor copy, media notes, imagery and promotional material that needs ownership and review.
Example: event collateral intake records
Example only: intake records describe realistic organiser material and how it may be prepared before drafting.
| Collateral received | Intake structure added | What stays human-controlled |
|---|---|---|
| PDF programme with 38 sessions and three room names. | Programme source type, session fields, room references and missing speaker notes. | Final schedule accuracy and whether each session is ready to publish. |
| Venue accessibility document from operations. | Visitor guidance source, owner, freshness note and page suggestions. | Accessibility wording, current entrance details and operational approval. |
| Sponsor logo pack and paragraph submitted by a partner. | Partner source type, rights note, approval owner and related sponsor page. | Logo usage, claims, public placement and partner sign-off. |
Collateral received
PDF programme with 38 sessions and three room names.
Intake structure added
Programme source type, session fields, room references and missing speaker notes.
What stays human-controlled
Final schedule accuracy and whether each session is ready to publish.
Collateral received
Venue accessibility document from operations.
Intake structure added
Visitor guidance source, owner, freshness note and page suggestions.
What stays human-controlled
Accessibility wording, current entrance details and operational approval.
Collateral received
Sponsor logo pack and paragraph submitted by a partner.
Intake structure added
Partner source type, rights note, approval owner and related sponsor page.
What stays human-controlled
Logo usage, claims, public placement and partner sign-off.
A content intake workflow
Intake prepares source material before it enters the source library, AI assistant or structured guide editor.
- 1
Collect the material
Bring together the files, notes and submissions the event team already uses.
- 2
Classify the source
Identify whether the material describes programme, venue, tickets, FAQs, partners, media or visitor guidance.
- 3
Record ownership
Capture who supplied the material and who should approve its use.
- 4
Check readiness
Mark missing, uncertain or stale information before it feeds drafting.
- 5
Use in page creation
Make prepared source material available for guided creation, purpose-built templates and section-level AI assistance.
Content intake is not the same as the source library
The two capabilities work together but answer different operational questions.
Content intake
- Focuses on collecting and preparing new or scattered material.
- Helps teams classify files, notes, submissions and content requests.
- Surfaces missing information before drafting begins.
Source library
- Maintains governed source records after intake.
- Tracks ownership, provenance and stale-content warnings.
- Gives reviewers a durable reference for page claims and AI-assisted drafts.
Ticket facts remain canonical elsewhere
Intake can make ticket-related facts visible to content teams, but Event Growth Studio does not become the checkout, inventory or availability authority. Ticket facts should remain read-only inputs from the authoritative system, then reviewers can confirm how they are referenced in page copy.
- Use ticket facts to inform audience guidance.
- Do not make generated copy the source of truth for prices or availability.
- Keep payments, orders and scanning outside the intake workflow.
Where intake connects into the launch-prep system
Intake is an early workflow layer that prepares the material later used across Event Growth Studio.
- Event Growth StudioSee how intake supports the complete parent content and publishing workflow.
- Guided event microsite creationPlan the page structure that prepared source material will populate.
- Event source libraryMove prepared records into a governed, traceable source layer for later reuse.
- AI event content assistantDraft section-level event content once sources are organised and ownership is clear.
Related capabilities
Explore connected Event Growth Studio workflows without leaving the creation and CMS cluster.
- Event Growth StudioCreate, manage, publish and promote a complete digital event guide from trusted facts.
- Guided event microsite creationChoose page families, sources and review steps for a dedicated digital event guide or microsite.
- Event source libraryKeep source ownership, provenance and freshness visible across the event guide and outputs.
- AI event content assistantDraft, refine and adapt event page sections while humans retain approval and publishing control.
- Event content review and approvalMove pages through draft, review, approval and publication with human sign-off.
Frequently asked questions
What types of content can be collected?+
Teams can collect programmes, PDFs, briefs, biographies, venue documents, FAQs, sponsor copy, partner materials, media assets, campaign copy and visitor information.
Does intake automatically publish content?+
No. Intake prepares material for source management, AI drafting and review. Publication still requires approved pages.
How is intake different from the source library?+
Intake collects and prepares material. The source library maintains governed records, ownership, provenance and stale warnings over time.
Can intake replace ticketing data?+
No. Ticket facts remain canonical in the ticketing source and are treated as read-only context for content work.
Prepare source material before launch pressure hits
Use intake to organise the event facts, collateral and owner context the wider Event Growth Studio workflow depends on.
Bring fragmented event content together before AI drafting, review and publishing begin.
Feed the source library, section assistant and guided microsite workflow from the same prepared material.
Keep official ticketing, event-site structure and discovery outputs grounded in approved source inputs.
Structured before drafting.
Owned before publishing.