Every year, the Red Hat Summit review committee evaluates roughly 1,500 proposals to build a catalog of around 350 sessions.
You may be wondering: What distinguishes a successful abstract from one that falls flat? Accepted proposals typically feature practical, real-world troubleshooting over high-level marketing.
Attendees travel to Red Hat Summit to connect with peers, explore technical realities, and learn how other teams solve complex architectural challenges. They want to know what worked, what unexpected hurdles surfaced, and how the presenting team engineered a solution.
If you're hoping to take the stage at Red Hat Summit 2027, your abstract needs to show reviewers that your session delivers genuine technical substance combined with real-world experience.
7 steps to build a compelling proposal
Before writing your abstract, take some time to set up a solid foundation to build on:
- Choose the right session type: A 40-minute breakout session is one way to share your story, but if you have a targeted tool, configuration, or architectural pattern, a 20-minute lightning talk might be a better way to deliver fast, concentrated value. If you want a number of Red Hat and other industry experts to participate in an interactive discussion, a 60-minute panel is your best bet. For a tech-heavy session where attendees will roll up their sleeves and work in real environments, you should propose a 90-minute hands-on lab. Learn more about session types here.
- Confirm speakers and your Red Hat sponsor early: You may submit up to 5 proposals. If you're submitting as a customer or partner, make sure you have a designated Red Hat sponsor for the session. Submitting a proposal that includes multiple speakers? Confirm their participation well in advance so they'll be able to present in person in Boston.
- Aim deep rather than broad: Red Hat Summit attendees are experienced practitioners looking for technical depth. Proposal review teams consistently favor intermediate and advanced deep dives over high-level introductory overviews.
- Review hands-on lab requirements: If your proposed lab uses AI, it must use approved Model-as-a-Service (MaaS) options available on the Red Hat Demo Platform or include a clear technical justification for dedicated GPU access.
- Show what really happened: Enterprise IT projects rarely go according to plan. Reviewers want honest stories that explain the setbacks you faced, the compromises you made, and how your team cleared technical roadblocks.
- Focus on engineering, not sales: Keep the spotlight on architecture, open source technologies, and repeatable operational workflows. Focus on what practitioners can learn from your implementation.
- Craft a compelling title: Grab your audience’s attention with actionable, quantifiable results rather than vague, high-level marketing language. Use clear, punchy phrasing that immediately communicates the practical value, specific technical breakthroughs, or measurable efficiency gains attendees will take away from your session.
The 5 questions your abstract must answer
Review teams evaluate your proposal solely on what is on the page. To stand out, make sure your abstract directly addresses these 5 key questions:
1. Who is in the room?
Name your target audience. Skip broad labels like "anyone working in tech." List the exact roles you want to reach, such as platform engineers, Kubernetes administrators, security architects, or systems leads. State the required background knowledge upfront so attendees know right away if the session fits their experience level.
2. What technology is running?
Identify the exact platforms, open source projects, and architectural environments involved. Always use complete, official product names—such as Red Hat OpenShift, Red Hat Ansible Automation Platform, or Red Hat Enterprise Linux—rather than shorthand or outdated product names.
3. What concrete problem did you solve?
Anchor your proposal in an operational challenge. Are you migrating 2,000 virtual machines off proprietary hypervisors? Are you configuring hermetic, distroless container builds to minimize security vulnerabilities? Give reviewers the exact scope and architectural context.
4. How will you keep the session engaging?
Red Hat Summit sessions should be dynamic learning experiences. How will you bring your content to life? Will you conduct live terminal demonstrations, walk through detailed topology diagrams, or facilitate open audience Q&A? For hands-on labs, outline the specific exercises attendees will run on their own workstations.
5. What can attendees use right away?
Spell out the specific skills, steps, or setups attendees can put to work in their daily operations. Focus on clear, measurable results—such as cutting down network rebuild times, stopping configuration drift across hybrid cloud clusters, or securing container supply chains.
Why reviewers value real-world challenges
Practitioners learn the most from real stories about running into and solving technical problems. When a session description glosses over the rough patches, it misses an opportunity to connect with peers facing similar challenges.
- Establish the operational constraints: Describe your starting point—whether legacy systems, regulatory compliance requirements, or distributed edge footprints.
- Highlight the architectural pivots: Be transparent about the approaches that didn't scale, the bottlenecks you uncovered, and the assumptions you had to revisit.
- Demonstrate the resolution: Detail the automation workflows, architectural adjustments, and troubleshooting steps that led to a successful outcome.
A talk titled, "How we overcame migration bottlenecks and cut downtime by 80%" immediately signals practical value over an abstract titled, "A modern approach to enterprise virtualization."
Ready to send in your proposal?
The call for proposals for Red Hat Summit 2027 in Boston, MA is open until November 30, 2026, at 11:59 PM PT.
Explore the CFP guide to check out past examples of successful proposals and review the abstract guidelines.
Refine your draft, share it with a colleague for feedback, and submit your session through theRed Hat Summit CFP portal. If you have questions about submission requirements or session formats, contact the speaker management team at rh-summit-presenters@itagroup.com.












