Why hairline cracks vanish in a handover PDF

You stood 30cm from the living-room wall. Hairline, paint-thin, running from the window head. You shot it. You coded it B07. The branded A4 went out: cover, grids, legend, disclaimer.

Then WhatsApp from the buyer, forwarded to the contractor: "this one looks like nothing."

They pinched the photo. He says he doesn't see it. You remember the crack. They are looking at a postage stamp.

That is not a taste problem. It is a file problem. On vacant possession and handover jobs in Malaysia and Singapore, the PDF is the evidence pack for DLP. If the hairline is gone from the file, the thread becomes your memory versus their screen. Memory loses.

The file they zoom is not the file you saw

Your eye was in the room. Their eye is on a phone, pinch-zooming a JPEG that has already been through a meat grinder. A 3×2 grid on A4 looks pretty even when each cell is a crushed thumbnail. Pretty is not evidence. Evidence has to survive zoom. Hairlines die first. A hollow tile, a ponding patch, or a failed socket still reads at low resolution. A crack the width of a hair does not. Five ordinary ways that happens. None require a bad inspector. They require a pipeline that quietly replaces the original with something smaller.

1. WhatsApp and Camera Roll re-export

You send the good shot to the buyer, the office, or yourself, just so we have it. WhatsApp compresses on send. Someone saves it back to Camera Roll. That re-save is already smaller. Paste that file into Word, or into a developer portal zip, and you have compressed it twice. You did not archive the original. You archived the chat version.

WhatsApp is a conversation, not a vault. Do not generate the handover PDF from files that only exist because they travelled through a chat. When the buyer pinches the report, the hairline has already been smoothed by the WhatsApp encoder.

If your evening workflow is "scroll the chat thread, long-press each photo, save to gallery, paste into Word," you have replaced the camera's full-resolution file with a chat export. You cannot get the evidence back later. The file on the device after a round trip is not the file from 11am.

The trap is quiet: the preview looks the same. Pinch the hairline in the final PDF or in the gallery. If it is a mushy blur, the round trip ate it.

2. Word (and any paste-into-doc) downsamples

The evening bottleneck is not only captions. Word is also a compressor. Insert a photo into a cell. Word resizes it to fit the box. Save the .docx. Export PDF. What the buyer pinches is often a downsampled paste, not the file that was on the phone at 11am.

Phone + Word is a ceiling on evidence size. You can write a perfect legend for B07 and still ship a grid cell that cannot prove B07. The document layout looks clean. The embedded photo has been shrunk to the printable cell dimensions. At display size on a screen, it looks fine. Pinch-zoom it, and the hairline is gone.

The same logic applies to any "paste photo into a template" workflow — Google Sheets, Excel, generic builders that treat the image as a layout ingredient. If the tool downsizes on import, the original evidence never makes it into the deliverable file. The buyer never sees the file you shot — they see the file that survived the layout engine.

Learn more about how to write a property defect inspection report — capture habits and workflow choices that preserve evidence.

3. Generating from thumbnails that have not finished syncing

Capture can be offline. Client PDFs should not be. If you Generate while uploads are still pending, the PDF may lock in a low-res placeholder with the right room tag and code. Looks complete. Pinch the hairline: mush.

On-site tagging and capture are fast. Background upload is slower. The app has a thumbnail for display and a queued high-resolution file waiting to sync when signal returns. If you export the report before the queue drains, the report embeds what is available now: the thumbnail. The legend code, the room label, and the caption are all correct. The photo is not. It is a 800px thumb that barely shows the wall texture, let alone a hairline crack.

This happens most often when a team finishes a large unit (300+ photos), leaves the site, gets back to the office, and immediately presses Generate because the client is waiting. The phone shows "84% complete." They wait 30 seconds, still 84%, they generate anyway. The PDF locks in the partial state.

Pending uploads = 0. That is the gate. No partial syncs. No "looks good enough." The buyer only zooms the file they receive. Learn more about why offline mode matters for defect inspection apps.

4. Portal resize of already-crushed JPEGs

