Features
Part of Image and video verification: a practical guide
Fictional case: correcting an old flood video labeled as current
Flood video correction case tracing an old clip through reposts, geolocation, shadow and construction clues, source contact, publication repair, and prevention.
What to take away
- A genuine video can become false evidence through a new caption.
- Earliest upload, location, and recording date require separate findings.
- Construction and shadow clues can narrow time without proving an exact minute.
- Corrections must replace thumbnails, alerts, embeds, and partner copies.
- Preservation and a claim ledger make the repair reproducible.
This fictional case shows a visual correction workflow. The town, storm, accounts, and people are invented. The technical limits and editorial steps are realistic.
The alert
During severe rain in the fictional town of Bellweather, News Cod embedded a 22-second video labeled "Downtown bridge underwater this morning." The clip showed brown water crossing a road beneath a concrete rail bridge. A reposting account supplied the caption, and two local accounts shared it. The newsroom issued a mobile alert before contacting the original filmer.
Twenty minutes later, a reader said the bridge had been replaced two years earlier. The current bridge used steel side panels that were absent from the video.
Preserve and separate the claims
Editors stopped promotion, captured the article, alert, social posts, embed, caption, account pages, and referral chain, and saved the highest-quality available clip. They retained an unchanged copy and made keyframes from a working copy.
The claim ledger separated:
- The video depicted flooding.
- It showed Bellweather.
- It showed the downtown rail bridge.
- It was recorded that morning.
- The reposting account filmed it.
The pictures supported the first claim. None of the other four had been confirmed before the alert.
Trace origin and protect evidence
Exact-caption and keyframe searches found a three-year-old community forum post. That post embedded a 64-second version credited to a local road worker. The original page was still public, but the file had been recompressed several times.
The Berkeley Protocol on Digital Open Source Investigations advises investigators to record relevance, assess source and contextual reliability, consider removal risk, and collect the most reliable known version while further verification continues. The newsroom saved the older page and file, logged each version, and kept the uncertain repost separate from the likely origin.
Editors contacted the road worker through a number confirmed by an employer directory. The worker supplied a longer camera file and said it was recorded during a storm three years earlier. The device clock was one hour slow, so its metadata could not settle the exact time.
Confirm the place
The team compared the road curve, bridge piers, drainage sign, hillside roofline, and utility poles with municipal project photographs and archived street imagery. All aligned with the old Bellweather bridge from a viewpoint east of downtown. A similar bridge in another county failed on pier spacing and terrain.
The current bridge opened 22 months after the older forum post. This confirmed that the viral clip could not show the current morning from that viewpoint. It also explained why readers familiar with the new structure spotted the problem quickly.
Narrow the recording time
The longer clip showed a municipal clock, a strong shadow from a straight signpost, and a road-closure board carrying an event date. Weather archives confirmed heavy rain that day, but the nearest station was too distant to establish conditions at the minute shown.
The Naval Observatory's sun and moon data service returns rise, set, and transit times plus the beginning and end of civil twilight for a given date and place, back to 1700 and forward to 2100, and it warns readers to check its notes before relying on the figures for legal purposes. That is the shape of the evidence a shadow gives. Here, the shadow was consistent with late afternoon within a broad range. It did not repair the inaccurate device clock or justify an exact timestamp.
The event board, earliest upload, source account, bridge state, and daylight together supported the stated date and an afternoon range. Editors avoided claiming a precise minute.
Correct every surface
News Cod replaced the headline and caption, removed the current-storm framing, and added a correction stating that the clip showed flooding at the old Bellweather bridge three years earlier. The note preserved the original claim, corrected fact, publication time, discovery route, and scope.
The mobile alert could not be recalled, so the desk sent a correction alert to the same audience. It changed the homepage card, social post, thumbnail, alt text, newsletter draft, video poster frame, and partner feed. The current storm article retained only verified rainfall and closure information from current records.
Prevent the next error
The newsroom added a visual hold to breaking alerts. Before media can carry a current-event label, an editor must record origin search, source contact or reason unavailable, location evidence, time evidence, and the exact status used in every caption. Reposting accounts are treated as discovery routes, not creators, until confirmed.
Common questions
Was the video manipulated?
No material manipulation was found. The false element was the current-event caption.
Did two local shares corroborate it?
No. Both repeated the same repost and supplied no independent evidence.
Why mention the bad device clock?
It explains why metadata was not used for an exact time and lets readers assess the limit.
Should the old footage remain online?
It can remain with its correct date, location, creator, and context. The newsroom should not let the corrected asset continue circulating under the false caption.
