Guide

How to make a retreat recap video, script first

A recap usually has no talking head to carry it. Write its script first, in 6 to 8 short lines, and let each line ask for one shot. The same order works for an event recap video.

Hound's list of what he added to the sample cut: each picture with the time it plays and the reason it went over that line
Each picture Hound places comes with its time and its reason, and Take off removes it. Boxed: a picture of the editor placed over the line about building videos at Takehound. From the sample project.

Before the event

Ask before you film

I'm Kyle. I built Takehound, and I'm not a coach, so this is how I'd do it. Consent comes first: a recap is an ad with your guests in it.

  • Ask in writing before anyone arrives: a yes or no on the booking form about being filmed for marketing.
  • Make a no easy. Tell whoever holds the phone who stays out of frame.
  • Name the sessions that are never filmed, and say so on day one.
  • Before you post a close-up, show it to the person in it.

Not legal advice. Rules differ by country.

During the event

The shot list: seven moments

You'll be busy hosting. One phone is enough.

Arrivals
Bags at the door, first hellos. Film it wide.
The space at dawn
The room set up and empty, the path, the view. Stand still.
Hands
Pouring tea, writing, rolling out a mat. No faces needed.
Meals
The table being laid, plates passed along.
Movement
The walk, the swim, the class, wide or from behind.
Quiet moments
One person with a view, from behind. Shoes at the door.
The last morning
Hugs, bags going into cars, the empty room again.

Hold each shot for a slow count of ten, and hold the phone the same way all week. On my trip, 119 of 135 clips were upright and the cut was sideways.

File each day's clips the same evening: How to organize B-roll on your iPhone suggests five albums and lists what to type in search to find a clip later.

The structure

60 to 120 seconds, one line per beat

Six to eight beats: one short line each, then a few seconds of picture with no words. Fill in the brackets.

  1. The place. “In [month], [number] of us met at [place].”
  2. Who came. “People came from [near] and from [far].”
  3. The mornings. “We started each day with [the first thing you did].”
  4. The work. “Then [what people came to do].”
  5. The table. “We ate [the meal people still mention] together.”
  6. The surprise. “On day [n], [the thing nobody planned].”
  7. The turn. “By the last night, [what you saw change, said plainly].”
  8. The invite. “The next one is [dates]. [Where to book].”
A retreat recap in 60 to 120 seconds: six to eight beats, one short line eachEight beats in order: The place, Who came, The mornings, The work, The table, The surprise, The turn, The invite. Each is one short line, then a few seconds of picture with no words.60 to 120 seconds, 6 to 8 beats1The place2Who came3The mornings4The work5The table6The surprise7The turn8The inviteEach beat: one short line, then a few secondsof picture with no words.
The structure above, beat by beat. Fill in each line from what happened.

After the event

Write it from what happened

  • Write it on the way home, before you open the footage.
  • Say what happened, not what it meant: “We swam before breakfast”, not “a week of renewal”.
  • Scroll the footage once. If a line has no picture, change the line.
  • Quote a guest only with their yes.

A real example

A trip, not a retreat, but the same job

This example has no retreat footage, only 135 clips from one trip I took to the Rockies. Five lines were written about it, and Takehound looked for a shot for each.

  1. Line 1

    “My girlfriend and I drove into the Rockies.”

    Takehound's reason
    “A car drives a scenic highway toward the mountains, matching the road trip into the Rockies. Shot portrait, but no landscape driving shot exists.” Mountains and pine forest through a car's side window, wing mirror in the corner; an upright clip over a blurred copy of itself
    On review
    Takehound placed the middle of the clip, with the driver in profile. It was moved by hand to the window.
  2. Line 2

    “Lake Louise was bluer than any photo of it.”

    Takehound's reason
    “A wide view of a turquoise lake between towering mountains shows just how vivid the water is.” A turquoise lake seen from high above, between a steep mountainside and pine branches, with a sun flare across the water
  3. Line 3

    “She just stood there, staring at the mountains in the fog.”

    Takehound's reason
    “A woman stands still in the forest, gazing at mist-covered mountains. It matches the line almost exactly.”
    On review
    Not exact: she is smiling, turned away from the fog. No still here: her face is in it.
  4. Line 4

    “We climbed a trail up through the pines.”

    Takehound's reason
    “Hikers climb a forested trail through towering evergreens, matching the climb up through the pines.” Three hikers seen from behind, climbing a rocky dirt trail through pines toward a rounded rock peak
  5. Line 5

    “And somewhere up there, I stopped checking my phone.”

    Takehound's reason
    “A lone hiker stands on a rocky outcrop gazing down at a forested valley with no phone in hand. Shot portrait, but it fits.” A person with long dark hair and a dark jacket, seen from behind, stepping down a rocky trail among pines; an upright clip over a blurred copy of itself
    On review
    Looser than it reads: rocks and trees, no valley. No phone, though.

