A source list should reveal what each source actually supports

Why a bibliography becomes useful only when readers can see which claim each document supports and where its evidential reach stops.

2026-09-10

This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.

A long bibliography can make a property article look thoroughly researched while leaving the reader unable to answer a basic question: which source supports which claim? That gap matters because property pages often combine several kinds of information that require different evidence. A government record, a developer brochure, a public listing and a calculation may all be legitimate inputs, but none of them has unlimited reach.

The editorial job is therefore not simply to collect authoritative names. It is to keep a visible relationship between claim, evidence, date and limitation. When that relationship disappears, even a strong source can be used to support a conclusion it never actually addressed.

A bibliography is not a proof map

Consider a page that says a development is associated with a particular company, shows an asking-price reference, describes an advertised facility and discusses whether a foreign buyer can acquire a specific home. Four statements may sit comfortably in one paragraph, yet they are not one evidential problem.

A corporate or government record may establish the identity of a registered entity. It does not automatically establish that the same entity is the contracting seller for a particular unit, owns every relevant right, or promises a return programme. A developer's marketing material can show that a facility or programme was advertised. It does not by itself prove that the promise became a contractual obligation. A public listing can show an asking price at a point in time. It does not prove a closed transaction price or current availability. A general legal source can explain a rule without resolving how a particular contract or title fits that rule.

If all four documents appear under a generic heading such as “Sources”, the page may still be technically sourced while remaining difficult to audit. The reader sees authority, but not the route from authority to the wording above.

A more useful source note states the purpose of the document. It can say that a registry record supports the legal identity of the company, that a developer page supports a stated completion target, that a dated listing provides a market asking-price reference, or that an official rule explains the general legal framework. This does not require an academic citation after every sentence. It requires enough specificity to prevent one source from silently expanding into another claim.

The date is part of that map. A document that was suitable for a status statement six months ago may still be historically useful today, but it should not automatically be treated as current evidence. The same is true of a price list, sales brochure or programme description. Naming the access or publication date helps a future editor understand which claims need re-checking when the page is updated.

The useful unit is claim, evidence and limitation together

The strongest editorial test is to take a sentence and ask what the cited document would allow us to write if we had no other information. That exercise often exposes hidden additions.

Suppose the source states a planned handover date. An article then says the buyer will be able to move in before the school year starts. The first statement may be directly supported. The second depends on the specific unit, contractual timing, handover procedure, fit-out and the buyer's own circumstances. A source list that merely names the developer document can make both statements appear equally evidenced.

The cleaner version separates them. It reports the dated plan as a sourced fact or developer statement, then labels the buyer's timing as a scenario that depends on further conditions. Nothing dramatic has changed in the prose, but the evidence has stopped doing work it cannot do.

This matters even more with legal or financially significant claims. An official rule can be highly authoritative and still be too general to answer a unit-specific question. The source note should therefore identify the precise document or official page and the proposition it supports. If the outcome still depends on the contract, title, parties or current administrative practice, the article should say so. “Official sources confirm” is rarely enough because it hides the exact subject and boundary of the confirmation.

A good source section also makes updates cheaper and safer. When an editor knows that one document supports the status, another supports the historical marketing claim and a third supports the legal framework, a change in one source does not require guessing which parts of the article are affected. The evidence architecture becomes maintainable.

Quantity is not the target. One primary source that directly supports the sentence may be more useful than five secondary articles repeating one another. Conversely, a page covering several distinct claim types may genuinely need several sources. Counting links cannot resolve that judgement.

For the reader, the result should be simple: the page makes it possible to tell what is known, who says it, when the evidence applies, and where editorial interpretation begins. A source list succeeds when it exposes those boundaries. It fails when it merely makes the bottom of the page look impressive.

Sources

• NovAsia — “NovAsia Editorial Policy” — describes primary-source priority and the requirement to check whether a source supports the specific claim; accessed 6 October 2026.
• NovAsia — “NovAsia Trust Center” — describes source states and the distinction between documents, party statements, calculations, conflicts and unconfirmed information; accessed 6 October 2026.
• NovAsia — “Ekaterina Andreeva — Editor-in-Chief at NovAsia” — describes the editorial role and its limits; accessed 6 October 2026.