A close-up can show a crack, scratch or wet area. It cannot, by itself, identify the unit, establish when the condition arose or decide who caused it.

A phone photo shows a damaged frame corner against an unrecognisable background. The file arrived through a messaging app, has no opening mark, and was taken after packaging was discarded and the unit moved twice. The condition may be genuine, but the evidence cannot connect it confidently to shipment, location or event. A stronger record captures identity, context, chronology and original-file provenance before the scene changes.

1. Anchor the record to the opening, unit, package and shipment

Record project, building, level, elevation/room/grid, opening mark, installed or intended unit identity, product/type/configuration, handing, glass or component identity and drawing/as-built revision where available. Photograph the readable mark and its physical relation to the unit without relying only on typed captions.

For delivered goods, trace package ID, parent crate/rack/container, packing-list and invoice lines, production/batch/lot or serial identities, container/seal and transport references. For split packs, identify frame, glass, hardware and accessory packages separately. Unknown identity remains unknown; do not select the most likely mark.

Create a claim/event ID that does not overwrite NCR, warranty, carrier or insurer numbers. Cross-reference them with issuer and date. Record who supplied each identity and the source document so later corrections remain auditable.

Affected-object identity record
Identity layerObserved/controlled valueSource/evidenceConfidence/unknownCorrection history
Project/opening/location[facts][mark/context/drawing][status][event]
Unit/configuration/hand[facts][as-built/product record][status][event]
Package/rack/container/seal[IDs][labels/packing/transport][status][event]
Batch/lot/component[IDs][labels/production records][status][event]
Claim/NCR/carrier references[IDs][issued notices][status][event]

2. Use an identity-to-context-to-detail capture sequence

Begin with a safe establishing view showing building/room, container/package or storage context. Move to a medium view linking the opening mark or package label to the complete unit and adjacent construction/cargo. Then take orthogonal and oblique details of the observed condition with scale only where authorised and non-destructive. Repeat the identity link after detail capture if the scene is complex.

Capture all sides and interfaces relevant to observation without dismantling: package exterior and supports, frame/sash/glass faces and edges where safely visible, hardware, adjacent finish, perimeter/interface, drainage or storage contact. Record what was inaccessible, concealed, cleaned, moved or already repaired. Absence from a photo is not proof of absence.

Use neutral descriptions: location, shape, dimensions from a controlled method if required, colour, continuity and visible material condition. Avoid labels such as impact damage, manufacturing defect, installer scratch or corrosion cause until qualified review. Include unaffected comparison units only when identity and configuration are controlled.

Claim image shot list
Shot familyMust linkPurposeEvidence limitationFile IDs
Establishing wideScene/location/custody contextWhere the object was observedMay not show detail[files]
Identity mediumMark/label plus full objectConnect identity to objectLabel can be wrong; reconcile[files]
Condition overviewWhole affected face/assemblyExtent/distributionPerspective limitation[files]
Detail/scaleExact observed featureSurface/edge detailScale/method limitations[files]
Interfaces/comparatorsAdjacent/package/control unitContext and hypothesesNot causal proof[files]

3. Build an event timeline from independent records

List last known acceptable observation, packing/closure, loading and seal, carrier and terminal custody, transshipment, arrival seal and opening, unloading, storage moves, unpacking, installation, protection, later-trade access, commissioning/use, maintenance and first discovery. Use source timestamps and time zones; distinguish planned, reported, system-recorded and directly observed events.

For every event record object identity, location, custodian, condition evidence, handling/change, witness/source, time accuracy and gaps. A chronological sequence narrows questions but does not prove that damage occurred between two images, especially when surfaces were concealed or inspections had limited coverage.

Preserve contradictory accounts rather than forcing one narrative. Document clock offsets, amended logs, missing custody signatures and retrospective statements. Ask authorised survey/legal parties which further records are required.

Condition and custody timeline
Event/time/time zoneObject/location/custodianCondition/change observedSource and coverageGap/next evidence
Last known observation[facts][neutral fact][original record][gap]
Pack/load/seal[facts][condition/configuration][record][gap]
Transport/transfers/storage[facts][events][custody record][gap]
Arrival/unpack/install[facts][condition/change][record][gap]
First discovery/containment[facts][observation][record][next step]

4. Send factual notice through the live transaction route

Read the signed contract, warranty, policy and carriage documents with authorised advisers to identify recipients, channels, triggers, deadlines, survey requirements and preservation duties. This article provides none. Maintain parallel notice routes where applicable rather than assuming a message to the supplier notifies carrier or insurer.

A factual initial notice can identify shipment/project, affected marks/packages and quantities, discovery time/place, neutral observed condition, immediate safe containment, evidence available and requested next coordination. Separate unknown cause, responsibility, coverage and remedy. Preserve exact sent version, attachments, transmission proof, acknowledgement and follow-up.

Do not wait for a complete technical diagnosis if live documents require prompt notice; equally, do not accuse a party to make the notice sound decisive. Record reservations or legal language only through authorised advice.

Notice control register
Route/recipientSource requirementFacts sent/filesSent/received evidenceFollow-up/authority
Seller/warrantor[contract/warranty][neutral notice][record][owner]
Carrier/forwarder/terminal[carriage terms][notice][record][owner]
Insurer/broker/surveyor[policy instruction][notice/survey request][record][owner]
Installer/project parties[project contract][notice/hold][record][owner]
Authority/safety route if applicable[official requirement][authorised facts][record][owner]

5. Preserve originals, provenance and every derivative

Retain original photos, video, audio and documents from the capturing device or system using an authorised transfer that preserves file bytes and available metadata. Record device/source, operator, capture clock/time-zone status, transfer path, original file name and size, storage location, access history and hash or integrity control where the evidence policy adopts one. A hash shows byte consistency, not truth of the scene.

