# Build the Fact-Check SOP in the Favourite1 template (white theme), long & beginner-friendly. # Topic: “Fact-Check SOP – verify stats, names, quotes, links, spellings, and dates; keep a source log.” # Graphics are placed BELOW each heading (Favourite1 style). # Output file: /mnt/data/fact-check-sop-favourite1-long.html file_path = “/mnt/data/fact-check-sop-favourite1-long.html” html = r””” Fact‑Check SOP — verify stats, names, quotes, links, spellings, and dates; keep a source log (Favourite1, White Theme)

Fact‑Check SOP — verify stats, names, quotes, links, spellings, and dates; keep a source log

Use this friendly, repeatable system to make sure everything in your post is true and traceable. You will check stats, names, quotes, links, spellings, and dates, and you will keep a simple source log so anyone can see where your facts came from. Graphics sit below each heading to guide your eyes before you read.

Favourite1
White Theme
Beginner‑Friendly
Text + Graphics
No Jargon
Fact‑Check Flow (20–40 minutes)
Prep & log Stats Names Quotes Links Then: Spellings & dates → final scan → export clean source log and publish.

Table of Contents

Before you start

Why fact‑checking matters

Truth → Trust → Shares
True facts Reader trust Shares & saves

You fact‑check to protect your reader and your name. A true line is useful; a wrong line spreads fast and hurts trust. With this SOP, you follow a calm order, keep a short record of sources, and publish with confidence.

Outcome: A clean post backed by sources that anyone can review.
Fast mode

Quickstart: check a post in 30 minutes

Timer plan
5m: Prep & log 7m: Stats 5m: Names 5m: Quotes Links
  1. Prep & log: Open a copy of the post. Create the source log table (use our template below).
  2. Stats: Confirm the number, year, and original source. Replace weak “listicle blogs” with primary sources.
  3. Names: Check spelling, job titles, company names, and capitalization.
  4. Quotes: Confirm exact words and permission. Keep quote punctuation as in the source.
  5. Links: Test each link, remove trackers, and confirm it points to the right page.
  6. Spellings & dates: Decide US/UK spelling once. Confirm dates with local time zones when relevant.
Output: A tracked list of checks, fixed lines, and a neat source log attached to your draft.
Main process

The SOP in 10 Steps (Detailed & Simple)

Step 1 — Duplicate your draft and turn on “Suggest” or “Track Changes”

Safe editing setup
Copy the file • Enable suggestions • Title it “[Post] — Fact‑check”

Work in a copy to keep your original safe. Use suggestion mode so editors can see every fix. Rename the copy so the purpose is clear.

Step 2 — Create a source log table

Source log columns
Line/ID Claim Source (URL) Date Status Notes

Make a table with these columns: Line/ID, Claim, Source (URL), Source date or “Accessed on,” Status (OK / Fix / Replace), and Notes. Paste each checked item into a new row.

Step 3 — Check stats first

Stat → Source → Year
Number matches? Original / Primary? Year current?

Find the original report or dataset, not a repost. Match the exact number and the year. If the number is old, say the year in the line or replace it with a newer source from the same origin if available.

Step 4 — Check names and titles

Name → Spelling → Title
Official spelling? Title current? Company/Org name & casing

Use the person’s own site or LinkedIn for spelling. Check if their title is current. For companies, match the official casing (e.g., “YouTube,” not “Youtube”).

Step 5 — Check quotes

Exact words → Source → Permission
Exact wording? Where did it appear? Allowed to quote?

Match the quote word for word. Record where you found it (interview, article, report, video). If you interviewed the person, keep the recording or transcript. If the quote is long, check usage rights and context.

Step 6 — Check links

Point → Open → Clean
Correct page target? Loads & not paywalled? Remove trackers (utm)

Open every link. It must go to the right page and load. If the link has tracking parameters (like ?utm=), remove them. Link to the report page, not a copy of the PDF on a random site if possible.

Step 7 — Check spellings and style

Pick one style → Apply everywhere
US vs UK spelling Capitalization rules Product names exact

Decide once: US (color) or UK (colour). Match that choice everywhere. Check product and feature names exactly (e.g., “Google Search Console,” not “Google Search console”).

Step 8 — Check dates and time zones

Date → Zone → Context
Full date shown? Time zone relevant? Old stat marked with year?

Write full dates (e.g., 31 October 2025). If the event relates to a place, consider that place’s time zone. When citing older numbers, always show the year so the reader understands freshness.

