How buyers use a defect inspection PDF during the DLP

Six weeks after vacant possession. The buyer WhatsApps you from a KL condo WhatsApp group — or a Singapore group chat with the agent copied in.

"Developer asked for a defect notice. Which codes were the bathroom leaks again? Also the hollow tiles in Bed 2?"

You remember the walkthrough. They remember the PDF.

On vacant possession and handover jobs in Malaysia and Singapore, the inspection day is not the end of the product. The Defect Liability Period (DLP) is when the buyer actually uses the report — to list defects, forward codes to the developer or contractor, and argue about what was already in the pack when keys were handed over.

If the PDF cannot travel into that thread, the fee you charged was for a morning visit. Not for DLP evidence.

The inspection sells a walkthrough. The PDF sells the DLP.

Buyers book you because the unit is raw, dusty, and unfamiliar. They want someone who knows what to look for on handover day.

What they open later is different:

A branded cover with their unit details
Photo grids with stable codes (A01, B07…)
A legend that says what each code is
Optional socket / spirit / water-ponding pages
A disclaimer they can still find months later

That pack is what gets attached to a defect notice, forwarded to a spouse, or dropped into a developer portal conversation. QLASSIC-shaped workmanship language in Malaysia and CONQUAS-shaped expectations in Singapore both reward documented defects — not "I think the bath leaked."

A WhatsApp album from site day starts the conversation. A coded defect inspection PDF is what the DLP conversation can still open.

What "defect notice" actually means in practice

Formal process differs by SPA, developer, and country. The field pattern is boring and repeatable:

Buyer (or their lawyer / agent) lists defects during the DLP window
Evidence is referenced — often photos, sometimes a full report
Developer / contractor replies, disputes, or schedules rectification
Follow-ups reuse the same references weeks later

When your report used stable codes and a legend, step 2 is "B07 — Bath 1 wall, damp stain near window head." When your deliverable was a Camera Roll dump, step 2 is "the one near the window? I'll resend the photos."

Codes survive forwarding. Verbal memory does not.

That is why "report tonight" is not only about looking professional on day one. It is about whether month-two WhatsApp still points at the same evidence.

How buyers actually open your PDF during the DLP

Not like an inspector. Like a purchaser who is tired, slightly angry, and reading on a phone.

Opens cover — confirms it is their unit
Skims summary / TOC — finds the hot rooms
Jumps to Bath 1 — pinches a photo
Matches the code in the legend under the grid
Forwards "B07, B08, C12–C17" to developer / contractor
Comes back two weeks later — same codes still mean the same defects

If step 3 fails (crushed hairline, no annotation, wrong room tag), the thread becomes taste. If step 4 fails (blank legends, unstable numbering), the thread becomes archaeology. See why hairline cracks vanish in a handover PDF for the pixel half of this problem, and how to write a defect inspection report for the spine the buyer is navigating.

Five ways a handover PDF fails the DLP (after you already left site)

None of these require a bad walkthrough. They require a deliverable that cannot be reused.

1. Codes that only lived in your head

You numbered photos mentally on site. The Word file used different numbers. The WhatsApp captions used room names. By DLP week six, nobody shares a language.

Stable per-area codes (A01… in Foyer, B01… in Living) in the PDF and the legend are the shared vocabulary for buyer ↔ inspector ↔ developer.

2. Legends that say nothing

A photo without a description is a suggestion. A legend row with element + issue ("Wall — hairline crack above window head") is something a defect notice can quote. Blank or vague rows force the buyer to invent wording under pressure.

3. Evidence that dies on pinch-zoom

DLP arguments are phone arguments. If the hairline or damp edge vanished through WhatsApp / Word / half-synced thumbs, the contractor's "I don't see it" is sometimes honest. Pretty grids are not DLP evidence.

4. No annotation on the fragile shots

Circle, arrow, or short text on the close-up tells the next reader where to look. Without it, week-six forwarding is "see the crack" — which is how threads restart from zero. Annotation is not decoration. It is how the PDF speaks when you are not in the chat.

