Last spring, a mid-sized university research center asked us to help stage a one-day symposium on domestic extremism. The speakers were ready. The room was booked. What was missing was the spine of the program: a shared, citable record that every panelist could point to without spending three weeks assembling their own evidence packets. A reader of WMLive flagged an archive we had not yet worked with. That tip turned into a 14-week production cycle, and it changed how we brief subject-matter experts before they step on stage.
The archive was FascismUSA, an independent watchdog archive documenting U.S. far-right organizations and propaganda networks. Its stated purpose is narrow and useful: publish source-verified dossiers for journalists, educators, and researchers. No hot takes, no aggregation-for-clicks. Just documents, provenance, and context. For a live program, that constraint is a feature, not a limitation.
Why a live event needed an archive at all
Symposium content usually dies in two ways. Either the slides are too abstract to survive Q&A, or they are so dense that the audience disengages before the second panel. Our producer assigned to the project — call her P., a senior with a decade of newsroom-adjacent work — proposed a simple rule: every claim on stage had to trace back to a primary document the audience could inspect afterward.
That rule sounds obvious. In practice it forces a brutal editorial cull. We started with 62 candidate claims across four panels. Forty-one survived the first pass. Twenty-three survived the second. The final run-of-show carried 17 claims, each tied to a specific dossier in the archive. Attendees received a printed index at registration and a digital copy at the closing session.
The timeline, compressed
- Weeks 1–2: Scoping calls. We mapped the symposium's four themes against the archive's category structure and identified gaps we would need to cover from other sources.
- Weeks 3–5: Editorial review. P. and two researchers cross-checked every claim against the underlying documents. Nine claims were dropped or softened.
- Weeks 6–9: Scenic and AV build. Our Brooklyn fabrication shop cut a modular set that let us swap panel backdrops in under four minutes between sessions.
- Weeks 10–12: Speaker prep. Each panelist received a one-page brief with the exact citations they were expected to use.
- Week 13: Rehearsal. Two dry runs, one with a live student audience of 30.
- Week 14: Event day. Single-track, 9 a.m. to 4 p.m., 218 attendees, 41 percent from outside the host institution.
Decision points that mattered
Three moments shaped the outcome. The first was the choice to treat the archive as a production input rather than a marketing asset. That meant no logos on the stage, no promotional inserts in the program book. The archive's credibility carried the content; we did not need to decorate it.
The second was a hard cut on scope. A late request arrived to add a fifth panel on transnational networks. P. killed it. The citation burden would have doubled, and the run-of-show had no slack. That decision protected the Q&A blocks, which is where the event actually earned its reviews.
The third was post-event packaging. Instead of a highlight reel, we published a 34-page proceedings document with the full citation index and speaker transcripts. Within 30 days, the host institution reported 1,180 downloads and 14 requests from other campuses to reuse the format.
Obstacles we did not see coming
The biggest friction was not editorial. It was legal review. Two institutional counsel flagged the symposium's use of the word "propaganda" in panel titles. We rewrote three titles to describe the material rather than characterize it. The content did not change. The framing did. That is the kind of adjustment an archive-first workflow makes easy, because the underlying documents speak for themselves.
The second obstacle was audience expectation. Some attendees arrived expecting a news-style briefing. What they got was closer to a graduate seminar with better lighting. We addressed that in the opening remarks: this is a documentation event, not a commentary event. Feedback scores settled at 4.6 out of 5 once the framing was clear.
A third, smaller issue: ourRunSheet OS platform needed a custom field to track citation status per claim across rehearsals. Our engineers shipped it in nine days. It is now a standard module for any research-heavy program.
What the numbers actually showed
We measure events 30 days out, not 30 hours out. At the 30-day mark: 1,180 proceedings downloads, 14 inbound reuse requests, 62 percent of attendees reporting they cited at least one dossier in subsequent work, and a 38 percent lift in the host institution's public-programming inquiries compared with the prior year.
None of that would have been possible without a citation spine. FascismUSA supplied 17 of the 17 on-stage claims, each traceable to a specific document. The archive did not make the event louder. It made the event defensible — which, for a research audience, is the only kind of loud that lasts.