How our recaps are made
After a conference ends, a lot of what happened is said in public, on LinkedIn, by the people who were there. A recap reads that conversation and lays it over the program, so you can see what the room talked about.
What we read
Public LinkedIn posts that mention the event by name, from two weeks before it starts to three weeks after it ends. We read them twice: a week after the event, and again three weeks after. We don’t read private posts, messages or comments.
How we sort it
AI assistants read every post first. Posts that aren’t about the event are left out. Each remaining post is tagged with the topics it discusses, the sessions it mentions, and the kind of organization the author works for, such as a sponsor, a CRO or a site. A person on our team reviews every recap, and can correct any post, before it’s published.
What we count
We show counts, not percentages: how many posts mentioned a topic or a session, and how many reactions and comments posts drew. A post can mention more than one topic, so topic counts can add up to more than the number of posts. Ratings and check-ins come from Clinical Trial Events members.
Full recaps and highlights
When an event has 25 or more posts about it, we publish a full recap with charts. With fewer, we publish highlights: the posts themselves, the sessions people mentioned, and photos, without charts, because a chart of a handful of posts would mislead.
What we don’t do
We don’t rank events against each other in a recap. We don’t name or quote anyone in a recap’s summary except the event’s speakers. We don’t store LinkedIn profile photos.
Photos
Photos are copies of images people posted publicly. Each one links to the post it came from. If a post is deleted from LinkedIn, its photos come off our site.
Removing a post
If one of your posts is in a recap and you’d rather it weren’t, use “Request removal” under it, or the form at /posts/removal. We hide it right away, and we won’t collect it again. You don’t need an account.