The buyer PDF and the developer portal pack are different deliverables. Portals often cap uploads (20–50 photos) and file-size limits (sometimes 10MB for the whole batch). If you feed the portal already-crushed thumbs, it will crush them again. Export for Developer should start from report-quality files, not a 30-photo zip of crushed JPEGs.

The developer portal is not a photo service. It is a spreadsheet with a drag-drop box. It does not know that you already ran compression three times. It sees a large upload and runs its own resize — or the inspector pre-crushed the batch to fit under the 10MB portal limit. Either way, when the subcontractor zooms the defect cell in the portal, the hairline is a grey smudge.

The right sequence: keep the originals. Export for Developer from the app's Full evidence (4000px) or Report quality (2400px) selector. Let the tool pick the right 20–50 photos with full detail, not a manual zip of gallery saves that have already been through Word and WhatsApp.

5. Too far, no close-up, no circle

Resolution cannot invent a crack you never framed. Shooting from the doorway, even a 4000px file is a room photo. The buyer pinches the PDF. The wall is 5% of the frame. The crack is invisible.

Two shots, same code: context (which wall/window/room — lets the buyer map the defect to the layout plan or site walk) and close-up (30cm, crack is the subject). Circle or arrow on the close-up. Same code A01 or B07 in the legend. A 4000px file of the wrong distance still does not prove the hairline.

On-site discipline: if it is fragile evidence (hairline, paint delamination, damp edge, failed grout joint), step close. Fill the frame with the defect. Annotate the line with a circle or arrow. Link that shot to the same legend code as the context shot. The buyer gets one photo that shows where, and one photo that shows what. Both tied to the same defect code. That is the standard.

What report-quality actually means on a zoomable A4 grid

After layout into a 3×2 A4 cell, after PDF export, after the buyer pinches, the hairline is still a line. Practical bar: keep originals; do not paste into Word; do not Generate until pending uploads are zero; portal zip last from the same report-quality set; close-up plus context plus annotation plus matching legend code. Pinch the worst hairline on a phone before Share.

Report-quality is not about the label. It is about what survives the round trip from camera to the buyer's pinch gesture. If the hairline disappears before the buyer zooms, the file you sent is not evidence-grade — no matter how many pages or how polished the cover looks.

The test is simple: open the final PDF on a phone. Find the worst hairline (the one you annotated and noted in the legend). Pinch. If you can see the crack clearly when zoomed, the file is evidence-grade. If it is a fuzzy grey line or invisible, the file was crushed somewhere in the pipeline.

Before you hit Share

Checklist:

• WhatsApp-as-master? Do not use chat exports or Camera Roll re-saves as the source for client reports.
• Word/Camera Roll re-exports? Keep the on-device full-resolution file, not the version that bounced through a doc layout.
• Pending uploads = 0? Wait for sync to complete before generating the PDF.
• Close-up + context? Frame the hairline so it is the subject of the shot, and link a context shot under the same code.
• Annotation + matching code? Circle or arrow on the evidence shot; tie it to the same legend code as the context photo.
• Developer zip from report-quality files? Export from the app's Full evidence or Report quality selector, not a manual batch of crushed saves.
• Pinch the worst hairline on a phone. If the last box fails, you shipped a brochure, not evidence.

How Defiq Inspect treats evidence size

Defiq Inspect treats evidence size as part of the PDF. Capture is offline-first on Android and iOS. Generate waits until uploads finish. Starter tier uses the Defiq MVP template. Professional tier offers 2400px or 4000px PDF evidence (inspector chooses in Settings → PDF reports; default is Full evidence at 4000px). Business tier always uses 4000px at 95% JPEG quality. Export for Developer lets inspectors cap at 20/30/50 photos and always sources from report-quality files, not crushed chat exports.

Product walkthrough: How it works. Compare tiers: Pricing.

Frequently asked questions

You remember standing 30cm from the wall. They zoom the file you shipped. Pretty grids do not keep hairlines. Full-resolution files, close-ups, and annotations do.

Ready to test report-quality evidence on a real unit? Start a free trial, compare plans, or read software for defect inspection. Related: how to write a defect inspection report, why offline mode matters, why companies need software, or browse more guides. Help after signup: help centre. Legal: terms · privacy.