Skip to main content
JiranLink

How we work

Editorial policy.

This page explains the standards JiranLink holds itself to: where data comes from, how it gets verified, how errors get corrected, and what we refuse to publish. Read it if you want to understand why you can — or cannot — trust a given field on a building page.

Independent

No commissions, no developer partnerships, no agent listings.

Primary sources

Structural data requires official records, not second-hand claims.

Labeled honestly

Verified, Partially Verified, and Unverified are shown where data quality differs.

Correctable

Errors are fixable. We aim to resolve flagged corrections within 5 working days.

Editorial independence

JiranLink earns no commissions from property rentals or sales. We have no commercial partnerships with developers, no sponsored listings, and no arrangement — formal or informal — with any real estate agency. A building's ranking in search results, its editorial coverage, and the completeness of its profile are determined entirely by research quality and data availability, not by who paid for exposure.

This independence is not incidental. It is the founding condition. If a development has documented flooding problems, poor management, or systematically negative resident feedback, we publish that alongside its marketed features. We do not soften findings because a developer is active in our coverage area.

Sourcing standards

Structural data — unit count, number of floors, built-up sizes, car park ratio, tenure, land title type — must be sourced from at least one primary source before publication. Acceptable primary sources include:

  • Official developer materials — sales brochures, official project websites, and sales kits issued by the project developer.
  • COB (Commissioner of Buildings) filings — strata title applications, strata management documents, and associated public filings.
  • NAPIC — the National Property Information Centre, for transacted prices, project completion records, and approved housing scheme data.
  • Local council and government portals — DBKL, MBPJ, MPSJ, and equivalent authorities for development orders and planning approvals.
  • Ministry of Federal Territories and Housing and Local Government (KPKT) — for licensed housing developer records and project registration.

Secondary sources — news articles, property portal listings, forum posts — are acceptable for context and community notes but are never used as the sole basis for a structural data field. When a secondary source is cited, it is labeled as such.

Verification labels

Every building profile carries one of three verification states. These are applied at the building level and may differ from field to field within a profile.

Verified

All key structural fields (unit count, floors, built-up, car park ratio) have been checked against at least two independent primary sources. The data is as reliable as publicly available records permit.

Partially Verified

Some fields are confirmed against primary sources; others are sourced from a single source or are still under active review. Partially verified fields are individually labeled so readers know which data points to treat cautiously.

Unverified

Data originates from community contribution only and has not yet been cross-checked against primary sources. Treat these fields as directional, not authoritative. We are actively working to verify them.

Buildings graduate between states as new primary sources are located or submitted. A building that was Unverified at launch may be reclassified as Partially Verified or Verified once the research meets the threshold. Downgrades also occur: if a source is found to be inaccurate or superseded, the classification is revised down until the correct data is confirmed.

Community contributions

Residents, past residents, and local researchers can submit tips, corrections, and building notes through the community hub. Every submission is reviewed by an editor before publication. We do not auto-publish user content.

During review, we assess whether the claim is plausible given what we already know, whether the submitter appears to have genuine local familiarity, and whether the information can be corroborated against any available source. Claims that pass this review are published as community notes, clearly labeled as resident-contributed and not independently verified unless our own research confirms them.

Submissions that are rejected include: claims that appear commercially motivated (e.g., a submission that reads like marketing copy), statements that directly contradict documented primary sources without supporting evidence, and anything that identifies a specific individual without their clear consent.

Anonymisation policy: All community contributions are anonymised by default. We publish the substance of a note, not the name, unit, or identity of the submitter. If you want attribution, you can request it, but the default is protection. We do not share contributor contact details with third parties under any circumstances.

Corrections policy

Property data changes. Buildings complete, management companies rotate, maintenance fees are revised. Some errors are ours; others are the result of data changing after a profile was published. Both kinds are treated the same way: correct as quickly as the evidence allows.

To flag an error, email hello@jiranlink.com with the building name, the specific field you believe is wrong, and the source you are relying on. We aim to respond within 5 working days. If the correction is straightforward and the source checks out, we update the field and note the correction date in the building notes. If the correction is contested or requires additional research, we mark the field as under review while we investigate.

Corrections are date-stamped in building notes with the format Updated [date] — [brief reason]. We do not silently overwrite data. The revision history is part of the record.

What we do not publish

The following types of content are excluded from JiranLink regardless of who submits them or how prominently they appear elsewhere:

  • Rumours without a traceable source. "I heard the building has structural issues" is not publishable without documentation. If residents believe there is a real problem, we encourage them to point us to formal complaints, inspection reports, or council filings.
  • Unverified pricing claims presented as fact. Asking prices and rental rates change frequently. We do not present point-in-time figures as current market data unless they are sourced, dated, and labeled accordingly.
  • Developer PR without independent corroboration. Press releases, launch announcements, and developer-commissioned materials are useful starting points, but they are not published as editorial findings. Promotional claims require independent confirmation before they appear in a building profile as factual statements.
  • Content that identifies individuals without consent. This includes management committee members, individual tenants, or any private individual connected to a building complaint.

Sponsorship disclosure

To sustain the project, JiranLink accepts native sponsorships from relevant service providers: internet providers, utility services, and relocation or moving companies. These sponsorships are commercially motivated and clearly labeled as such in every placement.

Sponsorships do not affect building data, verification labels, or editorial coverage. A sponsored internet provider appearing on a building page does not mean JiranLink endorses that provider for that building, and it does not influence which buildings we cover or how we describe them. The editorial and commercial functions are kept strictly separate. If you see a labeled sponsorship, the building data on that same page was compiled without reference to who sponsors what.

We do not accept sponsorships from property developers, real estate agencies, JMBs, or any entity with a direct financial interest in how a building is described or ranked.

Currency of data

Property data is not static. Maintenance fees are revised annually or when strata accounts run short. Management companies change. Facilities fall out of use. Neighborhoods shift. JiranLink profiles reflect the best available information at the time of last verification, which is noted on each building page.

Fields where time-sensitivity matters most — maintenance fee estimates, JMB contact details, facilities status, and management quality notes — carry a last-verified date. A Verified structural record from two years ago is still reliable for unit count and floor count. The same record's maintenance fee figure should be treated as an estimate pending a current confirmation.

If you know a field is outdated, submit a correction. Currency of data is a shared responsibility between the editorial team and the community we serve.

Flag an error or ask a question

Found something wrong? Disagree with a verification label? Email us directly or submit through the community hub.

Sponsored resources

Fibre coverage links for KL condos. Sponsorship does not influence editorial building research.