Fact Check Policy

Website: creatifyo.com Last Updated: June 2026


The WhatsApp Forward That Sent Hundreds of People to the Wrong Office

Somewhere around early 2024, a screenshot started circulating on WhatsApp in Punjab. It claimed the government had launched a new Ehsaas Emergency Cash installment — Rs. 14,000 per household, registration open at a specific tehsil office, deadline in two weeks.

It looked official. It had logos. It had a toll-free number.

It was completely fabricated.

Dozens of people showed up at the office mentioned in the screenshot. Some had traveled for hours. A few had taken unpaid leave from daily wage work to make the trip. The office had no idea what they were talking about. There was no such installment. The toll-free number went nowhere.

We heard about this from three different readers in the same week. And the worst part? Several of those readers had first seen “confirmation” of this scheme on a blog — a real website, with articles, that had simply copy-pasted the WhatsApp screenshot content as if it were news.

That’s the environment Creatifyo operates in. Misinformation about government schemes isn’t an occasional problem here — it’s constant, it travels fast, and it causes real harm to people who can least afford to waste a day chasing a ghost.

This page explains exactly how we verify the information we publish, and what we do when something we’ve already published turns out to be wrong.


Why Fact-Checking Government Scheme Information Is Harder Than It Sounds

You’d think it would be simple. Government announces scheme. We report it. Done.

The reality is messier.

Announcements happen in stages. A minister gives a speech announcing a program. That speech gets covered by news channels. Social media picks it up. Blogs write about it. And then — sometimes weeks later — the actual official notification comes out with different numbers, different eligibility criteria, or a different rollout timeline than what was originally announced.

If you published based on the speech, you published something that turned out to be inaccurate. Not because anyone lied, but because policy announcements and policy implementation are two different things.

Portals lag behind announcements. We’ve had situations where a scheme was announced, we went to verify on the official portal, and the portal hadn’t been updated yet. Waiting means being slower than the misinformation. Publishing means potentially getting details wrong.

Regional variations exist. The same scheme can have different registration processes in different provinces, different documentation requirements in different districts, and different payment timelines depending on which bank or payment agent is handling disbursement in a given area. A fact that’s true in Lahore might not apply in Quetta.

Old content doesn’t disappear. Something we published accurately in 2023 shows up in Google search results in 2026. If the scheme changed and we didn’t update the article, we’re still spreading outdated information to every reader who finds it.

All of this shapes how we approach fact-checking on Creatifyo.


Our Fact-Checking Process — Step by Step

Step 1: Trace the Claim to Its Origin

Every piece of information that goes into a Creatifyo article has to be traced back to its original source. Not the tweet about it. Not the news article about it. The actual original source.

For government scheme information, that means:

  • The official government portal (bisp.gov.pk, ehsaas.gov.pk, finance.gov.pk, etc.)
  • An official press release from the relevant ministry
  • A published government notification or gazette entry
  • A verified official social media account (with the blue checkmark, and even then we cross-reference)

If we can’t trace a claim to one of those sources, we don’t publish it as fact. We might note that something is being reported or circulating, but we’ll say explicitly that we haven’t been able to verify it from official sources.

Step 2: Read the Actual Document — Not the Summary

This sounds obvious. It’s not always done.

News articles summarize. Summaries sometimes drop important qualifiers. “Eligible households will receive Rs. 10,500” might leave out that the eligibility cutoff is a PMT score below 32, or that disbursement is only in specific districts for the first tranche, or that you need a specific type of bank account to receive it.

We go to the actual notification whenever possible. We read it. We note the specific conditions, the specific numbers, the specific timelines. And we include those specifics in what we publish — because the conditions are often exactly what determines whether a reader qualifies.

Step 3: Check the Date on Everything

Government documents can stay online long after they’ve been superseded. An eligibility criterion published in a 2022 notification might have been revised in a 2024 update that’s sitting on a different page of the same portal.

Before we treat any official document as current, we check:

  • When it was published
  • Whether there are more recent documents from the same program
  • Whether the portal has any “latest update” or “revised” notices

We also check the dates on news coverage. If the most recent articles about a scheme are from 18 months ago and the official portal hasn’t been updated, we flag that internally and try to confirm through other channels before publishing.

Step 4: Verify Numbers Independently

Payment amounts, eligibility thresholds, loan limits, income cutoffs — any number that appears in our articles gets verified against the source document directly.

We don’t rely on what another blog or even a news outlet says the number is. We go back to the official notification and check the actual figure.

This has caught errors more than once. A commonly circulated figure for a particular scheme installment was off by Rs. 500 from the official notification. It seems small, but when readers are planning around that amount, it matters.

Step 5: Flag Time-Sensitive Claims for Follow-Up

Anything with a deadline or a registration window gets a follow-up review scheduled. We use a shared calendar to track these — articles about upcoming deadlines are reviewed a week before the deadline to check if anything has changed, and again after the deadline to update the article accordingly.