5. Missing unit-level test pages when those checks were sold

Socket / spirit / water-ponding pages turn "I felt the floor slope" into a recorded check. If the buyer paid for those tests and the PDF omitted them — or left them half-filled — the DLP notice has a hole you created on generate day.

What to ship if the buyer will still open this file in month two

Practical bar for VP / handover work in MY and SG:

Cover fields correct for this unit (they screenshot it for family)
Areas ordered the way someone walks the unit
Every photo has a stable code that matches the legend
Legend rows have real descriptions; group honest ranges (C12–C17) instead of fourteen identical lines
Fragile defects: close-up + context + annotation, same code
Socket / ponding / spirit included only when relevant — and complete
Pending uploads = 0 before Generate (placeholders do not become sharper during the DLP)
Open the PDF on a phone before Share — navigate like a buyer writing a defect notice

If the last box fails, you shipped a same-day brochure. You did not ship a DLP instrument.

Where software helps without replacing judgment

You still decide what is a defect. Software decides whether the evidence pack is reusable.

Defiq Inspect is built for Malaysia and Singapore handover workflows: offline-first capture with area + issue tags, automatic coding, photo annotation (circle, arrow, text), and a branded PDF spine (cover, grids, legend, disclaimer, optional socket / spirit / ponding pages) aligned to QLASSIC- and CONQUAS-shaped report expectations. Generate waits until uploads finish so the file the buyer opens in the DLP is not a thumbnail fiction.

Starter (SGD 99 / MYR 299 per month, 1 seat, 60 units/month; first month free with no card on pricing) uses the Defiq MVP report template. Professional (SGD 299 / MYR 899; 10 seats) adds admin template control and 2400px or 4000px PDF evidence. Business (SGD 499 / MYR 1,499) is always 4000px with fuller branding control. Free Trial is available in-app at app.defiq.app.

See how it works. Soft CTA — the unpaid gap is the DLP reuse, not another evening of Word.

Frequently asked questions

What is the DLP in a vacant possession / handover inspection?

The Defect Liability Period is the window after handover when the buyer can notify the developer of defects for rectification under the sale agreement. Exact length and process depend on the SPA and jurisdiction. Inspectors in Malaysia and Singapore routinely produce coded photo PDFs that buyers later attach or quote when raising those notices.

Why do buyers reopen the defect inspection PDF weeks later?

Because the walkthrough is over, but rectification is not. Buyers use the report to find room codes, pinch evidence, copy legend wording into a defect notice, and forward specific items to developers or contractors — often on a phone, often under time pressure.

Is a WhatsApp photo album enough for a DLP defect notice?

It can start a chat. It rarely survives as shared language. Albums lack stable codes, legends, cover identity, and often lose resolution when forwarded. A structured handover PDF is built for reuse; a chat dump is built for conversation.

What should a DLP-ready defect inspection PDF include?

At minimum: correct cover identity, area-ordered photo grids with stable codes, a filled legend, and honest test pages if those checks were part of the job. Annotation on fragile close-ups and full-resolution evidence help when the contractor pinches the file weeks later.

Does Defiq Inspect help with DLP evidence packs?

Defiq Inspect captures and codes on site (including offline), supports photo annotation, and generates a branded handover PDF with legends and optional socket / spirit / ponding pages. Professional and Business tiers can ship higher-resolution PDF evidence (2400px or 4000px; Business always 4000px). The inspector still judges defects; the file is what the buyer reopens during the DLP.

You sold a morning on site. The buyer will judge you on the file they open when the developer asks for a defect notice.

Codes, legends, annotations, and zoomable evidence are how a handover PDF earns its fee during the DLP — not only on vacant possession day.

Ready to ship a PDF buyers can still use in month two? Start a free trial, compare plans, or read software for defect inspection. Related: why hairline cracks vanish in a handover PDF, how to write a defect inspection report, why offline mode matters, or browse more guides. Help after signup: help centre. Legal: terms · privacy.