Step 9 — Resolve conflicts and record decisions

Conflicting sources → Decision note
Compare methods Prefer primary Explain in Notes

If two sources disagree, check how they measured the thing. Prefer the original measurement (primary). Write a short note in your log explaining the choice you made.

Step 10 — Export the source log and attach it to your draft

Shareable proof
Export CSV or paste table Link it at the top of the draft

Download your log as CSV or keep it as a table in the doc. Put a small link near the top so editors can open it fast.

Deep dive

Check Stats — how to do it

Stat checklist
Original source only Year & sample size Exact wording of metric

When a line has a number, copy the exact number and metric from the original report. Check the year, country, and sample size. If the number is rounded on a blog, use the original precise number or state it as “about X” if the source does that.

Deep dive

Check Names — how to do it

People & brands
Official bios Company press pages Recent interviews

Prefer the person’s official bio or the company’s press page. If someone changed roles, say “as of [month year]” or avoid the title if not needed. Keep diacritics (e.g., “Nadía”) as shown in the source.

Deep dive

Check Quotes — how to do it

Quote controls
Verbatim Punctuation preserved Attribution & context

Do not “clean up” words unless you use brackets […] and say you did so. Keep punctuation as said. Add who said it and where. If you translated the quote, say that.

Deep dive

Check Spellings — how to do it

Consistency beats perfection
Pick a variant Keep it across the post Use style guide if given

Many words have two correct versions. Choose one and stay with it. If the publication has a style guide, follow it. For product names, copy the exact casing from the official site.

Deep dive

Check Dates — how to do it

Write dates clearly
Day Month Year (31 Oct 2025) Avoid 10/11 confusion Add “as of” when needed

Write dates in a way that is clear for all readers. If information changes often (like job titles or prices), add “as of [full date]”.

Proof

Keep a Source Log (template)

Your audit trail
Every claim ↔ a source • status (OK/Fix) • note Export as CSV • Paste into doc • Share link
Line/IDClaimSource (URL)Source Date / AccessedStatusNotes
H2‑2, para 3“40% of readers skim posts”https://…/original‑report2024‑09‑15OKPrimary report page
H3‑1 bullet 2“Quote by A. Patel”https://…/interviewAccessed 2025‑10‑31FixMissing words; replaced with exact line
CSV starter (copy to your sheet/app):
Line ID,Claim,Source URL,Source Date/Accessed,Status,Notes
"H2-2, para 3","40% of readers skim posts","https://.../original-report","2024-09-15","OK","Primary report"
"H3-1 bullet 2","Quote by A. Patel","https://.../interview","Accessed 2025-10-31","Fix","Adjusted wording to match source"
Copy‑paste

Templates you can use today

Template A — Short email to confirm a quote

Quote confirmation
Keep it short • Paste the exact line • Ask for a quick yes/no
Subject: Quick quote check for your approval
Hi [Name],

I’m finalizing a post and included your line below. Can you confirm this is accurate?
“[Exact quote here]”
If you’d like a tiny tweak for clarity (not meaning), let me know.

Thanks,
[Your name]

Template B — Replace weak blog source with a primary source

Instead of linking: random-blog.com/“100-stats”
Link to: the original report page (e.g., organization.gov/report-2025)
Add note: “Data from [Agency], 2025 report (Table 3).”

Template C — Link hygiene (quick rules)

• Remove ?utm= and tracking bits
• Prefer HTTPS over HTTP
• Point to report/article page (not a file dump)
• Add “Archived on [date]” if the page often changes
See it in action

Demo Before/After

One paragraph, fact‑checked
Stats updated Names corrected Links cleaned

Original: “Around 50% readers skim, says a popular blog; source: random site.”

After fact‑check: “About 43% of readers skim posts, according to [Agency]’s 2024 report (Table 3).” (Link points to the report page. Year shown.)

Help

FAQ

How many sources do I need?

For each important claim, keep at least one reliable source. For big or sensitive claims, keep two.

What is a primary source?

The original report, dataset, official page, or the person who said the words. A news article about a report is secondary; the report itself is primary.

Do I need special tools?

No. Your browser, a notes app or spreadsheet for the log, and careful reading are enough. If your publisher uses a specific tool, follow their steps too.

“”” with open(file_path, “w”, encoding=”utf-8″) as f: f.write(html) file_path

Leave a Comment

Your email address will not be published. Required fields are marked *

Shopping Cart
Scroll to Top