Build an event story from contributions teams choose to share

Recognize the problem?

Useful work. An unclear message.

An event produces work, questions and connections, yet the recap often has to be reconstructed from scattered messages and photographs. Teams may have different plans for sharing. A small contribution process gives the organizer usable material and keeps each team in control of its explanation.

What you will make

Prepare an official brief, a voluntary contribution request, a review register and a recap outline. Each highlight has an approved version, clear credit and a chosen next step. The event can still communicate from its own confirmed facts when team material is unavailable.

What you need

Confirmed event purpose, audience, dates, format, public links and a person responsible for official communication.
A clear explanation of what a team may contribute, where it will appear and how the team can decline, revise or withdraw it.
Separate records for public editorial material, private event administration and any results awaiting official confirmation.

Step 01

Start with the event’s own invitation

Explain whom the event is for, the work it invites and the actual participation route. Keep registration, submission and demo deadlines distinct and include their time zone. Before any projects exist, the event can communicate its confirmed purpose and program without promising what teams will achieve.

Step 02

Ask for one bounded contribution

Invite a team to share its problem, a demonstrable flow, current limitations and a next question. Request only the necessary passage, image or link. Specify the intended use and destinations, and let the team decline or offer different material. Access to its repository, chat or registration record is not approval of a public highlight.

“May we use this description, sample screenshot and project link in the event recap and official social summary, with the credit below? You can revise the wording or decline.”

Step 03

Review the exact material and official framing

Keep the team’s accepted version, permitted use, attribution, reviewer and date together. Separately review the event’s framing. If the wording, asset or intended use changes, return it for the necessary review. Pending or withdrawn material stays out of new drafts and exports. If it was already published, record the correction or removal action and confirm the result separately.

Step 04

Build useful highlights without turning them into rankings

Explain the problem, what the demonstration establishes and what remains to test. Show prototype status clearly and confirm credits, sponsors and award claims with their responsible source. Group projects by the problems they address. Count unique projects separately from multiple challenge entries; inclusion in a recap is not an award.

Step 05

Make the recap a route back to the work

Use confirmed event facts and the currently approved highlights. Give each team its chosen demo link, public contact route or next milestone, and verify access before sharing. A personal reflection remains its author’s choice. Offer a feedback question about the event and explain how responses will be used.

Step 06

Record what the event made possible

Review approved coverage, unresolved permissions, usable links and actual follow-up observations. Keep reactions, conversations, tests and ongoing projects separate. Assign an owner and review date to each promised next action. Capture one lesson for the next event; a planned follow-up or a large impression count does not establish adoption.

Fictional worked example

The facts stay. The perspective changes.

The starting material

Fictional Common Ground event. Trailnote’s team approves one description of its trip-note-to-checklist demo, a sample screenshot and its chosen follow-up question for the official recap. A second team is still reviewing; a third has withdrawn its contribution. No event attendance, reach, prize or adoption result is claimed.

The company or project voice

The personal perspective

Make it your own

Contribution register and event recap

Copy this into the tool you already use. Fill in what you know and leave unknowns visible.

Event purpose, audience and confirmed public facts:
Official links and date checked:
Registration / submission / demo times and zone:
Official communication owner and reviewer:

For each optional team contribution:
Unique project ID and team credit:
Problem / demonstrated flow / current limits:
Exact excerpt and asset or link version:
Permitted destinations and intended use:
Team reviewer, decision and date:
Status: pending / approved / declined / withdrawn / needs new review
Official framing reviewer and decision:
Already published? Correction/removal action and confirmed result:

Recap: event context → approved highlights → chosen next steps
Unique projects represented / contributors invited:
Challenge entries recorded separately:
Access-checked links and review date:
Team-selected next action, owner and date:
Observed follow-up, with source and observation date:
Unanswered questions and lesson for the next edition:

Stay faithful to the work

The boundaries to keep.

Common Ground, Trailnote and all contribution states in the example are fictional; they are not evidence of a Tellshift partnership.
Approval applies to the identified material and intended use. Team registration, an accessible image or a public project link is not blanket editorial permission.
The two-stage review is a proposed editorial practice, not legal advice or a universal event rule. Actual agreements and event policies still apply.
This method can run manually. The public demo does not contact teams, obtain real approval, publish a recap or remove previously published content.

Bring the event together through its teams.

Set the event brief, inspect what teams allow you to use, prepare an official story and give the next step an owner.

No sign-in required. Progress stays in this browser; nothing is submitted or published. The guided workspace currently uses English. You can prepare content in English or French.

Try the organizer journey Hackathon organizers