How to document FF&E damage and shortages.

Why damage and shortage documentation matters

FF&E problems are easier to investigate when the project creates a factual record at the time the condition is discovered.

Without that record, the team may later be trying to reconstruct:

• what arrived
• how much arrived
• what condition it was in
• where the product was located
• what the packaging looked like
• who discovered the issue
• when the issue was discovered
• what happened to the product afterward

That reconstruction becomes harder as packaging is discarded, product is moved, people leave the site, and the project continues.

Good documentation does not decide who is responsible.

It creates evidence that the project team, vendor, manufacturer, carrier, insurer, or other applicable party can review when determining what happened and how the issue should be resolved.

FF&E Receiving Guide

First, stop and protect the product

When a problem is discovered, avoid making the condition worse.

A practical first response is:

• stop unnecessary handling
• prevent further installation
• move the item only when needed to keep it safe
• protect it from weather, construction, traffic, or additional damage
• keep the affected product identifiable

If the item is damaged but still usable, that does not mean the project should immediately repair or install it.

If the wrong product arrived, do not mix it into the normal installation flow where it can become harder to identify later.

The goal is to stabilize the situation before evidence or project history is lost.

Preserve packaging, labels, and related records

Packaging can be part of the evidence.

Depending on the issue, useful materials may include:

• carton
• crate
• pallet
• bands
• shrink wrap
• protective material
• product label
• carton label
• manufacturer label
• shipment markings
• packing list
• bill of lading or delivery receipt
• electronic proof of delivery
• receiving report
• purchase order
• shipment record

Do not discard relevant packaging immediately when a damage investigation may follow.

Labels can connect the physical product to the vendor, manufacturer, order, item number, or shipment.

The goal is to preserve enough context that another person can understand which product the project is discussing.

Photograph the condition before it changes

Photographs should document context as well as detail.

Depending on the issue, useful photographs can include:

• the loaded trailer before unloading
• the full pallet, crate, or carton
• the damaged packaging
• the entire product
• close-up photographs of the damage
• carton and manufacturer labels
• item numbers
• visible shipment markings
• the surrounding location
• the delivery-receipt notation
• any condition that helps explain how the product was found

Take photographs before the condition is altered through unpacking, repair, installation, cleanup, or disposal when practical.

A close-up of a scratch can show the damage.

A wider photograph can show where that damaged item was, how it was packaged, and what surrounded it.

Both can be useful.

Document facts, not assumptions about blame

The written record should describe what the team observed.

Useful facts can include:

• item or product
• purchase order
• vendor or manufacturer
• room or location
• quantity affected
• date discovered
• time discovered
• who discovered the issue
• visible condition
• packaging condition
• shipment reference
• receiving information

Avoid turning the initial report into an unsupported conclusion about who caused the problem.

For example:

“Carton punctured on right side; tabletop inside has visible edge damage”

is a factual observation.

“Carrier damaged the table”

is a conclusion about responsibility.

The first statement gives the project something concrete to investigate.

Fault can be evaluated later using the available evidence and applicable agreements.

Classify the type of problem

Different problems require different follow-up.

A useful initial classification can include:

Visible freight damage Damage observable before or during unloading, such as crushed cartons, punctures, water marks, leaning pallets, broken wrap, missing bands, or opened packaging.

Concealed damage Damage discovered after packaging is opened when the exterior packaging did not clearly reveal the condition.

Delivery shortage or overage The physical quantity received differs from the expected shipment quantity.

Incorrect product The item, finish, color, size, model, or quantity does not match the approved order information.

Manufacturing defect A problem in material, finish, construction, operation, or workmanship that appears to be associated with the manufactured product rather than obvious freight or field handling.

Handling or installation damage Damage discovered after the product has been moved, unpacked, assembled, installed, adjusted, or cleaned on site.

The initial classification does not have to be a final determination of responsibility.

It helps the project route the issue and gather the right supporting information.

Document visible freight damage and shortages during receiving

Visible freight damage and shortages should be documented while the delivery is being received whenever practical.

That can include:

• specific notation on the carrier delivery receipt or electronic proof of delivery
• actual quantity received
• item or carton count
• description of visible damage
• photographs
• retained copy of the signed delivery paperwork
• related packing list or shipment documents