This is the system we built after the Ehsaas deadline situation mentioned in our Editorial Policy. It’s not perfect, but it’s caught several deadline changes before they could mislead readers.


What We Do When a Fact Turns Out to Be Wrong

Mistakes happen. The question is what you do with them.

If we discover — or a reader points out — that something we’ve published is factually incorrect, here’s the exact process:

Immediate review. We look at the original source material and compare it against what we published. We determine what’s wrong and what the correct information is.

Correction within 24 hours. For factual errors affecting scheme eligibility, amounts, deadlines, or application processes — the things that directly affect readers’ decisions — we correct the article and add a clearly labeled “Correction:” notice at the top. The correction notice explains what was wrong and what the right information is. We don’t just quietly change the text.

Note the date. The correction notice includes the date it was made, so readers know when the information was updated.

Respond to the reader who flagged it. If a reader told us about the error, we acknowledge it. We’ve gotten corrections from readers who were on the ground dealing with a program and knew the reality didn’t match what we’d written. Those people are doing us a service and they deserve a response.

Review related articles. If one article had a factual error, we check whether the same incorrect information appears elsewhere on the site and fix those too.

We don’t delete articles with errors and replace them with new ones without explanation. That approach hides the mistake while leaving readers who bookmarked the original URL in the dark. Transparency about what changed and when is how trust is built and maintained.


How We Handle Rumors, Viral Claims, and WhatsApp Forwards

This is probably the most practically useful part of this page.

At any given time, there are multiple fabricated or exaggerated scheme announcements circulating on WhatsApp, Facebook, and TikTok in Pakistan. Some are entirely fake. Some are real announcements that have been distorted — numbers inflated, eligibility broadened, timelines invented.

Our policy is:

We don’t publish it until we’ve verified it from official sources. Full stop.

If a claim is circulating widely and causing confusion, we might publish a clarification article — “Is the new Rs. 25,000 BISP installment real? Here’s what we found” — that explains what the official information actually says. This helps readers who are searching to find out if something is true.

What we won’t do is publish the claim as fact because it’s going viral. Virality is not verification.

If we’re actively trying to verify something and can’t yet confirm or deny it, we might note that we’re looking into it — but we’ll say clearly that it’s unverified and tell readers what official sources they should check themselves.


Sources We Trust — and Sources We Don’t

Sources we treat as authoritative:

  • Official Pakistani government portals (.gov.pk domains)
  • Official ministry press releases
  • Published government notifications and gazette entries
  • Verified official social media accounts of government departments
  • Statements from named officials reported in established news outlets — but always cross-referenced

Sources we treat with caution:

  • Unverified social media posts, even from accounts with large followings
  • WhatsApp screenshots (always traced to origin)
  • Blogs and websites that don’t cite their sources
  • News articles based on “sources” without named attribution for scheme-specific details
  • YouTube videos and TikToks about government schemes (often contain speculation or outdated information)

Sources we reject outright:

  • Anonymous Telegram channels claiming insider information
  • Websites that mimic official government styling but aren’t .gov.pk
  • Any source that can’t be traced to a verifiable original document

How Readers Can Help

Our readers are genuinely one of our best fact-checking resources.

People who’ve been through a BISP registration process, who’ve sat in the queue at an Ehsaas center, who’ve tried to apply for a Kamyab Jawan loan — they know things that official portals don’t always reflect. They know which documents are actually being asked for versus which ones are listed online. They know which helpline numbers actually work.

If you read something on Creatifyo that doesn’t match your experience or what an official office told you:

  • Leave a comment on the article
  • Send us a message through the Contact page
  • Tell us exactly what you were told, and ideally which office or center told you

We’ll investigate. If the official information has diverged from what’s actually happening on the ground — which does happen — that’s an important update and we’ll reflect it.

We’d rather be corrected by a reader and fix an article than have that article mislead the next hundred people who find it.


A Note on Schemes We Haven’t Covered Yet

If there’s a scheme you’ve heard about that we haven’t written about, it might be because:

  • We’re still trying to verify the details from official sources
  • It’s a very regional or district-specific initiative we haven’t researched yet
  • The official notification hasn’t been released yet despite announcements

In any of these cases, the best thing you can do is reach out and tell us what you’ve heard and where you heard it. We’ll look into it. And if we can verify it properly, we’ll cover it.


Contact Us About Fact-Check Concerns

📧 Email: support@creatifyo.com 🌐 Contact Form: creatifyo.com/contact

Messages flagging factual errors or unverified claims are prioritized. We read them, we take them seriously, and we act on them.


Creatifyo.com — Pakistan Government Schemes & Benefits, Explained Clearly. Our fact-checking process is designed to protect readers from misinformation. We are an independent platform and do not represent any government department or ministry.