Scene 01Take 1●
Start with the match record, then build the video
A useful sports timeline answers three questions for each selected event: when was it played, what happened and where did it take place? Put those facts in a source sheet before opening the editor. Then give each game one readable card and use a map transition only when a change of venue helps the story.
The finished example below covers only Games 6 and 7 of the 2024 Stanley Cup Final, completed on 21 and 24 June 2024. It uses public game locations, original map-render footage and factual labels. It contains no match footage, league logos, music or narration.
The two-game sports edit uses renderer sources from NASA, Natural Earth, Flagpedia and HYG v3 (David Nash / Astronomy Nexus), adapted from Geographical Adventures by Sebastian Lague. This named local movie and its poster are shared under CC BY-SA 2.5. Keep the map-source credits and change notes with copies. The record identifies any separate factual-data credits; it does not license other complete videos or hosted exports.
Download the descriptive transcript and edit timing or the example data and primary-source URLs. Sources were checked on 24 October 2026. The clip’s cutoff remains 24 June 2024; it is not a current-season recap.
Scene 02Take 1●
Check every field in the two-game example
| Local game date | Game | Public venue | Result |
|---|---|---|---|
| 21 June 2024 | Final, Game 6 | Rogers Place, Edmonton | Edmonton 5–1 Florida |
| 24 June 2024 | Final, Game 7 | Amerant Bank Arena, Sunrise | Florida 2–1 Edmonton |
Primary references: NHL Game 6 official summary and Game 7 official summary, with the league’s structured Game 6 record and Game 7 record for the local game dates, venues and scores.
Keep the home and away teams attached to their scores when copying data. The league records give local game dates of 21 and 24 June; their UTC start timestamps fall on 22 and 25 June. Use one date convention throughout the viewer-facing timeline. Do not shift the match to the following date by copying a UTC timestamp without its context.
Scene 03Take 1●
Reproduce the twenty-second edit
| Finished time | What appears | Edit decision |
|---|---|---|
| 0:00–0:05 | Edmonton, Game 6, 21 June, EDM 5–1 FLA, Rogers Place | Hold the first location and readable score card |
| 0:05–0:09 | Map moves toward the next game location | Use the transition for geography; keep the score cards separate |
| 0:09–0:14 | Sunrise, Game 7, 24 June, FLA 2–1 EDM, Amerant Bank Arena | Hold the second location and score card |
| 0:14–0:20 | Source references, game dates and scope | Leave a source card viewers can pause; also link it in the article |
- Select Edmonton and Sunrise in chronological game order. For a general city-level recap, use approximate city locators and name the exact venues in text.
- Set a five-second pause at each location and a four-second transition between them. Keep route lines and transport vehicles off: the story concerns game locations, not a verified flight or road trip.
- Render the fourteen-second map sequence. In a video editor, place the dated score panels beside it, keeping each panel attached to the correct hold.
- Append the six-second source card. Export the complete twenty-second result, then check the game cards and source references on the intended screen.
For this sample, the map was rendered locally with the AlbumMap map-renderer project in Unity 2021.3.2f1. FFmpeg added the separate score panels and source card. Those panels are part of the finished edit, rather than a claim that the hosted builder automatically generates score graphics. No hosted export test is claimed for this particular clip.
For the checked place-selection and timing controls, follow the three-stop route tutorial. Use its controls for your own map sequence, then assemble the score cards in the editor you choose.
Scene 04Take 1●
Keep a longer tournament in one compact source table
A complete tournament needs more rows, but the same fields. This retained example covers Spain’s 2026 World Cup matches through the completed final on 19 July 2026. The dates below are local match dates, and the venue column uses FIFA’s tournament venue names.
| Local date | Round | Official tournament venue | Result |
|---|---|---|---|
| 2026-06-15 | Group H | Atlanta Stadium | Spain 0–0 Cabo Verde |
| 2026-06-21 | Group H | Atlanta Stadium | Spain 4–0 Saudi Arabia |
| 2026-06-26 | Group H | Guadalajara Stadium | Uruguay 0–1 Spain |
| 2026-07-02 | Round of 32 | Los Angeles Stadium | Spain 3–0 Austria |
| 2026-07-06 | Round of 16 | Dallas Stadium | Portugal 0–1 Spain |
| 2026-07-10 | Quarter-final | Los Angeles Stadium | Spain 2–1 Belgium |
| 2026-07-14 | Semi-final | Dallas Stadium | France 0–2 Spain |
| 2026-07-19 | Final | New York New Jersey Stadium | Spain 1–0 Argentina after extra time |
The match rows were checked against FIFA’s fixtures, results and stadiums, knockout results and Spain tournament record. The final report confirms that the final was decided after extra time. Checked 24 October 2026; this table’s cutoff is 19 July 2026.
An official venue name can describe a host market rather than the stadium’s municipality. Resolve the actual venue before placing a precise pin. Repeated venues still represent separate match dates: keep both Atlanta group games and both later visits to Los Angeles and Dallas in the timeline.
For a short tournament cut, introduce the group stage as one chapter and give each knockout result its own card. Choose the readable hold time after testing the text. Do not force all eight full rows onto one tiny video frame. The table is the factual planning sheet; it is separate from the two-game demonstration above.
Scene 05Take 1●
Choose the events that explain a season or tournament
| Format | Useful order | What to retain |
|---|---|---|
| Tournament | Opening round → later rounds → final | Round, opponent, local date, result and public venue |
| Season | Opener → early test → turning point → finish | Selected results and moments that explain a change |
| Public tour | Dated appearance → next confirmed appearance | Public event and venue; no invented private travel |
| Championship | Setup → decisive earlier games → final result | Enough context to explain the finish, including setbacks |
A recap for players and families may need more faces and short memories than a fan-facing results video. Select the audience first. For a long season, “First road win” can be a better chapter title than another crowded statistics screen, provided the underlying claim is checked.
The earlier sports map showcase remains a separate format reference. Its route is not evidence for the match rows in this article. Use primary event records for dates and results.
Scene 06Take 1●
Collect relevant media and write one clear line
Contributor request: “We are making a recap of the completed season. Please send one photo or short clip you have permission to share, the match date, the public venue or city, and one sentence about why the moment mattered. Tell us who should be credited and whether it may appear in the planned shared video.”
A score card can simply read: “24 June 2024 — Game 7 — Sunrise — Florida 2, Edmonton 1.” Optional narration can add: “The final moved to Sunrise for the deciding game.” Avoid adding a dramatic turning point that the source record does not establish.
Keep approved media attached to the right event in your source sheet. The group message collection guide helps organize contributions, while the caption and accessibility guide covers speech captions and written alternatives.
For a season reel built around your team’s own footage, follow the sports highlight video editing guide for clip selection and pacing.
Scene 07Take 1●
Review the source sheet beside the final export
- Check each game’s date, teams, score, round and venue against its primary reference. Confirm how extra time or a shootout is labeled.
- Pause each finished card and read it at the audience’s screen size. Keep essential results in nearby text when a small inline player makes them difficult to read.
- Check that the map represents the stated location precision. A city locator should not look like a measured stadium coordinate or a recorded team journey.
- Use footage, photographs, logos and music only with the permission appropriate to your project. A factual score does not grant rights to a broadcaster’s video.
- Confirm participant approval and the intended audience for personal contributions, especially in school or youth-team projects.
Save the source sheet and the finished export together. For later updates, add newly checked records and update the cutoff explicitly. This keeps a completed historical example useful without making it appear to report a live tournament.
End card
That’s a wrap
- Start with the match record, then build the video
- Check every field in the two-game example
- Reproduce the twenty-second edit
- Keep a longer tournament in one compact source table
- Choose the events that explain a season or tournament
- Collect relevant media and write one clear line
- Review the source sheet beside the final export
Helpful answers
Frequently asked questions
Does the map show the team’s actual travel?
No. The worked clip shows two public game locations in chronological order. The map movement is illustrative and does not establish how, when or where the team traveled between games.
Why use a different date from a UTC start timestamp?
The example consistently uses the league’s local gameDate. Its evening games have UTC timestamps on the following day; copying those without context would shift the displayed match date.
Can a sports timeline work without broadcast clips?
Yes. The worked example uses original map-render footage and independently typeset factual score cards. Photos or clips are optional and need appropriate permission.



