NovA screenshot proves what was displayed, not that the claim was true
How to use screenshots as editorial evidence without overstating them: distinguish a captured display from the underlying fact, preserve context, and verify the claim through the right source.
This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.
Screenshots feel unusually authoritative because they look concrete. There is a logo, a price, a message bubble, perhaps a timestamp and the name of a project. In an editorial review, that visual certainty can make people skip an important distinction: the image may prove that a statement appeared on a screen, while proving nothing about whether the statement was correct.
That is not a reason to distrust screenshots. They are extremely useful evidence when the question is framed properly. The mistake is asking them to establish a different fact from the one they actually capture.
Start with the narrowest claim the image can support
Consider a buyer who sends a screenshot showing a unit at USD 115,000. The live page now says USD 120,000. If the image contains enough context, it may establish that the earlier page displayed USD 115,000 at the time the screenshot was taken.
It does not automatically establish that the seller offered that exact unit at that price under the same terms, that the price was still valid when the buyer contacted the seller, or that the seller had a contractual duty to honour it. Those are separate questions.
The wording should therefore preserve the difference. “A screenshot supplied by the buyer shows USD 115,000 on the project page on 2 September” is a claim about the display. “The property cost USD 115,000 on 2 September” is broader. It may be true, but the screenshot alone has not proved it.
Editorial precision often means resisting that small expansion from “shown” to “was”.
A screenshot can document an error perfectly
The distinction becomes even clearer when the website itself is wrong.
Imagine that a project page accidentally publishes the wrong completion date. A screenshot is strong evidence that readers were shown the incorrect date. It can support a correction notice and help the team identify where the error appeared. It does not convert that incorrect date into the developer's actual commitment.
This matters because sites sometimes end up citing their own historical display as evidence of the underlying fact. That creates a circular chain: an unsupported claim is published, captured, and then treated as confirmation because a screenshot exists.
The right response is two-track. First, acknowledge what was displayed and correct the publication. Second, verify the underlying project term through an appropriate source such as the relevant contract, official project documentation or a current written confirmation from the responsible party.
The screenshot is evidence of the publication event. The other source is evidence of the external condition.
Context can disappear at the crop line
Screenshots are also vulnerable to missing context. A cropped image may omit the URL, the unit identifier, the date range of a promotion, the disclaimer below the price or the paragraph explaining that a figure is illustrative.
This does not make the image false. It makes the scope of the conclusion narrower.
A useful editorial habit is to preserve the original file where possible and ask what sits just outside the frame. Was the screenshot taken from a public page, a private sales message, an archived brochure, a test environment or a social post? Does the page identify the unit? Does a nearby line state that the amount is a “from” price? Is the message quoting a current offer or forwarding an older one?
One extra piece of context can change the editorial sentence substantially.
Screenshots are particularly good at identifying a conflict that deserves investigation. They are much less reliable as a shortcut around that investigation.
Time needs its own interpretation
A screenshot can also contain several different dates at once. The phone clock may show the capture time. A post may have a publication date. A chat may refer to a price that was issued earlier. The page may itself display a “last updated” date that does not correspond to the underlying offer.
An editor should therefore specify what the date represents. “Captured on 5 October” is different from “offer valid on 5 October”. “Message sent on 5 October” is different from “price effective from 5 October”.
This sounds fussy until the validity period is the very issue being disputed.
The same caution applies to screenshots of rules, government pages or policy statements. An image can preserve the wording seen at one point in time, which is valuable for version history. But a current legal or regulatory conclusion still needs to be checked against the current authoritative source and the relevant effective date.
Preserve the evidence status when the copy gets shorter
The final risk often appears during editing rather than research.
A research note may say: “The sales manager's screenshot states that the package includes furniture.” After polishing, the article becomes: “Furniture is included.” The sentence is cleaner, but the evidence has become stronger without any new verification.
That is exactly the kind of improvement I would reverse.
Readers do not need to see every internal research step, but they do need to know when a material condition is a statement from one party rather than an independently verified fact. If the evidence later improves — for example, the signed schedule lists the furniture package — the wording can improve with it.
A screenshot is a valuable editorial record. It can preserve what a page displayed, what a manager wrote, how an error appeared and when a conflict became visible. Its usefulness is greatest when we let it prove precisely that, instead of asking the image to guarantee the truth of everything shown inside the frame.
Sources
- NovAsia Estate — “Editorial Policy: how we create, verify and update materials”, sections on source checking, developer data and evidence states; checked 6 October 2026.
- NovAsia — Ekaterina Andreeva profile, describing the editorial distinction between claims, sources, marketing and unresolved information; checked 6 October 2026.