TranskribatorTranskribator
Workshop report: what was decided, what to test and who takes it forward
From workshop to follow-up

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.

The Transkribator team5-minute read
SOURCEWORKSHOPObjective and participantsMaterials and statusesDecisions and constraintsFollow-up and ownersFROM WORDS TO RESULTS
Working with a real recordingIllustrated training exampleTemplate to copy
From workshop to follow-up

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.

Workflow

Build the report step by step

  1. Restate the objective

    Explain what practical problem participants were meant to solve.

  2. List the materials created

    List diagrams, prototypes and checklists. Note each item’s status and where it is stored.

  3. Identify the decisions

    Connect each decision with its reason, constraint and the person who confirmed it.

  4. Plan the follow-up

    Specify the test, owner, deadline and format for the next check-in.

Worked example

Example: an onboarding workshop

This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.

Excerpt from a training recording · 12:40
“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.

Objective and participantsSourceMaterials andstatusesChecksDecisions andconstraintsDecisionFollow-up andownersOutcome
Workshop report structure, from the objective to the next check
ItemStatusAction
New-user flowApprovedMove to prototyping
Administrator tipsHypothesisTest in interviews
Journey mapWorking draftClarify two steps
List of questionsOpenAssign owners
Ready-to-use template

Workshop report template

Copy the template and fill it in using a specific recording. Label unconfirmed assumptions as hypotheses.

Template for your workSelect and copy
Objective and participants:
What was created:
Status of each item:
Decisions made:
What still needs testing:
Owners, deadlines and next check-in:
Check the result

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.
WorkshopWork togetherMaterialsName what was createdStatusesDistinguish approved work from hypothesesFollow-upSchedule the next check
From a recording to a document you can verify and use
Frequently asked questions

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.

Keep working with the recording