Create working copies for crop, annotation, redaction, format conversion or compression. Link each derivative to its original and record software/process, date, operator and purpose. Never edit the only copy, rewrite metadata to repair a clock error or circulate unredacted personal/commercial information beyond authority.

Preserve physical packaging, failed component, fragments, residues or samples only under safe authorised survey/legal instructions, with object identity, custody, storage condition and transfers. Photos do not automatically replace physical evidence.

Digital and physical evidence provenance
Evidence objectOriginal identity/location/integrityDerivative or transfer historyAccess/custodyLimitation
Photo/video original[file/device/hash if used][transfer][log]Metadata not self-authenticating
Annotated/redacted copy[parent original][process/software/date][log]Derivative only
Message/email/export[source object][platform/export][log]Compression/context limits
Physical part/package[object ID][custody/storage][log]Safety/sampling limits
Measurement/survey record[instrument/method/source][revision][log]Method uncertainty

6. Assemble a review pack that keeps observation and conclusion separate

Index identity, timeline, wide-to-detail media, packing/loading/receiving records, drawings/as-built configuration, inspection and maintenance records, weather or environmental data where authorised, notices, custody and physical evidence. State scope and missing records. Give qualified reviewers originals or controlled access, not a curated slideshow only.

Maintain three fields for each issue: observed fact, hypothesis/question and authorised conclusion with author, discipline, date, method and evidence cited. Multiple experts may address product, glass, packaging, transport, installation or contractual questions; one discipline's opinion should not silently decide another.

Close evidence collection only through authorised disposition. Preserve additions, rejected/withdrawn conclusions, repair or disposal authority and final commercial/legal decision separately. A complete file improves reviewability but does not prove responsibility or claim success.

Claim review separation
IssueObserved factOpen hypotheses/questionsExpert evidence/conclusionCommercial/legal status
[condition][neutral observation][multiple possibilities][author/date/scope][not decided/status]
Identity/timeline gap[fact][question][review][status]
Package/transport interface[fact][questions][specialist][status]
Product/install/interface[fact][questions][specialist][status]
Notice/remedy[record][contract/policy questions][authorised advice][status]

7. Audit evidential coverage before anyone argues causation

Build a coverage map, not just a file count. For each relevant surface, edge, interface, package face, lifecycle event and custody period, record whether evidence is continuous, sampled, partially visible, concealed, unavailable or created after disturbance. Link the reason: access, safety, inspection scope, lost record, compression or late discovery. A hundred close-ups can still leave the decisive identity or earlier custody period uncovered.

Check internal consistency mechanically where possible: opening and package IDs across filenames/index and documents; capture times against event records and declared clock offsets; file hashes against the evidence register; package counts against packing and arrival lists; and notice attachments against the retained originals. Flag mismatches for human review rather than automatically correcting them.

Prepare alternative chronologies when dates conflict. One view can follow device capture time, another verified system/gate events and another witness accounts, each with provenance and uncertainty. Do not choose the sequence that favours a claim. Ask the authorised investigator which evidence has probative significance under the actual process.

Document negative findings narrowly. 'No visible scratch in image X at its resolution and angle' is different from 'the scratch was absent'. 'Seal number readable and matching at arrival' is different from proof that custody was uninterrupted or contents unchanged. This disciplined wording keeps a useful record from becoming an unsupported responsibility statement.

Evidence coverage and consistency audit
Question/windowCoverage classificationPrimary evidenceConflict or limitationNext authorised review
Object identity[continuous/partial/etc.][files/labels/records][gap][owner]
Pre-pack/load condition[coverage][records][gap][owner]
Transport/storage custody[coverage][events][gap][owner]
Arrival-to-discovery[coverage][records][gap][owner]
Notice/original provenance[coverage][files/transmissions][gap][owner]

FAQ

Do timestamped photos prove when damage occurred?

No. They document a capture record subject to clock, metadata, identity and coverage limits. Build an independent event timeline.

Is a close-up enough for a claim?

No. Capture location, opening/package identity, full-object context, detail and interfaces in one indexed sequence.

Should damaged packaging be discarded after photos?

Only with authorised safety, survey, carrier, insurer and legal direction. Physical evidence may remain important.

Can metadata authenticate a photograph?

Metadata can support provenance but can be absent, changed or wrong. Preserve originals and surrounding custody records; expert/legal review decides significance.

Should the notice identify who caused the damage?

Report neutral observed facts unless an authorised conclusion exists. Cause, coverage and responsibility remain separate.

Does a complete evidence pack guarantee recovery?

No. Policy, carriage, contract, law, causation, value and notice are transaction-specific decisions.

Continue the project review

Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.

Official sources used

NIST — Digital Evidence preservation resources ↗NIST — Secure Hash Standard FIPS 180-4 ↗C2PA — Technical Specification ↗UNCITRAL — Model Law on Electronic Commerce ↗IMO/ILO/UNECE — CTU Code ↗ISO — ISO 8601-1 Date and time representations ↗

Related buyer guides

Editorial boundary

This article is claim-neutral evidence-control education, not legal, insurance, carrier, forensic, survey, engineering, glazing, repair, privacy, cybersecurity or warranty advice. It does not prescribe unsafe access or scene entry; authenticate an image or metadata; diagnose damage or cause; determine when loss occurred, coverage, fault, liability, breach, value, notice compliance or remedy; or state any Cavorlen claim, product, incident, warranty or after-sales policy. Follow actual contract, policy, carriage documents, law, privacy rules, site safety controls and authorised survey, insurer, carrier, technical and legal advice.