Crafting Compelling Session Abstracts: Your Guide to FabCon & SQLCon Success

The Call for Content for FabCon & SQLCon Europe 2026 opens on February 17th, and with hundreds of submissions expected, your session title and abstract need to work harder than ever to stand out. Drawing from years of experience and feedback from successful speakers, here's your comprehensive guide to crafting submissions that get noticed and accepted.

The Critical Timeline

Mark your calendars: Workshop submissions open February 17th and close March 23rd, while Breakout Session submissions run from February 17th through April 17th. The conference itself takes place September 28 - October 1, 2026, in Barcelona. This generous timeline gives you ample opportunity to refine your proposals, but don't wait until the last minute—early submissions often receive more thoughtful review.

The Title: Your First Impression

Your title is the gateway to your session. It needs to immediately answer the attendee's question: "What's in it for me?" Think about what will make someone stop scrolling and click to learn more.

Focus on outcomes, not just topics. Instead of "Introduction to Power BI," consider "Creating Compelling Dashboards That Drive Business Decisions." Rather than "SQL Server Performance Tuning," try "Cutting Costs by Optimizing Your Database Performance by 40%."

Be specific but not overwhelming. Your title should give a clear sense of what attendees will learn without trying to cover everything about a product. "Learn Power BI" is too broad for a 60-minute session, but "Mastering DAX for Complex Calculations in Power BI" sets clear expectations.

Skip the gimmicks unless they serve a purpose. While humor and wordplay can work, they shouldn't come at the expense of clarity. A dad joke title might get a chuckle, but if attendees don't understand what your session covers, they won't attend—and reviewers might question your clarity of thought.

The Abstract: Three Essential Components

A strong abstract follows a simple formula: problem, solution, and learning outcomes. This structure helps reviewers understand your session's value and helps attendees decide if it's right for them.

Define the Problem

Start by establishing why this topic matters. Are attendees struggling with performance issues? Do they lack knowledge about a new feature? Are they looking to modernize their infrastructure? Frame the problem in terms your audience will recognize.

For example: "Many organizations struggle with slow report generation in Power BI, leading to frustrated users and delayed decision-making." This immediately resonates with anyone who's experienced this pain point.

Introduce the Solution

Once you've established the problem, present your solution. This is where you showcase your expertise and the value you'll provide. Explain the approach, methodology, or technology you'll cover.

Continuing the example: "This session demonstrates how to leverage DirectQuery mode and optimize data models to reduce report load times by up to 70%."

Describe Learning Outcomes

Finally, be specific about what attendees will learn. Will they gain a new skill? Understand a concept? Leave with a practical implementation plan? Set clear expectations about the session's depth and breadth.

"Attendees will learn when to use DirectQuery versus Import mode, how to structure data models for optimal performance, and practical techniques for monitoring and troubleshooting slow reports."

Technical Considerations

Acronyms and terminology: Always spell out acronyms on first use. Not everyone knows what DAX, T-SQL, or PaaS means, and you don't want to exclude potential attendees or confuse reviewers.

Buzzword balance: While industry terms are sometimes necessary, overloading your abstract with jargon can make it feel generic or inaccessible. Focus on clear, specific language that demonstrates your expertise without relying on buzzwords.

Level accuracy: Be honest about your session's difficulty level. An abstract describing basic concepts shouldn't be marked as advanced, and vice versa. Reviewers check for this alignment, and mismatched levels can lead to rejection.

The Final Polish

Before submitting, run your abstract through several quality checks:

Human review: Have a colleague—preferably someone both technical and non-technical—read your abstract. Can they understand what you're presenting? Does it sound engaging?

Grammar and spelling: While minor errors are understandable, your abstract should demonstrate clear communication skills. Reviewers need to trust that you can effectively present to an audience.

Character count: Most conferences have strict limits. If you're over, use tools like Copilot to help tighten your language. Try prompts like "make it more precise" to reduce word count without losing meaning.

Track alignment: Review the topic definitions provided by the conference organizers. Ensure your session fits the track you've selected and follows any specific guidelines for that category.

Common Pitfalls to Avoid

Don't include your name if the review process is blind. This seems obvious but happens frequently.

Don't submit to every track. Be strategic about where your session fits best. Multiple submissions to different tracks for the same content can appear spammy to reviewers.

Don't demand immediate feedback if your session isn't accepted. Conference organizers receive hundreds of submissions and provide feedback when they can. A polite follow-up after a reasonable time is fine, but respect their decision either way.

Don't use AI to write your entire abstract. While AI tools can help with editing and refinement, reviewers can often spot completely AI-generated content. Your abstract should reflect your voice and expertise.

The 60-Minute Reality Check

Be realistic about what you can cover in your allotted time. A 60-minute session allows for introduction, content delivery, and Q&A, but not comprehensive coverage of complex topics. If your abstract promises to teach everything about a subject, reviewers will question whether you understand the time constraints.

Instead, focus on depth over breadth. It's better to cover three key concepts thoroughly than to skim the surface of ten topics. This approach also makes for a more engaging session and better learning outcomes for attendees.

Making Your Submission Count

The competition for speaking slots at major conferences is fierce, but a well-crafted abstract significantly improves your chances. Remember that reviewers are looking for sessions that will provide value to attendees, showcase expertise, and fit the conference's overall themes and goals.

Take time to refine your proposals, seek feedback, and ensure every word serves a purpose. Your effort in crafting a strong submission will pay off whether you're selected to speak or not—the process of distilling your knowledge into a clear, compelling abstract makes you a better communicator and presenter.

Good luck with your submissions, and we hope to see you in Barcelona for FabCon & SQLCon Europe 2026!