Specific notes are more useful than vague statements.

For example:

“Expected 20 cartons; received 18”

provides more usable information than:

“Shipment may be short.”

If the driver will acknowledge the notation, retain that documentation.

If the driver does not, continue documenting the project’s observations, photographs, and paperwork rather than abandoning the record.

Timely documentation can materially affect later investigation or claim handling, subject to the applicable terms and contracts.

Treat concealed damage differently

Concealed damage is different because the problem was not clearly visible when the delivery was received.

The team may discover it later when:

• a carton is opened
• protective material is removed
• furniture is unwrapped
• a component is assembled
• installation begins

Once concealed damage is discovered, document and report it promptly according to the applicable project, vendor, manufacturer, carrier, or insurance requirements.

Do not wait for the entire shipment to be unpacked if a significant issue has already been discovered.

Preserve:

• the affected product
• the packaging
• labels
• photographs
• receiving documents
• shipment information

The project may later inspect additional items to determine whether the issue is isolated or more widespread.

Verify shortages before calling product missing

A product that cannot immediately be located is not always a true delivery shortage.

Before reporting an item as missing, check:

• staging areas
• storage rooms
• temporary receiving areas
• installation areas
• other floors
• other rooms
• recently moved inventory
• split-shipment records
• receiving counts

This is particularly important on large projects where product may be moved several times after unloading.

Independent verification of the count can also help distinguish a true shortage from a counting or location error.

The project should be able to explain whether the product:

never arrived,

arrived and was misplaced,

was assigned to another shipment,

was moved into installation,

or is truly unresolved.

FF&E Multiple Shipments Guide

Connect the issue to the approved specification and order

When the problem involves an incorrect product or suspected defect, compare the physical item with the approved project record.

That may include:

• specification
• purchase order
• item number
• manufacturer
• model
• finish
• color
• dimensions
• quantity
• approved drawing
• vendor acknowledgment
• shipment record

The question is:

Does the delivered product match what the project approved and ordered?

If not, document the difference clearly.

For example:

The order specifies one finish; the received product label identifies another.

The purchase order shows 36-inch width; the delivered product measures differently.

The model number on the carton does not match the order.

Clear comparison makes the problem easier for the appropriate parties to evaluate.

FF&E Specification Guide

Keep a complete issue record

A strong issue record may include:

• project
• purchase order
• vendor
• manufacturer
• item description
• item number
• room or location
• quantity affected
• shipment designation
• date and time discovered
• person who discovered it
• factual condition description
• classification of issue
• photographs
• packing list
• bill of lading or ePOD
• receiving report
• product and carton labels
• related correspondence
• current resolution status

The record should be complete enough that another project team member can understand the issue without searching through several unrelated inboxes.

That becomes especially important when resolution takes days or weeks.

project closeout

Common damage-claim documentation mistakes

Common problems include:

Discarding the packaging immediately. Labels and packaging condition may be useful to later investigation.

Taking only close-up photographs. The project may lose context showing where the product was and how it arrived.

Writing conclusions instead of observations. Unsupported blame can distract from the actual evidence.

Failing to connect the issue to the PO and item. The vendor or manufacturer may not know which product the team is discussing.

Waiting too long to report concealed damage. Applicable terms may include notification requirements.

Repairing or installing the product before documenting it. The original condition may become impossible to show later.

Reporting an item missing before checking staging and storage. The problem may be inventory control rather than delivery shortage.

Losing the receiving paperwork. The project can lose the record tying the issue to the original delivery.

Assuming documentation guarantees claim approval. Documentation supports the process; it does not determine fault or guarantee recovery.

The goal is faster, clearer resolution

The best documentation process is not about creating a larger claims file.

It is about giving the project enough reliable information to make the next decision.

Protect the product.

Preserve the evidence.

Photograph the condition.

Document the facts.

Classify the issue.

Connect it to the order and specification.

Notify the right people.

Retain the records.

Then work the issue toward resolution.

The earlier the project creates that clear record, the easier it is to separate facts from assumptions and keep a small delivery problem from becoming a larger installation or schedule problem.

Protect the customer. Protect the project.