Call for Workshop and Tutorial Proposals
This page summarizes how researchers and practitioners can prepare proposals for workshops, tutorials, and related focused sessions within the symposium program. The goal is to help prospective organizers shape a clear, technically relevant, and feasible event concept that fits the broader wireless communications agenda of the conference.
Workshops and tutorials are typically meant to complement the main technical tracks by giving space to emerging topics, deeper technical discussion, hands-on learning, or interdisciplinary viewpoints. A strong proposal usually explains why the topic matters now, who the intended audience is, and how the session will add value beyond the regular paper program. Because this is a conference information page rather than an official submission portal, the guidance below is general and should be matched with the current call text and organizer instructions on the relevant conference pages.
What a strong proposal usually includes
Organizers of a workshop or tutorial should present a focused theme, a clear rationale, and a realistic plan for delivering the session. The proposal is more persuasive when it shows that the topic is specific enough to attract a defined audience, yet broad enough to support a useful program.
- A concise title that reflects the topic and format.
- A short description of the technical scope and expected audience.
- The motivation for the session and its relation to current research or practice.
- Proposed structure, such as keynote-style talks, paper presentations, demonstrations, or discussion blocks.
- Information about the organizers and their relevant experience.
For tutorial proposals, it also helps to specify whether the session is introductory, intermediate, or advanced, and whether it is intended for academic researchers, industry engineers, students, or mixed participants.
How to frame the technical scope
Scope is often the first thing reviewers evaluate. A proposal that is too broad may be difficult to schedule and hard to market, while one that is too narrow may not attract enough interest. The best balance is usually a topic with a clear technical center and enough depth for a substantial session.
When framing scope, explain the link between the theme and the symposium’s wireless communications focus. For example, a session might address new signal processing methods, network intelligence, spectrum management, testbeds, or system-level integration. The emphasis should stay on technical substance, not promotional language.
Review and organization considerations
Conference organizers often look for practical signs that a session can be delivered well. That includes a coherent agenda, realistic timing, and a plan for bringing in knowledgeable speakers or contributors. If the session involves papers, the proposal should explain how submissions will be selected and reviewed. If it is tutorial-based, the outline should show how the material will be paced for the intended audience.
Useful elements to mention include:
- Expected number of contributions or speakers.
- Whether the session is half-day or full-day, if such formats are allowed.
- Any planned interactive elements, such as Q&A or panel discussion.
- How the organizers will maintain topical relevance and quality.
It is also wise to avoid overpromising. A proposal should be ambitious but feasible, with a structure that matches the resources available to the organizers.
How to check your proposal before submission
Before submitting, review the proposal carefully from both a technical and an administrative perspective. The following checks can reduce avoidable problems:
- Make sure the title and abstract describe the same topic.
- Check that the target audience is clearly identified.
- Confirm that the session goals are specific and measurable in plain terms.
- Read the conference instructions for format, deadlines, and required fields.
- Verify that all organizer names, affiliations, and contact details are current if the submission form asks for them.
When possible, ask a colleague to read the proposal as a first-time attendee would. If the topic is hard to understand in one pass, it may need a clearer explanation.
Questions and answers
What is the difference between a workshop and a tutorial?
A workshop usually centers on discussion, emerging research, and paper contributions around a focused theme. A tutorial is more instructional and aims to teach methods, tools, standards, or concepts in a structured way.
Should the proposal be broad or highly specialized?
It should be specialized enough to have a clear identity, but not so narrow that it cannot draw a meaningful audience. The best proposals usually define a specific technical problem area with enough room for several contributions or teaching points.
Do organizers need to explain the audience?
Yes. A good proposal identifies who will benefit most, such as researchers, PhD students, engineers, standardization participants, or practitioners working on implementation.
Can a proposal cover an emerging topic?
Yes, and emerging topics are often a strong fit for workshops or tutorials. The proposal should, however, explain why the topic is timely and what makes it relevant to the symposium community.
What should be avoided in the proposal text?
Avoid vague claims, unrelated marketing language, and unsupported promises about impact. The text should stay focused on the technical theme, session format, and practical value for attendees.
For related conference information, you can also review the pages on program structure, co-located workshops, technical tutorials, and special sessions.
