Event planning guides
Richmond client workshops with clear deliverables
Prepare a Richmond client workshop by agreeing what participants will produce and what remains outside the session. A clear deliverable makes room time useful and reduces competing expectations.
What you'll learn
- Confirm who can decide
- Define the deliverable before the workshop
- Decisions to resolve before you commit
A client workshop can produce discovery questions, a prioritized scope, or a decision—not necessarily all three. Agree on the intended result and who may approve it. That gives the facilitator a basis for redirecting useful but out-of-scope discussion.
Confirm who can decide
Identify participants who provide information, review options, and approve next steps. Send preparation questions in advance. Keep a visible list of assumptions that need later confirmation rather than presenting every workshop idea as an approved commitment.
Define the deliverable before the workshop
A discovery workshop might produce a prioritized question list instead of a finished project plan. Say that in the invitation and read back the result before closing.
Send a brief: “The session will produce __. Participants should review __ and bring __. Decisions requiring approval outside the room will be recorded for follow-up.” Close by showing the actual output and labeling working ideas separately from accepted commitments.
Decisions to resolve before you commit
| Decision | What a usable answer includes |
|---|---|
| Output | Describe what participants will leave with |
| Roles | Distinguish contributors, reviewers, and approvers |
| Open questions | Assign an owner to assumptions needing confirmation |
Avoid the mistake that creates extra work
Avoid reporting a lively discussion as client approval. Confirm the agreed decision process and record which outcomes still require review.
Bring client participants and logistics together
Before finalizing the room, use the work event collection to choose the agenda, facilitation approach, and decision record that support the promised output.
Work through a discovery workshop example
Imagine a client team wants to improve a customer onboarding process. The workshop's output is a prioritized list of questions to investigate, not an approved redesign. The client sponsor can prioritize the questions, while another person must later approve project scope and spending.
Ask participants to bring one observed problem and the evidence they can appropriately share. Group the problems, identify what is known, and separate assumptions from observations. Then compare the questions using criteria agreed with the sponsor, such as the effect on the intended outcome and whether the team can investigate them.
| Working item | Status at the close | Next owner action |
|---|---|---|
| A confusing instruction | Observation to validate | Gather the agreed supporting examples |
| A proposed replacement step | Idea, not approved scope | Assess feasibility with the responsible team |
| Three priority questions | Sponsor's agreed investigation order | Assign research and a review date |
Read back the status of each item before leaving. If someone says “we approved the new process,” correct that interpretation while the decision makers are present. Record who accepts the workshop output and which separate approvals remain.
Use the offsite decision log to keep those distinctions visible and the facilitator checklist to prepare the closing read-back.
Further planning resources
For the surrounding logistics, use the Richmond event planning guides. Research local options with Richmond Region Tourism meeting resources. Confirm specific property arrangements directly.
A little more clarity
Common questions
Does workshop agreement equal final project approval?
Not automatically. Clarify the client's approval process and distinguish working ideas from confirmed decisions.
