Preventing repeated content across summit tracks
Each track has its own chair and its own speakers, and nobody sees the whole programme at once.
The short answer
Repeated content happens because tracks are planned separately. Prevent it with one shared topic map that lists, for every session, the question it answers and what it will not cover, and with a short brief to each speaker that names neighbouring sessions.
Check overlap at three points: when outlines are collected, when slides are due and in a short call just before the event. A repeat caught at outline stage costs a conversation; one caught on the day costs a delegate's trust.
Where repetition comes from
- Several tracks cover the same regulatory change from different angles with the same case example.
- One speaker is invited by two track chairs and gives a near-identical talk twice.
- Sponsor-supported sessions repeat the plenary theme with a product slant.
- Panel and workshop on the same topic reuse the same three slides.
- A new chair did not see last year's content and re-commissions it.
A shared topic map
Build one table with a row per session across all tracks. Each row states the audience question the session answers, the angle, the primary speaker and the boundary: what neighbouring sessions will cover instead.
Share it with every track chair before speakers are briefed. It becomes the reference when a speaker proposes drifting into another session's ground.
| Track | Session | Question it answers | Boundary (not covered here) | Speaker | Adjacent sessions |
|---|---|---|---|---|---|
| Regulation | Reporting changes | What changes for filings next quarter? | Implementation tools | Speaker A | Tools session, panel |
| Technology | Reporting tools | Which tools help meet the new filings? | What the regulation says | Speaker B | Reporting changes |
Briefing speakers
- Send each speaker the session question, the boundary and the titles of adjacent sessions.
- Ask for a one-paragraph outline and a list of examples they plan to use.
- Compare outlines in the topic map and resolve overlaps through the track chairs.
- Ask for slides by a set date and check examples again against neighbouring sessions.
- Hold a short call with chairs the week before to settle last-minute changes.
When some overlap is useful
A topic that matters to two groups can be covered twice if the angle and level differ, for example a policy view for managers and a practical view for technical staff. Label each so delegates choose knowingly.
Plenary summaries can intentionally repeat what tracks cover, but only as a short recap that points to the detail.
Who owns it
The programme owner holds the topic map and settles disputes between track chairs. The secretariat or project lead keeps it up to date and chases outlines. Track chairs own the quality of their own sessions within the map.
Worked example · Fictional example
A fictional overlap caught early
Fictional organisation and figures, for illustration only.
A fictional professional accountants' body runs three tracks. The topic map shows that both the tax track and the audit track plan a 40-minute talk on the same reporting change, each with the same fictional company example.
The programme owner asks the audit chair to shift the angle to evidence and controls, and the tax chair keeps the filing view. Each session names the other in its brief. Delegates see two distinct titles in the programme instead of two similar ones.
Use this yourself
Content overlap check
Copy this checklist and run it at outline stage, slide stage and the week before the event.
- Every session has a stated audience question and a boundary.
- No two sessions answer the same question for the same audience.
- No speaker appears in two tracks without the chairs agreeing the content differs.
- Case examples and data slides are listed and checked across tracks.
- Sponsor-supported sessions are checked against the plenary and keynote themes.
- Plenary recap points to detail rather than repeating it.
- Changes after outline stage go through the programme owner.
- Topic map updated and shared with all chairs on this date:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Two tracks with chairs who talk regularly.
- A small speaker pool that you know well.
- A programme owner who reads every outline.
Outside planning help earns its fee when
- Three or more tracks with separate committees.
- Many invited speakers and last-minute substitutions.
- The programme is built from open calls and sponsor offers that cut across topics.
Need someone to keep the topic map and chase outlines?
A conference project lead can build the shared topic map with your track chairs, collect and compare speaker outlines, run the three overlap checks and keep the programme document consistent with what speakers actually plan to present. The programme owner decides what stays. Send your draft session list and the track chairs' names.
Questions organisers ask
Is any overlap acceptable?
Yes, if the angle and level differ and the programme says so. Unplanned overlap with the same examples is the problem.
Who resolves a dispute between track chairs?
The programme owner. The topic map and each session's boundary give them a basis for the decision.
How early should speaker outlines be collected?
Early enough to change a session without losing the speaker, and before slides are drafted. Set the date in the speaker confirmation.
What about sponsor-supported sessions?
Treat them like any other session in the topic map. The programme owner confirms the angle and the boundary before the speaker is briefed.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.