Knowledge / Journalism and Mass Communication / Fact-checking and verification

Fact-checking and verification

Journalism and Mass Communication (BA/BJMC) · Journalism · free study notes for exams, placements and interviews

In short

Fact-checking is the discipline of testing a claim against primary evidence before (pre-publication, or "editorial" fact-checking) or after it is published (post-publication, or "ex-post" fact-checking of public claims and viral content). Verification is the narrower craft of establishing whether a piece of content — a photo, video, document, quote, dataset or forward — is authentic, original, correctly dated and correctly located, and who made it and why. In India it matters because WhatsApp forwards, AI-generated audio and recycled visuals have triggered lynchings, communal riots, market rumours and election falsehoods, and because the IT Rules, 2021 make due diligence a legal obligation for digital publishers and intermediaries. It is examined in BJMC papers on reporting, digital journalism and media law, and tested in placement rounds at India Today (AFWA), BOOM, Alt News, Factly, Vishvas News (Jagran), NDTV, The Hindu, Newschecker, Fact Crescendo, Logically Facts and in the trust-and-safety teams of Meta, Google and ShareChat.

Explained

Definitions and the information-disorder framework

The verification process — five pillars and a working sequence

The five questions (First Draft / UNESCO): provenance (is this the original?), source (who captured it?), date (when?), location (where?), motivation (why was it shared?).

  1. Freeze the evidence. Download the file, archive the URL (Wayback Machine, archive.today) and screenshot with timestamp — deleted posts are the norm, not the exception.
  2. Find the original (provenance). Reverse image search on Google Lens, Yandex (strongest for faces and Indian street scenes), Bing and TinEye; for video, extract keyframes with InVID-WeVerify and reverse-search each; sort results by oldest date to find the earliest upload.
  3. Interrogate the source. Account age, first posts, handle changes, follower-to-engagement ratio, posting hours (a "local eyewitness" posting on a different time zone's rhythm), whether the uploader says "I shot this" or "received".
  4. Date it. EXIF DateTimeOriginal where present (stripped by WhatsApp, Facebook, Instagram and Twitter/X), weather archives for that day and place, shadow direction and length, newspaper or hoarding visible in frame, Google Earth historical imagery, YouTube upload time in UTC.
  5. Locate it (chronolocation and geolocation). Match signboard language and script, vehicle number-plate series (state codes such as KL, MH, UP; BH series for Bharat registration), electricity pole and meter markings, uniform and insignia, road markings, shop names, mobile towers, terrain and skyline, then confirm on satellite or Street View.
  6. Establish motivation and spread. Who gains; was it seeded in a cluster of pages; is it a reflown hoax (check your own and others' archives first — most "new" claims are repeats).
  7. Right of reply. Put the claim to the person or institution named, on record, before publishing; log the attempt if they do not answer.
  8. Publish the method. A fact-check is reproducible only if every source, archive link and non-digital step is stated.
  9. SIFT (Mike Caulfield), the quick field version: Stop; Investigate the source; Find better coverage; Trace claims, quotes and media to the original context.

Tools and techniques, by evidence type

Standards, codes and Indian law that bear on verification

Output, ratings and corrections

Key points

Formulas and examples

Sun elevation from a shadow: tan θ = h / s — h = object height (m), s = shadow length (m), θ = solar elevation angle (degrees); compass direction of the shadow gives the sun's azimuth.
Crowd estimate (Jacobs' method): N = A / d — A = occupied area (m²), d = area per person (m²/person): ≈0.25 for a crush, 0.5 tightly packed, 1.0 shoulder-to-shoulder with movement, 2.5 loose.
Speed from video: v = D / (F / f) — D = distance covered (m), F = number of frames, f = frame rate (frames per second); v in m/s, × 3.6 for km/h.
Percentage change = (New − Old) / Old × 100 (%); percentage point change = difference of two percentages.
Rate normalisation: incidence per lakh = (cases / population) × 100,000.
Correction rate = corrections issued / stories published × 100 (%); accuracy rate = 100 − correction rate.
Audit sample size (large population, 95% confidence): n = 1.96² p(1 − p) / e² — p = expected proportion, e = margin of error.

1. Dating a video by shadow. A frame shows a 3.0 m electricity pole casting a 5.2 m shadow pointing almost due west. tan θ = 3.0 / 5.2 = 0.577 → θ ≈ 30°. A 30° elevation with a westward shadow means mid-morning (sun in the east), so a clip captioned "evening lathi-charge" is inconsistent with its own frame; cross-check the date on a solar calculator for those coordinates.

2. Testing a crowd claim. Organisers claim 1,00,000 people at a maidan rally. Satellite measurement of the fenced area: 120 m × 80 m = 9,600 m². Tightly packed, d = 0.5: N = 9,600 / 0.5 = 19,200. At a realistic 1.0 m²/person: 9,600. Even an unphysical crush (0.25) gives 38,400. Verdict: the claim overstates attendance by roughly 5 to 10 times — report the measured range, not a single number.

3. Speed claim from CCTV. A car is said to be "doing 120 km/h". Footage at 25 fps shows it crossing a 30 m marked stretch in 40 frames. Time = 40 / 25 = 1.6 s; v = 30 / 1.6 = 18.75 m/s = 18.75 × 3.6 = 67.5 km/h. The claim is false; state the ±1 frame uncertainty (≈1.7 km/h) and the assumption that 30 m is correctly measured.

4. A statistics claim. "Crime in the district tripled — up 200%." NCRB-style figures: 1,200 cases in year 1, 2,400 in year 2. Change = (2,400 − 1,200)/1,200 × 100 = 100% (doubled, not tripled). Population also rose from 8,00,000 to 10,00,000, so rates per lakh = 1,200/8 = 150 and 2,400/10 = 240 — a 60% rise in rate. Verdict: *misleading* — the raw rise is 100%, the comparable rise is 60%.

5. Desk accuracy audit. A newsroom published 1,200 stories and issued 18 corrections: correction rate = 18/1,200 × 100 = 1.5%, accuracy rate 98.5%. To audit the remaining stories to ±5% at 95% confidence with p = 0.5: n = 3.8416 × 0.25 / 0.0025 = 384.16 → 385 stories must be re-checked — a sample, which must be reported as a sample with its denominator.

TypeExample in IndiaFirst test to run
False contextOld Bangladesh or Syria footage captioned as a fresh Indian riotReverse keyframe search, oldest-first
Manipulated contentClipped speech audio, morphed voter-list screenshotFind the full recording or the source document
Imposter contentFake PIB, ANI or BBC cards; cloned news domainsWHOIS, official handle check, Rule 3 complaint
Fabricated contentAI voice of a leader, deepfaked endorsement videoProvenance plus synthetic-media cues
Misleading statistics"Unemployment at X%" from an incomparable seriesGo to PLFS/MoSPI release, check base and sample

Where it is used

Interview questions

Common mistakes

Related topics

News writing and reporting · Editing and headlines · Media ethics and laws in India · Broadcast journalism · Digital and data journalism · Social media and OSINT research

Open in the Knowledge reader →Find jobs →