How 1City verifies
A structured framework of source tiers, confidence labels and dated updates — so you can judge every number yourself.
🗂️ Data source hierarchy
We use multiple source tiers and clearly label the reliability level of each information. Higher confidence is given to official and primary sources.
🏷️ Confidence labels
📜 The full policy
Every page on 1city runs on one contract: a number is either sourced or absent. This page describes the machinery behind that contract, so you can judge the results yourself.
The source hierarchy
| Tier | What | Examples from our pages |
|---|---|---|
| 1 — Official | Temple trusts, temple committees, government portals, district administrations, official panchang authorities | srjbtkshetra.org, shrikashivishwanath.org, kashi.gov.in, prayagraj.nic.in, registrationandtouristcare.uk.gov.in, tirumala.org, maavaishnodevi.org, Drik Panchang |
| 2 — Reported | Established news outlets, dated | Times of India, Hindustan Times, Economic Times, Indian Express |
| 3 — Supporting | Booking platforms, maps, travel guides, community reports | Platform price displays, route aggregators, guide sites |
Operational facts (timings, fees, procedures, dates) default to Tier 1. Where Tier 1 doesn’t exist — many secondary temples publish nothing — we say so rather than launder a blog into an authority.
The confidence labels
| Label | Meaning |
|---|---|
| Verified — official source | Retrieved from the governing body’s own pages, linked |
| Reported | Published by established news, dated, linked |
| Unconfirmed | Circulates in guides/summaries without official confirmation — pages say “unconfirmed — official notice awaited” |
| Not found | We looked; nothing exists. Silence beats invention |
The same fact carries the same label everywhere it appears on the site — a timing marked unconfirmed in prose is unconfirmed in its table row, its FAQ and its structured data.
The register behind the pages
Each city keeps a source register — a claim-by-claim table of fact → source → URL → date checked → status. Pages cite register rows; when a claim changes, the register changes first and the pages follow. Conflicts between sources are shown, not resolved silently (example: Kashi Vishwanath’s own pages disagree on Sugam Darshan’s price — our page shows both).
Last-checked and review
- Every page carries Last checked: DD Month YYYY — the date its facts were actually verified, not the publishing date.
- Data pages carry a next review date, weighted by volatility: booking systems monthly in season, seasonal pages before their festival, historical pages quarterly.
- Corrections are logged on the page’s maintenance record; a correction never silently rewrites history.
What we do not do
- No fabricated first-hand experience (“we visited” appears only where a visit happened).
- No invented specifics — a train number we can’t verify becomes “several trains connect; check the current timetable”.
- No paid placements inside data. Sponsorship never touches a timing table.
Frequently asked questions
Why show unconfirmed information at all?
Because a labelled uncertainty still helps planning, while silent omission often leaves the pilgrim to a search result that invents certainty. The label is the honesty.
How can I report an error?
Via the contact page — every correction gets checked against the source register before it ships.
Yatra Alerts — free
Booking windows opening, festival dates, crowd advisories — a short alert only when it matters. Get the next yatra alert before you plan.
⚠️ Known limitations
- Many secondary temples publish nothing official — those pages say so instead of quoting blogs
- Some operational details (advance booking windows, queue lengths) have no verifiable source and are labelled unconfirmed
- Conflicting figures (e.g. airport distances) are shown as conflicts, not averaged
- Coverage is growing city by city — guides are added as verification completes
🔄 Review and update cycle
- High-traffic operational pages (darshan timings, passes) re-checked monthly and before major festivals
- Every page carries its own "last checked" date — the stamp tells you exactly how fresh it is
- Material changes trigger a full re-verification of the affected page
- Stale content is labelled "needs update" rather than silently kept
❓ Have a question about our methodology?
We welcome your feedback and questions. If you believe any information is incorrect or needs an update, please let us know — your input helps keep the information accurate and useful for all travellers.
Contact us →🔗 Related guides
Yatra Alerts — free
The same machinery that powers our last-checked stamps, sent to you: Get alerts by email and WhatsApp →