Singapore · Methodology

How we build the Singapore bridging-loan lender library

Every fact rendered on bridgingloan.sg traces back to a public regulator page, lender marketing page, or industry-published guideline. This page documents the pipeline so anyone — buyers, brokers, journalists, regulators — can audit how a given fact got onto the site.

Current state

  • 12 lenders covered (7 banks, 3 MAS-regulated finance companies, 2 specialist lenders)
  • 3 product types (HDB / private property / EC deferred bridging)
  • Source-cited — every lender's published bridging-loan URL committed with a verified date

1. Source authority

Three tiers of source authority used in the library:

  • Regulators — MAS (Banking Act 1970 / Finance Companies Act 1967 / TDSR Notice 645 / SORA framework), HDB (resale eligibility, MOP, EC rules), IRAS (BSD, ABSD, remission framework), CPF Board (CPF withdrawal interaction), MinLaw (Moneylenders Act 2008).
  • Lender published pages — each MAS-regulated bank and finance company's bridging-loan marketing page is the source-of-truth for that lender's product details.
  • Industry guidance — Law Society of Singapore (conveyancing fee guidance), Credit Bureau Singapore (credit-report framework).

2. Ingestion process

For each lender on the corpus:

  1. Identify the lender's bridging-loan marketing page via the lender's primary website
  2. Verify the lender's regulatory status on the MAS Financial Institutions Directory (or MinLaw Registry of Moneylenders for licensed moneylenders)
  3. Extract the published facts — products offered, eligibility framework, fee structure, regulatory category — into a structured JSON entry
  4. Record `verified_at` — ISO date of the last manual verification against the live lender page
  5. Commit to the repo as part of src/data/sg-bridging-lenders.json

Unlike LifeInsuranceSG (where we use Claude vision + Sonnet to extract structured facts from PDF wordings), bridging-loan data is small enough to maintain manually — 12 lenders × ~10 structured fields each, refreshed quarterly.

3. Verification

Every lender entry carries:

  • bridging_page_url — the public URL on the lender's website
  • verified_at — ISO date of the most recent manual verification
  • regulator — explicit regulatory framework (Banking Act 1970 / Finance Companies Act 1967 / Moneylenders Act 2008)
  • products_offered — array of product types from the canonical 3-shape framework

A pre-build audit script (audit-sg-compliance.cjs) hard-fails any deploy that violates the SG compliance ruleset (PDPA / CPFTA / MAS reserved terms / Insurance Act underwriting impersonation / NRIC restriction).

4. Refresh cadence

  • Quarterly — full library refresh, every lender's bridging-loan page re-verified
  • Continuous — when a lender publishes a new bridging-loan page, an updated regulator framework, or a material product change, the affected entry is updated immediately
  • Ad-hoc — when a buyer, broker or lender flags a discrepancy via hello@bridgingloan.sg, the specific entry is prioritised

5. What we don't publish

  • Fabricated bridging-loan rates. Specific rates are quoted on application; we describe pricing-model mechanics, not invented numbers
  • Indicative SGD ranges presented as binding lender quotes — every SGD range is explicitly flagged as industry-typical, not lender-specific
  • "Best lender" or "#1 bridging loan" claims without disclosed methodology (CPFTA + ASAS hard rule)
  • Lender ratings without a real underlying survey + disclosed methodology

6. Corrections

If you spot an error or a stale source URL, please email hello@bridgingloan.sg. We respond to factual corrections within 1 business day and update the affected entry immediately.