5 lines, 5 shots. Made with the Mac version of Takehound from a typed script, with no recording. Across four runs, only line 5 ever got a different clip. Each frame shown was picked by hand.

All five lines found a shot. They were written about the trip the footage came from, which is why the script comes after the event.

My 50-second talk went worse: it asked for desks and I had mountains. The B-roll ideas guide goes through it line by line.

Put it together

  1. Put the event's footage in one folder, minus clips of anyone who said no.
  2. Lay one shot over each line, in script order, in any editor.
  3. Read the script as a voiceover, or set the lines as text on screen.
  4. Add air between lines and music you have the right to use.

Takehound does a first pass at step 2

Takehound runs in a desktop browser and is built for long videos where you talk to camera, so for a recap, read the script to camera and add the event's footage. A transcript and a few screenshots aren't the cut. A chat assistant or a coding tool leaves you to watch every render; on a talk, Hound, Takehound's editor, watches the cut himself, as moving picture and sound, before he changes anything and again after. He hears where every cut lands and sees what is already on screen.

One press makes a first pass while you watch: he cuts long pauses, filler words and repeated takes, places your own clips and photos over the lines they fit, puts your key lines on screen and gives a reason for every change in a feed. No stock and nothing generated goes in, and a line none of your footage fits stays on you. Steer him in plain words, undo any step or edit by hand, and he learns how you cut.

Export an MP4 from the browser, or a timeline (FCPXML) that opens in DaVinci Resolve once you point it at the folder your footage is in. Not Premiere. Final Cut has not opened one. Resolve has a free version (Blackmagic's page, read 2026-10-03). The air between lines and the music are yours to add. With no recording at all, the older B-roll tool takes the typed script and a folder instead, and times shots from the words alone, as the Mac version did here: the five lines came to 18 seconds. Sign in with Google for a free first video.

See Takehound for coaches
The sample project's files in the editor: pictures of Takehound given as Kyle's own footage, and his 8:44 recording
Hound picks from the files in the project and nothing else: here, Kyle's recording and the pictures he gave as his footage. No stock, nothing generated.

Questions

How long should a retreat recap video be?

I'd aim for 60 to 120 seconds, which is six to eight beats. If it runs long, cut a line, not the pauses.

Does this work for an event recap video?

Yes. For a workshop or a conference, swap the mornings and the table for the first session and the break. Film the room filling up and the speaker from the back row.

What if I barely filmed anything?

Write the script anyway and see which lines have a picture. Ask guests for their clips, and ask before you use them. For when stock or a generated clip is the right call, see AI B-roll generator: stock, generated or your own footage.

Does Takehound upload my guests' footage?

The video files go up only to keep your footage library: in the editor, they are uploaded when you are signed in and footage storage is on, so the library is there on any computer you sign in on. To edit, small stills of each clip and a small copy of the cut, picture and sound, go through Takehound's server to the AI models that edit; the server keeps none of it, and nothing trains a model. Stills and the cut can show faces, so only use footage of people who agreed. More on the privacy page.

More guides

All guides

Let Hound make your first pass

Hound, Takehound's editor, watches and listens to your talk, cuts the pauses and retakes, places your own footage and says why for every change. Sign in with Google for a free first video, up to 30 minutes.

Start free with Google

No card, no install. Privacy