Free proof of delivery form builder

Free AI Proof of Delivery Form Generator

Describe your workflow and Makeform creates a proof of delivery form drivers complete at the stop. Capture the shipment reference, recipient, result, photos, notes, time, and signature in one submission.

Chat input for the Makeform, best AI form builder. Press Enter to submit your request and generate a form. Use Shift+Enter to add a new line.
  • Unlimited free forms and responses
  • Editable before publishing
  • Signature and photo fields
  • Built for phones on delivery routes
Explore form features
31129+ makers build faster
Used by tools like ChatGPT, Perplexity & Claude

Send delivery records to Slack, Google Sheets, and Zapier.

Sample prompts for the builder

Choose a prompt, tailor it to your operation, or send it to the Makeform builder.

Prompt ready

Audience

Parcel couriers confirming residential and business stops

Format

Mobile form with recipient signature and photo

Prompt size

296 chars

Brief qualitySends to builder

Example form structure

Mobile form with recipient signature and photo

Prompt exampleEditable in builder

Driver, route, and tracking number

Short answerFirst ask
2

What was the delivery result?

Multiple choice
3

Recipient name and relationship

Short answer
4

Delivery photo

File upload
5

Recipient confirmation

Signature

Suggested routing tags

Suggested

Delivered

Exception

Redelivery needed

Use a required delivery-result choice before showing signature, exception, or redelivery questions with conditional logic.

Step 1

Identify

shipment, driver, route, and destination

Step 2

Check

quantity, condition, and delivery result

Step 3

Confirm

recipient name, signature, photo, and time

Step 4

Route

completed stops and exceptions to the right queue

A clearer last mile

Turn every doorstep handoff into a usable record.

A structured proof of delivery form connects confirmation to the shipment and makes exceptions visible to dispatch.

Match confirmation to the shipment

Require a tracking or order number, route, driver, address, and package count so staff can find the record.

Capture the handoff at the stop

Record recipient name, role, time, signature, and optional photo at the stop.

Separate success from exceptions

Conditional questions can open damage, shortage, refusal, access, or redelivery details only when a driver reports that outcome.

Designed around the stop

One starting point for four delivery workflows.

Choose a use case, then adjust identifiers, results, and confirmation requirements.

Parcel courier routes

Tracking numbers, recipient relationship, delivery result, signature, and doorstep photo for each stop.

Freight and warehouse receiving

Bill of lading, pallet count, visible condition, shortage notes, and receiver confirmation at the dock.

Equipment handoffs

Asset IDs, meter readings, accessories, condition checks, site-contact details, and signed receipt.

Contactless deliveries

Authorized placement, package count, photo, timestamp, and exception notes when no recipient signs in person.

Build the workflow

From route brief to driver-ready form in four steps.

Generate the questions, tune result paths, and publish a form drivers open at each stop.

Explore form features
01

Describe the route and handoff

State what drivers deliver, the shipment references, and the required confirmation.

02

Set conditional result paths

Show signatures for handoffs and reason, photo, note, and redelivery fields for exceptions.

03

Test the form on a phone

Test delivered and unsuccessful paths, required fields, signatures, and uploads.

04

Share and route submissions

Send deliveries or exceptions to your inbox, spreadsheet, Slack, or Zapier.

Choose the right record

Paper slip, generic checklist, or generated delivery form?

Choose between a simple route mark and a searchable record of shipment details and exceptions.

Approach
What it captures
Operational fit
ApproachPaper delivery slip
What it capturesHandwritten name, time, and signature filed later.
Operational fitSimple, but difficult to search or route.
ApproachGeneric mobile checklist
What it capturesStandard questions without shipment identifiers or result paths.
Operational fitBasic, but exceptions may hide in notes.
Approach
Generated proof of delivery form
What it capturesReferences, conditional outcomes, confirmation, photos, and signature.
Operational fitFor consistent, searchable stop records.

Field guide

What to include in a proof of delivery form.

These six groups connect confirmation to a shipment and capture details needed for exceptions.

Shipment identity

Start with references staff can search.

