Claimant contacts
Know who filed and who can answer questions.
Collect claimant, company, email, phone, account, shipper, and consignee details as separate fields.
- Claimant and company.
- Shipper and consignee.
- Account reference.
Describe how you handle damage, shortage, and loss. Makeform builds a freight claim form for shipment references, itemized amounts, condition details, files, and reviewer contacts.
Route new claims to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it, or send it to the builder. Each example is a starting structure, not a claim decision.
Audience
Consignees reporting visible or concealed damage
Format
Conditional claim form with photo evidence
Prompt size
329 chars
Example form structure
Conditional claim form with photo evidence
Claimant and company contact
PRO, tracking, and bill of lading numbers
When and how was damage discovered?
Affected goods and claimed amounts
Photos, receipt, invoice, and inspection files
Suggested routing tags
Damaged freight
Missing freight
Needs documents
Ask for the carrier tracking reference and internal order reference so reviewers can reconcile the shipment across systems.
Step 1
Identify
claimant, carrier, route, and shipment references
Step 2
Describe
damage, shortage, loss, items, and amounts
Step 3
Document
receipt, invoice, photos, and correspondence
Step 4
Route
complete packet sent to the right reviewer
Why structured intake matters
One freight claim form keeps shipment numbers, photos, and the requested amount with a single shipment record.
Separate PRO, tracking, bill of lading, order, and account fields make the shipment searchable across systems.
Connect each affected commodity, quantity, unit value, and requested amount to its invoice.
Receipts, photos, invoices, inspection notes, and correspondence stay with the submission.
Claim scenarios
The first claim-type choice can reveal only the fields and evidence relevant to the reported exception.
Record delivery notations, package condition, affected pieces, photographs, and where the freight is being held.
Ask when packaging was opened, how damage was discovered, whether an inspection occurred, and what packaging remains available.
Compare expected and received cartons, pallets, units, weights, and seal details, then identify every missing line item.
Collect the promised delivery date, last tracking event, trace reference, and carrier communications for the missing shipment.
Build the intake workflow
Start with your carriers and review process, then publish the form.
Name your claim types, carriers, shipment references, and required documents.
Require shipment identifiers and reveal questions based on claim type.
Label uploads for receipts, bills of lading, invoices, photos, and correspondence.
Send submissions to your inbox or connected workflow with claim-type tags.
Form vs email vs document
A static document can explain requirements, but a structured online form makes each required answer and upload part of one submission.
Field guide
Use these six sections as an intake checklist, then align them with your review process.
Claimant contacts
Collect claimant, company, email, phone, account, shipper, and consignee details as separate fields.
Shipment identity
Separate carrier, tracking, bill of lading, order, date, origin, and destination fields support reconciliation.
Exception details
Branch visible damage, concealed damage, shortage, and non-delivery into the right detail fields.
Items and amounts
Connect every commodity or SKU to its affected quantity, unit value, and requested amount.
Supporting records
Dedicated upload labels distinguish shipment, value, condition, and communication records.
Disposition and follow-up
Record where affected goods are held, their condition, disposition notes, and the inspection contact.
Related tools
Pair claim intake with incident, insurance, return, delivery, upload, and warranty forms already available in Makeform.
Collect incident facts and supporting records for a broader business insurance claim workflow.
Open toolDocument the underlying event, people involved, timeline, and immediate actions.
Open toolCoordinate approval and routing when goods need to move back through a return process.
Open toolCapture delivery details and handoff information before an exception becomes a claim.
Open toolCreate a focused upload flow for invoices, receipts, photographs, and other records.
Open toolGather product, purchase, fault, and evidence details for warranty review.
Open toolFAQ
Practical answers for shippers, consignees, brokers, carriers, and logistics teams organizing claim intake.
It is structured intake for shipment damage, shortage, or non-delivery. It identifies the claimant, carrier, shipment, affected goods, requested amount, and supporting records for review.
Include contacts, carrier, tracking and bill of lading references, route, dates, claim type, event details, itemized quantities and values, total requested amount, disposition, and evidence.
Add labeled uploads for the delivery receipt, bill of lading, invoice, packing list, photos, inspection material, repair estimate, and carrier correspondence. Allow multiple photos when needed.
Yes. Conditional logic can show damage and photo fields, expected-versus-received shortage fields, or tracking and trace fields based on claim type.
Yes. Use item fields for commodity or SKU, description, affected quantity, unit value, requested amount, invoice reference, and overall total.
Yes. Makeform provides unlimited free forms and responses. You can generate, edit, publish, and collect submissions without a form or response cap; paid service only removes the Makeform badge.
Yes. Submissions can reach your Makeform inbox and connect with Google Sheets, Slack, and Zapier. Claim-type and status fields support your routing workflow.
No. It organizes intake but does not decide responsibility, eligibility, value, deadlines, or outcome. Tailor it to the receiving organization's instructions and review process.
Turn scattered claim emails into one intake flow.