A supplier event earns its place in the calendar when it helps the buyer and suppliers make progress on something they cannot resolve through routine transactions. That might mean explaining a future requirement, understanding a shared constraint or developing an idea that needs several people in the room.
The WOP archive conversation with Supplier Day's Caitlyn Lewis covers communication, event preparation, virtual participation and making decision-makers visible. This companion develops the practical planning questions around those themes. The interview's service descriptions are historical, rather than a claim about the provider's current offering.
Decide what the event needs to accomplish.
Write one clear purpose before preparing invitations. “Build relationships” is too broad to design an agenda around. A more useful purpose might be to explain a forthcoming requirement and identify which suppliers can contribute, or to agree the next stage of a supplier innovation challenge.
Describe the intended output. It could be a set of qualified ideas, an agreed action plan or a clearer understanding of supply constraints. Decide who will use that output and what decision follows. If there is no owner for the follow-up, the event risks becoming a production project with no operational destination.
Test the purpose with colleagues and a small number of relevant suppliers. Ask whether the proposed discussion is useful and what information they would need beforehand. Supplier participation has a cost. A good invitation explains why attending is worth that cost.
Choose participants for the work you want to do.
Include the people who understand the requirement and those who can make or sponsor the next decision. A buyer can ask suppliers to innovate while accidentally excluding the operational person who knows whether an idea is feasible. Conversely, a room full of senior titles can struggle to answer the detailed questions that determine implementation.
Explain the role of procurement. The team might facilitate the discussion, clarify the commercial route and make the follow-up manageable. It should also make clear where a conversation is exploratory and where a formal sourcing process will be required. Participants need a consistent understanding of what the event can commit to.
Be careful about information shared in a multi-supplier setting. Decide in advance which material is suitable for the group and which questions need separate conversations. A well-designed agenda allows useful collaboration without inviting participants to disclose commercially sensitive information inappropriately.
Give suppliers enough preparation material.
Provide the business context, the challenge and the questions the event will address. Explain any practical constraints. An organisation asking for a new operating idea should identify the systems, locations or implementation conditions the idea must accommodate.
Ask for concise preparation where it improves the session. A short response to a defined question can help the facilitator identify common issues. Avoid asking every supplier for a large generic presentation. That can turn the day into repeated sales pitches and consume the time intended for discussion.
Tell participants how outputs will be recorded and used. If ideas will be assessed afterwards, explain the route and expected timing. Suppliers should know whether they are entering an informal discussion or a process that requests further work.
Design the agenda around participation.
Use the opening to explain the purpose and context. Then move into discussion, demonstrations or focused working groups that suit the required output. Leave time to test ideas against the business constraints and identify the people needed for the next step.
Virtual sessions can widen participation and reduce travel, but they still need facilitation. Check access, audio, breakout arrangements and how questions will be collected. Give quieter participants a way to contribute. The technical setup should support the work, rather than become the main thing people remember.
Name a facilitator and a recorder for each working group. Agree what will be captured: the problem, proposed idea, assumptions, dependencies and next action. Those records make the session usable after the participants return to their ordinary workloads.
A hypothetical supplier innovation day.
Imagine a manufacturer wants to reduce packaging waste without increasing damage in transit. Procurement invites packaging suppliers, logistics colleagues and the operational owner. The preparation pack explains the current materials, damage evidence and implementation constraints.
During the session, suppliers propose alternatives and the business tests them against the distribution process. The group identifies two options for a controlled trial. The record names the trial owner, required test evidence and decision date. Procurement then manages the appropriate commercial steps with the selected participants.
The event has produced a route to a decision. A collection of positive comments from attendees would be useful feedback, but it would not demonstrate that the packaging problem has improved.
Make follow-up part of the invitation.
Agree who will consolidate the output, acknowledge contributions and progress the actions. Give each action a business owner and a date. Explain when suppliers should expect an update, including when an idea is not taken forward.
Review the event against its original purpose. Which decisions advanced? Which assumptions were clarified? What is still blocked? Use participant feedback to improve the next session, while keeping the operational outcome visible.
The Supplier Day conversation brings attention to the work required around the meeting itself. Procurement can make that work more deliberate. Start with a clear challenge, give the right people a useful reason to attend and ensure the conversation has somewhere to go afterwards.