Window and Door Unit Receiving Damage Log
Log damage on incoming window and door units against the BOL, capture photos, tag affected units, and track claim follow-up in one receiving record.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Construction · Building Materials Distribution · Fenestration Manufacturing · Property Development · Commercial Glazing
Overview
The Window and Door Unit Receiving Damage Log is a receiving form for documenting damage found on incoming window and door units before they are installed, stored, or signed off as accepted. It captures the BOL reference, receiving date, carrier name, shipment condition, affected unit identifiers, damaged components, severity, photos, tagging status, and claim follow-up details.
Use this template when a shipment arrives with broken glazing, dented frames, damaged hardware, torn packaging, or any other visible issue that could affect acceptance or a carrier claim. It is especially useful at the dock, in a staging yard, or during project receiving where multiple units arrive together and each damaged unit needs to be tracked separately.
Do not use this form as a general inventory receipt for undamaged shipments, and do not rely on it after the units have already been installed or repaired. If your team needs to record hidden defects found later in the job, create a separate inspection or punch-list workflow. This template works best when the damage is observed immediately and the team can preserve evidence, tag the unit, and decide whether to hold, quarantine, or accept with notation.
What's inside this template
Submission Notice
This section anchors the record to the exact receiving event and tells the team what happens after the form is submitted.
-
What happens after I submit?
This log is saved for receiving records, claim review, and follow-up with the carrier or vendor. Attach photos and any BOL reference before submitting if available.
-
Bill of Lading (BOL) Reference
Enter the BOL number or shipment reference used to match the incoming units.
-
Receiving Date
Date the shipment was received.
Shipment and Unit Identification
These fields identify the carrier, shipment condition, and specific units so the damage can be traced back to the right delivery.
-
Carrier or Vendor Name
Name of the carrier or vendor associated with the shipment.
- Condition on Arrival
- Unit Type
-
Number of Units Affected
Count only the units with visible or documented damage.
-
Unit Identifier(s)
Add one row per damaged unit. Include the SKU, model, serial number, or other receiving identifier if available.
Damage Assessment
This section captures what was damaged, how severe it is, and what visible evidence was present at receipt.
- Damaged Components
- Damage Severity
-
Damage Description
Describe what was observed, including the exact location on the unit and whether the damage appears to be shipping-related.
-
Visible Packaging Damage?
Check if cartons, crates, pallets, or wrapping were also damaged.
Photos, Tagging, and Disposition
These fields preserve proof, prevent accidental use of damaged units, and document the immediate handling decision.
-
Damage Photos
Upload clear photos of the damaged unit, packaging, and any visible labels or tag numbers.
- Was the unit tagged as damaged?
-
Damage Tag Number
Enter the tag number applied to the damaged unit or shipment.
- Immediate Disposition
Claim Follow-Up and Review
This section tracks whether a claim was opened, who reported it, and what follow-up still needs to happen.
- Claim initiated?
-
Claim Number
Carrier or vendor claim number, if one has been issued.
-
Reported By
Optional internal contact name for follow-up. Avoid collecting unnecessary PII.
-
Additional Notes
Use this field for any other receiving details relevant to the claim or audit trail.
How to use this template
- Enter the BOL reference and receiving date as soon as the shipment is checked in so the damage record is tied to the correct delivery.
- Record the carrier name, shipment condition on arrival, unit type, and the number of affected units before the shipment is moved from the dock.
- List each damaged unit identifier and describe the affected components using specific field values for glazing, frame, hardware, or packaging.
- Attach clear damage photos, mark whether the unit was tagged, and enter the tag number if the unit is being held or quarantined.
- Select the disposition, initiate the claim if needed, and add the reporter name and notes so follow-up can continue without reopening the record.
Best practices
- Photograph the outer packaging, the shipping label, and the damaged component before the unit is moved or repacked.
- Use specific component names such as glazing, sash, frame, hinge, lockset, or weatherstripping instead of a vague damage label.
- Keep required fields limited to the information needed for receiving and claims, and use conditional logic to show claim fields only when damage is confirmed.
- Tag the unit immediately if it is being held so installers do not confuse it with accepted stock.
- Record the shipment condition on arrival in plain terms such as intact, crushed, punctured, wet, or shifted.
- Match each photo set to a single unit identifier when more than one unit is damaged in the same shipment.
- Add a short disposition note when the unit is rejected, held, repaired, or accepted with exception so the next team knows what to do.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
Use this template to record damage found when window and door units arrive at receiving. It ties the issue to the bill of lading, captures which components were affected, and preserves the evidence needed for a carrier or supplier claim. It is designed for one shipment or receiving event at a time.
Who should complete the log?
The receiving clerk, warehouse lead, site superintendent, or quality inspector usually completes it at the dock or staging area. The person filling it out should be able to compare the shipment to the BOL, identify the affected units, and attach photos before the units move into storage or installation.
How often should this form be used?
Use it every time a shipment of window or door units arrives with visible damage, missing parts, or packaging failure. It is also useful when damage is discovered during unloading or short-term staging, even if the unit looked acceptable on the truck. If nothing is damaged, a separate clean-receipt record is usually enough.
What should be documented before the units are moved?
Record the BOL reference, receiving date, carrier name, shipment condition on arrival, affected unit identifiers, and the specific damaged components. Add photos of the packaging and the unit itself before repacking, repair, or relocation. That sequence helps preserve the audit trail and reduces claim disputes.
Does this template help with carrier or supplier claims?
Yes. The form includes claim initiation, claim number, and follow-up fields so the receiving team can track the issue from discovery through resolution. Clear documentation of visible packaging damage, severity, and unit tagging makes it easier to support a claim and avoid missing deadlines.
How should we customize it for our operation?
Add fields for project number, warehouse location, purchase order, or installer handoff if those are part of your workflow. You can also use conditional logic to show claim fields only when damage is reported, and to separate glazing, frame, and hardware subfields when multiple components are affected. Keep required fields limited to what you actually use.
Can this be integrated with our receiving or ERP process?
Yes. The log can feed a receiving workflow, a quality hold process, or a claims tracker through integrations or exports. Common connections include inventory systems, document storage for photos, and task assignments for follow-up. Keep the data model simple so the form stays usable at the dock.
What is the biggest mistake people make with this kind of log?
The most common mistake is waiting until after unloading or installation to document the damage. Another frequent issue is using vague descriptions like "scratched" without naming the component, severity, and location. A third pitfall is forgetting to tag the unit, which makes later identification and claim handling harder.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
-
Integrated digital workplace task management tips to keep work moving, reduce stalls, and turn conversations into accountable action.
-
MangoApps is named a Leader in the IDC MarketScape for Content Management in Authenticated Digital Workspaces. See what sets our intranet platform apart.
-
Compare the top internal communications platforms of 2026—MangoApps, Staffbase, Simpplr, and more—by workforce fit, features, and frontline reach.
Ready to use this template?
Get started with MangoApps and use Window and Door Unit Receiving Damage Log with your team — pricing built for small business.
