Workshop report: what was decided, what to test and who takes it forward
A workshop report connects the objective, materials created, decisions and next steps. Attach photos of the board for reference. The reader needs the outcome, each item’s status and who takes it forward.
How to write a workshop report people can use
A workshop report connects the objective, materials created, decisions and next steps. Attach photos of the board for reference. The reader needs the outcome, each item’s status and who takes it forward.
A transcript lets you verify what was said. It preserves context, qualifications and the order of the reasoning. The author still needs to decide what the final document says and ask participants to review it.
Build the report step by step
Restate the objective
Explain what practical problem participants were meant to solve.
List the materials created
List diagrams, prototypes and checklists. Note each item’s status and where it is stored.
Identify the decisions
Connect each decision with its reason, constraint and the person who confirmed it.
Plan the follow-up
Specify the test, owner, deadline and format for the next check-in.
Example: an onboarding workshop
This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.
“The new-user flow is ready, but we haven’t tested the administrator tips yet.”
Record two statuses: the new-user flow is approved, and the administrator tips are a hypothesis to test. Marking both “ready” hides the difference.
A photo of the journey map can help people recall details. Record the decision in writing, including who will run the test, with whom, what counts as a signal and when the team will revisit it.
| Item | Status | Action |
|---|---|---|
| New-user flow | Approved | Move to prototyping |
| Administrator tips | Hypothesis | Test in interviews |
| Journey map | Working draft | Clarify two steps |
| List of questions | Open | Assign owners |
Workshop report template
Copy the template and fill it in using a specific recording. Label unconfirmed assumptions as hypotheses.
Objective and participants: What was created: Status of each item: Decisions made: What still needs testing: Owners, deadlines and next check-in:
Four checks before sending
- The reported outcome matches the objective.
- Every item has a status.
- Decisions are distinguished from ideas.
- Each next step has an owner and a deadline.
A closer look
Do I need a detailed recap?
Only if it helps explain a decision. Usually the reason, constraint and a link to the original material are enough.
Who approves the report?
The owner or the facilitator, according to a rule agreed in advance. State the deadline for corrections explicitly.