Reuse identifiers from dispatch or order systems so staff can match confirmation to a shipment.

  • Tracking, order, consignment, or bill of lading number.
  • Route, driver, and vehicle identifiers.
  • Destination and customer name.

Delivery result

Make the outcome unambiguous.

A required delivered, partial, refused, damaged, or unsuccessful choice can control the remaining fields.

  • Delivered, partial, refused, damaged, or no-access status.
  • Package, carton, pallet, or item quantity.
  • Date and time at the stop.

Recipient confirmation

Identify who accepted the delivery.

Ask for the recipient's name and role before signature. For unattended delivery, collect the authorized placement method.

  • Recipient name and role or relationship.
  • Signature for an in-person handoff.
  • Authorized unattended-delivery choice.

Condition evidence

Record visible condition and placement.

Use a condition choice and focused upload to document damage or placement without a long inspection.

  • Packaging or equipment condition at handoff.
  • Photo upload for damage, shortage, or placement.
  • Notes that describe only what was observed.

Exception details

Ask the next question only when needed.

Conditional logic keeps delivered stops short while collecting reasons and notes for exceptions.

  • Access, address, absence, refusal, shortage, or damage reason.
  • Affected items and photos.
  • Redelivery, depot return, or follow-up.

Internal routing

Turn the response into the next task.

Use delivery status to sort submissions and notify the team responsible for the next step.

  • Delivered, exception, and redelivery tags.
  • Dispatch or customer-service notification.
  • Fields matching existing references.

Related tools

Build the forms around delivery operations.

Connect delivery confirmation with vehicle checks, incident reporting, returns, address collection, and general delivery intake using live Makeform tools.

Explore all AI tools

AI Delivery Form Generator

Create a broader delivery form for order, address, schedule, and handoff details.

Open tool

AI Vehicle Inspection Form Generator

Give drivers a structured vehicle condition check before or after a route.

Open tool

AI Incident Report Form Generator

Capture a detailed record when an accident, injury, or property incident occurs.

Open tool

AI Product Return or Exchange Form Generator

Collect return reasons, product details, and the requested resolution after delivery.

Open tool

Shipping Address Form Generator

Standardize the destination details customers provide before fulfillment.

Open tool

Warranty Claim Form Generator

Gather product, issue, purchase, and photo details for post-delivery claims.

Open tool

FAQ

Proof of delivery form questions

Practical answers for courier, freight, rental, and local delivery teams.

What is a proof of delivery form?

It records what happened when a shipment reached its destination, tying a tracking or order reference to the driver, time, recipient, result, notes, photos, and signature.

What fields should I include?

Include shipment number, route, driver, destination, time, result, quantity, recipient details, and signature or unattended-placement confirmation. Add photos, shortage or refusal details, and redelivery routing when relevant.

Can recipients sign on a phone or tablet?

Yes. Add a signature field for the driver's phone or tablet. Pair it with recipient name and role fields, and review your customer requirements and local rules for signature use.

How should contactless delivery be recorded?

Use a contactless path with order reference, authorized placement, count, time, driver note, and photo. When nobody is present, record the chosen confirmation method instead of requiring a signature.

Can the form handle failed deliveries and damage?

Yes. A required result and conditional logic can reveal reason, affected quantity, photos, notes, contact attempt, and next action only for failed or damaged stops.

Is this proof of delivery form generator free?

Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect delivery submissions without an artificial response cap. The paid tier removes the Makeform badge; it is not required to keep collecting responses.

Where do completed delivery forms go?

Submissions arrive in your Makeform inbox and can route to Google Sheets, Slack, or other applications through Zapier. Consistent reference and result fields help teams sort stops and exceptions.

How do I make the form quick for drivers?

Use choices instead of long text fields, prefill known shipment details where possible, and show exception questions only when needed. Test both result paths on a driver's phone.

Replace loose delivery slips with structured confirmation.

Generate a proof of delivery form your drivers can complete at every stop.

Unlimited free forms and responsesRecipient signature and photosConditional exception routing
Browse templates