For event organizers, community teams and ecosystem partners

Make the projects the story of your hackathon.

Give people a reason to join, help them follow the work and leave them with a useful next step. Tellshift brings the event brief, voluntary team contributions and reviewed highlights into one editorial workflow, from the first invitation to the post-event recap.

Try the organizer journeyOpen the full workspace

Organizers · communities · ecosystem partners

No sign-in required. A fictional example with decisions and drafts you can change.

  1. Before: give people a reason
  2. During: collect approved stories
  3. After: make the recap useful

Taking part in a hackathon?

Explore the hackathon pace

Make it your example

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.

What you can prepare

An event story grounded in approved contributions and useful follow-up.

Interactive example · no account required

Continue in the full studio ↗

This workspace is saved in this browser. Imported files remain on this device. No social account is connected.

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.

Concrete work to prepare

A useful story, with somewhere to go next.

Track invited and contributing teams, ready and pending stories, source coverage, review time and confirmed follow-up. Keep those counts separate from reach. Sponsor value, recruitment and participant satisfaction need their own evidence.

An event brief and contribution kit

The audience, confirmed facts, invitation, short team prompt, attribution choices, permitted uses and a clear review process.

Reviewed highlights and a project roundup

An agreed selection of official drafts and project references built from permitted material, with pending contributions and unsupported claims left out.

A recap and follow-up record

Confirmed event facts, approved project stories, team-selected next steps, observed responses and open questions for the next edition.

The friction

The best moments rarely arrive as a finished event story.

One team posts a clip, another shares an unfinished note and the event team collects links in a spreadsheet. Reconstructing the story after closing takes another round of requests, while a list of winners leaves much of the work unexplained.

Help the right people decide to join

Show the purpose, who can participate, what they can expect and how to take the next step. Keep practical details aligned with the current event brief.

Make a range of projects discoverable

Show each included team’s problem, demonstrated result and chosen invitation. Use an explicit editorial selection and acknowledge its coverage, including projects beyond the winners.

Give participants and partners a credible recap

Separate confirmed event facts, approved project stories and observed follow-up. A clear record can support continued conversations and planning for the next edition.

Why Tellshift

One event brief. Distinct team stories. A useful handoff.

  1. Make participation easier to understand

    Explain who the event is for, the challenge, the practical requirements and the next action. Reuse confirmed event facts across the invitation, website and updates.

  2. Get usable stories without chasing every team

    Offer one short contribution prompt: what changed, what can be shown and what comes next. Keep attribution, permitted use and review status attached to each contribution.

  3. Carry the value beyond the closing session

    Prepare a project roundup and recap from approved material. Give attendees and partners clear demo references, team-selected next steps and an honest account of what is still unknown.

The workflow, roles and pace

Who this is for

Organizers, community leads and partners communicating an in-person, online or multi-stage hackathon. Keep the official event voice separate from each team’s project. Start with a few voluntary contributions or work from the event’s own material.

A first useful result

An event brief and contribution kit

The audience, confirmed facts, invitation, short team prompt, attribution choices, permitted uses and a clear review process.

An event story built from the brief and contributions people choose to share

  1. Before: prepare the invitation and contribution rules

    Confirm the event facts, audience, official destinations and reviewer. Set contribution prompts, credit and reuse choices. A team can participate in the event without contributing a public story.

  2. During: gather selected, reviewable moments

    Collect short checkpoints and permitted visuals from willing teams. Keep pending material outside the official draft. Review a useful selection within the time your event team has available.

  3. Demo: assemble accurate project highlights

    Use approved descriptions and links, label prototype limits and check attribution. Confirm results and award names with the official source before adding them; showcase coverage is an editorial choice, not a ranking.

  4. After: deliver the recap and follow through

    Bring the approved stories together with confirmed event facts. Keep each team’s chosen next step and observed response. Review unanswered requests, corrections and the next edition’s communication needs.

Clear roles, even when one person wears several hats

The event communication team

Owns the event brief, official destinations, editorial selection and final event message. It checks logistical facts and awards and keeps corrections attached to the published record.

The participating teams

Choose whether to contribute, which material may be used, how they are credited and which next step to invite. Their project work and personal communication remain theirs.

A light start or a deeper editorial workflow

Begin with an event brief and a few approved contributions. Add more projects, formats and reviewers as needed. If no teams contribute, prepare the invitation and recap from the event’s own permitted material.

A method you can use now

Build an event story from contributions teams choose to share

Prepare an invitation, approved project highlights and a recap with useful next steps, while keeping team and organizer responsibilities clear.

Read the guide and copy the templateUnderstand the inputs

A first project

Try one event before expanding the program.

Explore the organizer example, then bring the event brief and your communication goal. We will agree which outputs matter, who reviews them and how much coordination the pilot can require.

What a first pilot would include

  • An event brief and contribution kit

    The audience, confirmed facts, invitation, short team prompt, attribution choices, permitted uses and a clear review process.

  • Reviewed highlights and a project roundup

    An agreed selection of official drafts and project references built from permitted material, with pending contributions and unsupported claims left out.

  • A recap and follow-up record

    Confirmed event facts, approved project stories, team-selected next steps, observed responses and open questions for the next edition.

Plan an event storytelling pilot

Proposed starting scope: one event, an official reviewer and a small voluntary group of teams. Agree participation, outputs, review windows, editorial support and any service price before committing. Organizer and team approval are separate decisions in this workflow. The demonstration does not connect private team sources, message participants or publish.

As your context changes